[teamleaderleo]

Base red, priority zero (coord-deputy). The cmux-next base autofix has not landed a Mac export since 02:14Z. schemas/settings/settings-schema.json on feat-cmux-next still says chief-pet where the source says chief (#22848), so settings/categories.test.ts fails on every webview run.

Why the Mac job never started. From 11:15Z to 11:36Z every run's action exports (Mac) job had a start time and no runner, and was cancelled 3 to 4 minutes later. Runs 39590571817 through 39592618210 are examples. The job's concurrency group (cancel-in-progress: false) never cancels a running job, but it replaces a pending one. With the Mac std runners saturated, each job waited minutes for a runner, and the next push, a few minutes later, replaced it before it started. #23315's fixes for a running Mac job never got the chance to apply.

Fix

• action-exports has no concurrency group, so a queued job keeps its place.
• A new step in action export areas, scripts/cmux-next/base-autofix-mac-busy.sh, skips this run's Mac job while another run's Mac job is queued or running. That job regenerates the settings exports on the newest tip when it starts (base autofix: regenerate the settings exports on the newest tip, so they land #23249).
• A run that skipped its Mac job fails at the end ("Mac exports deferred to the run already making them"). The next run diffs from the last successful run, so its changes stay in the next run's range.
• A failed API read starts the Mac job: two Mac jobs beat none. Two runs checking at the same moment can also both start one.

Also fixes my own base red from #23315: tests/test_cmux_next_pr_autofix_settings.py SettingsOnlyArtifactLeavesTheActionFollowers. Three base subtests fail with exit 127 in cmux-next checks at 92c12bc (seen on #23330). #23315 moved the base Repair step into scripts/cmux-next/base-autofix-repair.sh, which reads EXPORTS_DIR from the step env. The test ran the step's script without that file or env. That job was already red on base for other reasons, which hid this on #23315.

Test

Red commits first:

• 51e1cea fixes the test itself. It was red on base: python3 tests/test_cmux_next_pr_autofix_settings.py, FAILED (failures=3), base-autofix-repair.sh: No such file or directory.
• 926833d adds the queue tests. python3 tests/test_cmux_next_base_autofix_finishes.py against base's workflow gives FAILED (failures=8):
  • the Mac job has no group;
  • a run skips its Mac job while one is in flight;
  • a deferred run fails;
  • base-autofix-mac-busy.sh with a gh stand-in: another run's queued, waiting or in-progress Mac job counts; its own, a completed one or none doesn't; an unreadable API starts the job.

Green at the head: both files OK (27 and 6 tests), and actionlint on the workflow is clean.

Observed / Not run

• Observed: the tests above, red then green, on huge-blue. The job timings above come from the Actions API.
• Not run: a real feat-cmux-next run of the new workflow. After this merges I'll do one glaeda-gh wait on the first run whose Mac job finishes. Then I'll check that settings-schema.json says chief on base and that settings/categories passes, and report both.
• tests/test_ci_no_shallow_dev_fetch.py fails in this sparse checkout only (a file not checked out).

Changelog

none

Agent session: huge-blue

🤖 Generated with Claude Code

---

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

---

Summary by cubic

Fixes the base autofix pipeline so a queued Mac export job keeps its place instead of being replaced by the next push, and a deferred run passes its changes to the next run instead of losing them.

• Removes the action-exports job's concurrency group; a queued job now waits for a runner indefinitely.
• Adds base-autofix-mac-busy.sh, which skips this run's Mac job when another run's is queued or running.
• A run that deferred its Mac exports ends green with a "Mac exports deferred" job naming the run that carries them; base-autofix-since.sh makes the next run diff from the newest successful run that made its own exports, so the deferred run's changes stay in range.
• Fixes SettingsOnlyArtifactLeavesTheActionFollowers failing on base by giving the test the step env after base autofix: remake held repairs on the moving tip instead of starving #23315 moved Repair into base-autofix-repair.sh.
• Registers test_crash_class_fast_gate.py in test-execution.toml, which cmux-next fast gates: the crash-class rules are the fifth gate, red only for findings the PR adds #23331 left out.

^{Written for commit a7ab126. Summary will update on new commits.}

[teamleaderleo]

Owned by land-and-ci on huge-blue · session

[github-actions]

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

Review a7ab126: 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=pr23352 -f ref=claude/autofix-mac-exports-keep-queue -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
/tmp/tmpi7fg91lm/summary-missing.json (live):/summary-missing.json (live):	View Logs
/tmp/tmpm_d71v3s/summary-fail.json (live):/summary-fail.json (live):	View Logs

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

[teamleaderleo]

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

[teamleaderleo]

Review (subagent, correctness first): SHIP at a7ab126

Covers the whole PR at this head. An earlier full review passed 34936c1. The delta review covers 34936c1..a7ab126: d47a3d2 (red tests), 364891d (a deferred run ends green with a "Mac exports deferred" job; base-autofix-since.sh passes over such runs in both change lookups) and a7ab126 (registers tests/test_crash_class_fast_gate.py, lane linux-guard).

• No change can be skipped for good. While R1's Mac job is in flight, later runs diff from the success before R1, so they see Mac areas and defer. When R1 succeeds, since moves to h1. When R1 fails, since stays and the next run makes its own exports.
• Deferred runs push no Mac exports (--unverified-exports, no --generated).
• since.sh fallbacks only widen the set of repairs. Re-runs work as intended with the jobs endpoint's filter=latest.
• Registry: right lane (cmux-next-guards.yml:323 runs the file), no duplicate, and the validator on the merge tree reports nothing for it.
• The test files pass and actionlint is clean. The new tests fail on 34936c1.

Nits: at the head alone (before #23331), the registry validator flags the file as missing, but CI checks the merge ref. A cancelled 2-minute deferred job makes its run red, which is rare and loses no changes.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3960833477001 (4482e41d31)
• cmux NEXT nightly 1.0.0-nightly.3960894798201 (0b1a93e9c0)
• cmux NEXT nightly 1.0.0-nightly.3961101575901 (101cc33db2)