Distillation

Date: Sep 16, 2026

• 🟡 (15:57) User supplied implementation code defining Responses accumulator lifecycle tracking with ResponsesAccState, OutputLifecycle, lifecyclesFor(acc), and per-output/per-part normalization state including authoritativeValueSeen, argumentDeltaSeen, valueDone, created, and terminal.
• 🟡 (15:57) Responses normalization rejects conflicting streamed/final content with errors including Responses ${description} changed content for index ${outputIndex}:${partIndex}.
• 🟡 (15:57) Recall execution configuration uses opts.maxRecallExecutions ?? opts.maxRecallDepth ?? MAX_RECALL_EXECUTIONS; retained transactional state is limited via maxTransactionalBytes = maxRetainedStateBytes.
• 🟡 (15:57) Recall transaction rollback restores state from transactionBaseline, clears the baseline afterward, and logs rollback errors with log.error("recall transaction rollback failed:", err).
• 🟡 (15:57) Principal transport retry configuration is maxPrincipalTransportRetries = 1.
• 🟡 (15:57) Recall argument validation requires an object and throws invalid recall function arguments: expected object otherwise. Supported argument handling shown includes id, ids, detailOffset, and detailLimit, with validation preventing incompatible combinations.
• 🟡 (15:58) Responses event validation requires valid output_index values for applicable events and throws invalid Responses output_index for ${event} on failure; behavior includes a validation-specific branch for opts.validation === "codex".
• 🟡 (15:58) Responses output item handling validates streamed items, tracks them in state.rawItems, and supports item types including function_call; function-call processing handles arguments, final call_id, and consistency against previously declared or existing items.
• 🟡 (15:58) Responses content normalization handles event families beginning with response.content_part, response.reasoning_text, and related text/refusal events. It seeds text parts through seedTextParts(...), including "reasoning summary" handling.
• 🟡 (15:58) Responses content validation rejects authoritative content changes with Responses content_part.done changed content for index ${outputIndex}:${contentIndex} and streamed-content divergence with Responses ${event} changed streamed content for index ${outputIndex}:${contentIndex}.
• 🟡 (15:58) Responses event validation requires a valid summary_index for applicable events and throws invalid Responses summary_index for ${event} on failure.