Distillation

Date: Sep 15, 2026

• 🟡 (22:54) User supplied additional session-recovery code adding const Phase = Schema.Literals(["ready", "safe", "unknown", "continue"]), time-based claim handling via Clock.currentTimeMillis, and claim validation involving claim.assistant_message_id and the latest message ID.
• 🟡 (22:54) The diff adds a new 305-line recovery implementation using SessionRecoveryTable, synthetic recovery inputs, input.delivery !== "queue" validation, assistant-message type checks, and error logging through Effect.logError("Failed to redrive Session input", cause).pipe(Effect.annotateLogs({ sessionID })).
• 🟡 (22:54) packages/core/src/session/run-coordinator.ts was changed to retain completion state in entry.exit, read SessionExecutionTable.phase, promote recovery inputs with SessionInput.promoteExact(db, events, session.id, promotion.recoveryInputID, ...), and define terminalCommit: () => updateExecution({ phase: "safe", assistant_message_id: null }).
• 🟡 (22:54) Session-run admission logic now includes the guard if (!recovering && !input.force && !hasSteer && !hasQueue) return, replacing logic that directly assigned shouldRun from SessionInput.hasPending(db, input.sessionID, "queue").
• 🟡 (22:54) Message recovery/materialization logic iterates tool content and restricts handling to tools whose tool.state.status is "pending" or "running"; it also checks whether event.data.assistantMessageID === undefined.