Distillation

Date: Sep 16, 2026

• 🟡 (21:58) User supplied a further partial patch excerpt showing Effect error-handling constructs Effect.orDie, Effect.tapCause((cause) => ...), and Effect.catchDefect((defect) => ...).
• 🟡 (21:58) The patch excerpt showed recovery phase guards involving "unknown" and "continue", including if (current && current.phase !== "unknown" && current.phase !== "continue") and if (event.data.phase === "continue") return Effect.void.
• 🟡 (21:58) The patch excerpt showed recovery wake-state updates using .set({ wake_pending: true }), plus a call yield* publish(db, events, sessionID, [row], commit).pipe(...).
• 🟡 (21:58) The patch excerpt showed recovery-message handling that queries SessionMessageTable.id against recovery.assistant_message_id and creates an identifier formatted as recovery:${event.data.executionID}.
• 🟡 (21:58) The patch excerpt visibly modified packages/core/src/session/projector.ts, selecting phase: SessionRecoveryTable.phase and setting wake_pending: true.
• 🟡 (21:58) The patch excerpt imported SessionEvent from ./event and added an optional parameter excludeRecoveryExecutionID?: string.
• 🟡 (21:58) The patch excerpt showed execution leasing via .set({ owner_id: ownerID, expires_at: now + SESSION_EXECUTION_LEASE_MS }) and quarantine logic comparing SessionExecutionTable.expires_at with quarantinedAt.
• 🟡 (21:58) The patch excerpt selected a recovery candidate with phase.value === "continue" || claim.assistant_message_id === null ? undefined : latest and queried messages ordered by desc(SessionMessageTable.seq).