[teamleaderleo]

Fixes the base red on feat-cmux-next: cmux-next/compile (SwiftPM Release, -Onone) has failed on every landing from 00d6d54 (#26517) on, 17 in a row as of 0da5bc3. While it is red, no NEXT nightly can build a newer commit, so the feed falls further behind the tip on every landing (Leo: "it is unacceptable to have nightlies >30min out of date").

Cause

#26517 made FolderChanges.events() async (it returns once its watches are registered). #27223 landed alongside it, and its MachineConsentChanges.events(armed:) in JoinConsent+App.swift calls FolderChanges(...).events() without await. Each PR compiled on its own base. Together they don't compile.

Change

• MachineConsentChanges.events(armed:) is now async, and it awaits the folder's registration before it arms the files and runs armed. That keeps the documented order (folder, then files, then armed, then the first element) and gets cmux-next: FolderChanges.events() returns once its watches are registered #26517's stronger readiness guarantee.
• Its one app caller (JoinConsent+App.swift:138) and the two JoinConsentTests call sites add await. The package enables NonisolatedNonsendingByDefault, so the non-escaping armed closure stays on the caller's actor.

5 lines changed. No behaviour change beyond the readiness await.

No capture: a compile fix with no visible change. The consent watch arms the same files in the same order, and no view changes.

Risk

Low. A compile fix on a type-checked call path. The fleet Release compile on this head is the check.

Agent session: agent session

🤖 Generated with Claude Code

[teamleaderleo]

Owned by an agent session · session

[blacksmith-sh]

Found 1 test failure on Blacksmith runners:

Failure

Test	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]

Superseded by #27758 (same fix), merged as cec0a36.

[teamleaderleo]

Independent review (Codex gpt-6-astra, high, fast) at 4f7825d: no P1/P2 findings. Swift 6 isolation, the async events() and its callers (every caller in the head tree awaits), task inheritance, arming order and the updated tests are consistent.

[teamleaderleo]

Closing: #27758 (merged as cec0a36) makes the same fix, adding the missing await on MachineConsentChanges.events() and FolderChanges.events() in JoinConsent+App.swift plus both test call sites, and #27722 adds nothing beyond it. Base cmux-next/compile is fixed by #27758.

[teamleaderleo]

Review (codex-review-box/gpt-6-astra high, lane-place): SHIP at 4f7825d

SHIP

1. No correctness findings. All FolderChanges.events() and MachineConsentChanges.events() callers are awaited; the folder → files → armed → initial yield order remains intact (JoinConsent+App.swift).

SHIP at 4f7825d

[teamleaderleo]

Review (codex gpt-6-astra high, review-job): SHIP at 4f7825d

No blocking findings.