[azooz2003-bit]

Summary

feat-cmux-next does not compile. Two changes that landed an hour apart don't build together:

• cmux NEXT: This Mac's join consent: Screen sharing and Control switches, and a one-time sheet (Labs) #27223 (15:42) added MachineConsentChanges.events(armed:), which calls FolderChanges(folders:).events() from a synchronous function.
• cmux-next: FolderChanges.events() returns once its watches are registered #26517 (16:43) made FolderChanges.events() async, so it returns only after its watches are registered.

Fleet build 549a2bfa50c634b6131799d8 at 6d8838a09200 fails in swift_compile:

Packages/macOS/CmuxNext/Sources/CmuxNextApp/Remote/JoinConsent+App.swift:222:29: error: 'async' call in a function that does not support concurrency

This change makes MachineConsentChanges.events(armed:) async and awaits the folder watch. That ordering is what its doc comment already promised: folder watch registered, then file watches, then armed, then one yield. Its three callers (the model's watch task and two JoinConsentTests) now await it. The package runs with NonisolatedNonsendingByDefault, so the non-Sendable armed closure stays on the caller's actor.

Changelog

none

Review

A subagent did a correctness review of 8dec64d15a7b and found nothing blocking. It checked:

• every FolderChanges.events() and MachineConsentChanges.events call site in Packages/;
• isolation under the package settings;
• ordering;
• cancellation: a cancelled FolderChanges wait returns a finished stream, the detached loop exits, and the file watches are cancelled and the continuation finished. Nothing leaks.

It noted one older issue that this PR does not cause: watchFiles resumes its file sources without waiting for registration, the race #26517 fixed for folders. That's left for a follow-up.

Observed / Not run

• Observed: base 6d8838a09200 fails to compile on the fleet (job 549a2bfa50c634b6131799d8, error above).
• Pending: scripts/ci/package-test-lane.sh suite Packages/macOS/CmuxNext JoinConsentTests at the head (cmux-ci step 22cfe1759689444cd520dd0e). The result will be posted here before ready-to-land.
• Not run: no runtime change beyond the ordering above, so no capture (No capture: build fix, no UI change).

🤖 Generated with Claude Code

---

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

---

Summary by cubic

Fixes the feat-cmux-next build break by making MachineConsentChanges.events(armed:) async to match the now-async FolderChanges.events().

• The folder watch is now awaited before file watches fire, matching the ordering the doc comment already promised.
• The three callers (model watch task and two JoinConsentTests) now await the call.

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

[azooz2003-bit]

Head 8dec64d15a7b: CmuxNext builds and scripts/ci/package-test-lane.sh suite Packages/macOS/CmuxNext JoinConsentTests passes (cmux-ci step 22cfe1759689444cd520dd0e on cmux19-perf: JoinConsentTests passed 18s, All 1 suites passed). The base 6d8838a09200 fails to compile (fleet job 549a2bfa50c634b6131799d8, JoinConsent+App.swift:222). The correctness review in the description found nothing blocking; its one note (file-watch registration in watchFiles) is older than this PR and left for a follow-up.

[github-actions]

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

Review 8dec64d: 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=pr27758 -f ref=fix-next-machine-consent-async -f platform=macos -f backend_mode=local

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4099263986101 (1816f75ed1)

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4099184203401 (0b45ce8ec3)
• cmux NEXT nightly 1.0.0-nightly.4099502414501 (b02c564547)
• cmux NEXT nightly 1.0.0-nightly.4099558415201 (c0331557f5)