Dashboard › opencode-lore › Distillation
d34d334c-ad75-43a9-8c50-f1449e653f20["lore_tm_v1_NPpcR55XlCzQIfftXs3AzbQ_ucLbWfWot7XlZrIZkO0","lore_tm_v1_7Ht11ebeCd9FAUwKMuvr3mfWrLred0f5q3B6vviXETc"]
Date: Sep 16, 2026
vitest.config.ts lines 10–15 define top-level resolve.alias: "@loreai/core" → path.resolve(__dirname, "packages/core/src") and "@loreai/gateway" → path.resolve(__dirname, "packages/gateway/src"). Root cause documented in lines 5–9: placing aliases under test.resolve.alias does not work because Vite’s resolver is top-level; the previous placement silently resolved to the stale dist build and masked real test failures.vitest.config.ts test inclusion order is: 1. packages/core/test/**/*.test.ts, 2. packages/core/eval/**/*.test.ts, 3. packages/gateway/test/**/*.test.ts, 4. packages/opencode/test/**/*.test.ts, 5. packages/pi/test/**/*.test.ts. Fast, pure eval-suite unit tests run from packages/core/eval/**/*.test.ts; heavy end-to-end *.eval.ts tests run under vitest.evals.config.ts.vitest.config.ts uses setupFiles: ["./packages/core/test/setup.ts"] for DB isolation, environment: "node", pool: "forks", testTimeout: 300_000 (5 minutes per test), and hookTimeout: 300_000.vitest.config.ts test-isolation environment variables are NODE_ENV: "test", SENTRY_ENABLED: "0", and LORE_DEBUG: "0".vitest.config.ts coverage uses provider "v8" and reporters ["text", "json", "html", "lcov"]; lcov supports Codecov CI upload, while text/json/html are retained for local inspection.vitest.config.ts coverage exclusions are: **/*.test.ts, **/test/setup.ts, **/test/helpers/**, **/script/**, **/dist/**, packages/website/**, packages/pi/**, **/eval/**, **/*.eval.ts, *.config.ts, and scripts/**. The documented rationale for excluding non-tested/non-source packages is that only core, gateway, and opencode have tests, so website and pi should not reduce or pollute patch coverage.