[teamleaderleo]

Composer draft hydration preserves an authoritative daemon clear when the native mirror refuses the empty write. Per-session ordered state retains the latest daemon observation, so a later unavailable daemon read cannot resurrect stale native text; a newer local edit still wins. The repair adds the delayed refusal regression and keeps unreadable daemon metadata retryable without inventing a durable tombstone.

This is the text/hydration child stacked on foundation 87d8459a652168f33482c2012f9203e20156df2a, targeting lane/nx-draft-persistence. Child-relative diff: 17 files, 779 insertions + 21 deletions (800 changed lines). Aggregate stack from 9445568053d73aaed41afefe1e7afa0dd9246aee: 26 files, 1,573 insertions + 54 deletions (1,627 changed lines), including the prerequisite foundation work.

Validation: focused composer draft actions 11 pass, 0 fail (21 expects), including clear -> delayed mirror refusal -> daemon unavailable -> stale mirror and newer-local-edit cases. webviews/bun --bun run check passed (format, lint, typecheck, protocol, and ratchets). Exact web-lint against the foundation and exact prepush-gate both pass; prepush reports no new violations, with only baseline app-size warnings. The eight-file focused aggregate suite is 88 pass/2 fail; both reds reproduce unchanged at baseline 5caece6d05f (NewTab sent route missing Send button and sandbox receipt-order assertion), so they are unrelated baseline failures.

Native compile/tests remain UNEXECUTED/HOLD under #26809/HQ4779. Fresh independent exact-head review is running at c63183b877adc9b656bba5a57e82bdbff9163b2e; this draft remains pending review and native verification. No CI, ready transition, or merge is claimed.

Agent session: agent session

[blacksmith-sh]

Found 110 test failures on Blacksmith runners:

Failures

Test	View Logs
src/pages/settings/layout.test.ts/layout.test	View Logs
src/pages/settings/layout.test.ts/layout.test	View Logs
test/agent-pane-background-tasks.test.ts/agent-pane-background-tasks.test	View Logs
test/agent-pane-background-tasks.test.ts/agent-pane-background-tasks.test	View Logs
test/agent-pane-chat-unavailable.test.ts/agent-pane-chat-unavailable.test	View Logs
test/agent-pane-chat-unavailable.test.ts/agent-pane-chat-unavailable.test	View Logs
test/agent-pane-dock-gutters.test.ts/agent-pane-dock-gutters.test	View Logs
test/agent-pane-dock-gutters.test.ts/agent-pane-dock-gutters.test	View Logs
test/agent-pane-hairline-focus.test.ts/agent-pane-hairline-focus.test	View Logs
test/agent-pane-hairline-focus.test.ts/agent-pane-hairline-focus.test	View Logs

...and 100 more test failures. View all on Blacksmith

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

[cmux-bot]

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

Probably yours: changes-stage-hunk-keys.test.ts, composer-mention.test.ts, agent-pane-background-tasks.test.ts fails here but not on main's latest full suite. Seen on other PRs too (likely flaky): agent-pane-dock-gutters.test.ts, agent-pane-dock-gutters.test.ts, agent-pane-queue-steer.test.ts and 18 more.

CI failed on c63183b877 (run 40712133958 attempt 1): 3 code, 1 unknown.

Job	Verdict	Why
web / react-apps-base-check (1)	code	a web test failed
web / react-apps-base-check (2)	code	a web test failed
web / react-apps-base-check (4)	code	a web test failed
web / react-apps-check	unknown	no known signature; failed step: Check webview test shards

Failures:

• seen on other PRs agent-pane-dock-gutters.test.ts chromium > the gutter beside every part of the stack scrolls the transcript, and the part keeps the ...: failed (job)
• seen on other PRs agent-pane-dock-gutters.test.ts webkit > the gutter beside every part of the stack scrolls the transcript, and the part keeps the po...: failed (job)
• seen on other PRs agent-pane-queue-steer.test.ts queued and steering prompts > the queue takes its own place in the stack: nothing is cut off or draw...: failed (job)
• new in this PR changes-stage-hunk-keys.test.ts n then s stages the hunk n stopped at: failed (job)
• seen on other PRs composer-footer-harness.test.ts with no harness installed the row still says Add harness: failed (job)
• new in this PR composer-mention.test.ts (unnamed): failed (job)
• seen on other PRs composer-permission-pill.test.ts claude: permission control keeps the shared capsule geometry: failed (job)
• seen on other PRs composer-quiet-chips.test.ts chromium: keyboard focus pills the focused button only, ringless, with its outline: failed (job)
• new in this PR agent-pane-background-tasks.test.ts the summary card lists the chat's background tasks: running ones first, the finished folded: failed (job)
• seen on other PRs agent-pane-chat-unavailable.test.ts loading never shows the unavailable text: a slow attach, then a machine still connecting: failed (job)
• ... 14 more in the job logs

Matched log lines

web / react-apps-base-check (1): (fail) chromium > the gutter beside every part of the stack scrolls the transcript, and the part keeps the pointer [9207.90ms]
web / react-apps-base-check (2): (fail) the summary card lists the chat's background tasks: running ones first, the finished folded [977.07ms]
web / react-apps-base-check (4): (fail) only page.css imports the page's sheets [24.13ms]

Not re-run automatically: web / react-apps-base-check (1), web / react-apps-base-check (2), web / react-apps-base-check (4), web / react-apps-check are not machine failures.

Written by scripts/ci/classify_failures.py (ci-failure-attribution.yml); signatures are its SIGNATURES table. A machine verdict is the runner's fault, not this PR's; yours means the failing file is one this PR changes, also red on main that main's latest full suite fails the same way, seen on other PRs that it failed on another pull request's run lately.

CI fast guards failed on c63183b877 (https://github.com/manaflow-ai/cmux/actions/runs/40712133958). It does not block the merge; a red guard merged into main breaks it for every open PR.
The log named no failed step; see the run.

Agents: python3 scripts/ci/guard_attribution.py fix applies the mechanical fixes locally.