[lawrencecchen]

tooling-tests is red on every feat-cmux-next PR (seen on #31013). The registry check fails with:

tests/test_ci_overflow_pick_reads_pool.py: linux-guard lane is not run by any workflow   (#30878)

#30878 registered this test as linux-guard but added no ci-guards.yml step that runs it. CLAUDE.md does not allow new CI tests (Lawrence 2026-10-23). So the test becomes lane = "manual", with the command to run it, as #30624 and #30872 did for earlier tests.

Side effect: the nightly-next car guards (car_guards.py, focused_tests.py) run only linux-guard tests. Before this PR they could pick this test when a car changed a workflow it names. As a manual test it is not run there. The only way to keep it in that lane is a new CI step, which CLAUDE.md does not allow. #30624 and #30872 had the same effect.

Red and green

• python3 scripts/ci/validate_test_execution_registry.py --pr-lanes feat-cmux-next --base-sha HEAD: exit 1 at the feat tip, exit 0 at this head (601 tests).
• test_ci_test_execution_registry.py and test_pr_lane_coverage.py: OK.
• The test itself passes (about 2 s).

Observed / Not run

• Observed: the commands above.
• Not run: nothing else is needed; this PR changes only the registry.

Changelog

none

[github-actions]

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

Review 4d368eb: 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=pr31065 -f ref=fix/base-red-registry-1101d -f platform=macos -f backend_mode=local

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4132418488301 (5f712a27cc)
• cmux NEXT nightly 1.0.0-nightly.4132492786501 (3c0c02a5ae)
• cmux NEXT nightly 1.0.0-nightly.4132569907101 (641e45405d)
• cmux NEXT nightly 1.0.0-nightly.4132675672201 (1d9d0c83e6)
• cmux NEXT nightly 1.0.0-nightly.4132727143001 (fe90490c5d)

[lawrencecchen]

Review (subagent, correctness first): SHIP at 4d368eb

What the reviewer confirmed:

• At origin/feat-cmux-next 69104a3, the validator fails on exactly this entry.
• No workflow runs the file. The ci-guards tests/*.py step only compiles it, and the discovery runners point at other folders.
• At this head, the validator exits 0 (601 tests). The registry tests pass (34 and 17).
• The reason is accurate, and the test passes (4 tests, 2.4 s).

Note: the car guards no longer pick this test, because they run only linux-guard tests. This is now stated in the description.