Distillation

Date: Sep 17, 2026

• 🔴 (08:34) User’s repository guidance requires runtime dependencies to flow Schema → 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.
• 🔴 (08:34) User’s import style requires: never alias imports (import { foo as bar } and renamed imports such as resolve as pathResolve are prohibited).
• 🔴 (08:34) User’s import style requires: never use star imports (import * as Foo and import type * as Foo are prohibited); namespace-style use should import a module’s own named exported namespace, e.g. import { Project } from "@opencode-ai/core/project" and reference Project.ID.
• 🔴 (08:34) User requires always running bun typecheck from package directories such as packages/opencode, never tsc directly.
• 🔴 (08:34) User’s testing workflow prohibits running tests from the repository root because of the do-not-run-tests-from-root guard; tests must run from package directories such as packages/opencode.
• 🔴 (08:34) User’s repository guidance says generated files under packages/client/src/generated and packages/client/src/generated-effect must not be edited directly; after public Protocol or Server HttpApi changes, run bun run generate from packages/client; regenerate the legacy JavaScript SDK with ./packages/sdk/js/script/build.ts.
• 🔴 (08:34) User’s repository uses dev as the default branch; local main may not exist, so diffs should use dev or origin/dev.
• 🔴 (08:34) User’s branch naming convention requires at most three hyphen-separated words, without slashes or type prefixes such as feat/ or fix/; commit messages and PR titles use type(scope): summary with valid types feat, fix, docs, chore, refactor, and test.
• 🟡 (08:34) Review provenance verification showed the checkout at base commit ab9408c81cc9916177641ae8e9f08624fc27b5b9 in detached-HEAD state, with 34 changed paths: 30 modified and 4 untracked.
• 🟡 (08:34) The 4 untracked review paths were packages/core/src/database/migration/20260914170650_session-recovery.ts, packages/core/src/session/execution/claim.ts, packages/core/src/session/recovery-id.ts, and packages/core/src/session/recovery.ts.
• 🔴 (08:34) User’s V2 Session Core guidance requires durable prompt admission to remain separate from model execution: SessionV2.prompt(...) admits one durable session_input row before advisory SessionExecution.wake(sessionID), unless resume: false requests admit-only behavior; the serialized runner promotes admitted inputs at safe boundaries.
• 🔴 (08:34) User’s V2 Session Core guidance requires SessionExecution to remain process-global and Session-ID based, while SessionRunner, model resolution, tool registry, permissions, and filesystem remain Location-scoped; interruption targets the active process-local ownership chain, and idle or missing interruption is a no-op.
• 🔴 (08:34) User’s V2 Session Core guidance requires exactly one explicit llm.stream(request) call per provider turn and reloading projected history before durable continuation; orchestration must not bridge through legacy SessionPrompt.loop(...) or an in-memory tool loop.
• 🔴 (08:34) User’s V2 Session Core guidance says SessionRunCoordinator joins explicit same-Session resumes, coalesces prompt wakeups, and permits different Sessions to run concurrently; advisory wakes only drain eligible durable inbox rows, while post-crash continuation recovery requires a separate explicit design.
• 🔴 (08:34) User’s delivery semantics require prompts to default to steer and promote at the next safe provider-turn boundary; explicit queue inputs remain pending until the Session would otherwise idle, then one queued input is promoted before continuation is reevaluated.
• 🔴 (08:34) User’s Schema guidance requires browser-safe serializable contracts in @opencode-ai/schema, preserving dependency direction @opencode-ai/schema <- @opencode-ai/protocol <- @opencode-ai/server; runtime behavior, services, side effects, and host-local details remain in their owning domain packages.
• 🔴 (08:34) User’s HTTP API guidance requires normal and streaming endpoints to use HttpApiBuilder.group(...); declared routes needing raw request/response use handleRaw(...); raw HttpRouter.use(...) is reserved for routes outside the declared API surface, such as catch-all UI fallback.