From e0373de4d9e9decac0120b6ca26f6e5d56950166 Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Sun, 2 Aug 2026 09:36:34 +0900 Subject: [PATCH] docs: clarify counter-bearing module scope --- .../plans/2026-08-02-counter-bearing-coverage-provenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/superpowers/plans/2026-08-02-counter-bearing-coverage-provenance.md b/docs/superpowers/plans/2026-08-02-counter-bearing-coverage-provenance.md index f7cea71..df2db1a 100644 --- a/docs/superpowers/plans/2026-08-02-counter-bearing-coverage-provenance.md +++ b/docs/superpowers/plans/2026-08-02-counter-bearing-coverage-provenance.md @@ -10,7 +10,7 @@ ## Global Constraints -- `runtime.ts` declarations/initializers and direct execution statements are counter-bearing. +- Runtime declarations/initializers and direct execution statements are counter-bearing. - Type-only modules, `import type {}`, `import {}`, bare side-effect imports, value imports, named value re-exports, and star value re-exports are counterless under the observed Vitest/V8 producer. - Counterless does not mean non-executable; code, artifacts, diagnostics, tests, and documentation must not make that claim. - Exact all-zero rows are accepted only for statically counterless modules.