Distillation

Date: Sep 17, 2026

• 🔴 (09:12) User requires continuation to never be committed before unresolved hosted tools are reconciled.
• 🔴 (09:12) User requires a Step end to never be committed after the provider stream fails.
• 🔴 (09:12) User requires assistant start state to never be recorded when Step start publication defects.
• 🔴 (09:12) User requires execution to never be woken when retrying an already promoted prompt.
• 🔴 (09:12) User requires durable wake to never be armed for a conflicting execution retry.
• 🟡 (09:12) packages/core/test/session-runner.test.ts test "never commits continuation before unresolved hosted tools are reconciled" begins with prompt text "Mixed tools" and injects a database abort with SELECT RAISE(ABORT, 'crash before hosted tool reconciliation'); the unresolved hosted tool uses ID call-hosted-pending.
• 🟡 (09:12) packages/core/test/session-runner.test.ts includes defect-boundary tests "never commits a Step end after the provider stream fails" and "never records assistant start state when Step start publication defects"; the latter streams LLMEvent.stepStart({ index: 0 }) followed by LLMEvent.textStart({ id: "failed-step-start" }).
• 🟡 (09:12) packages/core/test/session-runner.test.ts uses SQL trigger fail_step_failure_publication to simulate failure while publishing a Step failure, then removes it with DROP TRIGGER fail_step_failure_publication.
• 🟡 (09:12) Additional cancellation/interruption coverage shown in packages/core/test/session-runner.test.ts includes "settles cancellation when interrupted tool publication defects" and a failed-Step cancellation scenario using prompt text "Cancel failed Step"; assertions verify SessionExecutionTable is empty after settlement.
• 🟡 (09:12) packages/core/test/session-prompt.test.ts contains 16 matched scenarios in order: 1. "exposes the execution registry" (line 140), 2. "delegates execution continuation through SessionExecution" (line 147), 3. "durably admits one user message before transcript promotion" (line 181), 4. "resumes through a recorded message without appending another prompt" (line 254), 5. "wakes execution when an exact prompt retry recovers a committed message" (line 310), 6. "never wakes execution when retrying an already promoted prompt" (line 330), 7. "durably records execution intent before advisory wake" (line 374), 8. "replays historical prompt admission without execution intent as admit-only" (line 408), 9. "turns an admit-only exact retry into durable execution intent" (line 440), 10. "never arms durable wake for a conflicting execution retry" (line 514), 11. "reprojects pending inbox input without scheduling execution" (line 642), 12. "returns an exact retry of a legacy projected prompt" (line 668), 13. "returns an exact retry of a legacy projected queued prompt" (line 689), 14. "starts execution by default after recording the prompt" (line 761), 15. "starts execution when resume is explicitly true" (line 775), 16. "only records the prompt when resume is false" (line 793).
• 🟡 (09:13) Database migration tests use in-memory SQLite via SqliteClient.layer({ filename: ":memory:", disableWAL: true }) and import eventSourcedSessionInputMigration from @opencode-ai/core/database/migration/20260604172448_event_sourced_session_input.
• 🟡 (09:13) Visible DatabaseMigration coverage includes: legacy workspace migration using row ('wrk_legacy', 'remote', 'main', '/repo', '{}', 'proj_legacy'); "imports unnamed legacy Drizzle journal entries by their actual migration timestamps"; "rejects unknown legacy Drizzle journal timestamps instead of guessing completed migrations"; concurrent migration use through two Database.layerFromPath(filename) layers; and migration verification via bun ${fileURLToPath(new URL("../script/migration.ts", import.meta.url))} --check.
• 🟡 (09:13) Migration schema assertions include table/index names session_context_epoch and session_input_session_promoted_seq_idx; migration application uses DatabaseMigration.applyOnly(db, [sessionRecoveryMigration]).
• 🟡 (09:13) Search of packages/core/src/event.ts found 23 commit-related references. PublishOptions defines commit?: (seq: number) => Effect.Effect<void> as a local operational projection committed atomically with a new durable event and not replayed or serialized. commitDurableEvent(...) invokes the projector and then commit(seq); publishEvent(...) rejects a commit hook for a non-durable definition with message "Local commit hooks require a durable event".