[teamleaderleo]

Base red: cmux-next guards / nightly-guards / workflow-guard-tests / release-notary fails on feat-cmux-next (for example run 41504624858) and on four open PRs. Two steps fail.

• Validate nightly push throttle, tests/test_ci_warm_sources.py:
  • Cause: ci(nightly): get nightly.yml back under its size cap (base red) #32513 moved "Build and sign the release notes" into scripts/ci/nightly-steps/release-notes-build-sign.sh. The warm-sources detector treats any script named *build*.sh as a compile, so sign-release-notes became a compile job with no warm sources.
  • Fix: the step compiles nothing, so the script is renamed release-notes-sign.sh. The rule itself is unchanged.
• Validate universal nightly workflow, tests/test_nightly_universal_build.sh:
  • Cause: ci: every runner selection reads its size's declared pool (no single-size pins, 1/2) #32457 turned literal runner labels into declared pool reads (fromJSON(vars.RUNNER_POOLS).<pool>, whose first member is the old literal). Three of this script's exact-expression checks still expected the literals: the decide gate, refresh-compilation-cache and build-nightly-ghostty-cli-helper. The script exits at its first FAIL, so the later two only surfaced after the first was fixed.
  • Fix: the three checks now expect the pool reads ci: every runner selection reads its size's declared pool (no single-size pins, 1/2) #32457 wrote. Each still matches the job's whole runs-on expression, not a prefix. I checked the updated helper expectation against the expanded workflow.

Locally, every command in both steps passes: test_nightly_universal_build.sh, test_nightly_trusted_routing, test_nightly_build_state, test_ensure_setup_node, and the nine tests in the push throttle step (warm sources included). test_workflow_file_size, test_nightly_step_coverage and test_nightly_next_identity pass too.

Base-red-job: cmux-next guards / nightly-guards / workflow-guard-tests / release-notary

Agent session: agent session

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Clears the release-notary nightly-guard reds by updating two tests that broke after recent workflow changes.

• Renames release-notes-build-sign.sh to release-notes-sign.sh; the warm-sources detector treats any script named *build*.sh as a compile, but this step compiles nothing.
• test_nightly_universal_build.sh now expects the fromJSON(vars.RUNNER_POOLS) pool reads for the decide gate, refresh-compilation-cache, and build-nightly-ghostty-cli-helper, matching the expressions ci: every runner selection reads its size's declared pool (no single-size pins, 1/2) #32457 wrote.

^{Written for commit 90676bf. Summary will update on new commits.}

[cursor]

Bugbot needs on-demand usage enabled

Bugbot uses usage-based billing for this team and requires on-demand usage to be enabled.

A team admin can enable on-demand usage in the Cursor dashboard.

[github-actions]

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

Review 90676bf: 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=pr32529 -f ref=lane/nightly-release-notary-red -f platform=macos -f backend_mode=local

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4150891005901 (2fdcbbae7e)
• cmux NEXT nightly 1.0.0-nightly.4151067571301 (546cb0bf70)
• cmux NEXT nightly 1.0.0-nightly.4151196080201 (8d6a5624a6)
• cmux NEXT nightly 1.0.0-nightly.4151284660301 (22fd89a839)
• cmux NEXT nightly 1.0.0-nightly.4151418814301 (b899f6b4f0)

[teamleaderleo]

Review (subagent claude-sonnet-5-5): SHIP at 90676bf

No reference to the old script name remains, and the script compiles nothing. The refresh and helper runs-on expectations match nightly.yml's whole expressions exactly, and the decide check stays a regex of the same shape it had before. test_nightly_universal_build.sh, test_ci_warm_sources and test_nightly_next_identity pass.

Follow-ups: none