Distillation

Date: Sep 16, 2026

• 🟡 (21:58) User supplied another patch excerpt showing recovery-row selection ordered by asc(SessionRecoveryTable.wake_attempts).
• 🟡 (21:58) The patch excerpt showed recovery eligibility filtering with isNull(SessionRecoveryTable.recovery_error).
• 🟡 (21:58) The patch excerpt joined recovery continuations via .leftJoin(SessionRecoveryTable, eq(SessionRecoveryTable.continuation_message_id, SessionInputTable.id)).
• 🟡 (21:58) The patch excerpt showed recovery processing logs annotated with { sessionID: row.sessionID, executionID: row.executionID } through Effect.annotateLogs(...).
• 🟡 (21:58) The patch excerpt showed runner state clearing entry.pendingWake = false and exposing { active: Effect.sync(() => new Set(active.keys())), run, wake, interrupt }.
• 🟡 (21:58) The patch visibly modified packages/core/src/session/runner/llm.ts, including handling for tools whose tool.state.status is "pending" or "running".
• 🟡 (21:58) In packages/core/src/session/runner/llm.ts, execution claims were integrated with publication through { commit: () => SessionExecutionClaim.update(db, claim) }.
• 🟡 (21:58) The runner patch queried SessionExecutionTable.phase, wrapped an operation with Effect.exit, and updated execution state through updateExecution(...).
• 🟡 (21:58) The runner patch promoted steering inputs using SessionInput.promoteSteers(db, events, session.id, cutoff, () => updateExecution()), accumulating the result in promoted.
• 🟡 (21:58) The runner patch added overflow-recovery handling through recoverOverflow(...) and introduced runAfterOverflowCompaction: RunTurn.
• 🟡 (21:58) The overflow-compaction retry path could call runTurn(sessionID, executionID, undefined, defect.transition.step, ownerID).
• 🟡 (21:58) Recovery-aware steering logic set hasSteer to false while recovering; otherwise it called SessionInput.hasPending(db, input.sessionID, "steer").
• 🟡 (21:58) Continuation logic included the guard if (!recovering && !needsContinuation).
• 🟡 (21:58) The patch changed assistant-message publication to obtain IDs through publisher.assistantMessageID(event.id) and publisher.startAssistant().
• 🟡 (21:58) The event-publisher changes added publication of SessionEvent.Reasoning.Ended and reused startAssistant() when assigning assistantMessageID.