Distillation

Date: Sep 16, 2026

• 🔴 (11:23) packages/core/test/session-execution-local.test.ts uses in-memory Database.layerFromPath(":memory:"), session ID SessionSchema.ID.make("ses_execution_local"), project worktree /project, and helper effects insertSession and claims.
• 🔴 (11:23) The SessionExecutionLocal test suite asserts that a successful resume(sessionID) drain clears the execution claim.
• 🔴 (11:23) The suite asserts that closing the scope of an active execution preserves its claim: after Scope.close(firstScope, Exit.void), one row remains in SessionExecutionTable.
• 🔴 (11:23) The suite asserts that explicit execution.interrupt(sessionID) clears the execution claim.
• 🔴 (11:23) User specified the invariant “never starts a second owner while the lease is live”: after the first owner starts, a second owner’s resume(sessionID) must leave secondRuns at 0 and retain exactly one claim.
• 🔴 (11:23) User specified the invariant “never overwrites an expired lease”: after manually setting the first claim’s expires_at to 0, a second owner’s resume(sessionID) must leave secondRuns at 0 and preserve the stale claim’s original id and owner_id.
• 🔴 (11:23) User specified the invariant “never re-enters its own uncertain live lease”: a run changes its claim’s phase to "unknown" and dies with "simulated failure"; a subsequent resume(sessionID) must not run again, leaving runs === 1 and one claim.
• 🔴 (11:23) Heartbeat renewal is based on the current clock: the initial expires_at is 30_000; after successive TestClock.adjust("10 seconds") calls it becomes 40_000 and then 50_000.
• 🔴 (11:23) User specified the invariant “never revives an expired claim on heartbeat”: after expires_at is manually set to 0, advancing TestClock by "10 seconds" must leave it at 0.
• 🔴 (11:23) The suite asserts cancellation settles before a pending successor starts: while the first run’s finalizer is blocked, a new wake(sessionID) is registered and the clock advances "40 seconds"; the claim expiry remains greater than 40_000, releasing the finalizer starts the successor, total runs becomes 2, and all claims are eventually cleared.
• 🔴 (11:23) The partially displayed SessionRunCoordinator tests include an invariant named "snapshots only active executions".
• 🔴 (11:23) The partially displayed SessionRunCoordinator tests include an invariant named "runs a wake registered during interruption cleanup"; the visible expectation requires runs to become 2.