Distillation

Date: Sep 16, 2026

• 🔴 (13:45) User stated that jj never fails on conflict: merge conflicts are recorded in the resulting commit and must be detected with jj st, then resolved by manually editing conflict markers rather than using interactive jj resolve.
• 🔴 (13:45) User’s Jujutsu workflow requires using jj, not git, for mutations when .jj/ exists; forbids interactive flags; requires -m "msg" for commit descriptions; requires verifying mutations with jj st and jj log; prefers stable letter-based change IDs over hexadecimal commit IDs; and prohibits rebasing or describing immutable commits.
• 🟡 (13:45) Initial repository verification found a clean, empty working-copy commit qwnymkxpumsyysknopxqwwyypmzzywry / 9285e4185a10a4e4734964fed7e342ada4fda044, whose parent is candidate ozrmvotwxzuykyvutstpwpzukpptktxv / 583020fad43e1481470aac2588251b8636d16251.
• 🟡 (13:45) Candidate range contains two non-conflicted commits in order: unznwpylspzqykmnpxwnnswmnzpspxzq / ab979df5cddfec3952680e423e39564664e881fe (fix(responses): project hidden output consistently) followed by ozrmvotwxzuykyvutstpwpzukpptktxv / 583020fad43e1481470aac2588251b8636d16251 (fix(responses): stabilize sparse principal projection).
• 🟡 (13:45) Repository status warned that bookmark fix/responses-private-references has conflicts, while the candidate range itself reported no conflicts.
• 🔴 [enforced-test-isolation] (13:46) User stated tests use a temporary SQLite database through packages/core/test/setup.ts, never the production DB.
• 🔴 [enforced-release-workflow] (13:46) User stated versions and CHANGELOG.md must never be bumped or edited manually; Sentry Craft handles both automatically through GitHub Actions.
• 🔴 [enforced-tdd] (13:46) User stated, “Never trust the fix without seeing it fail”: each bug-fix regression test must fail on the base branch and pass on the fix.
• 🔴 [enforced-mutation-testing] (13:46) User’s review discipline requires any test claimed to cover a guard to fail when that guard is deleted.
• 🟡 (13:46) quality/REVIEW.md review workflow calls for enumerated adversarial cases, apply-then-revert mutants, property-test stability across 10 runs, exact evidence, and a structured overall MERGE / DO-NOT-MERGE conclusion rather than an unstructured “LGTM.”
• 🟡 (13:46) Project runtime/toolchain configuration: root package.json uses pnpm@10.28.0; Volta pins Node 24.16.0 and pnpm 10.28.0; AGENTS.md states Node.js >=22.5; packages/gateway/package.json declares Node >=22.15.
• 🟡 (13:46) Root verification scripts are pnpm test (vitest run, preceded by pnpm --filter @loreai/gateway run bundle), pnpm run typecheck, pnpm run lint (oxlint --type-aware), pnpm run format:check (oxfmt --check), pnpm run build, and pnpm run mutation (stryker run, preceded by gateway bundling).
• 🟡 (13:46) Gateway package metadata: @loreai/gateway version 0.40.0; build scripts include tsx script/build.ts, tsx script/bundle.ts, tsx script/build.ts --binary, and tsx script/build-binary-sea.ts; runtime entry is tsx src/index.ts.