Route tests through a #testing alias, ban ../ imports, and document the alias ownership rule

2026-10-17 14:45:52 +09:00
parent 15fe481181
commit bfa8269801
15 changed files with 103 additions and 65 deletions
@@ -1,5 +1,5 @@
 ---
-description: Vitest via vp test; unit tests sit next to code as *.test.ts, regression/integration tests in tests/ via the public entry; scripts/ has no tests
+description: Vitest via vp test; unit tests sit next to code as *.test.ts, regression/integration tests in tests/ via the public entry (through its # alias, never ../); scripts/ has no tests
 ---

 Decided 2026-10-14 for all repos.
@@ -11,9 +11,12 @@ Decided 2026-10-14 for all repos.
  config needed. Packages publish only `dist/`, so colocated tests cost nothing
  in the tarball.
 - **Regression and integration tests** live in the top-level `tests/` folder
-  and use only the public entry point through a relative import
-  (`../src/index.ts`; no alias may target `src/` itself, see
-  [[imports-aliases-barrels]]), never internals. `vp test tests` runs just these.
+  and use only the public entry point, imported through its `#` alias (e.g.
+  `#plugin` for `./src/plugin/index.ts`), never internals and never `../`,
+  which is banned in every file. `vp test tests` runs just these
+  ([[imports-aliases-barrels]]). In bot-agents, `tests/` imports only
+  `#testing` (`./src/testing.ts`), which re-exports the few source helpers
+  those tests need.
 - **No in-source tests** (`import.meta.vitest`).
 - **`scripts/` gets no tests** (2026-10-15): it is repo tooling, not
  production code (`project-lint.ts`, `decorators.ts`, `lit-check.ts`,