supercov 4.20.0 → 4.20.2

package/docs/cli.md

@@ -923,6 +923,7 @@ terminal or offline environment after the package has been downloaded.
 | `SUPERCOV_SOURCE_ROOTS` | Comma-separated directories or files that hold your own code, in any language; everything else is left out |
 | `SUPERCOV_TEST_KIND` | Label the wrapped command as a test level such as `unit` or `e2e` |
 | `SUPERCOV_SOURCE_TOOLS` | Comma-separated names of tools the test command runs that read source as text, such as a linter or a spell checker, besides Biome, oxlint, dprint, cspell and knip. Each is run on your source as you wrote it instead of on the instrumented copy |
+| `SUPERCOV_RUN_ID` | Set by Supercov, not by you: in every process a measured command starts, the run's id, so a test or harness can tell it is measured |
 | `SUPERCOV_RUN_ID_FILE` | A file to write the recorded run's id to, for a script to query that run rather than `latest` |
 | `SUPERCOV_KEEP_WORKSPACE` | Set to `1` to leave the instrumented copy of the project in `.supercov/workspaces/` after the run, to inspect what the command ran |
 

package/docs/supported-suites.md

@@ -274,8 +274,11 @@ of that build is not counted, and wasm-only code is, whatever target
 `cargo test` builds the rest for. The crate counts whether or not
 `cargo test` compiles it (`cargo test -p host` does not) and whether or not
 a test started its Worker, so every run of the workspace has one
-denominator. Where no test of a run started a Worker, its files say so, in
-`gaps` and the file view, rather than reading as code the tests missed.
+denominator. Where no test of a run started a Worker, its files are not
+measured, rather than read as code the tests missed: they leave the run's
+totals, the file view says why at the top, `scope` lists them as left out,
+the run names them after the tests' output, and `runs check` refuses to judge
+a floor over a run that left them unmeasured.
 
 `wrangler dev --remote` runs the Worker on Cloudflare's edge, and wrangler
 opens no inspector into it there, so nothing can read what it ran. A test
@@ -292,7 +295,11 @@ Worker of a session, and Supercov reads each through workerd's own, whose
 address a small preload in wrangler's Node process reports. A test that
 sets its own `NODE_OPTIONS` keeps them; the preload is added after. A workspace with several Worker crates counts each crate
 once, and runs of different tests -- each starting different Workers, or
-none -- merge with `supercov merge`. Tests that run a Worker only when its `build/` exists, as a test
+none -- merge with `supercov merge`. A crate the Worker is built with, such
+as a core library the native tests call too, is measured inside the Worker:
+its probes run in the Worker's wasm and are read with the Worker's, into the
+same file as its native tests, each test credited what it reached either
+way. Tests that run a Worker only when its `build/` exists, as a test
 kit that will not start an unbuilt Worker does, run it: a `build/` you made
 beforehand and keep out of git is in the copy, and `wrangler dev` builds the
 crate with probes over it there.
@@ -308,10 +315,40 @@ What a project needs:
 
 The project needs no `cfg` flag or build step of its own for Supercov.
 
