[teamleaderleo]

Summary

fleet/compile-check compiles only the app executable, which links no test target, and merge_compile_guard.py accepts its pass in place of a queued Release compile. Two PRs passed it today and then broke feat-cmux-next's test build: #23360 (a throwing call inside #expect without try, CmuxNextActionsTests) and #23163 (a FakeClient missing the requirement #21258 added, CmuxNextAppTests). On #23360 every Mac job that builds tests was still queued when it merged.

This adds an advisory check as a bridge, and leaves the merge gate alone:

• fleet/compile-check is unchanged: still the Linux app compile, same timing, same github-actions[bot] status. fleet-compile-check.yml and merge_compile_guard.py are byte-identical to feat-cmux-next.
• New fleet-test-compile.yml runs on pull requests into feat-cmux-next that touch Packages/ or vendor/. A Linux job plans with scripts/ci/compile_test_plan.py over the merge commit's diff: the CmuxNext test targets that depend on a changed target in the existing SwiftPM target graph (cmux_next_route.route, the swift test tier's routing), every one for a manifest or graph change, plus the macOS package lane's packages whose sources or path dependencies changed. An empty plan passes on that Linux runner in seconds and queues no Mac. A plan runs package-test-lane.sh compile-tests BASE as a light fleet step, which builds each planned CmuxNext test target with swift build --target (no link, no run) and a lane package with --build-tests. The check, fleet/test-compile (advisory), goes red only when a planned test target fails to compile. The lane prints its failure marker as soon as a target fails, so a later package's setup failure can't hide it. Anything else (queue or run timeout, setup, the client) is a warning, and the job's 55-minute timeout outlasts the client's 20-minute queue plus 25-minute run timeouts, so a slow fleet never reads red. If SwiftPM refuses --target, the package falls back to one --build-tests in place of its remaining targets.
• Nothing waits for it: the guard reads only the Release compile and fleet/compile-check; gh-merge-green is main-only and this workflow runs only on feat PRs.

It's a bridge until the Linux pool compiles test targets. The pool's darwin SDK can't find Testing today (job 1382fbdb06c0fc7c023643d3 at df5e2eb: no such module 'Testing'); cmuxterm-hq #2750 adds Xcode's platform search paths and reaches the pool with the next image bake. The per-target pool argument is manaflow-ai/cmuxterm-hq#2759.

Testing

Red/green on a fleet Mac with the build the new phase runs (the reviewed package-test-lane.sh suite phase, which runs swift build --build-tests over CmuxNext before one suite):

head	result	fleet step
#23360's head 4f867f5e57c2d943ac1f4e9743d42cc89730e683	red, exit 1: PaletteMenuVocabularyTests.swift:74:106 and :79:101, "call can throw, but it is not marked with 'try'"	ed72e6e6f72d215befe9bb9b (aws-m4pro-8)
feat-cmux-next df5e2ebb1c03db048843083530e86feeda2c1b2a	green: Build complete! (89.11s), then CmuxNextActionsTests (136 tests) passed	54d316aebe3d339a9a2126eb (aws-m4pro-7)

cmux-ci run --class light --script scripts/ci/package-test-lane.sh --ref <sha> --arg=suite --arg=Packages/macOS/CmuxNext --arg=CmuxNextActionsTests; cmux-ci log <step> on the tailnet prints each log. Each ran about 1.5 to 2 minutes after 11 minutes in the light-class queue, which is why this is advisory and off the merge gate.

