Distillation

Date: September 9, 2026

• 🟡 (09:08) User asked whether the Lore compatibility review was still running.
• 🟡 (09:08) Assistant corrected its prior status report: the Lore compatibility review had finished, found Lore 0.40 incompatible with V2, and the V2 port had not yet started.
• 🔴 (09:24) User requested making Lore compatible “both ways,” covering both the legacy interface and V2.
• 🟡 (09:24) Assistant proposed adding a separate V2 server entrypoint while preserving Lore’s strict legacy root export, first identifying shared routing and gateway-lifecycle seams, then writing fail-first adapter tests before changing runtime code. The frozen pilot target and production would remain untouched.
• 🟡 (09:24) Assistant established this ordered implementation plan: 1. Inspect Lore guidance and exact legacy, routing, gateway lifecycle, and V2 plugin contracts; 2. Add fail-first tests for dual entrypoints, V2 routing, lifecycle, and multi-location behavior; 3. Implement shared request routing and a V2 Lore server adapter while preserving legacy behavior; 4. Run package tests, typecheck, lint, format check, and repeated stability validation; 5. Package and activate Lore only in a separate disposable V2 environment; 6. Obtain independent correctness and security reviews for the frozen Lore port.
• 🔴 (09:24) User-provided /home/byk/Code/opencode-lore/AGENTS.md defines Lore as a three-tier memory architecture for AI coding agents, running on Node.js >= 22.5 and TypeScript with pnpm workspaces, using SQLite in WAL mode with FTS5 at ~/.local/share/lore/lore.db.
• 🔴 (09:24) User-provided monorepo structure identifies 4 packages: @loreai/core at packages/core/, @loreai/gateway at packages/gateway/, @loreai/opencode at packages/opencode/, and @loreai/pi at packages/pi/. @loreai/core is shared by gateway, OpenCode, and Pi; gateway bundles core into one CJS file via esbuild, while the OpenCode package ships raw TypeScript.
• 🔴 (09:24) User-provided legacy OpenCode contract says @loreai/opencode hooks into OpenCode through @opencode-ai/plugin.
• 🔴 (09:24) User-provided Lore architecture has: Tier 1 temporal storage in packages/core/src/temporal.ts; Tier 2 distillation in packages/core/src/distillation.ts, with segments capped at 16K tokens and meta-distillation after the gen-0 count exceeds 20; and Tier 3 gradient context management in packages/core/src/gradient.ts, using Layer 0 full passthrough, Layer 1 distilled prefix plus compressed raw content, Layer 2 aggressive tool-output stripping, and Layer 3 emergency compression.
• 🔴 (09:24) User-provided LTM schema in packages/core/src/ltm.ts uses categories decision, pattern, preference, architecture, and gotcha; fields are id (UUIDv7), project_id, category, title, content (maximum 1200 characters), confidence (0.0–1.0), and cross_project.
• 🔴 (09:24) User-provided LTM creation paths are: 1. LLM Curator in packages/core/src/curator.ts; 2. regex-based Pattern Extraction in packages/core/src/pattern-extract.ts; 3. File Import in packages/core/src/agents-file.ts; 4. consolidate() in curator.ts when entry count exceeds maxEntries of 25.
• 🔴 (09:24) User-provided .lore.md behavior uses <!-- lore:UUID --> markers; entries are sorted alphabetically by title within category; exportLoreFile() skips writes when the content hash is unchanged; importLoreFile() updates changed known UUIDs and creates unknown UUIDs; shouldImportLoreFile() performs an mtime check followed by content-hash comparison.
• 🔴 (09:24) User stated tests use a temporary SQLite database through packages/core/test/setup.ts and never the production DB.
• 🔴 (09:24) User stated release policy: never manually bump versions or edit CHANGELOG.md; Sentry Craft handles both automatically through GitHub Actions.
• 🔴 (09:24) User-provided release commands are gh workflow run release.yml -f version=auto for conventional-commit-derived semver or gh workflow run release.yml -f version=0.23.0 for an explicit version.
• 🔴 (09:24) User-provided release workflow order is: 1. scripts/bump-version.sh updates all package.json versions; 2. generate the changelog from conventional commits; 3. create and push release/X.Y.Z; 4. CI tests and builds npm tarballs, standalone binaries, and delta patches; 5. Craft opens a publish issue and the Publish workflow runs once labeled accepted; 6. publish npm packages through OIDC trusted publishing and create the GitHub Release with binaries and patches.
• 🔴 (09:25) User-provided review discipline requires every adversarial-review defect to receive a deterministic regression test in the same PR that fails on the base branch, passes on the fix, and exercises the real precondition; a guard test must fail if the guard is deleted.
• 🔴 (09:25) User stated the TDD rule: “Never trust the fix without seeing it fail.”
• 🔴 (09:25) User-provided adversarial state setup requires state to exist before the operation that must handle it and explicitly covers delete-then-recreate across lifecycle boundaries and modify-while-off scenarios.
• 🔴 (09:25) User-provided fan-out registry batteries are: SYNCED_TABLES → packages/core/test/sync-registry-contract.test.ts; MIGRATIONS → the db.test.ts schema-version assertion plus migration-specific tests; AGENTS → agents.test.ts, requiring name, displayName, binary, and detect(), with binary as a constant placeholder string.
• 🔴 (09:25) User-provided recurring-bug guidance identifies skip/early-return branches as the highest-risk surface; every skip branch needs a test that makes it wrongly skip something and proves that it does not.
• 🔴 (09:25) User-provided test guidance says property-based tests over faithful mocks exposed 4 sequence-dependent engine bugs missed by example tests across enable/disable/push/pull boundaries.
• 🔴 (09:25) User-provided implementation guidance says shared memoized arrays such as the syncedColumns PRAGMA cache should be frozen so accidental mutation raises a TypeError in strict mode rather than silently corrupting cache state.
• 🔴 (09:25) User-provided testing gotcha says db().query monkeypatches are shadowed by the tracing Proxy; SQL-counting tests must use log.registerSink({ withDbSpan }).
• 🔴 (09:25) User-provided review workflow requires two separate review passes: 1. adversarial/correctness review covering enumerated break states, 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.
• 🔴 (09:25) User-provided review requirements mandate pnpm test, pnpm run typecheck, pnpm run lint, and pnpm run format:check, checking exit codes; property tests must run ×10; the working tree must finish unmodified and hash-verified; findings require per-point PASS / FAIL / CONCERN / MUST-FIX verdicts with file:line evidence and an overall MERGE / DO-NOT-MERGE verdict.
• 🔴 (09:25) User-provided policy requires adversarial review for every non-trivial PR and for any change touching correctness-critical sync engine, hashing, lifecycle, or migration paths; security review is required according to risk profile.
• 🔴 (09:25) User-provided repository /home/byk/Code/opencode-lore contains both .jj/ and .git/, making it a colocated Jujutsu repository where mutations must use jj, not git.
• 🔴 (09:25) User-provided Jujutsu rules prohibit interactive flags such as -i and --interactive, require -m "msg" for commit descriptions, require verification with jj st and jj log after mutations, prefer stable change IDs over commit IDs, and prohibit rebasing or describing immutable commits.
• 🔴 (09:25) User stated jj never fails on conflict: conflicts are recorded in the resulting commit and must be detected with jj st and resolved by manually editing files, not by using interactive jj resolve.
• 🔴 (09:25) User-provided recovery guidance says jj undo reverses the last operation, jj op log shows operation history, and jj op restore <op-id> rewinds repository state.
• 🔴 (09:25) User-provided current repository state showed modified .lore.md; working-copy change ID ptswrqrr, commit 79e212d6, with no description; parent change ID uutomtup, commit 42911412, on main, described as fix(gateway): preserve large recall continuations (#1730).