Distillation

Date: September 16, 2026

• 🔴 (21:59) User/project invariant: “Always accumulate into the internal state for postResponse.” In packages/gateway/src/pipeline.ts:10400-10401, this is implemented with applyResponsesEvent(state, event, parsed).
• 🔴 (21:59) User specified that the gateway never forwards response-side item_reference lifecycle events; the regression test is named test("never forwards response-side item_reference lifecycle events", async () => {.
• 🟡 (21:59) Retained-context recall found 26 disableRecall matches: packages/gateway/test/recall.test.ts lines 825, 853, 865, 932, 1011, 1028, 1067, 1092, 1113, 1162, 1195, 1215, 1229, 1249; packages/gateway/src/recall.ts:1324; packages/gateway/src/translate/types.ts:234; packages/gateway/src/translate/openai.ts:734; packages/gateway/src/translate/openai-responses.ts:946,1037,1124; packages/gateway/src/translate/gemini.ts:369,394,396; and packages/gateway/src/translate/anthropic.ts:495,527,530.
• 🟡 (21:59) Retained-context recall established that final-round recall denial already exists on current main: shared follow-up requests set disableRecall, and all four protocol translators enforce it.
• 🔴 (21:59) User-supplied changed-code evidence showed retained continuation state is accumulated before checking retainedStateBytes > maxRetainedStateBytes; the accepted event remains authoritative even when it trips the limit.
• 🔴 (21:59) User-supplied changed-code evidence showed principal resource-limit handling uses the fixed failure category principal_resource_limit, including expected log text openai-responses recall-aware stream failed category=principal_resource_limit.
• 🟡 (21:59) Retained context showed packages/gateway/src/pipeline.ts imports cloneResponsesAccState and validateResponsesSourceSequence, introduces rollbackPendingPrincipalTerminal, snapshots terminal state through terminalRecallSnapshot, restores recallDetected, unresolved tool-byte state, and lifecycle state, and tracks provider failures through providerFailureTerminal and providerFailureSeen.
• 🟡 (21:59) Retained context identified the chosen recovery design in packages/gateway/src/recall.ts: coupled runRecallRecovery(), which builds the recovery clone and dispatches through the same strict JSON or accumulated-SSE executors as normal follow-ups. A direct recovery-forwarding prototype was rejected because it accepted mislabeled JSON when Codex requested SSE, weakening the stream/consumer invariant.
• 🟡 (21:59) Recall output showed 15 of 60 results before truncation; full output was saved to /home/byk/.local/share/opencode/tool-output/tool_0ac341f9b001lrGOa3x0FHT0qa.
• 🟡 (21:59) The recall shell command exceeded its 120000 ms timeout and was terminated.
• 🟡 (21:59) Recall reported recurring tool failures: edit → other:could-not-find-oldstring 113 times across 45 sessions; plan_exit → other:the-user-dismissed-this 48 times across 39 sessions; read → not_found 40 times across 34 sessions; webfetch → other:statuscode-non-xx-status 69 times across 22 sessions; and bash → aborted 20 times across 16 sessions.