supercov 0.0.17 → 0.0.18

package/docs/agent-loop.md

@@ -1,10 +1,8 @@
 # Agent loop
 
-Supercov exists because coverage reports are built for people and coding agents
-need something different: small answers, a stable format, and a way to prove
-that the test just written actually changed the result. This page describes the
-loop, the prompt, and the failure modes worth guarding against when nobody is
-watching.
+Use Supercov in a repeatable agent loop: run the suite, query uncovered
+obligations, add a focused test, rerun, and compare results. This page covers
+the loop, the recommended prompt, and failure handling.
 
 ## The shape of the loop
 

package/docs/coverage-model.md

@@ -1,10 +1,8 @@
 # Coverage model
 
-Line coverage answers a question nobody actually has. "This line executed" says
-nothing about whether the interesting thing on that line was ever true, ever
-false, or ever mattered. Supercov measures **completeness**: of everything the
-structure of the code obliges a suite to exercise, how much has been exercised,
-and with what quality of evidence.
+Supercov derives coverage obligations from code structure. It reports which
+obligations ran and the quality of the available evidence, including line,
+branch, value-path, control-flow, and MC/DC coverage.
 
 ## Obligations
 

package/docs/evidence.md

@@ -1,9 +1,7 @@
 # Evidence and runs
 
-A coverage number is only as trustworthy as the thing it was computed from.
-Supercov keeps exactly one artifact per run and derives every view from it on
-demand, so a report can never quietly disagree with the evidence it claims to
-summarise.
+Each run stores one evidence artifact and its metadata. Reports, queries, and
+comparisons are derived from those files on demand.
 
 ## What a run is
 

package/docs/getting-started.md

@@ -1,8 +1,8 @@
 # Getting started
 
-Supercov measures coverage completeness for a JavaScript or TypeScript test
-suite without changing the suite. There is no config file to add, no import to
-insert, and no reporter to register: you prefix the command you already run.
+Supercov measures coverage for JavaScript, TypeScript, and Rust test suites.
+Prefix the command you already run; no config file, import, or reporter is
+required.
 
 ```sh
 npx supercov -- npm test

package/docs/supported-suites.md

@@ -1,9 +1,8 @@
 # Supported suites
 
-Supercov works by wrapping a command and following the processes it launches,
-so the interesting question is not "does my runner work" but "how precisely can
-coverage be attributed to individual tests". Both answers are visible in every
-query.
+Supercov wraps a test command and instruments the processes it launches.
+Runner support differs by attribution level: exact per-test attribution or
+aggregate coverage.
 
 ## Attribution by runner
 

package/docs/verification.md

@@ -1,13 +1,8 @@
 # Verification
 
-Supercov rewrites your source before running it. That is a strong claim to make
-about someone else's production code, so the burden of proof sits with the
-instrumenter: it has to demonstrate, on every release, that the rewritten
-program behaves exactly like the original and that the coverage it reports is
-arithmetically correct.
-
-Seven independent gates block publication. A failure in any one of them stops
-the trusted-publishing workflow.
+Supercov instruments source before the test command runs. Seven release gates
+check that the instrumented program matches the original program and that
+coverage calculations are correct. Any failed gate blocks publication.
 
 ## 1. Semantic differential execution
 

package/docs/workspace-isolation.md

@@ -1,9 +1,8 @@
 # Workspace isolation
 
-Supercov's primary filesystem guarantee is stronger than “we clean up when the
-command exits”: the user's source and ordinary build artifacts are never
-Supercov's write targets. Cleanup is useful for space, but correctness cannot
-depend on a signal handler running.
+Supercov writes generated and temporary files only under the project's
+`.supercov/` directory. Application source and ordinary build artifacts are
+not write targets, and cleanup does not depend on a signal handler.
 
 ## Owned paths
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "0.0.17",
+  "version": "0.0.18",
   "description": "Zero-edit, runner-aware coverage completeness for JavaScript test suites",
   "license": "MIT",
   "repository": {
@@ -37,6 +37,7 @@
     "sync:rust-assets": "node scripts/sync-rust-package-assets.mjs",
     "test:rust-assets": "node scripts/sync-rust-package-assets.mjs --check",
     "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",
     "test:rust-nextest-runner": "cargo build -p supercov && node scripts/rust-nextest-runner-integration.mjs",
     "test": "cargo test --workspace",
@@ -66,12 +67,12 @@
     "prepublishOnly": "npm run release:check"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "0.0.17",
-    "@supercov/cli-darwin-x64": "0.0.17",
-    "@supercov/cli-linux-arm64-gnu": "0.0.17",
-    "@supercov/cli-linux-arm64-musl": "0.0.17",
-    "@supercov/cli-linux-x64-gnu": "0.0.17",
-    "@supercov/cli-linux-x64-musl": "0.0.17"
+    "@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"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",