tests/test_ci_compile_test_plan.py (linux-guard) was committed red first (ec4b51c) and passes: #23360's diff selects CmuxNextActionsTests and its reverse dependents and nothing that doesn't reach CmuxNextActions; a new CmuxNextAppTests file selects only that target; the manifest selects every target; a CMUXAuthCore change selects it, its lane dependents and the CmuxNext targets that use it; iOS-only, docs, CI and app-host changes plan nothing; the phase refuses a bad merge base. The same file runs the compile-tests phase with a fake swift (committed red first in a9201f8): a target that doesn't compile exits 1 with the marker; an earlier target failure stays red when a later package's setup fails; a setup failure alone has no marker; a refused --target falls back to --build-tests once per package; an empty plan builds nothing. It also runs the workflow step with a fake client to check how exits map to red, warning or green, and that the job timeout outlasts the client's. cmux-next.yml now runs it with the merge guard tests. tests/test_merge_compile_guard.py adds that a red or pending advisory check never holds a merge or stands in for the Release compile, and that the advisory workflow is not the fleet check the guard trusts. Passing on Linux (huge-blue): those two, test_ci_cmux_ci_client_guarded, test_ci_workflow_guards_are_wired, test_supplychain_security, test_runner_label_policy, test_ci_pr_runner_pool, test_ci_fork_runner_routing, test_ci_merge_queue_required_checks, test_ci_workflow_path_filter_parity, test_ci_workflow_run_sources, the reusable-workflow and cache guards, package-test-lane-suite-args.test.sh; actionlint; prepush-gate.py.

Observed / Not run

• Ran: the two fleet steps above, the pool probe (no such module 'Testing'), the tests listed above, compile_test_plan.py on cmux-next palette: titles end in "…" exactly when the action asks first, outside Phone #23360's diff (12 CmuxNext test targets including CmuxNextActionsTests and CmuxNextAppTests).
• Not run: the compile-tests phase and fleet-test-compile.yml on the fleet. A changed allowlisted script runs on the fleet only after it lands (hq step_reviewed.go), so the first real run is the first feat PR touching Packages/ after merge. Unverified there: swift build --target <test target>; if SwiftPM refuses it, the phase falls back to --build-tests for that package.
• Known: next_autoland holds a PR on any red check, including this advisory one, until teamleaderleo/leo-workspace#746 (skip checks named ... (advisory)) lands. Expected red here: this PR's own swift-package-tests fleet step is refused until package-test-lane.sh lands, as for every allowlisted-script change.

Changelog

none

Agent session: cosmic-gray

🤖 Generated with Claude Code

[teamleaderleo]

Owned by ci-speed on cosmic-gray · session

[github-actions]

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

Review 3a2851b: 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=pr23423 -f ref=ci-speed/compile-check-tests -f platform=macos -f backend_mode=local

web and size checks: green

[blacksmith-sh]

Found 7 test failures on Blacksmith runners:

Failures

Test	View Logs
/tmp/tmp1karsm2b/summary-fail.json (live):/summary-fail.json (live):	View Logs
/tmp/tmpgs7o6ys4/summary-missing.json (live):/summary-missing.json (live):	View Logs
[new_workspaces] debug.new_workspace timed 0 of 50 new workspace rows/ [new_workspaces] debug.new_workspace timed 0 of 50 new workspace rows	View Logs
[new_workspaces] the window draws no frames/[new_workspaces] the window draws no frames	View Logs
[tabs] debug.tab_switch timed 0 of 40 switches/ [tabs] debug.tab_switch timed 0 of 40 switches	View Logs
[tabs] the window draws no frames/[tabs] the window draws no frames	View Logs
scripts the package test job runs are not global inputs: ['scripts/ci/ compile_test_plan.py']	View Logs

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

[teamleaderleo]

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

[teamleaderleo]

cmux-next guards / defaults-snapshot is red on 17 of 17 fresh feat-cmux-next PR heads in the last 2:00:00, so it is most likely a base red, not this PR's. The base-reds lane has it; a base merge picks up the fix once it lands.

[teamleaderleo]

Review (independent subagent, correctness first): SHIP at b96188a

[teamleaderleo]

Review (independent subagent, correctness first): SHIP at 3a2851b. The SHIP at b96188a still stands: the only change since then adds scripts/ci/compile_test_plan.py to GLOBAL_INPUTS in select_package_tests.py, which fixes this PR's own 'Validate package test selection' red. The defaults-snapshot check-menu-actions failure (FileExplorerSectionView.swift) is red on base 68a3517 too.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3962134573301 (c6459deaec)
• cmux NEXT nightly 1.0.0-nightly.3962509665801 (ed547f0e27)