+#### What a test harness can rely on
+
+- **Any configuration, anywhere.** A test may write its own wrangler
+  configuration, per test, outside the crate, with a `main` of its own: a
+  module that loads the built Worker and adds stand-ins or test controls.
+  Supercov leaves every configuration as it was written. When a test runs
+  `wrangler dev`, Supercov's `wrangler` hands it a copy of the configuration
+  it was given (`-c`, or the one wrangler finds from its directory), beside
+  the original as `.supercov-wrangler-<pid>-<n>.toml` (or `.json`), whose
+  `main` is a small entry that remembers the Worker's wasm instances and then
+  loads your `main`. The copy is removed once that `wrangler` exits. A Worker
+  is read when wasm built from the crate's measured source runs in it,
+  whatever the configuration's `main` imports.
+- **The measured build.** The configuration's `[build]` builds the crate
+  with worker-build (any `cwd`), or its `main` imports a build made in the
+  run's copy. A `build/` made before the run, without probes, has nothing to
+  read. Supercov builds nothing itself: as a JavaScript suite builds the wasm
+  it loads, build the Worker in the measured command or in the tests.
+- **Why a Worker was not measured.** Where tests started `wrangler dev` and
+  no measured build ran in it, the Worker's files name each `wrangler dev -c
+  <path>` the tests started, and why a configuration was left as it was (no
+  `main`, say), in the file view, `scope` and the run's output.
+- **`--inspector-port`.** A test may pass its own: Supercov reads the Worker
+  through that port.
+- **Knowing the run is measured.** `SUPERCOV_RUN_ID` is set in every process
+  a measured command starts, holding the run's id. The other `SUPERCOV_`
+  variables a test may see are Supercov's own wiring and change without
+  notice.
+- **Output.** `cargo test -- --nocapture` shows each test's output as it is
+  written, as plain `cargo test` does.
+
 The Worker built with probes stays in the copy: its `build/` output is never
-returned to the project, and neither is the copy's configuration, which
-points `main` at Supercov's entry. wrangler's `.wrangler/` state is not a
-build input, so writing it does not make the run stale.
+returned to the project, nor are wrangler's `.wrangler/` state and the
+configuration copies above. Writing them does not make the run stale.
 
 ### Rust tests compiled to wasm
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "4.20.0",
+  "version": "4.20.2",
   "description": "Coverage, security and code quality for coding agents",
   "keywords": [
     "coverage",
@@ -97,7 +97,8 @@
     "benchmark:python": "cargo build -p supercov && node scripts/python-benchmark.mjs",
     "check": "npm run check:lint && npm run check:tests",
     "check:lint": "cargo fmt --all -- --check && cargo clippy --workspace --all-targets -- -D warnings",
-    "check:tests": "npm run test && npm run test:release-tooling && npm run test:runtime && npm run test:action && npm run test:rust-assets && npm run test:agent-commands && npm run test:assertions && npm run test:sweep-target && npm run test:skip-guard && npm run test:windows-tls && node scripts/package-preflight.mjs && node scripts/verify-binstall-metadata.mjs --offline",
+    "check:tests": "npm run test && npm run check:tooling",
+    "check:tooling": "npm run test:release-tooling && npm run test:runtime && npm run test:action && npm run test:rust-assets && npm run test:agent-commands && npm run test:assertions && npm run test:sweep-target && npm run test:skip-guard && npm run test:windows-tls && node scripts/package-preflight.mjs && node scripts/verify-binstall-metadata.mjs --offline",
     "release:check": "cargo clean && node scripts/sweep-target.mjs && npm run check && npm run test:engine && npm run test:go && npm run test:jvm && npm run test:launcher && npm run test:fixture && npm run test:watchdog && npm run test:engine-contract && npm run test:agent && npm run test:child-attribution && npm run test:host-loader && npm run test:python && npm run test:ruby-coverage && npm run test:rust-public-cargo && npm run test:packed-npx && npm run test:clang-mcdc && npm run benchmark:check",
     "release:bump": "node scripts/bump-version.mjs",
     "sweep": "node scripts/sweep-target.mjs",
@@ -121,14 +122,14 @@
     "test:windows-tls": "node scripts/windows-tls-test.mjs"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "4.20.0",
-    "@supercov/cli-darwin-x64": "4.20.0",
-    "@supercov/cli-linux-arm64-gnu": "4.20.0",
-    "@supercov/cli-linux-arm64-musl": "4.20.0",
-    "@supercov/cli-linux-x64-gnu": "4.20.0",
-    "@supercov/cli-linux-x64-musl": "4.20.0",
-    "@supercov/cli-win32-arm64": "4.20.0",
-    "@supercov/cli-win32-x64": "4.20.0"
+    "@supercov/cli-darwin-arm64": "4.20.2",
+    "@supercov/cli-darwin-x64": "4.20.2",
+    "@supercov/cli-linux-arm64-gnu": "4.20.2",
+    "@supercov/cli-linux-arm64-musl": "4.20.2",
+    "@supercov/cli-linux-x64-gnu": "4.20.2",
+    "@supercov/cli-linux-x64-musl": "4.20.2",
+    "@supercov/cli-win32-arm64": "4.20.2",
+    "@supercov/cli-win32-x64": "4.20.2"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",