Distillation

Date: September 16, 2026

• 🔴 (22:40) User directed that stream events must always accumulate into the internal state for postResponse.
• 🟡 (22:40) Continued inspection of packages/gateway/src/pipeline.ts covered approximately lines 9817–10779, including late-reader cancellation, synthetic response construction, abort cleanup, SSE parsing, principal failure categorization, recall-tool stream handling, transactional rollback, and continuation retries.
• 🟡 (22:40) The stream-processing loop uses parseSSEStream(reader, ...) and accumulates events into internal state even when handling hidden recall-tool behavior, ensuring postResponse receives the complete accumulated state.
• 🟡 (22:40) Recall-tool handling tracks bounded hidden argument data using hiddenRecallBytes and maxHiddenRecallBytes; malformed argument streams are constrained so they cannot grow without bound.
• 🟡 (22:40) Recall completion can fail with "recall stream ended before function arguments completed" and uses settleRecall; an executed.rollback result triggers rollback handling.
• 🟡 (22:40) Recall continuation logic tracks recallContinuationTransportRetries and initializes continuation accumulation with const contState = makeResponsesAccState().
• 🟡 (22:40) The inspected streaming code tracks state including principalReadFinished, ordinaryToolEmitted, resolvingRecallTool, transactionalBytes, and deferredBytes, and invokes late-reader cancellation when signal.aborted.