Distillation

Date: Sep 16, 2026

• 🟡 (14:05) In packages/gateway/test/openai-responses-recall-aware-stream.test.ts lines 1120–1147, a principal stream initial-read failure triggers retryPrincipal; if abort.signal then expires with DOMException("foreground expired", "TimeoutError"), client.text() rejects with name: "TimeoutError" and the newly returned retry response body is cancelled (retryBodyCancelled === true).
• 🟡 (14:05) Test "classifies a missing principal response body as unexpected" at packages/gateway/test/openai-responses-recall-aware-stream.test.ts:1150–1177 passes new Response(null) to streamResponsesRecallAware(). Expected behavior: exactly one response.failed event containing PUBLIC_GATEWAY_ERROR, no PUBLIC_RECALL_ERROR, no leaked "Upstream response has no body" text, no recall-continuation failure-hook categories, and one logged error: "openai-responses recall-aware stream failed category=principal_unexpected".
• 🟡 (14:05) Test "rejects response.in_progress changing the created response identity" at packages/gateway/test/openai-responses-recall-aware-stream.test.ts:1179–1197 creates response ID resp_identity_a, then sends response.in_progress and completion under resp_identity_b; draining the client must produce response.failed.
• 🟡 (14:05) Test "rejects malformed named Responses events in a continuation" at packages/gateway/test/openai-responses-recall-aware-stream.test.ts:1199–1226 uses principal response resp_bad_principal with recallCall(0, { query: "architecture" }), then follow-up response resp_bad_continuation containing malformed named event event: response.completed\ndata: {not-json}\n\n. Expected behavior: expose PUBLIC_RECALL_ERROR, do not leak {not-json}, and report exactly ["follow_up_protocol"] through setRecallContinuationFailureHook().
• 🟡 (14:05) Test setup for "retries a dropped recall continuation before exposing any output" at packages/gateway/test/openai-responses-recall-aware-stream.test.ts:1228–1259 defines a first follow-up response resp_dropped_followup that emits response.output_item.added at output_index: 0 for assistant message ID msg_retry_identity, then fails with Error("socket reset"). The recovery response resp_recovered_followup emits text "recovered answer" using the same message ID msg_retry_identity; the principal response is resp_retry_principal and invokes recallCall(0, { query: "retry continuation" }).