Distillation

Date: Sep 14, 2026

• 🔴 (23:25) packages/core/test/database-migration.test.ts test defaults missing workspace names while preserving legacy workspace data creates legacy workspace wrk_legacy with type="remote", branch="main", directory="/repo", extra="{}", and project_id="proj_legacy"; after DatabaseMigration.applyOnly(db, [workspaceNameMigration]), it expects name="" while preserving branch, directory, and extra.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test imports unnamed legacy Drizzle journal entries by their actual migration timestamps inserts Date.UTC(2026, 3, 10, 17, 45, 13) into __drizzle_migrations.created_at and expects migration ID 20260410174513_workspace-name.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test rejects unknown legacy Drizzle journal timestamps instead of guessing completed migrations inserts timestamp 1234567890000 and expects an error containing does not match any known migration.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test serializes concurrent embedded initialization for one database path concurrently builds 2 Database.layerFromPath(filename) layers for the same embedded.sqlite path with { concurrency: "unbounded" }.
• 🔴 (23:25) On Linux, packages/core/test/database-migration.test.ts test declared schema has no ungenerated migrations runs bun packages/core/script/migration.ts --check via the script URL.
• 🔴 (23:25) A database migration test verifies AbsolutePath.make("D:\\Moved\\Thing") is encoded in SQLite as D:/Moved/Thing, sandboxes is stored as JSON.stringify(["D:/Moved/Thing"]), querying ProjectTable.worktree by the normalized path finds the project, and reading an invalid raw value "not-absolute" throws.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test imports existing drizzle migration state imports named legacy migration 20260127222353_familiar_lady_ursula from __drizzle_migrations into migration.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test does not replay a migrated session metadata column records legacy migration 20260511173437_session-metadata, applies [sessionMetadataMigration], and expects only that migration ID in the new journal.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test accepts the temporary replacement session metadata migration id begins with 20260530232709_lovely_romulus and expects both it and canonical ID 20260511173437_session-metadata after applying sessionMetadataMigration.
• 🔴 (23:25) packages/core/test/database-migration.test.ts test skips drizzle import when migration table already has state seeds migration with ID existing, also seeds legacy 20260127222353_familiar_lady_ursula, and expects only existing to remain after DatabaseMigration.applyOnly(db, []).
• 🔴 (23:25) At commit dc661f30cb2055ad6248fdc59b14998d834497be, packages/core/test/session-projector.test.ts uses exact recovery error { type: "unknown", message: "Provider Step outcome unknown after server restart" }, including a text part { type: "text", id: "recovery:execution", text: "Provider Step outcome unknown after server restart" }.
• 🔴 (23:25) packages/core/test/session-projector.test.ts invokes SessionRecovery.recover() repeatedly with Effect.provideService(SessionExecution.Service, recoveryExecution), including 2 consecutive calls at lines 200-201.
• 🔴 (23:26) User requires abandoned local tools inherited from a prior process to be durably failed before the next provider request with exact model-visible error Tool execution interrupted; such tools must never be silently re-executed because their outcome and side-effect completion are unknown.
• 🔴 (23:26) User requires retries, compaction, restart, and continuation recovery to rely only on explicit durable state and never silently replay ambiguous or partial provider/tool side effects.
• 🔴 (23:26) User requires execution intent and progress to be persisted before execution, with durable facts distinguished from process-local ownership and advisory wakeups.
• 🔴 (23:26) User requires unfinished sessions to be claimed atomically and separately from unrelated ownership fields, with duplicate-safe multi-node fencing in clustered deployments.
• 🔴 (23:26) User permits automatic resumption only for admitted work proven never to have started.
• 🔴 (23:26) User requires ambiguous work to receive interrupted or unknown outcomes; projected running tools must be settled with Tool execution interrupted, stale projections or partial output must not be reopened, and a newer turn supersedes older incomplete work.
• 🔴 (23:26) User requires recovery to admit exactly 1 deterministic synthetic continue through the normal execution path so the model decides whether to retry in a new Step.
• 🔴 (23:26) User requires work to be repeated only after an explicit retry decision or proven idempotency, and recovery must remain bounded to prevent loops.
• 🔴 (23:26) At commit dc661f30cb2055ad6248fdc59b14998d834497be, packages/core/src/session/input.ts filters on null SessionInputTable.promoted_seq and exports SessionInput.hasPending; packages/core/src/session/projector.ts:489 compares both admitted_seq and promoted_seq against boundary.seq.
• 🔴 (23:26) At commit dc661f30cb2055ad6248fdc59b14998d834497be, packages/core/src/session/runner/llm.ts:456-472 checks pending "steer" input before "queue" input: hasQueue is forced false when hasSteer, continuation can be triggered by pending steer input, and queue input determines shouldRun afterward.
• 🔴 (23:27) Repository instructions state the default branch is dev; local main may not exist, so diffs should use dev or origin/dev.
• 🔴 (23:27) Repository branch names must contain at most 3 short hyphen-separated words and must not use slashes or type prefixes such as feat/ or fix/; examples are session-recovery, fix-scroll-state, and regenerate-sdk.
• 🔴 (23:27) Commit messages and PR titles must use type(scope): summary; allowed types are feat, fix, docs, chore, refactor, and test, with optional scopes such as core, opencode, tui, app, desktop, sdk, or plugin.
• 🔴 (23:27) Repository dependency direction must remain Schema → Core and Protocol, then Core and Protocol → Server. Client runtime code may depend on Schema and Protocol but never Core or Server; sdk-next composes Client, Core, and Server.
• 🔴 (23:27) After changing the public Protocol or Server HttpApi, run bun run generate from packages/client; do not edit src/generated or src/generated-effect directly. The legacy JavaScript SDK is regenerated with ./packages/sdk/js/script/build.ts.
• 🔴 (23:27) User requires always running bun typecheck from package directories such as packages/opencode, never invoking tsc directly.
• 🔴 (23:27) At commit dc661f30cb2055ad6248fdc59b14998d834497be, packages/schema/src/session-event.ts defines event types session.next.step.interrupted and session.next.step.recovered.
• 🔴 (23:28) The durable-event manifest exports namespace DurableEventManifest; SessionDurable.definitions is Event.durable(SessionEvent.DurableDefinitions), SessionDurable.schema is SessionEvent.Durable, and aggregate Durable combines durable SessionV1.Event.Definitions with all SessionEvent.DurableDefinitions.
• 🔴 (23:28) Migration packages/core/src/database/migration/20260603040000_session_message_projection_order.ts first deletes every row from session_message because pre-launch projections cannot be assigned truthful aggregate order, then adds required integer column seq, drops session_message_session_type_time_created_id_idx, and creates indexes session_message_session_seq_idx on (session_id, seq) and session_message_session_type_seq_idx on (session_id, type, seq).
• 🔴 (23:28) Migration packages/core/src/database/migration/20260303231226_add_workspace_fields.ts adds workspace columns type text NOT NULL, nullable name text, nullable directory text, and nullable extra text, then drops config.