Distillation

Date: September 16, 2026

• 🔴 (23:20) User’s regression-test discipline requires every bug fix to have a test that fails on the base branch, passes with the fix, and fails again when the relevant guard is deleted; “Never trust the fix without seeing it fail.”
• 🔴 (23:20) User’s test policy requires adversarial lifecycle coverage, including skip/early-return branches, lifecycle sequences, fan-out behavior, and delete-then-recreate sequences across lifecycle boundaries.
• 🔴 (23:20) User’s review workflow requires enumerated cases, apply-then-revert mutants, property-test stability across 10 runs, structured evidence, and an overall MERGE / DO-NOT-MERGE conclusion rather than an unstructured “LGTM.”
• 🔴 (23:20) User stated tests must use the temporary SQLite database configured through packages/core/test/setup.ts, never the production database.
• 🔴 (23:20) User stated releases use Sentry Craft through GitHub Actions; versions and CHANGELOG.md must never be manually updated because Craft handles both automatically.
• 🟡 (23:20) Project package layout: @loreai/core at packages/core/ is the shared memory engine; @loreai/gateway at packages/gateway/ is the transparent LLM proxy and lore CLI; @loreai/opencode at packages/opencode/ is the OpenCode adapter using @opencode-ai/plugin; @loreai/pi at packages/pi/ is the Pi coding-agent extension adapter.
• 🟡 (23:20) Gateway binary flow is packages/gateway/src/cli/bin.ts → packages/gateway/src/cli/main.ts via _cli().
• 🟡 (23:20) Key ltm.ts functions include create() / update() / remove() for CRUD with a dedup guard, forSession() for relevance-ranked budget-capped system-prompt entries, and search() / searchScored() for FTS5 BM25 search with LIKE fallback.
• 🟡 (23:20) exportToFile() writes the lore pointer section between markers, while splitFile() preserves content outside those markers.
• 🟡 (23:20) Build details: packages/gateway/script/build.ts produces the gateway CJS bundle, script/bundle.ts creates the standalone binary, and packages/core/script/build.ts produces Node.js-compatible CJS output.
• 🟡 (23:20) Initial repository inspection found working-copy change zkttmwun / commit 05d99983 titled fix(responses): close reference lifecycle gaps, modifying packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts; its parent was wywumkpt / 8063355c, titled fix(responses): keep item references private.
• 🟡 (23:20) jj status warned that bookmark fix/responses-private-references had conflicts, while the inspected working copy itself was not reported as conflicted.
• 🟡 (23:23) Exact revision inspection identified candidate zkttmwuntxzm / 05d9998321f5fcd782163bb35c25cf5470de13e9 as nonempty and conflict=false, with parent 8063355cb32832bd8fac492bcbba7da22ae1976c.
• 🟡 (23:23) Candidate parent was change wywumkptssoy / commit 8063355cb32832bd8fac492bcbba7da22ae1976c, nonempty and conflict=false, with parent 2cbf40060c67df229731cf1b9e34d5bf22ec2145.
• 🟡 (23:23) Earlier ancestry shown was pxrvwsvvkmpo / 2cbf40060c67df229731cf1b9e34d5bf22ec2145 titled feat(cch): add seeds for Claude Code up to 2.1.272 (#1780), followed by xpzmsyowwmzs / e977b4b1da8f8197c3238466d41de0bccd8eb054 titled feat(semantic-lint): lint small PRs holistically (#1778); both were nonempty and conflict=false.
• 🔴 [requested-validation] (23:28) User granted one same-session retry because the prior warning-only result was invalid and required completion of the assigned read-only validation with a substantive PASS/FAIL result.
• 🔴 [enforced-command-order] (23:28) User required first running the local CLI—not model recall—with the exact command lore recall --project /home/byk/Code/opencode-lore --scope project --limit 30 reference v2 item_reference validation exact tree, then directly inspecting /home/byk/Code/opencode-lore-responses-reference-v2.
• 🔴 (23:28) User required the validation report to include, at minimum, the exact candidate, head, parent, path scope, diff hash, repository status, every completed command and result, and the exact blocker for every command not run.
• 🔴 (23:28) User required continuing from filesystem evidence even if Lore recall fails; the response must never be warning-only or empty.
• 🔴 [enforced-read-only-workflow] (23:28) User reiterated that the retry must make no edits, install no dependencies, perform no VCS mutations, start/use no server, and access no production database.