Distillation

Date: Sep 16, 2026

• 🟡 (13:42) The five-case projection invariant battery passed 10 consecutive runs: each run reported 1 test file passed, 5 tests passed, and 208 skipped out of 213; aggregate result was 50/50 repeated invariant cases.
• 🟡 (13:42) Assistant reported the formatted projection tree fully green: 218/218 adjacent tests, 50/50 repeated invariant cases, formatting, workspace typecheck, warning-only lint, and the production bundle.
• 🔴 (13:42) User asserted that JJ never fails on conflict: rebase, new, or squash records the conflict in the resulting commit; afterward run jj st, resolve files manually, and do not use interactive jj resolve.
• 🔴 (13:42) User-provided JJ workflow rules stated that repository mutations must use jj, never interactive flags, always provide -m "msg" when committing/describing, verify mutations with jj st and jj log, prefer stable change IDs over commit IDs, and avoid mutating immutable commits.
• 🔴 (13:42) User-provided JJ conventions stated that the working copy is commit @, bookmarks do not auto-advance, jj commit leaves an empty @ with content in @-, and jj new creates a new empty change rather than committing existing work.
• 🟡 (13:43) Exact correction audit found only packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts changed. The correction added one production mechanism and four targeted assertion additions; it did not alter hidden-index or continuation policy.
• 🟡 (13:43) Production correction behavior: principal frames now use a stored dense public output-index map and reject subsequent mapping changes.
• 🟡 (13:43) The JJ correction was committed as stable change ID ozrmvotw, commit 583020fad43e1481470aac2588251b8636d16251, description fix(responses): stabilize sparse principal projection. A new empty working-copy child qwnymkxp / 9285e4185a10a4e4734964fed7e342ada4fda044 was created, and the working copy was clean.
• 🟡 (13:43) Bookmark fix/responses-hidden-output was moved to ozrmvotw / 583020fa; no other bookmark was moved. JJ continued warning that fix/responses-private-references had conflicts.
• 🟡 (13:43) Verified candidate lineage: ozrmvotw / 583020fa (fix(responses): stabilize sparse principal projection) is a child of unznwpyl / ab979df5cddfec3952680e423e39564664e881fe (fix(responses): project hidden output consistently), over main at pxrvwsvv / 2cbf40060c67df229731cf1b9e34d5bf22ec2145.
• 🟡 (13:44) Frozen immutable projection candidate was ozrmvotw / 583020fa over base 2cbf4006. Scope was exactly 2 files with 654 insertions and 62 deletions: packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts.
• 🟡 (13:44) Frozen candidate patch SHA-256 was 83d7c15b3b0c7dd4b58df93af5f20b0e18de6ad99e939d02aa75c0d5e7dea30d; packages/gateway/dist/index.cjs bundle SHA-256 was 37e33a5aeb66b81d1c8b307ed9f511aa20b56d095f8e31cf8f037eb993bd20a5.
• 🟡 (13:44) Validation plan status: exact public Responses projection fix and mutation proof completed; focused/static/bundle/exhaustive validation in progress; independent correctness/security reviews pending; provider-candidate security review/publication gate pending; accumulation, Codex, recovery, and private-reference lanes pending.
• 🟡 (13:44) Assistant launched exact-head exhaustive validation as background task ses_f5589e73fffez1izPtpH4xa63K.
• 🟡 (13:45) Assistant launched independent correctness review as background task ses_f558983d3ffeS1F5MQKcmkYkt8.
• 🟡 (13:45) Assistant launched independent security review as background task ses_f558920f3ffelTQFnAsKsJc7Jn.
• 🟡 (13:45) The three background lanes were instructed to review the same immutable head, preserve their sessions, and use lore recall if model-recall warnings appeared.
• 🟡 (13:45) Assistant resumed the non-overlapping accumulation repair in its separate workspace, planning to use lore recall to recover the exact blocker state, inspect the frozen candidate, and add terminal-only reasoning and omitted-item regressions before changing production code.