Distillation

Date: Sep 16, 2026

• 🔴 (20:26) User stated retry-budget invariant: a retry must “never be given MORE room — retrying would either shrink the budget or waste”; retries must not increase the available room.
• 🟡 (20:25) packages/gateway/test/codex-usage-metadata.test.ts defines request-wide Codex quota metadata caps of MAX_CODEX_RATE_LIMIT_EVENTS = 64 and MAX_CODEX_RATE_LIMIT_BYTES = 16 * 1024.
• 🟡 (20:25) packages/gateway/test/codex-usage-metadata.test.ts verifies buffered rebuilding preserves every ordered codex.rate_limits bucket before response.completed, including on ResponsesTerminalError from an incomplete terminal.
• 🟡 (20:25) Codex quota projection tests verify a private allowlist strips unrelated fields and events—including authorization, debug, codex.private_metadata, unknown nested rate-limit buckets, and private credit fields—from both buffered and passthrough output.
• 🟡 (20:25) Codex quota metadata is response-scoped: tests verify it is not retained across responses or after a terminal event, while true streaming forwards accepted quota events without duplication.
• 🟡 (20:25) Adjacent identical quota updates are deduplicated before request-wide caps are applied; retained events preserve prefix order, stop at at most 64 events, and remain within 16 KiB of canonical JSON bytes.
• 🟡 (20:25) Property tests in packages/gateway/test/codex-usage-metadata.test.ts run seeds 0 through 9, each with numRuns: 25, generating 1–20 ordered quota updates; they verify exact update order and unchanged consumption metadata, including inputTokens = 600000.
• 🟡 (20:26) Search results in packages/gateway/test/openai-responses-recall-aware-stream.test.ts identify coverage for: retrying a principal read failure before any client event; continuing after a post-text read failure without replaying the request; transactionally failing final continuations without retry; avoiding double-charging transactional output during continuation retry; restoring every continuation retry budget and identity baseline; and suppressing retry when cancellation races a dropped continuation.
• 🟡 (20:26) Continuation-stream tests exercise deferred spool limits, sparse unresolved function-call state, transactional output accounting, and maxDeferredBytes configurations including 2 * 1024 * 1024 and 16 * 1024; failures are collected through setRecallContinuationFailureHook() using RecallContinuationFailureCategory.