Distillation

Date: Sep 17, 2026

• 🔴 (09:18) User established the invariant/test requirement "never wakes execution when retrying an already promoted prompt" in packages/core/test/session-v2.test.ts.
• 🔴 (09:18) User established the invariant/test requirement "never arms durable wake for a conflicting execution retry" in packages/core/test/session-v2.test.ts.
• 🟡 (09:18) packages/client/src/generated/types.ts defines session.next.prompt.admitted with delivery: "steer" | "queue" and optional requestExecution?: boolean, and defines session.next.prompt.execution_requested with timestamp, sessionID, and messageID.
• 🟡 (09:18) packages/client/src/generated/types.ts defines session.next.step.recovered with timestamp, sessionID, executionID, optional assistantMessageID, and phase: "ready" | "unknown" | "continue".
• 🟡 (09:19) packages/core/test/session-projector.test.ts test "recovers assistant-less continuation at its current assistant boundary" creates execution "assistant-less-current" at phase: "continue" and assistant_seq: 0; after SessionRecovery.recover(), the execution row is removed, the recovery row has assistant_message_id: null and phase: "continue", and its continuation input is { prompt: { text: "continue" }, delivery: "queue" }.
• 🟡 (09:19) packages/core/test/session-projector.test.ts test "redrives a durable recovery wake after admission" publishes SessionEvent.Step.Recovered for execution "lost-wake" at phase "unknown"; the resulting recovery row has wake_pending: true and recovery_error: null. Two calls to SessionRecovery.recover() produce exactly 2 wakes while retaining the recovery row with continuation_message_id: continuation("lost-wake"), assistant_message_id: null, phase: "unknown", and wake_pending: true.
• 🟡 (09:19) packages/core/test/session-projector.test.ts includes test "quarantines a malformed recovery row without blocking a valid wake".
• 🟡 (09:19) SessionExecutionTable mutations/references were found in packages/core/src/session/execution/claim.ts at lines 53, 70, 91, and 103; packages/core/src/session/execution/local.ts at lines 53, 110, and 188; packages/core/src/session/recovery.ts at lines 74, 86, 106, 129, and 295; and packages/core/src/session/runner/llm.ts at lines 205 and 418.
• 🟡 (09:20) Verification reported patch SHA-256 2ae4eea72024cafe8b69c0461063ee25cbf54608856cd258866b7f3b86620b36, base commit ab9408c81cc9916177641ae8e9f08624fc27b5b9, and exactly 34 patch paths matching exactly 34 worktree paths (path_sets_equal=True).
• 🟡 (09:20) /home/byk/Code/opencode/packages/opencode/dist/server/opencode-server had SHA-256 10a3698a5e3b009f811a1b27eefab9e1083b560e24efee5f537f003d7edd7384, size 157879104, mtime 2026-09-17 09:18:02.709852813 +0000, and inode 19532879.
• 🟡 (09:20) Assistant issued a MUST-FIX and DO-NOT-MERGE: the frozen SEA /home/byk/Code/opencode/packages/opencode/dist/server/opencode-server changed during review from required initial SHA-256 aa98d64abb3bf6ac0ef88a940f9c41c6eb14ffeab3c3a7846921ba01ef46643d to final SHA-256 10a3698a5e3b009f811a1b27eefab9e1083b560e24efee5f537f003d7edd7384, so the reviewed artifact was no longer immutable and the candidate could not be approved.
• 🟡 (09:20) Assistant found no independent source-level MUST-FIX or CONCERN before the artifact changed. Base remained ab9408c81cc9916177641ae8e9f08624fc27b5b9; patch remained 2ae4eea72024cafe8b69c0461063ee25cbf54608856cd258866b7f3b86620b36; exactly 34 patch/worktree paths matched; reverse-applicability and whitespace checks passed.
• 🟡 (09:20) Assistant reported packages/core/schema.json:4-7 directly names base snapshot f14a9b18-8207-487e-a3d3-227e629ba9ad.
• 🟡 (09:20) Assistant reported recovery behavior in packages/core/src/session/recovery.ts:179-218: completed failed Steps never enter recovery continuation, and unresolved tools are durably failed one at a time before claim removal.
• 🟡 (09:20) Assistant reported continue-phase completed Steps still enter recovery in packages/core/src/session/recovery.ts:179-220.
• 🟡 (09:20) Assistant reported lease mutations use exact Session, execution, owner, and unexpired predicates in packages/core/src/session/execution/claim.ts:27-33.
• 🟡 (09:20) Assistant reported interruption waits for runner finalizers before durable settlement; concurrent callers share one barrier; and wakes received during cleanup survive, implemented across packages/core/src/session/execution/local.ts:168-210 and packages/core/src/session/run-coordinator.ts:100-130.
• 🟡 (09:20) Assistant reported auth and dependency direction remained intact.
• 🟡 (09:20) Review performed no tests, builds, services, or VCS mutations. The unavailable repo-setup skill was the only setup limitation; disclosed final check-call, process-local routing, and bounded clock-skew residuals remained accepted.