supercov 0.0.36 → 0.0.38

package/README.md

@@ -102,6 +102,19 @@ From lines and branches to MC/DC, every gap becomes a concrete test target. Supe
 
 The denominator comes from source structure before the run, so adding or removing tests cannot silently change what 100% means. Ambiguous source scope, uninstrumented code, and missing evidence remain visible as completeness blockers.
 
+## Install for your language
+
+The same binary ships through each language's own package manager, at the same version, from one release:
+
+```bash
+npx supercov -- npm test                          # npm
+uvx --from supercov-cli supercov -- pytest        # PyPI
+gem install supercov && supercov -- bundle exec rspec   # RubyGems
+cargo install supercov && supercov -- cargo test  # crates.io, built from source
+```
+
+`pip install supercov-cli` and `gem install supercov` install a wheel or gem that carries the binary for your platform; nothing is compiled. The crate builds from source and needs Rust 1.95.
+
 ## Supported languages
 
 | Language | Status | Start with |
@@ -124,10 +137,10 @@ The CLI is a single native binary. `npx supercov` selects the build for the mach
 | Operating system | Architectures | Notes |
 | --- | --- | --- |
 | macOS | arm64 (Apple silicon), x64 (Intel) | macOS 11 or newer |
-| Linux | arm64, x64 | glibc and musl (Alpine) builds, chosen automatically |
+| 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 |
 
-On Windows, JavaScript and TypeScript suites are verified on every release; Python, Ruby, and Rust suites are not yet verified there. Containers, VMs, and remote executors run the same Linux builds. The npm package is the current release channel for every language, including Rust, Python, and Ruby projects. A PyPI package (`supercov-cli`), a RubyGems gem (`supercov`), and a crate (`supercov`) exist for macOS arm64 at an earlier version and are being brought up to date with each release.
+On Windows, JavaScript and TypeScript suites are verified on every release; Python, Ruby, and Rust suites are not yet verified there. 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/getting-started.md

@@ -15,19 +15,22 @@ Supercov supports JavaScript, TypeScript, Rust, Python, and Ruby today.
 
 You need:
 
-- macOS (arm64 or x64), Linux (arm64 or x64, glibc or musl), or Windows (arm64
-  or x64; JavaScript and TypeScript suites are verified there today);
+- macOS (arm64 or x64), Linux (arm64 or x64, glibc 2.28 or newer or musl), or
+  Windows (arm64 or x64; JavaScript and TypeScript suites are verified there
+  today);
 - Node.js 22 or newer;
 - a test command that already works in the repository; and
 - for Rust, the Rust 1.95 toolchain;
 - for Python, CPython 3.12 or newer with pytest or unittest;
 - for Ruby, Ruby 3.4 or newer with RSpec, Minitest, test-unit or Cucumber (3.3 measures lines, methods and simple branches only).
 
-The CLI is a native binary distributed through npm, even for Rust, Python, and
-Ruby projects: `npx supercov` picks the build for your operating system and
-architecture, and nothing is compiled on install. The first `npx` invocation may
-download Supercov from the npm registry. Supercov itself does not upload your
-source or coverage evidence to a Supercov service.
+The CLI is a native binary. `npx supercov` picks the build for your operating
+system and architecture, and nothing is compiled on install; the same binary is
+on PyPI as `supercov-cli` (`uvx --from supercov-cli supercov`) and on RubyGems
+as `supercov` (`gem install supercov`), at the same version, and the source is
+on crates.io (`cargo install supercov`). The first invocation may download
+Supercov from the registry. Supercov itself does not upload your source or
+coverage evidence to a Supercov service.
 
 ## 1. Run your real test command
 

package/package.json

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