Distillation

Date: Sep 16, 2026

• 🔴 [requested-validation] (22:40) User stated the resumed output was still warning-only and therefore not a result; required completion of the original immutable-projection exhaustive validation with substantive PASS/FAIL, exact counts, exit codes, durations, hash verification, and isolation evidence.
• 🔴 (22:40) User requires validation results to be “Never warning-only/empty.”
• 🔴 [enforced-workflow] (22:40) User directed continuation in the same session while preserving all completed long-running test and shard output.
• 🔴 [enforced-workflow] (22:40) User required reporting an already completed aggregate run rather than rerunning it; if interrupted or inconclusive, only missing deterministic shards may be run, not completed shards.
• 🔴 (22:40) User directed immediate context recovery through the dedicated CLI, exemplified by lore recall --project /home/byk/Code/opencode-lore --scope project --limit 30 projection exhaustive f3023670 b7df7356, or local /ui/search; broken recall must not be used.
• 🔴 (22:40) User prohibited edits, VCS operations, server operations, and production-database operations during this validation.
• 🟡 (22:43) Recovered immutable candidate context: repository /home/byk/Code/opencode-lore-responses-projection-security; stable change lnvrxqoqsqut; commit f30236708bc9; literal base/main 2cbf40060c67; expected cumulative plain-diff SHA-256 b7df735637f9d033c895867ebe157cb05f8d390bea78842d58d14fd8091fd3e1; expected clean empty child kwmswwmt.
• 🟡 (22:43) Recovered candidate graph: lnvrxqoqsqutpvpx / f30236708bc9 (fix(responses): complete hidden-output state) parent a3fa555bdcab; zlsmzkntqzzxsqvy / a3fa555bdcab (fix(responses): harden hidden-output projection) parent 583020fad43e; ozrmvotwxzuykyvu / 583020fad43e (fix(responses): stabilize sparse principal projection) parent ab979df5cddf; unznwpylspzqykmn / ab979df5cddf (fix(responses): project hidden output consistently) parent base 2cbf40060c67; all shown with conflict=false.
• 🟡 (22:43) Recovered candidate diff changes exactly 2 files: packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts; diffstat was 1,100 insertions and 96 deletions across those files.
• 🟡 (22:43) Recovered status showed clean working copy kwmswwmt / 2ad3e064 as an empty child of lnvrxqoq / f3023670; unrelated conflicted bookmark warning remained for fix/responses-private-references.
• 🔴 (22:43) User asserted Jujutsu rebase never fails on conflict; it records the conflict in the resulting commit, after which jj st must be used to identify it and files must be resolved later.
• 🔴 (22:43) User established the mismatch-cleanup invariant in packages/gateway/src/pipeline.ts: cleanup is best-effort and must never delay the caller.
• 🔴 (22:43) User established that provider data represented by a hidden codex.rate_limits event was never delivered publicly and was never emitted to the client, although after recall detection it could still reach onComplete following a later failure.
• 🟡 (22:43) Recovered prior focused validation evidence: the five-case projection invariant battery passed 10 consecutive runs, each with 1 test file passed, 5 tests passed, and 208 skipped out of 213, totaling 50/50 repeated invariant cases; the formatted projection tree also reported 218/218 adjacent tests, formatting, workspace typecheck, warning-only lint, and production bundle completion.
• 🟡 (22:45) A recall invocation exceeded its 180,000 ms timeout after returning results; the output nevertheless recovered candidate identity, graph, status, changed files, expected hash, prior validation evidence, and the unrelated conflicted-bookmark warning.