Distillation

Date: September 16, 2026

• 🟡 (22:41) Continued inspection of packages/gateway/src/pipeline.ts covered approximately lines 10817–11783, focusing on follow-up continuation streaming, held-event release, nested recall handling, continuation failure recovery, transaction finalization, principal-stream retries, and usage reporting.
• 🟡 (22:41) Follow-up events are read through parseSSEStream(follow.reader, ...); continuation accumulation uses contState, streamed reasoning is retained via preserveStreamedReasoning(contState, ci), and selected held events are removed with heldContinuationEvents.splice(index, 1).
• 🟡 (22:41) Continuation recall processing tracks pending output positions through contPending.map((recall) => recall.outputIndex) and distinguishes continuation items whose type === "function_call".
• 🟡 (22:41) The continuation path explicitly assigns continuationFailureCategory = "follow_up_protocol" for follow-up protocol failures and recognizes RecallContinuationFailure during error handling.
• 🟡 (22:41) Continuation usage is folded into principal accumulated usage with mergeUsage(state.usage, contState.usage), including handling when contState.terminalEvent === "response.incomplete".
• 🟡 (22:41) Recall continuation requests include finalRecallRound: recallBudget.mustFinalizeNext(), allowing the recall budget to force the next round to produce a final response.
• 🟡 (22:41) Transaction cleanup can clear pending rollback callbacks with transactionRollbacks.length = 0; post-delivery completion failures are logged as "recall onComplete failed after delivery".
• 🟡 (22:41) Principal stream cleanup sets principalReader = null; retry handling checks error instanceof SSEStreamTransportError, tracks principalTransportRetries, and can call opts.retryPrincipal.
• 🟡 (22:41) Final failure reporting uses continuationFailureCategory ?? "unexpected" when no more specific continuation failure category was assigned.