Distillation

Date: Sep 16, 2026

• 🔴 (11:16) User specified a pending architecture requirement: “Replace local ownership with durable multi-node ownership when clustered.”
• 🔴 (11:16) User specified a pending runtime-safety requirement: honor interruption and reject stale work after runtime attachment replacement.
• 🔴 (11:16) User supplied Session runner code whose completed behavior includes incrementally persisting assistant text and usage events as they arrive.
• 🔴 (11:16) User supplied Session runner code whose completed behavior reloads projected history and starts the next explicit provider turn after local tool results.
• 🔴 (11:16) User supplied Session runner logic that loads V2 history, translates it, resolves a model through a core service, materializes tool definitions, streams provider events, captures snapshots, and handles continuation transitions through TurnTransitionError, including ContinueAfterCompaction.
• 🔴 (11:16) User supplied provider-turn persistence code documented as persisting one provider turn without executing tools or starting a continuation turn.
• 🔴 (11:16) User supplied event-publishing logic centered on SessionRunner.publishLLMEvent, covering reasoning start/delta/end, tool input, tool calls, tool results, tool errors, step finish, assistant failure, and unsettled-tool failure handling.
• 🔴 (11:16) User supplied strict streamed-event consistency checks: deltas before fragment start are fatal; changing a tool input name for an existing event ID triggers Tool input name changed for ${event.id}: ${tool.name} -> ${event.name}; changing a tool call name triggers Tool call name changed for ${event.id}: ${tool.name} -> ${event.name}.
• 🔴 (11:16) User supplied tool-event state that tracks tools by call ID, associates them with assistantMessageID, records whether they are settled, and distinguishes provider execution with providerExecuted: false where applicable.