[Raing5Days]

Problem

Submitting /compact put /compact back into the composer at the moment the compaction finished.

submitCompactFromInput clears the composer and then awaits the desktop compact_session command, which does not settle when the request is admitted: ConversationCoordinator::compact_session_manually awaits the terminal state of the maintenance turn. The failure path restored the submitted text, so the refill landed minutes later - including when the compaction had already been applied and only its terminal bookkeeping failed. /usage, /init and /reload use the same failure-restore pattern but return immediately, which is why only /compact shows the symptom.

Fix

• Clear the composer through the submission contract - value, pending large pastes, machine queue, history cursor - before sending the command. A machine-queue entry left behind lets the queuedInput sync effect write the text back into the now-empty composer.
• Restore /compact only when the host never admitted it. An early rejection (session busy, context not loaded, agent unavailable) creates no maintenance turn, so the text is still a retryable draft. Once a manual_compaction turn appeared after the submission, the outcome already lives in the transcript and the composer stays cleared.
• Failure feedback is unchanged: a notification plus the turn's own terminal state in the transcript.

Verification

• vitest run for the composer-ownership contract, the draft-recovery rules and the image-intake contract: 3 files / 22 tests pass.
• tsc --noEmit on src/web-ui passes; ESLint reports no problems for the touched files.
• Not reproduced against a running desktop build - a manual compaction needs a configured model and a session with history. The root cause is derived from the command's await semantics plus the /usage control case reported in the issue.

Notes

The desktop entry point stays blocking (its promise settles when the compaction ends). Making the Web UI observe the outcome through the turn events instead would be a separate change: it needs a non-blocking command path and a Product Operation Registry row.