Distillation

Date: Sep 16, 2026

• 🔴 (14:04) User stated jj never fails on merge conflict; conflicts are recorded in the resulting commit and must be detected with jj st and resolved manually rather than with interactive jj resolve.
• 🔴 (14:04) User’s jj workflow rules: use jj, not git, for mutations when .jj/ exists; never use interactive flags; always pass -m "msg" when describing/committing; verify mutations with jj st and jj log; prefer stable change IDs over rewritten hexadecimal commit IDs; never rebase or describe immutable commits; use jj undo or jj op restore <op-id> for recovery.
• 🟡 (14:04) Start-of-review verification found a clean working copy at empty commit lrqlyykxvwoqrxzowonmmytxulyqmqlu / d890b184d786a4348e30bcdac7412baa7ae01ae9, whose parent was candidate tklkqxytmpkzzryqlolnpvxouropxznp / ce88c614c0ae55d229cb605aa7c7369d918d3650; both commits reported conflict=false.
• 🟡 (14:04) Start-of-review verification confirmed base pxrvwsvvkmpoxnsqmrkwrnlqvvkoltwz at 2cbf40060c67df229731cf1b9e34d5bf22ec2145, candidate description fix(responses): complete lifecycle reconciliation, and exactly 3 modified files: 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) Start-of-review verification confirmed plain diff SHA-256 02d06b2f84d7d2d8cfa5f22443384d12a2a9bc922ade879449de9b0b9d971d1c.
• 🟡 (14:04) Repository status warned that bookmark fix/responses-private-references was conflicted, while the working-copy and candidate commits themselves were not conflicted.
• 🔴 (14:04) User stated tests use a temporary SQLite database through packages/core/test/setup.ts, never the production DB.
• 🔴 (14:04) User directed never to manually bump versions or edit CHANGELOG.md; Sentry Craft handles both automatically through the release workflow.
• 🔴 (14:04) User’s regression-test discipline requires a bug-fix test to fail on the base branch and pass on the fix; tests intended to exercise a guard must fail when that guard is deleted. User stated: “Never trust the fix without seeing it fail.”
• 🔴 (14:04) User’s review workflow requires adversarial correctness review for every non-trivial PR and explicitly includes skip/early-return branches, lifecycle sequences, fan-out registry coverage, apply-then-revert mutants, enumerated cases, and property-test stability across 10 runs.