Distillation

Date: Sep 16, 2026

• 🔴 (13:23) User’s Jujutsu workflow states that jj never fails on conflict; rebase/new/squash records conflicts in the resulting commit, after which jj st must be checked and files resolved manually rather than with interactive jj resolve.
• 🔴 (13:23) User requires jj rather than git for mutations when .jj/ exists; /home/byk/Code/opencode-lore-embedding-runtime is a colocated repository containing both .jj/ and .git/.
• 🔴 (13:23) User’s Jujutsu safety rules: never use interactive flags; always pass -m "msg" when describing/committing; verify mutations with jj st and jj log; prefer stable letter-based change IDs over hexadecimal commit IDs; never rebase or describe immutable commits; use jj undo or jj op restore <op-id> for recovery.
• 🔴 (13:23) User’s repository uses Node.js >=22.5 and TypeScript in a pnpm workspace monorepo; root package.json pins Volta Node 24.16.0, pnpm 10.28.0, and packageManager pnpm@10.28.0.
• 🔴 (13:23) User stated tests use a temporary SQLite database through packages/core/test/setup.ts, never the production database at ~/.local/share/lore/lore.db.
• 🔴 (13:23) User requires releases to be managed by Sentry Craft and GitHub Actions; never manually bump versions or edit CHANGELOG.md.
• 🔴 (13:23) User’s release workflow is: 1. scripts/bump-version.sh updates all package.json versions, 2. changelog is generated from conventional commits, 3. a release/X.Y.Z branch is created and pushed, 4. CI tests and builds npm tarballs, standalone binaries, and delta patches, 5. Craft opens a publish issue that triggers publishing when labeled accepted, 6. npm packages are published through OIDC and a GitHub Release receives binaries and patches.
• 🔴 (13:23) User’s release commands are gh workflow run release.yml -f version=auto for conventional-commit-determined semver or gh workflow run release.yml -f version=0.23.0 for an explicit version.
• 🔴 [enforced-tdd] (13:23) User requires failing-first regression discipline: every defect found in adversarial review must receive a deterministic test that fails on the base branch, passes on the fix, drives the real precondition, and fails if the tested guard is removed; never trust the fix without seeing it fail.
• 🔴 (13:23) User identifies skip/early-return branches as the highest-risk correctness surface, specifically guards involving NOT EXISTS, latest <> 'upsert', and content matching; each skip branch needs a test that makes it skip something it should not.
• 🔴 (13:23) User requires adversarial state setup in real lifecycle order, including state existing before the handling operation, delete-then-recreate across disabled/enabled boundaries, and content modification while synchronization is off.
• 🔴 (13:23) User’s review workflow requires two distinct passes: 1. adversarial/correctness review covering break-inducing state, enumerated cases, apply-then-revert mutants, property-test stability ×10, hash-equivalence proofs, frozen-array mutation safety, and stale-cache analysis; 2. security/pentest review covering injection, credential leaks, protocol attacks, and privilege escalation.
• 🔴 (13:23) User requires reviewers to run pnpm test, pnpm run typecheck, pnpm run lint, and pnpm run format:check; inspect exit codes because a blank tail can conceal lint/format failures; run property tests ×10; hash-verify that the working tree remains unmodified; and report per-point PASS/FAIL/CONCERN/MUST-FIX findings with file:line evidence plus an overall MERGE/DO-NOT-MERGE verdict.
• 🔴 (13:23) User’s fan-out registry test requirements are: SYNCED_TABLES must be covered by packages/core/test/sync-registry-contract.test.ts; MIGRATIONS must have a db.test.ts schema-version assertion using toBe(MIGRATIONS.length) plus migration-specific behavior tests; AGENTS must be covered by agents.test.ts, validating name, displayName, binary, detect(), and a constant placeholder string for binary.
• 🔴 (13:23) User’s documented testing seam states that db().query monkeypatches are shadowed by the tracing Proxy; SQL-statement-counting tests must use log.registerSink({ withDbSpan }).
• 🔴 (13:23) User prefers frozen shared arrays for memoized results such as the syncedColumns PRAGMA cache, so accidental mutation throws TypeError in strict mode rather than silently corrupting shared state.
• 🔴 (13:24) User’s root scripts include test: "vitest run" with pretest: "pnpm --filter @loreai/gateway run bundle", typecheck: "pnpm -r run typecheck", lint: "oxlint --type-aware", format:check: "oxfmt --check", build: "pnpm -r run build", and mutation: "stryker run".