docs: clarify per-package coverage in plan

2026-06-16 19:18:53 +05:00
parent a63ee8a700
commit 1b2c0214d0
1 changed files with 2 additions and 2 deletions
@@ -133,7 +133,7 @@ Replace the root `package.json` with a workspaces root that holds only shared de
 }
 ```

-Note: root `vitest.config.ts` is kept (Task 1.4 updates it to a multi-package projects config) so `vitest run` at the root drives every package's tests in one run with one coverage gate.
+Note: root `vitest.config.ts` is kept (Task 1.4 updates it to a multi-package projects config) so `vitest run` at the root drives every package's tests in one run. Coverage, however, is enforced per package via `npm run coverage --workspaces` (each package owns its threshold) — not as a single merged root gate.

 - [ ] **Step 2: Create `tsconfig.base.json`** with the shared compiler options (lifted verbatim from the current `tsconfig.json`):

@@ -318,7 +318,7 @@ git commit -m "chore: wire biome and workspace install"
 **Files:**
 - Create: `vitest.config.ts` (root)

- [ ] **Step 1: Create root `vitest.config.ts`** with named projects that glob into every package. (One root run = one coverage gate over all packages.)
+- [ ] **Step 1: Create root `vitest.config.ts`** with named projects that glob into every package. (One root run executes all packages' tests; coverage is enforced per package via the workspace fan-out, not from this root config.)

 ```ts
 import { defineConfig } from 'vitest/config'