Distillation

Date: Sep 16, 2026

• 🟡 (13:06) Investigation continued through /home/byk/Code/opencode-lore-provider-error/packages/gateway/test/openai-responses-recall-aware-stream.test.ts lines 1262–2466, covering recall-tool suppression, continuation-failure hooks, retry rules, abort handling, frame/state budgets, and stream-integrity validation.
• 🟡 (13:06) Recall suppression tests include test("suppresses a recall function_call and emits a marker (mixed tools)", ...), verify recall calls are not exposed or executed as ordinary tools, and exercise bounded suppressed argument events with maxRetainedStateBytes: 1.
• 🟡 (13:06) Continuation-failure tests collect exact RecallContinuationFailureCategory values through setRecallContinuationFailureHook((category) => failures.push(category)); scenarios use onRecall, runFollowUp, retryPrincipal, retry counters, captured error logs, and guard callbacks that throw "should not be called" or "should not run".
• 🟡 (13:06) Retry behavior includes test("does not retry a pre-output principal inactivity failure", ...), an assertion that exactly one response.failed SSE event is emitted, validation: "codex" coverage, and foreground cancellation via abort.abort(new DOMException("foreground expired", "TimeoutError")).
• 🟡 (13:06) Additional fixtures cover recall query "architecture", anchors built with buildAnchor("transport") and buildAnchor("retry frame budget"), provider errors such as { type: "provider_error", message: "private failure" }, and empty rawOutputItems: [] / output: [] states.
• 🟡 (13:06) Stream-consistency coverage includes test("rejects output_item.done changing finalized content", ...), ensuring an output_item.done event cannot mutate content that was already finalized.