supercov 0.0.18 → 0.0.20

package/docs/evidence.md

@@ -11,22 +11,27 @@ comparisons are derived from those files on demand.
   run.json          fingerprints, phase timings, schema version, integrity state
 ```
 
-Two files. No HTML, no derived report, no query cache. Loose evidence written
-during the run is removed only after the whole run directory is atomically
-visible, so a run is either complete or absent.
+Two durable source-of-truth files. No HTML or derived report is stored in the
+published run. Loose evidence written during the run is removed only after the
+whole run directory is atomically visible, so a run is either complete or
+absent.
 
 Run ids are UTC timestamps, which makes them sort chronologically and makes
 retention deterministic.
 
-## Derived, never stored
+## Derived views and their disposable cache
 
 Every coverage view — the summary, per-file rankings, gap lists, decision
 detail, per-test contribution, the minimizer, and the passed and failed filters
-— is reconstructed from the archive when you ask for it. Nothing is written back.
+— is derived from the archive. The first query may write a disposable,
+integrity-bound query index beside the two durable files; later queries reuse
+it while the run identity remains valid. Delete that index at any time and
+Supercov reconstructs it from `evidence.raw.gz` without losing coverage data.
 
 This is why `--filter passed` and `--filter all` can never contradict each
 other, and why a query added in a future version can answer questions about a
-run recorded today: the stored schema is the raw evidence, not a rendering of it.
+run recorded today: raw evidence remains the source of truth, while the query
+index is only a rebuildable acceleration structure.
 
 Fresh-process summary, files and gaps queries take roughly two tenths of a
 second on the reference run described in [Performance](/docs/performance).

package/docs/getting-started.md

@@ -18,8 +18,10 @@ Everything after `--` is your command, executed exactly as written.
 | Project | JavaScript or TypeScript, with a runnable test command |
 | Disk | A `.supercov/` directory in the project root, which Supercov creates |
 
-Nothing else is required. Supercov never contacts a network service, and no
-part of your source or evidence leaves the machine.
+No Supercov account or hosted service is required. During a coverage run, the
+Supercov CLI does not contact a Supercov service and no part of your source or
+evidence leaves the machine. Package tools such as `npx` may still contact the
+npm registry to resolve or download Supercov when it is not already cached.
 
 ## Your first run
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "0.0.18",
+  "version": "0.0.20",
   "description": "Zero-edit, runner-aware coverage completeness for JavaScript test suites",
   "license": "MIT",
   "repository": {
@@ -36,6 +36,7 @@
     "build": "cargo build -p supercov",
     "sync:rust-assets": "node scripts/sync-rust-package-assets.mjs",
     "test:rust-assets": "node scripts/sync-rust-package-assets.mjs --check",
+    "check:rustc-backend-spike": "(cd spikes/rustc-backend && RUSTC_BOOTSTRAP=1 RUSTUP_TOOLCHAIN=1.95.0 cargo fmt --check && RUSTC_BOOTSTRAP=1 RUSTUP_TOOLCHAIN=1.95.0 cargo clippy --all-targets -- -D warnings)",
     "test:rustc-backend-spike": "node scripts/rustc-backend-spike.mjs",
     "test:rust-compiler-spikes": "cargo build -p supercov && node scripts/rust-libtest-companion-spike.mjs && node scripts/rust-async-attribution-spike.mjs && node scripts/rust-subprocess-attribution-spike.mjs && node scripts/rust-custom-harness-spike.mjs && node scripts/rust-libtest-builder-lifecycle-spike.mjs",
     "test:rust-cargo-runner": "cargo build -p supercov && node scripts/rust-cargo-runner-integration.mjs",
@@ -67,12 +68,12 @@
     "prepublishOnly": "npm run release:check"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "0.0.18",
-    "@supercov/cli-darwin-x64": "0.0.18",
-    "@supercov/cli-linux-arm64-gnu": "0.0.18",
-    "@supercov/cli-linux-arm64-musl": "0.0.18",
-    "@supercov/cli-linux-x64-gnu": "0.0.18",
-    "@supercov/cli-linux-x64-musl": "0.0.18"
+    "@supercov/cli-darwin-arm64": "0.0.20",
+    "@supercov/cli-darwin-x64": "0.0.20",
+    "@supercov/cli-linux-arm64-gnu": "0.0.20",
+    "@supercov/cli-linux-arm64-musl": "0.0.20",
+    "@supercov/cli-linux-x64-gnu": "0.0.20",
+    "@supercov/cli-linux-x64-musl": "0.0.20"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",

package/runtime/javascript/launchSupervisor.js

@@ -546,7 +546,14 @@ function injectChildEnvironment(method, args) {
     const environment = existingEnvironment
         ? { ...existingEnvironment, ...inherited }
         : { ...process.env, ...inherited };
-    environment.NODE_OPTIONS = appendNodeImport(existingEnvironment?.NODE_OPTIONS ?? process.env.NODE_OPTIONS, pathToFileURL(resolve(process.env["SUPERCOV_PROJECT_ROOT"] ?? process.cwd(), ".supercov/register.mjs")).href);
+    // The register path must come from THIS module's own location, never from
+    // the environment or the working directory. Monorepo runners both defeat
+    // the old derivation at once: turbo's strict env strips SUPERCOV_PROJECT_ROOT
+    // from task children, and it runs each task with cwd inside the package --
+    // so the fallback fabricated packages/<name>/.supercov/register.mjs and
+    // every task aborted with ERR_MODULE_NOT_FOUND. launchSupervisor.js is
+    // generated into the same .supercov directory as register.mjs.
+    environment.NODE_OPTIONS = appendNodeImport(existingEnvironment?.NODE_OPTIONS ?? process.env.NODE_OPTIONS, new URL("./register.mjs", import.meta.url).href);
     next[index] = { ...options, env: environment };
     if (typeof original === "function")
         next.splice(index + 1, 0, original);