Distillation

Date: Sep 16, 2026

• 🟡 (15:42) User supplied an implementation excerpt spanning approximately lines 7976-9290 of the recall-aware Responses streaming code; it includes isSemanticResponsesEvent(event: string): boolean, recall argument parsing, indexed output projection, continuation-event normalization, terminal response validation, and rollback handling.
• 🟡 (15:42) Recall argument validation in the supplied implementation throws the exact error "invalid recall function arguments: unsupported scope" when an unsupported scope is provided and stores parsed calls in parsedInputs: Map<number, RecallArguments>.
• 🟡 (15:42) The implementation tracks indexed content lifecycle using valueDone and partDone, handles "response.content_part.done" and "response.output_item.done", and validates final values and authoritative-value state for projected output.
• 🟡 (15:42) The implementation separately processes reasoning summaries and can throw an error beginning "Responses reasoning summary ended before completion for index ${outputIndex}:${summaryIndex}" when a summary terminates prematurely.
• 🟡 (15:42) Recall tool detection checks that an output item has name === RECALL_TOOL_NAME; tool normalization also checks for type === "tool_use" and correlates the final call identifier with item.id.
• 🟡 (15:42) Codex-specific terminal validation contains an exception for response.status === "queued" and validates createdAt with Number.isFinite(createdAt); malformed terminal response data can therefore be rejected before completion is emitted.