Distillation

Date: Sep 16, 2026

• 🟡 (15:14) Code change in packages/gateway/src/stream/openai-responses.ts:827: while materializing text-item content, the loop now executes if (!part) continue; before reading part.type. This safely skips holes or undefined entries in sparse content arrays.
• 🟡 (15:15) Search of packages/gateway/test/openai-responses-recall-aware-stream.test.ts found 17 matches for assertions involving empty rawOutputItems, unsuccessful completion, or the terminal continuation-usage test. Empty rawOutputItems assertions occur at lines 1049, 1118, 1255, 2267, 2494, 7315, 7389, 7586, 7657, 7884, and 9776; successful === false assertions occur at lines 2890, 2961, 6372, 9552, and 9612; line 7794 defines accounts for terminal Codex continuation usage once when candidate flush exceeds the transaction limit.
• 🟡 (15:15) Regression test accumulates the continuation event that crosses the retained-state limit in packages/gateway/test/openai-responses-recall-aware-stream.test.ts:7250-7332 constructs a continuation message whose triggerText is "private continuation retained-state trigger " + "x".repeat(maxRetainedStateBytes), where maxRetainedStateBytes = retainedBeforeTrigger * 32. It verifies the limit-crossing event is present in the state passed to finalizeResponsesAcc, but the visible completed response has content: [] and rawOutputItems: []; output emits exactly one response.failed, contains PUBLIC_RECALL_ERROR, omits the private trigger text and any response.completed, reports { status: "failed", output: [], error: { type: "server_error", message: PUBLIC_RECALL_ERROR } }, records outcome [false], and classifies the continuation failure as ["resource_limit"].
• 🟡 (15:15) Parameterized regression test retains continuation %s state when it crosses the retained-state limit in packages/gateway/test/openai-responses-recall-aware-stream.test.ts:7334-7404 covers every LIFECYCLE_ONLY_EVENTS case. It verifies sparse materialization preserves only scenario.partIndex with exactly ["type", "text"], while the externally visible failure has empty content and rawOutputItems, exactly one response.failed, PUBLIC_RECALL_ERROR rather than PUBLIC_GATEWAY_ERROR, no scenario.privateMarker in stream output or completion data, failed output [], and completion outcome [false].
• 🟡 (15:15) Continuation sparse-coordinate boundary tests in packages/gateway/test/openai-responses-recall-aware-stream.test.ts:7406-7424 cover output, content, and summary before shifted sparse-state mutation. For output, coordinate 99_997 is accepted and 99_998 rejected; for content and summary, coordinate 99_999 is accepted and 100_000 rejected.