fix(desktop,ui): restage a selected message's quotes and attachments on edit

[ggbdpq]

Summary

Edit & resend refused a selected message that itself carried quotes or attachments: the replacement submit only carried the human-facing text, silently dropping the context the original answer was grounded in (#5109, reproduction cases A and B — case C, the TUI rewind side, landed in #5265).

The desktop edit now stages the selected message's quotes into the quote plate and its attachments into the attachment plate as retained refs, recording both on the revision draft:

• the plates make the carried context visible and explicitly removable, satisfying the issue's "removing is an explicit edit" expectation;
• after the revision commit, the staged attachment refs are swapped for the copied message's target-owned refs read back from the branch child transcript — the Host's copier already rewrote them, so the replacement submit only claims files the new Session owns (no protocol change);
• a no-op send (text and staged context both unchanged vs the draft) stays refused, cancel restores the pre-edit plates, and mid-edit staging of new context is refused so user additions cannot silently mix with the restored set.

The chat-turn edit gate drops quotes and attachments from its disabled list; directory references keep the gate, since they have no client-side restage path, and their two dead copy keys are removed together with the branches that rendered them.

Part of #5109 — with this, both clients restore the selected turn's quotes and attachments; directory references remain fail-closed on both.

Verification

Check	Result
New ui tests (attachment- and quote-carrying messages keep the edit action)	red on the old gate (2/2 fail via stash rebuild), 2/2 green after
Desktop revision-actions tests (source attachments/quotes stage and are recorded on the draft)	3/3 green; the replaced upstream test asserted the exact negation (rejection) and was green pre-change
@maka/ui full suite	446/450 — 3 failures (session-todo-panel, prompt-rail-observer-identity, transcript-history-notice) fail identically on pristine upstream/main via stash rebuild; composer-plus-menu fails only under full-suite concurrency and passes 11/11 in isolation
npm --workspace @maka/desktop run build:main (typecheck incl. renderer sources)	clean
check-locale-hygiene	passed
biome check on all 7 changed files	clean
check:asf-headers	passed locally

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: GLM-5.3-Flash (ZCode) implemented the desktop/ui changes and tests under human direction and review.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — a selected message carrying quotes or attachments is now editable; the replacement submit restages that context (attachments rewritten to target-owned refs after the revision commit).
• No

[ggbdpq]

Marking draft while the renderer debt ratchet question is settled — see the gate comment below.

The renderer architecture strict-base check freezes app-shell-revision-actions.ts at 2155 non-trivia tokens; the feature needs ~160 more than the slimmest extraction I could land (88dc60e, 2318). Two honest paths forward:

1. I extract the beginEditUserMessage orchestration into @maka/ui/revision-staged-context as well (fits the budget, but moves shell orchestration into the package), or
2. a one-time sanctioned budget bump for app-shell-revision-actions.ts in renderer-architecture.json.

Happy to do either — flagging before burning another CI round.

[github-actions]

No description provided.

[ggbdpq]

The ratchet conflict is resolved without touching the frozen budgets: the whole revision lifecycle (beginEdit / prepare / cancel / rollback + copy-attempt bookkeeping) moved into @maka/ui/revision-staged-context, and app-shell-revision-actions.ts is now a thin assembler injecting the bridge, the locale catalog, and the attempt tracker.

Measured against the frozen base budgets: app-shell-revision-actions.ts 2305 -> 506 tokens / 6 specifiers (base 2155/8); app-shell.tsx 13482 -> 13344 tokens / 104 specifiers (base 13386/104). The duplicate pre-send gate in the shell goes away with the move — prepareRevisionSend owns the unchanged and mixed-context refusals — and one stale guard referencing removed draft fields is gone with it.

Heads 0a5af05 / 0a5af05 have not started a CI run for a few hours (the pull_request workflow never fired on the pushes or the reopen — likely the external-contributor workflow approval); pull_request_target checks ran. Once a run is approved: local verification passed — desktop revision-actions 3/3, ui chat-turn 26/26, biome clean, ASF clean, and the refreshed ledger confirms both files under budget.