Distillation

Date: Sep 16, 2026

• 🔴 (14:04) User stated the repository follows jj semantics: operations never fail on merge conflict; conflicts are recorded in the resulting commit and must be detected with jj st and resolved by editing files manually.
• 🔴 (14:04) User stated that in a repository containing .jj/, mutations must use jj, not git; even in a colocated .jj/ + .git/ repository, Git is limited to read-only operations or unsupported functions such as git submodule.
• 🔴 (14:04) User stated jj commands must never use interactive flags such as -i or --interactive, jj resolve, or jj diffedit, because TUI prompts hang in agent environments.
• 🔴 (14:04) User stated jj describe/commit operations must always receive -m "msg" to prevent an editor from opening, and mutations such as squash, abandon, rebase, restore, and commit must be verified afterward with jj st and jj log.
• 🔴 (14:04) User stated immutable commits such as tracked main must never be rebased or described directly; work should target the commit above them or use main@origin as --destination.
• 🟡 (14:04) Initial read-only identity verification in /home/byk/Code/opencode-lore-responses-accumulation found a clean working copy: @ is empty change lrqlyykxvwoqrxzowonmmytxulyqmqlu at commit d890b184d786a4348e30bcdac7412baa7ae01ae9, whose parent is candidate change tklkqxytmpkzzryqlolnpvxouropxznp at ce88c614c0ae55d229cb605aa7c7369d918d3650; candidate parent/base is pxrvwsvvkmpoxnsqmrkwrnlqvvkoltwz at 2cbf40060c67df229731cf1b9e34d5bf22ec2145. All three revisions reported conflict=false; @ reported empty=true, while candidate and base reported empty=false.
• 🟡 (14:04) Initial verification confirmed exactly three modified paths between base and candidate: packages/gateway/src/pipeline.ts, packages/gateway/src/stream/openai-responses.ts, and packages/gateway/test/openai-responses-recall-aware-stream.test.ts.
• 🟡 (14:04) Initial verification reproduced the expected plain-diff SHA-256 exactly: 02d06b2f84d7d2d8cfa5f22443384d12a2a9bc922ade879449de9b0b9d971d1c.
• 🟡 (14:04) Repository status warned that bookmark fix/responses-private-references has conflicts; the verified working-copy, candidate, and base revisions themselves reported no conflict.
• 🟡 (14:04) The first custom jj template attempt failed because change_id.hex() is invalid: Method 'hex' doesn't exist for type 'ChangeId'; a subsequent compatible query produced the full change IDs, commit IDs, parents, conflict flags, and empty flags.
• 🔴 (14:04) User stated every non-trivial PR requires an adversarial correctness review before merge under quality/REVIEW.md, including regression-test discipline, adversarial-order state setup, fan-out registry coverage, recurring bug-class batteries, and a two-reviewer rule.
• 🔴 (14:04) User stated regression tests must fail on the base branch and pass on the fix, and tests intended to protect a guard must fail when that guard is deleted.
• 🔴 (14:04) User stated property-test stability must be verified across exactly 10 runs (×10).
• 🔴 (14:04) User stated: “Never trust the fix without seeing it fail.”
• 🔴 (14:04) User stated tests use a temporary SQLite database through packages/core/test/setup.ts, never the production DB.
• 🔴 (14:04) User stated releases use Sentry Craft through GitHub Actions and versions or CHANGELOG.md must never be manually bumped or edited; Craft handles both automatically.
• 🟡 (14:04) Release workflow details: trigger with gh workflow run release.yml -f version=auto or an explicit version such as gh workflow run release.yml -f version=0.23.0; the workflow runs scripts/bump-version.sh, generates a changelog from conventional commits, creates and pushes release/X.Y.Z, runs CI to build npm tarballs, standalone binaries, and delta patches, then Craft opens a publish issue whose accepted label triggers npm OIDC publishing and a GitHub Release.
• 🟡 (14:05) Root package.json specifies pnpm@10.28.0, Volta Node 24.16.0, Volta pnpm 10.28.0, root tests via vitest run, pretest bundling via pnpm --filter @loreai/gateway run bundle, typechecking via pnpm -r run typecheck, linting via oxlint --type-aware, formatting via oxfmt, and mutation testing via stryker run.