[teamleaderleo]

Base red on feat-cmux-next: cmux-next guards / tooling-tests, step "The Python test registry, and the tests no pull request runs", fails on every feat-cmux-next pull request (seen on #24136, run 39789311718, job 119860776563):

- tests/test_ci_tip_test_compile.py: linux-guard lane is not run by any workflow
warning: tests/test_ci_tip_test_compile.py: no job a pull request into feat-cmux-next runs executes it, so a change that breaks it lands green. Run it from a step of a job that runs on those pull requests (routed by the paths of the code it tests) ...

Origin: 77c3c5a ("ci(cmux-next): every feat-cmux-next push compiles the Swift test targets it can break…") registered tests/test_ci_tip_test_compile.py on the linux-guard lane in tests/test-execution.toml, but no workflow runs it; cmux-next-tip-test-compile.yml runs scripts/ci/tip-test-compile.sh only on feat-cmux-next pushes.

Change

One step in the tooling-tests job of .github/workflows/cmux-next-guards.yml (Linux, runs on every feat-cmux-next pull request and push, no path filter) runs python3 tests/test_ci_tip_test_compile.py, beside the other feat-cmux-next tooling tests and with the same if: ${{ !cancelled() }}. The test is stdlib Python driving the script against a fake cmux-ci client and a fake GitHub API: 9 tests, about 3 s. Nothing in cmux-next-tip-test-compile.yml or tip-test-compile.sh changes; this only makes the test run on pull requests, so a change that breaks the script no longer lands green.

Changelog

none

Observed / Not run

• python3 scripts/ci/validate_test_execution_registry.py --pr-lanes feat-cmux-next --base-sha cba27b07 (with PyYAML): at base cba27b07 it fails with tests/test_ci_tip_test_compile.py: linux-guard lane is not run by any workflow (exit 1); at this head it prints Python test execution registry valid: 455 tests (exit 0).
• python3 -I tests/test_ci_tip_test_compile.py: Ran 9 tests ... OK (run on macOS; the script uses only bash, sed, grep and python3, and the test strips GITHUB_*/RUNNER_*).
• actionlint .github/workflows/cmux-next-guards.yml: clean. scripts/cmux-next/prepush-gate.py: no new violations.
• Not run: the job itself on Linux before this PR's CI.

Risk: low (CI wiring, one test step).

Agent session: cosmic-gray

🤖 Generated with Claude Code

---

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

---

Summary by cubic

Fixes the red tooling-tests base check on feat-cmux-next pull requests so a change that breaks tip-test-compile.sh no longer lands green.

• tooling-tests in cmux-next-guards.yml now also runs tests/test_ci_tip_test_compile.py, which previously only ran on pushes via cmux-next-tip-test-compile.yml.
• tests/test_pr_lane_coverage.py now pins that test to the tooling-tests lane so the coverage check stays consistent.
• The test uses a fake cmux-ci client and GitHub API, runs in about 3 seconds, and leaves push-time behavior unchanged.

^{Written for commit 29212b6. Summary will update on new commits.}

[github-actions]

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

Review 29212b6: 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=pr24397 -f ref=deputy-2/tip-test-compile-pr-lane -f platform=macos -f backend_mode=local

[teamleaderleo]

Bead cx-6ek6t created for this PR by the cmux coordinator.

[teamleaderleo]

Review (independent subagent, correctness first): SHIP at 29212b6

• With --pr-lanes feat-cmux-next --base-sha HEAD^1, scripts/ci/validate_test_execution_registry.py exits 0. That clears both the linux-guard error (tests/test_ci_tip_test_compile.py: linux-guard lane is not run by any workflow) and the pull-request lane check. tests/pr-lane-exemptions.json doesn't list the test, so there's no stale-exemption error.
• tests/test_ci_tip_test_compile.py uses only stdlib Python with a fake cmux-ci client and a fake GitHub API: no network and nothing macOS-only. It passes 9/9 in about 3 s. The new step is placed like its sibling tooling-tests steps and has the same if: ${{ !cancelled() }}. cmux-next-tip-test-compile.yml and tip-test-compile.sh are untouched.
• Delta in 29212b6: the test is now in in_tooling_tests in tests/test_pr_lane_coverage.py, so dropping the step later turns that test red. tests/test_pr_lane_coverage.py passes.
• The CI on 6a6b4ce has tooling-tests green. The remaining reds fail on the same steps in feat-cmux-next push runs (23cc5a5, 3b01b70, d511296): release-notary's notices pair check, Guard status, and cmux-next checks' "Fail on any red check".

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3991367032401 (b9c3d5aabc)
• cmux NEXT nightly 1.0.0-nightly.3991575404801 (a62351daaa)