Closes Tarquinen#490 ## The reported symptom Running `/dcp compress` showed > Manual mode: compress blocked. Do not retry until `<compress triggered manually>` > appears in user context. even though the trigger came from the user, and the compress then ran anyway. On the current code that ordering is already gone: the command handler sets `manualMode = "compress-pending"`, `refreshManualMode` early-returns on that value in both `prepareSession` and `checkSession`, and the red line can only fire when the flag is *not* `compress-pending`. So the primary symptom does not reproduce here any more, and `tests/manual-trigger-lifecycle.test.ts` pins that down rather than leaving it to chance. ## The bug that was still there `compress-pending` was only ever cleared by `finalizeSession`, i.e. by a compress call actually happening. If the model answered the trigger without calling compress - which models do routinely, and which the report itself observed - the session stayed pinned in `compress-pending` for the rest of its life: - `refreshManualMode` kept early-returning, so the persisted manual-mode setting was never read again - `injectCompressNudges` returns early on any truthy `manualMode`, so the automatic context-limit, turn and iteration nudges were switched off permanently, and a later `/dcp compress` was the only way out ## Change - `PendingManualTrigger` records `restoreTo`: the manual mode that was in effect before the command flipped it to `compress-pending`. - `applyPendingManualTrigger` moves that into `state.consumedManualTrigger` once the prompt is written, together with the id of the user message it was written into. - When a later transform arrives with no pending trigger and the last user message is no longer that one, the flag is released and `restoreTo` is put back. So the trigger authorises exactly the one compress call that follows it. - `finalizeSession` clears `consumedManualTrigger` on the success path, so a compress that *did* run is unaffected. - `resetSessionState` clears it too. The red-line message text is unchanged; it is referenced from the compress prompt and the fix is that it no longer appears. ## Verification `tests/manual-trigger-lifecycle.test.ts`, seven cases. The three lifecycle ones fail on the current implementation - `manualMode` stays `"compress-pending"` and `consumedManualTrigger` does not exist. - the trigger is written into the command turn - an unused trigger is released on the next turn - **manual mode ON is restored, not dropped**, when the trigger goes unused - the trigger survives the turn that armed it, so the following compress works - the success path retires the bookkeeping - no trigger armed leaves state untouched Full suite 131 passing, `tsc --noEmit` clean, `prettier --check` clean.

Commits

Commits on Oct 1, 2026

fix(manual): release a manual trigger that produced no compress