[teamleaderleo]

Problem

cmux-next daemon tests never runs for a feat-cmux-next push. Its if: skips same_tree_origin == 'push', and a push's own run is superseded before its tree publishes. So scripts/ci/test_reds.py / base_red_excuse.py have had no base log for that job since 04:34Z, and no pull request's daemon red can be compared with the base (#27692 is stuck on 17 red daemon tests, #27868 likewise). Base logs existed only from hand dispatches (41001517417, 41024114885).

Even a dispatch did not reliably help. Its tree wait marker (origin dispatch) was dropped as superseded whenever the tip moved before the tree published, which in a landing burst is every time: 41023525520 and 41022857098 ended with daemon tests skipped.

Change

This follows how tip_swift_suite gives swift-test a base verdict. The dispatcher side is #28261 on main.

• cmux-next.yml takes a tip_daemon_suite input.
  • Path routing routes only the daemon tier, and only on refs/heads/feat-cmux-next.
  • The run is named cmux-next tip daemon suite · <tested sha>, using same_tree_sha in same-tree mode.
  • daemon-test's own if: is unchanged: a dispatch, and its same-tree run with origin dispatch, already run it.
• Its tree wait marker carries tip_suite: daemon.
  • cmux_next_tree_notify.py treats such a marker as current after the tip moves, like the DEV daily's: it tests its recorded sha.
  • It passes tip_daemon_suite on, so the same-tree run keeps the name.
  • Only a daemon-only dispatch marker on feat-cmux-next heads may carry it. Anything else is rejected as malformed.
• base_red_excuse.py looks up tip suite runs by name. If its window of the 100 newest base runs (up to 40 job reads) holds no verdict for cmux-next swift test or cmux-next daemon tests, it lists the base's workflow_dispatch runs and reads the newest tip suite runs of that job by name, at most 6 job lists. Base pushes crowd that window out within a couple of hours. test_reds.classify then judges per test as before. A crash or a cut-short run is still never a base red.

No workflow permission or secret changes.

Performance

Runner minutes added per base push (estimate). The daemon-test job took 9 to 13 minutes in 41024114885 and 41001517417. The base gets about 30 pushes an hour, and the dispatcher (#28261) starts at most 2 daemon suite runs an hour: when the daemon tier changed, or every 20 landings.

metric	before	after	delta	harness or run link
Mac runner-minutes per base push (daemon-test)	0	≤ 0.9 (≤ 2 runs/h × ~13 min ÷ ~30 pushes/h)	+≤ 0.9	runs 41024114885, 41001517417
REST reads per daemon/swift excuse lookup with no verdict in the window	1 + 40	1 + 40 + 1 + ≤ 6	+≤ 7 (only on that miss)	tests/test_base_red_excuse.py

Tests

These pass on the branch:

• tests/test_base_red_excuse.py:
  • a daemon red is excused by the tip daemon suite run past 45 base pushes with no verdict
  • a tip suite run green on the base still blocks
  • a DEV daily's jobs are never read
  • a job with no tip suite makes no extra lookup
• tests/test_cmux_next_tree_notify.py:
  • a tip daemon suite marker dispatches its exact sha with tip_daemon_suite after the tip moved
  • malformed tip_suite markers are ignored
• tests/test_cmux_next_tip_swift_suite.py:
  • the input, the run name, a daemon-only route and the marker field
• tests/test_test_reds.py and tests/test_cmux_next_generated_fold.py also pass.

Stop condition: after this and #28261 land, the next base daemon-test result appears without a hand dispatch, and #27692's daemon reds are compared by name against it.

Agent session: agent session

🤖 Generated with Claude Code

[teamleaderleo]

Owned by an agent session · session

[github-actions]

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

Review 026fafd: 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=pr28283 -f ref=lane/same-tree-daemon-base-log -f platform=macos -f backend_mode=local

web and size checks: green

[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.}

[teamleaderleo]

Review (codex gpt-6-astra high, next-review): BLOCK at b0b1b0e

• [P1] scripts/ci/base_red_excuse.py:228 — The fallback can excuse a regression using an obsolete failure. It filters out ordinary dispatches before checking their verdicts. After 40 newer runs exhaust the initial lookup, a passing ordinary base dispatch is ignored while an older failing tip suite is accepted. I reproduced this with the supplied fake GitHub harness: judge() excused the PR despite the newer base daemon result being green. Preserve the newest-verdict rule across dispatch types, or refuse when newer verdicts remain unchecked.

[teamleaderleo]

Head is now c0c10bc0e8ac788138a35a39d25b02d52f5b03a3.

tooling-tests (job 124018292337): the registry error was tests/test_cmux_tui_owned_mini_caches.py: linux-guard lane is not run by any workflow. The base fails the same way: #27840 registered the file as linux-guard, but no ci-guards.yml step ever ran it. This head adds that step in the release-notary group, and validate_test_execution_registry.py now passes. This PR adds no new test files; its tests are edits to files that already have registry entries. The same commit also stands alone for other PRs as branch lane/owned-mini-caches-guard (43312b47).

daemon tests (job 124022634651): one failing test, theFirstLaunchBringsEverythingOnce(_:) in the multiWindow case (ClassicUpgradeSimulationTests.swift:45 and :52). Two of the three classic workspaces come over in swapped order. This PR changes no Swift and no daemon code, only CI workflow and scripts, so the failure is not caused by this diff. I could not compare it by name, though: the only base daemon logs since 04:34Z did not run the suites at all.

• 41024114885 at d62d4d75: compile error in CloudAppLinkOwnerAnswerTests.swift:22 (main-actor isolation).
• 41033244125 at 7050ae30: no published cmux-tui tree.

That gap, no base daemon-test log that ran the suites, is exactly what this PR and #28261 fix. Once a tip daemon suite run completes, base_red_excuse.py can classify this test by name.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4111325355101 (df9b52b7d0)
• cmux NEXT nightly 1.0.0-nightly.4111671381901 (a0fc9a9a63)
• cmux NEXT nightly 1.0.0-nightly.4111685258501 (df3ee368f2)
• cmux NEXT nightly 1.0.0-nightly.4111911568201 (214b514c8c)