supercov 0.0.40 → 0.0.42

package/README.md

@@ -153,7 +153,7 @@ Supercov uses exact per-test attribution where an adapter is available. For othe
 | Jest | Exact per test, including concurrent and parameterized tests |
 | `node:test` | Exact per test |
 | AVA and Mocha | Aggregate structural coverage |
-| Cargo's standard libtest runner | Exact test and attempt identity |
+| Cargo's standard libtest runner | Exact test, attempt, and passing-assertion identity |
 | rustdoc doctests | Exact per doctest |
 | cargo-nextest | Exact test, attempt, retry, and binary identity |
 | RSpec | Exact example and before/example/after phase identity |

package/docs/supported-suites.md

@@ -109,7 +109,7 @@ whatever was still buffered.
 
 | Runner | Attribution | Current requirement |
 | --- | --- | --- |
-| Cargo's standard libtest runner | Exact test and attempt identity | Rust 1.95; run with `npx supercov -- cargo test` |
+| Cargo's standard libtest runner | Exact test, attempt, and passing-assertion identity | Rust 1.95; run with `npx supercov -- cargo test` |
 | rustdoc doctests | Exact doctest identity; every doctest runs in a process of its own | Rust 1.95; part of `npx supercov -- cargo test` |
 | cargo-nextest | Exact test, attempt, retry, and binary identity | cargo-nextest 0.9.138 or 0.9.140 |
 
@@ -125,7 +125,9 @@ literal `include!` calls; a `.rs` file nothing declares as a module, such as
 one embedded with `include_str!`, is left untouched. Statements, functions,
 `if`/`while`/match-guard decisions with their conditions (let chains
 included), match arms, `&&` and `||`, `for` and `while` loops and the `?`
-operator each take a probe; const contexts and macro expansions stay in the
+operator each take a probe; what a thread recorded before it passed an
+`assert!`, `assert_eq!` or `assert_ne!` is linked to that assertion, so the
+report can separate code a test checked from code it merely ran; const contexts and macro expansions stay in the
 denominator behind an explicit limitation. Use the repository's normal flags after the
 wrapped command:
 

package/docs/troubleshooting.md

@@ -176,3 +176,16 @@ never looks complete. Since 0.0.29 the background and execution-trace writers al
 clone sharing their file and move to a fresh one, so this should be rare; if it
 persists, check whether something outside Supercov appends to
 `.supercov/…/server/background/`.
+
+## "Complete ... — N declared boundary(ies)"
+
+A limitation is either blocking or declared. A blocking one means Supercov
+could not measure something inside the denominator it claims — corrupt
+evidence, a transport that never reported — and the run reads as
+"Incomplete". A declared one marks a boundary of the denominator itself: a
+Rust macro the compiler expands, a `const fn` body no runtime probe can
+enter, a proc-macro crate whose code runs inside the compiler. Nothing inside
+the measured denominator went unmeasured, so the run reads as complete within
+those boundaries, and each boundary is reported at the line it covers with a
+reason. `runs <run> file <path>` lists them per file; the `measurement`
+object in `--json` output counts them under `declared`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "0.0.40",
+  "version": "0.0.42",
   "description": "Zero-edit, runner-aware coverage completeness for JavaScript, TypeScript, Rust, Python, and Ruby test suites",
   "license": "MIT",
   "repository": {
@@ -74,14 +74,14 @@
     "test:rust-public-cargo": "cargo build -p supercov && node scripts/rust-public-cargo-integration.mjs"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "0.0.40",
-    "@supercov/cli-darwin-x64": "0.0.40",
-    "@supercov/cli-linux-arm64-gnu": "0.0.40",
-    "@supercov/cli-linux-arm64-musl": "0.0.40",
-    "@supercov/cli-linux-x64-gnu": "0.0.40",
-    "@supercov/cli-linux-x64-musl": "0.0.40",
-    "@supercov/cli-win32-arm64": "0.0.40",
-    "@supercov/cli-win32-x64": "0.0.40"
+    "@supercov/cli-darwin-arm64": "0.0.42",
+    "@supercov/cli-darwin-x64": "0.0.42",
+    "@supercov/cli-linux-arm64-gnu": "0.0.42",
+    "@supercov/cli-linux-arm64-musl": "0.0.42",
+    "@supercov/cli-linux-x64-gnu": "0.0.42",
+    "@supercov/cli-linux-x64-musl": "0.0.42",
+    "@supercov/cli-win32-arm64": "0.0.42",
+    "@supercov/cli-win32-x64": "0.0.42"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",