[teamleaderleo]

Base red

tooling-tests (cmux-next guards) fails on feat-cmux-next: https://github.com/manaflow-ai/cmux/actions/runs/41089026998

Python test execution registry validation failed:
  - tests/test_cmux_tui_owned_mini_caches.py: linux-guard lane is not run by any workflow

Cause

#27840 added tests/test_cmux_tui_owned_mini_caches.py, registered it as linux-guard, and ran it from ci-guards.yml. Its second commit ("ci: keep cache regression out of guard workflow") then removed that step on purpose, because the repo rule is no new CI tests (Lawrence 2026-10-23, CLAUDE.md). The registry entry was left unchanged and now names a lane that no workflow runs for this file.

Fix

Register the test as lane = "manual" with a reason, the way test_cmux_next_arch_layers.py and the guardrails tests are registered. No workflow change and no new CI step. The test still passes and is run by hand after changes to cmux-tui.yml's macOS job.

Evidence

Both runs come from one fast-checks run of this change (https://github.com/manaflow-ai/cmux/actions/runs/41090711559). The "before" run puts the entry back to the base's linux-guard.

Before (base registry):

$ python3 scripts/ci/validate_test_execution_registry.py
Python test execution registry validation failed:
  - tests/test_cmux_tui_owned_mini_caches.py: linux-guard lane is not run by any workflow
exit=1

After (this head):

$ python3 scripts/ci/validate_test_execution_registry.py
exit=0
$ python3 tests/test_cmux_tui_owned_mini_caches.py
Ran 2 tests in 0.056s
OK
$ python3 tests/test_ci_test_execution_registry.py
Ran 34 tests in 1.637s
OK
$ python3 tests/test_ci_guard_workflow_structure.py
exit=0

Observed / Not run

• Observed: the commands above, on a Linux fast-checks runner.
• Not run: the full tooling-tests job. This PR's CI runs it.

Changelog

none

risk: low (test registry only)

Agent session: agent session

🤖 Generated with Claude Code

---

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

---

Summary by cubic

Registers the owned-mini caches regression test as manual so tooling-tests stops failing on feat-cmux-next.

• The test was registered as linux-guard, but no workflow runs that lane for it, so registry validation fails.
• The repo rule is no new CI tests, so the test is now manual with a reason, matching how other no-new-CI-tests entries are registered. No workflow changes or new CI steps.

^{Written for commit 242601b. 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 242601b: 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=pr28426 -f ref=lane/fix-owned-mini-caches-registry -f platform=macos -f backend_mode=local

[teamleaderleo]

Owned by an agent session · session

[blacksmith-sh]

Found 2 test failures on Blacksmith runners:

Failures

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
test_the_repository_highlights_validate (main.DigestTests.test_the_repository_highl ights_validate)/ test_the_repository_highlights_validate (main.DigestTests.test_the_repository_highl ights_validate)	View Logs

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

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4109296117601 (72882288da)
• cmux NEXT nightly 1.0.0-nightly.4109410702301 (aead767cca)