#30872 base red: tooling-tests registry, three tests from #30648 and #30657 become manual

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

tests/test_ci_fast_checks_runner.py: linux-guard lane is not run by any workflow      (#30648)
tests/test_nightly_next_control_rescue.py: linux-guard lane is not run by any workflow (#30657)
tests/test_nightly_next_control_runner.py: linux-guard lane is not run by any workflow (#30657)

Those PRs registered each 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 each test becomes lane = "manual", with the command to run it, the same fix #30624 made for test_ci_blacksmith_linux_sizes.py.

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 (599 tests).
• test_ci_test_execution_registry.py and test_pr_lane_coverage.py: OK.

Observed / Not run

• Observed: the commands above, plus each of the 3 tests (all pass, about 1 s each).
• Not run: nothing else is needed; this PR changes only the registry.

Changelog

none

---

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

---

Summary by cubic

Fixes tooling-tests being red on every feat-cmux-next PR. Three tests from #30648 and #30657 were registered as linux-guard but no ci-guards.yml step runs them; since no new CI tests are allowed (Lawrence 2026-10-23), each becomes manual with its run command, as #30624 did for test_ci_blacksmith_linux_sizes.py.

With this change, python3 scripts/ci/validate_test_execution_registry.py --pr-lanes feat-cmux-next --base-sha HEAD exits 0 at this head (599 tests).