Distillation

Date: Sep 16, 2026

• 🔴 (13:45) User stated the immutable projection review target is /home/byk/Code/opencode-lore-responses-projection-fix, with base commit 2cbf40060c67df229731cf1b9e34d5bf22ec2145, candidate change ozrmvotwxzuykyvutstpwpzukpptktxv, and head commit 583020fad43e1481470aac2588251b8636d16251.
• 🔴 (13:45) User stated the expected SHA-256 of plain jj diff --from main@origin --to ozrmvotw is 83d7c15b3b0c7dd4b58df93af5f20b0e18de6ad99e939d02aa75c0d5e7dea30d.
• 🔴 (13:45) User stated exactly two files changed: packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts.
• 🔴 [requested-review] (13:45) User requested an independent, read-only, adversarial correctness review of the immutable projection candidate.
• 🔴 [enforced-read-only-review] (13:45) User prohibited editing files, formatting, or mutating VCS during the review.
• 🟡 (13:45) User requested reading AGENTS.md, quality/REVIEW.md, current scripts, every changed line, relevant callers, and relevant tests.
• 🟡 (13:45) User requested verification of identity, status, conflicts, scope, and hash both at the start and end of the review.
• 🔴 (13:45) User specified the core invariant for the stable source-index → public-slot map: every directly emitted and deferred principal output-index-bearing frame must be remapped through the same current terminal-visible map before sequencing/enqueue.
• 🔴 (13:45) User specified that an assignment must be recorded only after successful enqueue.
• 🔴 (13:45) User specified that any later visible or private item changing a recorded assignment must fail closed before exposure.
• 🔴 (13:45) User specified that sparse higher-index hidden recall must remain allowed.
• 🔴 (13:45) User specified that lower-index changes must fail with one sanitized output:[] failure.
• 🔴 (13:45) User specified that retries must reset assignments.
• 🔴 (13:45) User specified that continuations must be transactionally remapped separately and terminal output must remain consistent.
• 🟡 (13:45) User requested adversarial checks covering malformed frames, ordinary tools, unresolved candidates, terminal-discovered recall, backpressure, retries, cancellation, recovery, limits, identity collisions, and complexity.
• 🟡 (13:45) User requested confirmation that failing-first evidence and two guard-removal mutation evidence are discriminating.
• 🟡 (13:45) User allowed focused tests only if needed and stated exhaustive validation runs separately.
• 🟡 (13:45) User requested findings classified as PASS, CONCERN, or MUST-FIX, supported by exact current file:line evidence and residual risks.
• 🔴 (13:45) User required the review response to end exactly with either MERGE or DO-NOT-MERGE.
• 🔴 [enforced-workflow] (13:45) User instructed that if model recall warns, the assistant must keep the session and run local lore recall '<specific query>' rather than returning a warning or empty result.