Distillation

Date: Sep 16, 2026

• 🔴 (15:47) User directed: “Always feed the accumulator” in the Anthropic streaming lifecycle near line 3136.
• 🔴 (15:47) User asserted that injected tool_use never leaks to the client, in documentation near line 2704.
• 🔴 (15:47) User asserted that failed usage/accounting never depends on client demand, in a comment near lines 2864–2865; unsuccessful completion calls finish(false, finalizeUnsuccessfulResponsesAcc(state)).
• 🟡 (15:47) User supplied additional Responses-stream implementation spanning approximately lines 2526–3624. Visible logic includes responsesDoneItemMatchesAdded(completedSnapshot, accumulated), terminal-state handling for "incomplete" and failure, opts.stopAtTerminal, opts.requireCompletedTerminal, SSE framing as event: ${event}\n${dataLines}\n\n, external abort propagation via signal?.reason, keepalive cleanup, and demand resumption via resumeDemand?.().
• 🟡 (15:47) The supplied implementation includes an Anthropic-to-Responses streaming lifecycle beginning near line 3017, with demand waiting, mandatory accumulator feeding, translated events such as "response.output_item.added", text represented as "output_text", function-call call_id handling, final status mapping via mapStatusFromStopReason(resp.stopReason), cache usage accounting through ru.cacheReadInputTokens ?? 0, final output assembly, abort-listener cleanup, and the response header "content-type": "text/event-stream".