Distillation

Date: Sep 14, 2026

• 🟡 (08:56) packages/schema/AGENTS.md states @opencode-ai/schema owns browser-safe wire/storage contracts shared by protocol, server, core, and generated SDKs; runtime behavior, service layers, side effects, and host-local implementation details remain in the owning domain package.
• 🟡 (08:56) Schema package policy requires current contracts to be unversioned, retained legacy contracts to use explicit V1 naming, and permanent replacement architecture names/brands/identifiers to remove V2; retained V1 contracts are intended to move under src/v1/, and new/current code must not depend on that subtree.
• 🟡 (08:56) Schema event policy classifies definitions as current, shared transitional, or V1-only; V1-emitted events are not automatically included in Protocol or SDK Next, and clearly V1-only events such as message.updated and message.part.* stay outside the current Protocol/SDK Next event surface absent a documented current-client requirement.
• 🟡 (08:56) Schema module policy requires one canonical exported value per contract, rejects bridge aliases such as PluginID, PluginEvent, PtyInfo, PtyEvent, and SessionTodoInfo, and permits Core domain facades only when they re-export the exact canonical Schema value without creating a second schema identity.
• 🟡 (08:56) Schema contract conventions: public Schema.Struct records use same-name interfaces; unions, scalars, arrays, branded scalars, and event payload helpers use type aliases; closed string sets use Schema.Literals(...); public contracts are readonly by default and must not use Schema.mutable(...).
• 🟡 (08:56) Optional Schema properties must use the package optional(...) helper so encoded objects omit undefined; raw Schema.optional(...) is reserved for intentionally preserving an explicitly encoded undefined, and convenience defaults normally use decode-only Schema.withDecodingDefault(...).
• 🟡 (08:56) Current public Schema contracts avoid Schema.Any; JSON-serializable values use Schema.Json, genuinely opaque values use Schema.Unknown, and Schema.Any is allowed only at a documented unsafe compatibility boundary.
• 🟡 (08:56) Schema ID policy requires current constructors to expose create(), newly generated ID schemas to validate the exact emitted prefix including _, and reusable public schemas to have unique, stable, domain-qualified identifiers; legacy loose validators must not be tightened without an explicit compatibility and migration decision.
• 🟡 (08:56) Contract-change tests must cover optional properties omitting undefined, absence of accidental current-contract Schema.Any, stable and unique public identifiers, exact facade/schema identity, and exclusion of V1-only events from current Protocol manifests.
• 🟡 (08:56) packages/schema/src/session.ts exports the Session namespace from itself, defines ID = SessionID, Event = SessionEvent, and defines Session.Info with fields id, optional parentID, projectID, optional agent, optional model, cost, token counts (input, output, reasoning, and cache read/write), timestamps (created, updated, optional archived), title, location, optional subpath, and optional revert.
• 🟡 (08:56) packages/schema/src/session.ts:44 currently annotates the current Session.Info schema with identifier "SessionV2.Info", conflicting with the Schema package rule that current contract identifiers must remove V2.
• 🟡 (08:56) packages/schema/src/session.ts:46-51 defines Session.ListAnchor with id: ID, time: Schema.Finite, and direction: Schema.Literals(["previous", "next"]), annotated with identifier "Session.ListAnchor".
• 🟡 (08:56) Current Session.Info contains no durable execution/recovery state such as active-run identity, provider-turn status, tool-work status, recovery claim, recovery epoch, or recovery timestamp; the visible durable fields alone describe session metadata, accounting, placement, timestamps, and revert state.