[teamleaderleo]

Two jobs that hold the production Cloud journey's secrets now stay on routes no variable can move.

• tests/test_ci_runner_pool_reconcile.py: BACKEND_SECRET_JOBS gains journey-preview, journey-staging and journey-production. cloud: a headless NEXT Cloud journey on previews, staging and production deploys #35103 added these jobs to backend.yml. They read CMUX_DOGFOOD_STACK_* and CLAUDE_CODE_OAUTH_TOKEN, and the last two run in the cmux-next-cloud-journey environment, but the list was never updated. On feat-cmux-next today, test_backend_secret_jobs_use_only_the_ephemeral_linux_mirror fails its credentialed-set check, and the three routes go unchecked. With them listed, the test passes: their routes already have ci: keep backend credentials on bounded ephemeral Linux routes #30761's bounded pool-read shape, so backend.yml is unchanged.
• .github/workflows/cloud-journey-prod.yml: runs-on becomes ${{ github.repository_owner != 'manaflow-ai' && 'ubuntu-24.04' || vars.CI_CLOUD_OVERFLOW_SAVED && fromJSON(vars.RUNNER_POOLS).linux_16 || fromJSON(vars.RUNNER_POOLS).linux_8 }}. The job holds the production account and a Claude login. Its old route took vars.LINUX_RUNNER and ended in fromJSON(vars.RUNNER_POOLS).linux_2, which this branch's guards flag: a Blacksmith label was selectable outside manaflow-ai, and there was no overflow failover. It now ends in the same pools as backend.yml's credentialed jobs and no longer reads vars.LINUX_RUNNER. On main, ci: register the production Cloud journey (stub model hourly, real login every six hours) #35303 names a literal label instead, but feat-cmux-next's guards refuse one (ci: every runner selection reads its size's declared pool (no single-size pins, 1/2) #32457, ci: hard-coded Blacksmith Linux runs-on fail over to another Blacksmith size #26439). Schedules register only from main, so this copy does not run.

#30761 and #32457 stay as they are: the other credentialed backend jobs keep their pool reads.

Observed / Not run

• python3 tests/test_ci_runner_pool_reconcile.py SecretRouteBoundary: fails on base (journey-preview, journey-staging and journey-production missing), passes at this head.
• At this head, these pass for cloud-journey-prod.yml: tests/test_ci_runner_set.py, test_ci_blacksmith_linux_failover.py, test_ci_no_single_size_pins.py and test_ci_fork_runner_routing.py. On base, the last three flag it, as does test_ci_upload_artifact_retention.py (retention-days 14, unchanged here). The remaining fork-routing, failover-size and guard-wiring failures are in other files and also fail on base.
• Not run: the full fast-guard suite (CI runs it).

Agent session: agent session

🤖 Generated with Claude Code

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review 33e2ad7: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr35717 -f ref=lane/journey-prod-fixed-runner -f platform=macos -f backend_mode=local

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4190094575701 (036f8aa538)
• cmux NEXT nightly 1.0.0-nightly.4191131679101 (e01bbae5c9)

The feat-cmux-next push run https://github.com/manaflow-ai/cmux/actions/runs/41888017760 at dba5f44 failed: cmux-next checks (god files, concurrency, crash safety, l10n).
Those jobs last passed at 2955a17. This pull request is one of 5 merged since: #35756, #35717, #35759, #35521, #35641.
If the failure is in your change, fix forward on feat-cmux-next. Pull requests run only the tiers their paths reach (docs/ci/cmux-next-tiers.md); label a batch PR full-ci to run them all before merging.

[teamleaderleo]

Review (codex, router-review): SHIP at 0947100

Reviewer: codex gpt-6-astra high, fast tier.

SHIP at 0947100

Visual verdict: no images; Leo tries the build

Focused route, runner-set, YAML, and policy checks pass.

Follow-ups: none

[cmux-bot]

cmux-bot approves 0947100: an independent review passed this exact head (router-review receipt by teamleaderleo). A push needs a new review; a later BLOCK at this head dismisses this approval.

[teamleaderleo]

Review (codex, router-review): SHIP at 33e2ad7

Reviewer: codex gpt-6.1-sol xhigh, fast tier.

SHIP at 33e2ad7

Visual verdict: unchanged by this diff

Targeted routing and failover tests pass.

Follow-ups: none

[blacksmith-sh]

Found 1 test failure on Blacksmith runners:

Failure

Test	View Logs
test_every_listed_hook_is_one_glaeda_released_with_the_check (main.SigningHooksInSt epWithGlaedaTests.test_every_listed_hook_is_one_glaeda_released_with_the_check)/ test_every_listed_hook_is_one_glaeda_released_with_the_check (main.SigningHooksInSt epWithGlaedaTests.test_every_listed_hook_is_one_glaeda_released_with_the_check)	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[cmux-bot]

cmux-bot approves 33e2ad7: an independent review passed this exact head (router-review receipt by teamleaderleo). A push needs a new review; a later BLOCK at this head dismisses this approval.

[teamleaderleo]

Review (gpt-6.1-sol): SHIP at 33e2ad7

Review (codex, router-review): SHIP at 33e2ad7

Reviewer: codex gpt-6.1-sol xhigh, fast tier (router-review job 29fd0a25c3384124ff5775d1a41bfd5f; comment #35717 (comment)).

Visual verdict: unchanged by this diff

Targeted routing and failover tests pass.

Follow-ups: none