Distillation

Date: Sep 16, 2026

• 🔴 (13:09) User specified an invariant in packages/gateway/src/pipeline.ts around line 18530: “the follow-up's stream flag can never diverge from how the continuation” is delivered.
• 🔴 (13:09) User specified a robustness invariant in packages/gateway/src/pipeline.ts around line 18705 using the exact wording “Never throws / never”; the surrounding comment says this applies when a Lore context-warning banner is layered on.
• 🔴 (13:09) User specified that provisional requests “must never expose” provider diagnostics while proving a session identity; handleProvisionalConversationTurn cancels the upstream body and returns sanitizedUpstreamErrorResponse(upstreamResponse) when upstreamResponse.ok is false (packages/gateway/src/pipeline.ts, lines 15834-15838).
• 🔴 (13:09) User’s provisional-session design requires handleProvisionalConversationTurn to validate a provisional session identity without touching session-owned state. A full Lore turn occurs only on a later retry after a successful response confirms the presented header; failed or incomplete attempts leave the adopted session, project rows, auth registries, and gradient state untouched (packages/gateway/src/pipeline.ts, lines 15795-15800).
• 🟡 (13:09) handleProvisionalConversationTurn resolves route intent via prepareRequestUpstream(req, config) but keeps it private until a complete response and client EOF confirm the provisional identity (packages/gateway/src/pipeline.ts, lines 15811-15814).
• 🟡 (13:09) Provisional streaming responses are strictly accumulated by effective protocol: openai-responses uses accumulateResponsesSSEStream with validation: req.codex ? "codex" : "public", stopAtTerminal: true, and requireCompletedTerminal: true; openai uses accumulateOpenAISSEStream with strict: true, stopAtTerminal: true, and consumeUntilDone: true; gemini uses accumulateGeminiSSEStream with strict: true and stopAtTerminal: true; other protocols use accumulateSSEResponse with strict: true and stopAtTerminal: true (packages/gateway/src/pipeline.ts, lines 15841-15868).
• 🟡 (13:09) Provisional non-streaming responses use accumulateNonStreamResponse(upstreamResponse, forwarded.effectiveProtocol, req.codex === true, abortScope.signal, true) (packages/gateway/src/pipeline.ts, lines 15869-15875).
• 🟡 (13:09) When provisional accumulation raises ResponsesTerminalError, handleProvisionalConversationTurn schedules post-response handling with scheduleStreamingPostResponse; it waits for downstreamSettled, one setImmediate, and optional provisionalFinalizerPauseForTest, then abandons stale generations when requestGeneration !== streamingPostResponseGeneration (packages/gateway/src/pipeline.ts, lines 15876-15890).
• 🟡 (13:09) During provisional finalization, a guarded project conflict detected by conflictsWithConfidentSessionProject(identified.sessionID, pathResult) causes dropOwnedProvisionalKey(identified.provisionalKey, identified.sessionID) and immediate return (packages/gateway/src/pipeline.ts, lines 15891-15900).
• 🟡 (13:09) Provisional unsuccessful responses are passed to accountUnsuccessfulResponse with conversationTTLForAccounting(identified.sessionID); the dirty callback sets the matching session state’s _dirty = true. The scheduled work is associated with requestCredentialFingerprint(req.rawHeaders, config) ?? undefined (packages/gateway/src/pipeline.ts, lines 15901-15916).
• 🟡 (13:09) Same-protocol forwarding returns a validated limited stream when req.stream && upstreamResponse.body; otherwise it reads the body with readForegroundBody, validates non-streaming openai-responses using parseResponsesNonStreamEnvelope(JSON.parse(body)), copies usage-limit headers, and returns JSON with the upstream status (packages/gateway/src/pipeline.ts, lines 15670-15695).
• 🟡 (13:09) Cross-protocol Anthropic streaming translates directly with strict validation: translateAnthropicStreamToOpenAI, translateAnthropicStreamToResponses, or translateAnthropicStreamToGemini, each receiving signal: abortScope.signal (packages/gateway/src/pipeline.ts, lines 15700-15735).
• 🟡 (13:09) Other cross-protocol streaming combinations accumulate the upstream response under preserveIncompleteResponsesTerminal and re-emit it through nonStreamHttpResponse; non-streaming cross-protocol responses similarly use accumulateNonStreamResponse followed by nonStreamHttpResponse (packages/gateway/src/pipeline.ts, lines 15736-15792).