feat: one tsconfig.json and different rules

vitest.config.ts

@@ -5,9 +5,9 @@ export default defineConfig({
   // Vite ≥8 warns that this plugin can be replaced by the native (experimental)
   // `resolve.tsconfigPaths: true`. It cannot — keep the plugin. Tests run
   // unbuilt (see AGENTS.md): bare workspace names like `cordis` or
-  // `@deepseek-ai/dsh-llm` must resolve to src/, and the only place that
-  // mapping exists is the root tsconfig.json `paths` map inherited by
-  // tsconfig.test.json. The native option is a bare boolean: for each
+  // `@deepseek-ai/dsh-llm` must resolve to src/, and that mapping comes from
+  // the root tsconfig.json paths map. The native option is a bare boolean:
+  // for each
   // importing file it discovers the NEAREST tsconfig.json and applies that
   // file's own `paths`. Every workspace under packages/* and vendor/* has its
   // own tsconfig.json without `paths`, so native resolution maps nothing,
@@ -17,7 +17,7 @@ export default defineConfig({
   // 15 workspace tsconfigs — including vendor/* ones, which are pinned
   // upstream copies (vendor/README.md). The plugin's `projects` option
   // instead applies the one root map to every importer.
-  plugins: [tsconfigPaths({ projects: ['./tsconfig.test.json'] })],
+  plugins: [tsconfigPaths({ projects: ['./tsconfig.json'] })],
   test: {
     include: ['packages/*/tests/**/*.spec.ts', 'examples/*/tests/**/*.spec.ts'],
     coverage: {