supercov 1.0.0 → 1.1.0

package/README.md

@@ -4,10 +4,18 @@
 
 **Supercov tells your coding agent what to fix and what to test.** It scores your code quality with [Jev](https://typesafe.ai), runs the test command you already use, and turns uncovered paths into small, actionable queries. Your agent picks a target, writes a focused test or a focused refactor, proves what improved, and keeps going.
 
-Coverage needs no account, config file, import, custom reporter, or hosted service. Supercov is local, free, open source, and MIT licensed. Quality uses [Jev](https://typesafe.ai) and needs a key.
+Paste this to your coding agent to start:
+
+```text supercov-prompt
+Measure code quality with npx supercov.
+```
+
+Scoring needs a [TypeSafe AI](https://typesafe.ai) API key, and your coding agent will usually ask you for it. It costs about a cent per megabyte of source. Coverage needs no account, config file, import, custom reporter, or hosted service. Supercov is local, free, open source, and MIT licensed.
 
 [Website](https://supercov.com) · [Documentation](https://supercov.com/docs) · [npm](https://www.npmjs.com/package/supercov) · [GitHub](https://github.com/supercorp-ai/supercov)
 
+Supported languages: [JavaScript](https://supercov.com/docs/javascript) · [TypeScript](https://supercov.com/docs/javascript) · [Rust](https://supercov.com/docs/rust) · [Python](https://supercov.com/docs/python) · [Ruby](https://supercov.com/docs/ruby) · [Go](https://supercov.com/docs/go) · [Java](https://supercov.com/docs/java) · [Kotlin](https://supercov.com/docs/kotlin).
+
 Supported by [Supercorp](https://supercorp.ai).
 
 [Agent workflow](https://supercov.com/docs/agent-loop): ask your coding agent
@@ -211,21 +219,21 @@ Java and Kotlin have no registry of their own here, so a JVM project takes the b
 
 ## Supported languages
 
-| Language | Status | Start with |
-| --- | --- | --- |
-| JavaScript | Available | `npx supercov -- npm test` |
-| TypeScript | Available | `npx supercov -- npm test` |
-| Rust | Available | `npx supercov -- cargo test` |
-| Python | Available | `npx supercov -- pytest` |
-| Ruby | Available | `npx supercov -- rspec` |
-| Go | Available | `go run github.com/supercorp-ai/supercov/cmd/supercov@latest -- go test ./...` |
-| Java | Available | `npx supercov -- mvn test` |
-| Kotlin | Available | `npx supercov -- ./gradlew test` |
-| Zig | Coming soon | — |
-| PHP | Coming soon | — |
-| C | Coming soon | — |
-
-Supercov requires Node.js 22 or newer. Rust support currently uses Rust 1.95; cargo-nextest 0.9.138 and 0.9.140 are supported. Python support requires CPython 3.12 or newer and measures pytest and unittest runs. Ruby support requires Ruby 3.3 or newer (3.4 or newer for full measurement) and measures RSpec, Minitest, test-unit and Cucumber runs. Go support requires Go 1.22 or newer and measures `go test`. Java and Kotlin support requires a JDK 17 or newer with Maven or Gradle, and measures every JUnit Platform engine -- JUnit 5, JUnit 4 through Vintage, Kotest and Spock -- as well as TestNG.
+| Language | Status | Install | Start with |
+| --- | --- | --- | --- |
+| [JavaScript](https://supercov.com/docs/javascript) | Available | nothing, `npx` fetches it | `npx supercov -- npm test` |
+| [TypeScript](https://supercov.com/docs/javascript) | Available | nothing, `npx` fetches it | `npx supercov -- npm test` |
+| [Rust](https://supercov.com/docs/rust) | Available | `cargo install supercov` | `supercov -- cargo test` |
+| [Python](https://supercov.com/docs/python) | Available | `python -m pip install supercov-cli` | `supercov -- python -m pytest` |
+| [Ruby](https://supercov.com/docs/ruby) | Available | `gem install supercov` | `supercov -- bundle exec rspec` |
+| [Go](https://supercov.com/docs/go) | Available | nothing, `go run` fetches it | `go run github.com/supercorp-ai/supercov/cmd/supercov@latest -- go test ./...` |
+| [Java](https://supercov.com/docs/java) | Available | `brew install supercorp-ai/tap/supercov` | `supercov -- mvn test` |
+| [Kotlin](https://supercov.com/docs/kotlin) | Available | `brew install supercorp-ai/tap/supercov` | `supercov -- ./gradlew test` |
+| Zig | Coming soon | — | — |
+| PHP | Coming soon | — | — |
+| C | Coming soon | — | — |
+
+The `npx` path requires Node.js 22 or newer; the other installs need no Node. Rust support currently uses Rust 1.95; cargo-nextest 0.9.138 and 0.9.140 are supported. Python support requires CPython 3.12 or newer and measures pytest and unittest runs. Ruby support requires Ruby 3.3 or newer (3.4 or newer for full measurement) and measures RSpec, Minitest, test-unit and Cucumber runs. Go support requires Go 1.22 or newer and measures `go test`. Java and Kotlin support requires a JDK 17 or newer with Maven or Gradle, and measures every JUnit Platform engine -- JUnit 5, JUnit 4 through Vintage, Kotest and Spock -- as well as TestNG.
 
 ## Supported operating systems and architectures
 
@@ -237,7 +245,7 @@ The CLI is a single native binary. `npx supercov` selects the build for the mach
 | Linux | arm64, x64 | glibc 2.28 or newer (Debian 10, Ubuntu 18.10, RHEL 8 and later), or musl (Alpine); chosen automatically |
 | Windows | arm64, x64 | Windows 10 or newer |
 
-JavaScript, TypeScript, Python, Ruby, Rust, Go, Java and Kotlin suites are verified on Linux, macOS and Windows -- CPython 3.12, 3.13 and 3.14, Ruby 3.3, 3.4 and 4.0, and Go 1.22 and 1.25 on every one, and JDK 17 and 21 on every one that has them (Temurin publishes no 17 for arm64 Windows, so that pairing is 21 alone). Containers, VMs, and remote executors run the same Linux builds. Every release publishes the same binaries to npm, PyPI (`supercov-cli`, a wheel per platform) and RubyGems (`supercov`, a gem per platform except arm64 Windows, which Ruby has no platform for), and the source to crates.io (`supercov`).
+JavaScript, TypeScript, Python, Ruby, Rust, Go, Java and Kotlin suites are verified on Linux, macOS and Windows -- CPython 3.12, 3.13 and 3.14, Ruby 3.3, 3.4 and 4.0, and Go 1.22, 1.25, 1.26 and 1.27 on every one, and JDK 17 and 21 on every one that has them (Temurin publishes no 17 for arm64 Windows, so that pairing is 21 alone). Containers, VMs, and remote executors run the same Linux builds. Every release publishes the same binaries to npm, PyPI (`supercov-cli`, a wheel per platform) and RubyGems (`supercov`, a gem per platform except arm64 Windows, which Ruby has no platform for), and the source to crates.io (`supercov`).
 
 ## Supported test suites
 

package/docs/cli.md

@@ -55,7 +55,7 @@ the exact requests and contacts nothing.
 `quality diff` reports what declined between two assessments: which files lost
 health, which properties appeared, and which files entered or left the scope.
 
-Assessing needs a TypeSafe API key in `TYPESAFE_API_KEY`; reading a saved
+Assessing needs a TypeSafe AI API key in `TYPESAFE_API_KEY`; reading a saved
 assessment does not. The command prints a cost estimate before sending anything
 and caches answers by content, so a second run pays only for what changed.
 

package/docs/getting-started.md

@@ -15,9 +15,8 @@ tests; you don't need to do those steps yourself.
 To score the code itself rather than its tests, set a [Jev](https://typesafe.ai)
 key and ask:
 
-```sh supercov-example
-export TYPESAFE_API_KEY=...
-npx supercov quality
+```text supercov-prompt
+Measure code quality with npx supercov.
 ```
 
 See [Understanding quality](https://supercov.com/docs/quality).

package/docs/quality.md

@@ -9,8 +9,10 @@ arithmetic, so every part of a score is a claim you can check against the file.
 
 ## Set your key
 
-Assessing needs a TypeSafe API key, read from `TYPESAFE_API_KEY`. Get one at
-[typesafe.ai](https://typesafe.ai).
+Assessing needs a TypeSafe AI API key, and your coding agent will usually ask
+you for it. Get one at [typesafe.ai](https://typesafe.ai).
+
+Supercov looks for it in `TYPESAFE_API_KEY`:
 
 ```bash
 export TYPESAFE_API_KEY=...        # for this shell

package/docs/supported-suites.md

@@ -218,12 +218,24 @@ npx supercov -- python -m unittest
 | Runner | Attribution | Current requirement |
 | --- | --- | --- |
 | RSpec | Exact example and before/example/after phase identity | Ruby 3.4 or newer for full measurement; run with `npx supercov -- rspec` or `bundle exec rspec` |
-| Minitest (including Minitest::Spec and ActiveSupport::TestCase) | Exact test and setup/test/teardown identity; skips recorded | `ruby -Itest ...`, `rake test`, `rails test` |
+| Minitest (including Minitest::Spec and ActiveSupport::TestCase) | Exact test and setup/test/teardown identity; a test's coverage is a lower bound (see below); skips recorded | `ruby -Itest ...`, `rake test`, `rails test` |
 | test-unit | Exact test and setup/test/teardown identity; omissions and pendings recorded | `ruby -Itest ...`, `rake test` |
 | parallel_tests, Rails process workers | Exact per worker process | Workers inherit the run through `RUBYOPT`; verified on a Rails app with bootsnap, Zeitwerk and two forked workers |
 | Thread-parallel Minitest (`parallelize_me!`, `parallelize(with: :threads)`) | Probe observations exact per test; line, method and simple-branch observations made while phases overlapped go to the run, declared | |
 | Cucumber | Exact scenario identity (`features/x.feature:LINE`), hook steps as setup/teardown | `cucumber`, `bundle exec cucumber` |
 
+Ruby reports a line the first time it executes and never again, which is what
+makes collecting coverage cheap enough to leave on. So a test is credited with
+the lines it was first to reach, and a later test running the same lines is
+credited with none of them: what a test is credited with is really its own, and
+what it is not credited with is not evidence it did not run the code.
+
+Totals are unaffected — every line is credited to exactly one test. What this
+changes is per-test reporting: `supercov runs <id> test <name>` gives its
+numbers as "at least", and `tests affected` reports a test whose own record
+cannot settle the question as **undetermined** rather than unaffected, so
+`--names` includes it in the set to run.
+
 Your project runs in place with its own interpreter and bundle. Supercov loads
 through `RUBYOPT`; application files on disk and their backtrace line numbers
 stay unchanged. RSpec, Minitest and test-unit assertions can identify execution
@@ -261,6 +273,31 @@ npx supercov -- ruby -Itest test/shapes_test.rb
 npx supercov -- bin/rails test
 ```
 
+## Crediting a test with what it reached
+
+Most runners attribute exactly at no cost: Supercov runs each Rust test in its
+own process, Python's workers are processes, and JavaScript keeps a coverage
+map per test. Two cases cannot, because probes are a store into one array the
+whole process shares and two tests running at once cannot both be credited
+with what they reached:
+
+| | Left as written | `--exact-attribution` |
+| --- | --- | --- |
+| A Go test calling `t.Parallel()` | counted run-wide | announced after it resumes, with `-parallel=1` |
+| A JUnit suite with parallel execution enabled | counted run-wide | run in order |
+
+```sh supercov
+npx supercov --exact-attribution -- go test ./...
+```
+
+By default your command runs as you wrote it, and the run says what it could
+not credit. `--exact-attribution` buys that back by running the suite in order,
+which costs whatever its parallelism was worth — on sixteen I/O-bound JUnit
+tests across fifteen cores, 3.6x. Either way the coverage totals are the same;
+what changes is whether a line can be traced to the test that ran it.
+
+`supercov runs latest` reports which you got, under `Attribution`.
+
 ## Go
 
 | Runner | Attribution | Current requirement |
@@ -287,8 +324,19 @@ coverage never counts — a failed run cannot say which of it came from the test
 that failed.
 
 An `Example` with an `Output` comment and a `Fuzz` target's seed corpus are
-measured the same way. `go test` runs both, so what they reach is real
-coverage, but neither takes a `*testing.T` for a result to be named by.
+measured the same way: `go test` runs both, and what they reach is real
+coverage no test can claim.
+
+Such a test is still recorded as having run, with its outcome, and credited
+with no coverage. `supercov runs <id> test <name>` says that rather than
+reporting zeroes, coverage percentages leave it out, and `tests affected` lists
+it as **undetermined**: nothing can say a change missed it, so `--names`
+includes it in the set to run. A package where every test calls `t.Parallel()`
+is published like any other.
+
+A file Supercov cannot parse is a hole, not the end of the run. It is named on
+the line that reports the result and recorded in the run, and a run is refused
+only when nothing is left to measure.
 
 Supercov also writes evidence as the suite runs, not only at the end. Go offers
 no way to run code on `os.Exit`, and a `TestMain` need not reach the `m.Run()`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supercov",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Code quality and coverage for coding agents",
   "license": "MIT",
   "repository": {
@@ -77,7 +77,7 @@
     "test:test262": "cargo build --release -p supercov && node scripts/test262-equivalence.mjs",
     "benchmark:check": "cargo build --release -p supercov && node scripts/rust-transform-benchmark.mjs",
     "benchmark:python-monitoring": "cargo build -p supercov && node scripts/python-monitoring-benchmark.mjs",
-    "check": "cargo fmt --all -- --check && cargo clippy --workspace --all-targets -- -D warnings && npm run test && npm run test:runtime && npm run test:rust-assets && npm run test:assertion-maps && node scripts/package-preflight.mjs && node scripts/verify-binstall-metadata.mjs --offline",
+    "check": "cargo fmt --all -- --check && cargo clippy --workspace --all-targets -- -D warnings && npm run test && npm run test:runtime && npm run test:rust-assets && npm run test:assertion-maps && 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-monitoring && 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",
@@ -96,17 +96,21 @@
     "sync:assertion-schema": "cargo build -p supercov && node scripts/assertion-map-schema.mjs",
     "docs:sync": "node scripts/sync-docs.mjs",
     "docs:check": "node scripts/sync-docs.mjs --check",
-    "test:launcher": "go vet ./cmd/... && go test ./cmd/..."
+    "test:launcher": "go vet ./cmd/... && go test ./cmd/...",
+    "test:sweep-target": "node scripts/sweep-target-test.mjs",
+    "test:go-versions": "cargo build -p supercov-engine --tests && node scripts/go-version-matrix.mjs",
+    "test:skip-guard": "node scripts/skip-guard-test.mjs",
+    "test:windows-tls": "node scripts/windows-tls-test.mjs"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "1.0.0",
-    "@supercov/cli-darwin-x64": "1.0.0",
-    "@supercov/cli-linux-arm64-gnu": "1.0.0",
-    "@supercov/cli-linux-arm64-musl": "1.0.0",
-    "@supercov/cli-linux-x64-gnu": "1.0.0",
-    "@supercov/cli-linux-x64-musl": "1.0.0",
-    "@supercov/cli-win32-arm64": "1.0.0",
-    "@supercov/cli-win32-x64": "1.0.0"
+    "@supercov/cli-darwin-arm64": "1.1.0",
+    "@supercov/cli-darwin-x64": "1.1.0",
+    "@supercov/cli-linux-arm64-gnu": "1.1.0",
+    "@supercov/cli-linux-arm64-musl": "1.1.0",
+    "@supercov/cli-linux-x64-gnu": "1.1.0",
+    "@supercov/cli-linux-x64-musl": "1.1.0",
+    "@supercov/cli-win32-arm64": "1.1.0",
+    "@supercov/cli-win32-x64": "1.1.0"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",