Distillation

Date: Sep 16, 2026

• 🔴 (19:44) User stated that private source coverage in streamResponsesRecallAware() is “never emitted to the client” (packages/gateway/src/pipeline.ts:7854).
• 🟡 (19:44) packages/gateway/src/pipeline.ts:201-218 imports these exact artifacts from ./stream/openai-responses: accumulateResponsesSSEStream, streamResponsesPassthrough, translateAnthropicStreamToResponses, applyResponsesEvent, finalizeResponsesAcc, formatResponsesEvent, makeResponsesAccState, mapStatusFromStopReason, isSupportedResponsesOutputItemType, isValidResponsesOutputItemStatus, isValidResponsesReasoningEncryptedContent, responsesDoneItemMatchesAdded, responsesTerminalItemMatches, normalizeCodexResponsesEvent, ResponsesTerminalError, and ResponsesAccState.
• 🟡 (19:44) Documentation near packages/gateway/src/pipeline.ts:7781 states that the terminal response.completed reflects only client-visible output.
• 🟡 (19:44) The streamResponsesRecallAware() implementation tracks lifecycle state including deltaSeen, content parts in Map<number, TextPartLifecycle>, frame count via const frameCounter = { count: 0 }, transaction rollback callbacks executed in reverse order, and recall timing through opts.recallDeadlineAt.
• 🟡 (19:44) Recall argument validation in streamResponsesRecallAware() rejects unknown properties with invalid recall function arguments: unknown property "${unknown}", rejects a non-string query, and rejects unsupported scope with invalid recall function arguments: unsupported scope.