Distillation

Date: Sep 15, 2026

• 🟡 (12:50) Migration packages/core/src/database/migration/20260914170650_session-recovery.ts, ID 20260914170650_session-recovery, creates session_recovery with session_id, assistant_message_id, continuation_message_id, and time_created; primary key is (session_id, assistant_message_id), all three referenced IDs have ON DELETE CASCADE foreign keys, and session_recovery_continuation_message_idx uniquely indexes continuation_message_id.
• 🟡 (12:50) Migration packages/core/src/database/migration/20260914214636_session-execution.ts, ID 20260914214636_session-execution, creates session_execution with id as text primary key plus session_id, owner_id, optional assistant_message_id, and time_created; it adds non-null execution_id to session_recovery, a unique session_execution_session_idx on session_id, session_execution_owner_idx on owner_id, and unique session_recovery_execution_idx on execution_id.
• 🔴 [required-recovery-safety] (12:52) User requires recovery to “never recover a live execution lease”; the corresponding packages/core/test/session-projector.test.ts case uses expires_at: Date.now() + 60_000 and verifies that the execution remains while SessionRecoveryTable and SessionInputTable remain empty.
• 🔴 [required-recovery-safety] (12:52) User requires recovery to “never recover an execution superseded by a newer assistant”; the corresponding packages/core/test/session-projector.test.ts case associates the expired execution with msg_recovery_abandoned at sequence 0, adds msg_recovery_newer at sequence 1, and verifies that the stale execution is deleted without creating recovery or continuation rows.
• 🟡 (12:53) Current packages/core/src/database/migration.gen.ts includes all four recovery/execution migrations in order: 20260914170650_session-recovery, 20260914214636_session-execution, 20260914222526_session-execution-phase, and 20260914235657_session-execution-lease (replacing the previously inspected registry snapshot that omitted the lease migration).
• 🟡 (12:53) packages/core/schema.json contains session_execution and session_recovery, their foreign keys and primary keys, plus indexes session_execution_session_idx, session_execution_owner_idx, session_recovery_execution_idx, and session_recovery_continuation_message_idx.
• 🟡 (12:54) In packages/core/src/session/message-updater.ts:237-281, session.next.step.recovered creates an unknown error whose message is "Provider Step outcome unknown after server restart" for phase "unknown" and "Session execution interrupted by server restart" otherwise.
• 🟡 (12:54) Recovery without assistantMessageID appends a synthetic message using recoveryMessageID, the recovery timestamp, and the phase-dependent error text; recovery with an assistant marks that assistant completed with finish = "error", attaches the error, and appends text content with ID recovery:${event.data.executionID}.
• 🟡 (12:54) During recovered-assistant projection, every pending or running tool is completed at the recovery timestamp and changed to error "Tool execution outcome unknown after server restart"; string inputs become {}, while running tools preserve structured and content, and pending tools use empty values.
• 🟡 (12:55) packages/core/test/session-projector.test.ts verifies recovery idempotency across two startup scans: an expired "ready" execution produces exactly 1 SessionRecoveryTable row, 1 SessionInputTable row, no remaining execution row, and exactly 1 synthetic session message.
• 🟡 (12:57) packages/core/test/database-migration.test.ts runs bun ${fileURLToPath(new URL("../script/migration.ts", import.meta.url))} --check on Linux with a 30,000 ms timeout and expects exit code 0 plus "No schema changes, nothing to migrate".
• 🟡 (12:57) The empty-database migration test applies DatabaseMigration.apply(db), verifies session, session_input, and session_context_epoch exist, verifies transitional columns agent, replacement_seq, and revision are absent from session_context_epoch, and expects the migration-table count to equal migrations.length.
• 🟡 (12:57) The empty-database migration test expects these indexes in sorted query output: event_aggregate_seq_idx, event_aggregate_type_seq_idx, session_input_session_admitted_seq_idx, session_input_session_pending_delivery_seq_idx, session_input_session_promoted_seq_idx, session_message_session_seq_idx, session_message_session_time_created_id_idx, and session_message_session_type_seq_idx.
• 🟡 (13:01) Generated schema implementation packages/core/src/database/schema.gen.ts includes creation of session_execution and session_recovery, their cascade foreign keys, primary key session_recovery_pk, and indexes session_execution_session_idx, session_execution_owner_idx, session_recovery_execution_idx, and session_recovery_continuation_message_idx.