Distillation

Date: Sep 16, 2026

• 🔴 [enforced-workflow] (22:43) User-provided jj-guide states that /home/byk/Code/opencode-lore-provider-error is a colocated Jujutsu repository because both .jj/ and .git/ exist; mutations must use jj, while Git is limited to read-only operations or unsupported tasks such as git submodule.
• 🔴 (22:43) User stated jj never fails on conflict: rebase, new, and squash record conflicts in the resulting commit, after which jj st must be run and conflicted files resolved manually; jj resolve is prohibited because it is interactive.
• 🔴 [enforced-workflow] (22:43) User-provided jj rules prohibit interactive flags such as -i and --interactive, require -m "msg" when describing or committing, require verifying mutations with jj st and jj log, prefer stable letter-based change IDs over rewritten hexadecimal commit IDs, and prohibit rebasing or describing immutable commits.
• 🔴 [enforced-workflow] (22:43) User-provided jj guidance states bookmarks do not auto-advance; after jj commit, content is in @- and the bookmark must be moved with jj bookmark set <name> -r @-; @ is then a new empty working-copy commit.
• 🔴 (22:44) User stated the Lore project runtime is Node.js >= 22.5, its language is TypeScript in a pnpm workspaces monorepo, and its database is SQLite using WAL mode and FTS5 at ~/.local/share/lore/lore.db.
• 🔴 (22:44) User stated Lore has four packages: @loreai/core at packages/core/, @loreai/gateway at packages/gateway/, @loreai/opencode at packages/opencode/, and @loreai/pi at packages/pi/.
• 🔴 (22:44) User stated tests use a temporary SQLite database through packages/core/test/setup.ts, never the production DB.
• 🔴 [enforced-release-workflow] (22:44) User stated releases use Sentry Craft through GitHub Actions and versions or CHANGELOG.md must never be manually bumped or edited; release commands are gh workflow run release.yml -f version=auto or an explicit version such as gh workflow run release.yml -f version=0.23.0.
• 🔴 [requested-tests] (22:45) User-provided review discipline requires each regression test to fail on the base branch, pass on the fix, and fail when its target guard is deleted; user stated: “Never trust the fix without seeing it fail.”
• 🔴 [requested-tests] (22:45) User-provided review workflow calls for adversarial-order state setup, delete-then-recreate lifecycle sequences, fan-out registry coverage, recurring bug-class batteries, apply-then-revert mutants, and property-test stability across ×10 runs.
• 🔴 [enforced-review-workflow] (22:45) User stated every non-trivial PR requires an adversarial correctness review before merge, and high-risk changes such as migrations require adversarial review regardless of size; reviews must provide structured evidence rather than an unstructured “LGTM.”
• 🔴 (22:47) User identified three process-global maps as never evicted under candidate bug CB-003: sessionStates in packages/core/src/gradient.ts:304, p-limit instances in packages/core/src/session-limiter.ts:17, and globalHeaderValues in packages/gateway/src/session.ts:436.
• 🔴 (22:47) User-provided three-pass review framework maps requirements REQ-001 through REQ-014 and candidate bugs CB-001 through CB-012; its structural pass checks missing error handling, resource leaks, null/undefined hazards, async error propagation gaps, and unbounded growth without relying on requirement references.