Make the Int promotion toggleable via RUN_INT_DEPLOY (#69)

While the runner host is CPU/memory constrained, the Int stack can be shut
down to free resources — but the promote-int job redeploys it on every push.
Gate that job on a `RUN_INT_DEPLOY` Actions variable: set it to `false` to
keep Int down, unset/anything else keeps the normal promotion. Int is only a
preview stage; the CI quality gates (checks, auth-e2e, fidelity) are
unaffected.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1

.gitea/workflows/cd.yml

@@ -104,6 +104,14 @@ jobs:
     name: Promote to Int
     needs: smoke-test
     runs-on: ubuntu-latest
+    # Toggle: set the repo/org Actions variable `RUN_INT_DEPLOY` to `false`
+    # (Gitea → Settings → Actions → Variables) to stop redeploying the Int stack
+    # while the runner host is resource-constrained; the Int stack can then stay
+    # `docker compose down`. Unset/anything-else keeps the normal promotion, so
+    # this defaults to the previous behaviour and re-enabling is a variable flip
+    # (no code change). Int is a preview stage; the CI quality gates are
+    # unaffected either way.
+    if: ${{ vars.RUN_INT_DEPLOY != 'false' }}
     steps:
       - name: Log in to the Gitea registry
         run: printf '%s' "${{ secrets.REGISTRY_TOKEN }}" | tr -d '[:space:]' | docker login gitea.101010.cloud -u fable-5 --password-stdin