Distillation

Date: September 16, 2026

• 🟡 (22:36) Further packages/gateway/src/pipeline.ts inspection covered recall-input validation: detailLimitValue must not be less than 1; at least one of nonblank query, id, or ids is required; scope is checked against allowed values including "all"; and numeric detailLimitValue is conditionally included in the normalized input.
• 🟡 (22:36) Recall processing includes collectCompletedRecall, input propagation through id: input.id, and comparison/bounds logic that rejects values such as right < 0.
• 🟡 (22:36) Responses lifecycle inspection covered optional onDoneOnlyItem, detection of response.output_item.done introducing untracked reasoning with error text Responses output_item.done introduced untracked reasoning for index ${outputIndex}, and rejection of non-response.output_item.added events after lifecycle.outputDone.
• 🟡 (22:36) Output-item validation checks isValidResponsesReasoningEncryptedContent(item), handles item.type === "function_call" with initialArguments, validates optional item.status, and rejects response.output_item.done when the item was undeclared or its type changed, including error text Responses output_item.done changed item type for index ${outputIndex}.
• 🟡 (22:36) Content-event validation requires parsed.content_index to be a safe integer, distinguishes content types including "refusal", throws invalid Responses content type for ${event} for unsupported types, and tracks authoritativeValueSeen, partFinalValue, and final-part completion state.
• 🟡 (22:36) Reasoning-summary validation uses lifecycle.reasoning.get(summaryIndex), compares summaryState.authoritativeValue with initialValue, reads parsed.part, and tracks both summaryState.partDone and summaryState.valueDone.