Distillation

Date: Sep 16, 2026

• 🔴 (20:22) User specified that streamed events must always accumulate into the internal state for postResponse.
• 🟡 (20:22) Further inspection of packages/gateway/src/pipeline.ts lines 10085–11757 showed recall interception with deferred-event and byte limits, private recall-index tracking, and detection of other tool calls.
• 🟡 (20:22) Recall-only handling runs a streaming follow-up continuation, validates continuation events through validateResponseLifecycle(contState, ce, cparsed), tracks continuation recall and unresolved tool indexes, and requires continuation completion before merging results.
• 🟡 (20:22) Recall continuation transport failures can trigger retries logged as retrying recall continuation after ${error.kind} transport failure, optionally including a truncated session identifier; exhausted or aborted readers are released through cancelAndReleaseReader(follow.reader, signal.reason).
• 🟡 (20:22) Successful continuation merging checks usage compatibility with assertUsageMergeable(state.usage, contState.usage), transfers contState.terminalResponse, and preserves accumulated outputIdentities.
• 🟡 (20:22) The streaming path uses transactional buffering and settlement logic, remaps visible output indexes with remapVisibleOutputIndices(chunk, visibleIndices), categorizes principal failures including retry behavior for SSEStreamTransportError, and calls rollbackTransaction() when processing cannot be committed.