Distillation

Date: September 16, 2026

• 🟡 (22:35) Continued test-diff inspection covered strict final-content validation across stream kinds, including malformed reasoning-summary completion cases such as "done summary extra fields", test text "tracked summary", generated slugs via name.replaceAll(" ", "_"), IDs prefixed with fc_strict_${streamKind}_${slug}, and bounded content where index === 16 inserts a marker.
• 🟡 (22:35) Strict final-content tests configured maxRecallExecutions: 3, tracked callback counts with { recalls: 0, followUps: 0 }, initiated recallCall(0, { query: "first recall" }), drained the client via await drain(client), and asserted JSON.stringify(completions) did not contain the held marker.
• 🟡 (22:35) Additional fixture inspection showed URL citation annotations using { type: "url_citation", url: "https://example.test" } and an onRecall callback returning { anchorText: "", resultText: "" }.
• 🔴 (22:36) User stated private source coverage is never emitted to the client; the corresponding transaction field is documented as /** Private source coverage; never emitted to the client. */.
• 🟡 (22:36) Continued packages/gateway/src/pipeline.ts inspection covered recall continuation failure handling via new RecallContinuationFailure("depth_exhausted"), assignment of currentModifiedReq = followUp, held-back envelope forwarding through await safeEnqueue(encoder.encode(heldBack)), normal no-recall flow, abort handling through isAbort, and demand resumption via resumeDemand?.().
• 🟡 (22:36) Inspection covered the streaming function’s transaction and recall options, including onTransactionReady, maxStreamBytes, attempt metadata, recall query, accumulated GatewayResponse state in acc, private source coverage, and finalRecallRound.
• 🟡 (22:36) Validation/state internals inspected included responseLifecycleFor, lifecycle flags such as authoritativeValueSeen and outputDone, lifecycle maps initialized with new Map(), partValue, exact part kinds "summary_text" | "reasoning_text", strict key-count checks requiring keys.length === 2, finalized message content through finalizedMessageContent, and text-part tracking via Map<number, TextPartLifecycle> and emptyTextPartLifecycle(part.type).
• 🟡 (22:36) Transaction rollback inspection showed transactionRollbacks: Array<() => void>, restoration of state.rawItems = new Map(transactionBaseline.rawItems), and maxTransactionalBytes derived from maxRetainedStateBytes.
• 🟡 (22:36) Recall argument validation inspected handling for fields including "id", normalization of record.query === null ? undefined : record.query, and batch-ID enforcement against MAX_RECALL_BATCH_IDS.