Distillation

Date: Sep 16, 2026

• 🟡 (14:57) Full packages/gateway/test/openai-responses-recall-aware-stream.test.ts run initially had 3 failing tests: 1. "caps unindexed transactional continuation output at the retained-state limit" at line 6166 expected PUBLIC_RECALL_ERROR; 2. "caps client-visible output across chained continuations" at line 6217 expected PUBLIC_RECALL_ERROR; 3. "does not double-charge transactional output when retrying a continuation" at line 6271 expected a 600 KiB opaque event: extension frame to be client-visible.
• 🟡 (14:57) Root cause of the 3 failures: stale continuation-extension contracts conflicted with the reviewed privacy boundary by expecting opaque provider extensions—including a 1 MiB unindexed extension, two chained 600 KiB extensions, and a retried 600 KiB extension—to leak to the client or consume the transactional retained-state budget.
• 🟡 (14:58) Chosen replacement contract for the stale tests: opaque continuation frames are dropped; semantic answers and chained recall still complete; continuation retries remain exact-once; and no fixed PUBLIC_RECALL_ERROR appears solely because of dropped opaque frames.
• 🟡 (14:58) packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts were modified. Parsed metadata events continue to be applied to the accumulator before delivery redaction, preserving the accumulator-first invariant while preventing raw opaque-frame forwarding.
• 🟡 (14:59) Full Vitest run for packages/gateway/test/openai-responses-recall-aware-stream.test.ts passed: 1 test file passed; 222/222 tests passed; duration 6.20s.
• 🟡 (14:59) Assistant planned an exact two-file diff review for accidental scope growth, followed by the affected projection/transport matrix and static/build gates; no results for those later checks were available in this segment.
• 🔴 (15:00) User specified the security invariant/test contract "never exposes non-semantic %s frames after recall interception".
• 🟡 (15:00) The parameterized "never exposes non-semantic %s frames after recall interception" test covers both "principal" and "continuation" sources. It injects raw event: diagnostic data containing "private recall query, arguments, result, and identity", requires "safe answer" to remain visible, and requires "event: diagnostic" to remain absent.
• 🟡 (15:00) Audit of packages/gateway/src/stream/openai-responses.ts found five created_at assignments at lines 2628, 2858, 2876, 3201, and 3248.
• 🟡 (15:01) ResponsesAccState in packages/gateway/src/stream/openai-responses.ts retains response identity/model/status and usage, terminal event/response, codexRateLimits, rawItems, strict identity maps (itemIndexById, callIndexById, effectiveToolIndexById), output-index tracking, active/unbound/done item sets, and accumulated text/tool-use items.
• 🟡 (15:01) makeResponsesAccState() is defined at packages/gateway/src/stream/openai-responses.ts:556 and used at lines 1895 and 2417; applyResponsesEvent(state, event, parsed) begins at line 582 and is documented as the shared per-event accumulator that performs no I/O.