test: raise coverage to ~98% via grammar drift guard; bump to 2.0.1

.bca-baseline.toml

@@ -728,14 +728,14 @@ value = 16.0
 [[entry]]
 path = "src/metrics/cognitive.rs"
 qualified = "tcl_switch_decision_arms"
-start_line = 447
+start_line = 448
 metric = "nargs"
 value = 7.0
 
 [[entry]]
 path = "src/metrics/cognitive.rs"
 qualified = "tcl_switch_decision_arms"
-start_line = 447
+start_line = 448
 metric = "nexits"
 value = 6.0
 
@@ -968,7 +968,7 @@ path = "src/tools.rs"
 qualified = "<file>"
 start_line = 1
 metric = "loc.sloc"
-value = 761.0
+value = 767.0
 
 [[entry]]
 path = "src/tools.rs"

Cargo.toml

@@ -25,7 +25,7 @@ exclude = [
 ]
 
 [workspace.package]
-version = "2.0.0"
+version = "2.0.1"
 edition = "2024"
 rust-version = "1.94"
 license = "MPL-2.0"
@@ -76,11 +76,11 @@ tree-sitter-c = "=0.24.2"
 # Rationale and the rejected alternatives live on the umbrella
 # issue (dekobon/big-code-analysis#149); the operational details
 # (publish order, first-bootstrap workflow) live in `RELEASING.md`.
-tree-sitter-ccomment = { package = "bca-tree-sitter-ccomment", path = "./tree-sitter-ccomment", version = "=2.0.0" }
-tree-sitter-mozcpp = { package = "bca-tree-sitter-mozcpp", path = "./tree-sitter-mozcpp", version = "=2.0.0" }
-tree-sitter-mozjs = { package = "bca-tree-sitter-mozjs", path = "./tree-sitter-mozjs", version = "=2.0.0" }
-tree-sitter-preproc = { package = "bca-tree-sitter-preproc", path = "./tree-sitter-preproc", version = "=2.0.0" }
-tree-sitter-tcl = { package = "bca-tree-sitter-tcl", path = "./tree-sitter-tcl", version = "=2.0.0" }
+tree-sitter-ccomment = { package = "bca-tree-sitter-ccomment", path = "./tree-sitter-ccomment", version = "=2.0.1" }
+tree-sitter-mozcpp = { package = "bca-tree-sitter-mozcpp", path = "./tree-sitter-mozcpp", version = "=2.0.1" }
+tree-sitter-mozjs = { package = "bca-tree-sitter-mozjs", path = "./tree-sitter-mozjs", version = "=2.0.1" }
+tree-sitter-preproc = { package = "bca-tree-sitter-preproc", path = "./tree-sitter-preproc", version = "=2.0.1" }
+tree-sitter-tcl = { package = "bca-tree-sitter-tcl", path = "./tree-sitter-tcl", version = "=2.0.1" }
 
 # PyO3 powers the `big-code-analysis-py` cdylib. Pinned to a major
 # series; bumping is a deliberate, separate change because the Bound

README.md

@@ -91,7 +91,7 @@ Every tree-sitter grammar is gated behind a per-language Cargo
 feature. The default feature set is `all-languages`, so a bare
 
 ```toml
-big-code-analysis = "2.0.0"
+big-code-analysis = "2.0.1"
 ```
 
 pulls every grammar in (matching the library's historical behaviour
@@ -100,7 +100,7 @@ only need a subset of languages can opt out of the defaults and
 re-enable just the grammars they want:
 
 ```toml
-big-code-analysis = { version = "2.0.0", default-features = false, features = ["rust", "typescript"] }
+big-code-analysis = { version = "2.0.1", default-features = false, features = ["rust", "typescript"] }
 ```
 
 Supported language features: `bash`, `c`, `cpp`, `csharp`, `elixir`,

STABILITY.md

@@ -1,6 +1,6 @@
 # Stability policy
 
-`big-code-analysis` is on the `2.x` line (currently `2.0.0`). The
+`big-code-analysis` is on the `2.x` line (currently `2.0.1`). The
 crate graduated from the rapid-iteration `0.x` window into a written
 stability contract and has now made its first major (`2.0`) break:
 callers can pin a minor version and expect a working tree against any
@@ -31,7 +31,7 @@ pin bump (any `tree-sitter-*` crate in the root `Cargo.toml`) or a
 regression fix in a metric definition is by definition a value
 change but does not break the API surface. Callers who need
 bit-for-bit reproducibility should pin to an exact version
-(`big-code-analysis = "= 2.0.0"`) and store that version alongside
+(`big-code-analysis = "= 2.0.1"`) and store that version alongside
 their results — see [What is stable in value](#what-is-stable-in-value)
 below.
 
@@ -399,7 +399,7 @@ versions, even within `2.x`.** Concretely:
 This is the one deliberate carve-out in the `2.x` contract. The
 *shape* of the data is stable; the *numbers in the cells* are not.
 If you need to compare metric runs across time, pin to an exact
-version (`big-code-analysis = "= 2.0.0"`) and store the version
+version (`big-code-analysis = "= 2.0.1"`) and store the version
 alongside the results.
 
 ### Float precision and non-finite values

big-code-analysis-book/src/library/cargo-features.md

@@ -6,7 +6,7 @@ the default
 
 ```toml
 [dependencies]
-big-code-analysis = "2.0.0"
+big-code-analysis = "2.0.1"
 ```
 
 pulls every grammar in — matching the library's historical
@@ -24,7 +24,7 @@ A downstream service that only analyses Rust and TypeScript:
 
 ```toml
 [dependencies]
-big-code-analysis = { version = "2.0.0", default-features = false, features = ["rust", "typescript"] }
+big-code-analysis = { version = "2.0.1", default-features = false, features = ["rust", "typescript"] }
 ```
 
 The library still compiles, the `LANG` enum still has every

big-code-analysis-book/src/library/quick-start.md

@@ -8,7 +8,7 @@ metrics from a string of source code.
 ```toml
 # Cargo.toml
 [dependencies]
-big-code-analysis = "2.0.0"
+big-code-analysis = "2.0.1"
 ```
 
 The crate uses Rust edition 2024 and pins `rust-version = "1.94"`.

big-code-analysis-book/src/library/stability.md

@@ -1,6 +1,6 @@
 # Stability and versioning
 
-`big-code-analysis` is on the `2.x` line (currently `2.0.0`). The
+`big-code-analysis` is on the `2.x` line (currently `2.0.1`). The
 full stability contract lives in [`STABILITY.md`][stability] at the
 root of the repository — that file is the source of truth and is
 updated alongside the changelog at every release.
@@ -22,7 +22,7 @@ The headlines for library consumers:
   bump or a bug fix in a metric definition can shift any metric
   value on any file in any direction, even across a patch bump.
   Each such drift is flagged in the changelog. Pin to an exact
-  version (`big-code-analysis = "= 2.0.0"`) if you need bit-for-bit
+  version (`big-code-analysis = "= 2.0.1"`) if you need bit-for-bit
   reproducibility across runs.
 - **MSRV is `1.94`.** Bumping the MSRV is treated as a minor-bump
   event and is flagged in the changelog under **(breaking)** —

big-code-analysis-book/src/recipes/ci.md

@@ -103,7 +103,7 @@ so a green-path rerun skips the download entirely:
 
 ```yaml
 env:
-  BCA_VERSION: "2.0.0"
+  BCA_VERSION: "2.0.1"
   BCA_TARGET:  "x86_64-unknown-linux-gnu"
   # sha256 of big-code-analysis-${BCA_VERSION}-${BCA_TARGET}.tar.gz from the
   # release's SHA256SUMS file. Bump together with BCA_VERSION.
@@ -176,15 +176,15 @@ default for downstream adopters.
 - name: Install bca
   uses: taiki-e/install-action@v2
   with:
-    tool: big-code-analysis-cli@2.0.0
+    tool: big-code-analysis-cli@2.0.1
 ```
 
 ```yaml
 # Option 2: cargo-binstall
 - name: Install cargo-binstall
   uses: cargo-bins/cargo-binstall@main
 - name: Install bca
-  run: cargo binstall --no-confirm big-code-analysis-cli --version 2.0.0
+  run: cargo binstall --no-confirm big-code-analysis-cli --version 2.0.1
 ```
 
 If either action falls back to compilation, cache the cargo registry +
@@ -233,7 +233,7 @@ jobs:
       - name: Install bca
         uses: taiki-e/install-action@v2
         with:
-          tool: big-code-analysis-cli@2.0.0
+          tool: big-code-analysis-cli@2.0.1
       - name: Generate report
         run: |
           bca \
@@ -662,7 +662,7 @@ stages:
   - quality
 
 variables:
-  BCA_VERSION: "2.0.0"  # pin a published big-code-analysis-cli release
+  BCA_VERSION: "2.0.1"  # pin a published big-code-analysis-cli release
   BCA_TARGET:  "x86_64-unknown-linux-gnu"
   # sha256 of big-code-analysis-${BCA_VERSION}-${BCA_TARGET}.tar.gz from
   # the release's SHA256SUMS file. Bump together with BCA_VERSION.

big-code-analysis-cli/Cargo.toml

@@ -20,7 +20,7 @@ ignore = "^0.4"
 # The CLI exposes every language `bca` advertises, so it pins the
 # library's full feature set explicitly. Disabling default features
 # here would silently drop grammars from the CLI build. See #252.
-big-code-analysis = { path = "..", version = "=2.0.0", default-features = false, features = [
+big-code-analysis = { path = "..", version = "=2.0.1", default-features = false, features = [
   "all-languages",
   # End-user binary ships every backend that exists; `vcs` is the
   # umbrella turning on `vcs-git` (issue #328).

big-code-analysis-web/Cargo.toml

@@ -18,7 +18,7 @@ futures = "^0.3"
 # pins the library's full feature set explicitly. Disabling default
 # features here would silently drop grammars from the daemon build.
 # See #252.
-big-code-analysis = { path = "..", version = "=2.0.0", default-features = false, features = [
+big-code-analysis = { path = "..", version = "=2.0.1", default-features = false, features = [
   "all-languages",
   # `POST /vcs` change-history endpoint (issue #328).
   "vcs",

codecov.yml

@@ -27,6 +27,17 @@ comment:
 # always runs) and `python` (pytest-cov, only on PRs that touch the
 # bindings). carryforward keeps the python number from vanishing on
 # Rust-only PRs, where the python-test job is skipped.
+#
+# Measurement gap (intentional): the `python` flag measures only the pure-
+# Python surface via pytest-cov. The PyO3 *Rust* layer in
+# big-code-analysis-py/src/ (lib.rs, vcs.rs, node.rs, ast.rs, sarif.rs) is
+# exercised by those same pytest suites, but the crate has no `#[test]`s, so
+# `cargo llvm-cov nextest` (which only runs cargo tests) never instruments
+# it. Its standalone Rust-line coverage therefore reads far lower than it is
+# actually tested — do not "fix" that number by adding redundant cargo tests
+# that re-cover behaviour pytest already drives. Closing it for real means
+# instrumenting the maturin/pytest run and merging that profdata, tracked
+# separately.
 flag_management:
   default_rules:
     carryforward: true

enums/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "enums"
-version = "2.0.0"
+version = "2.0.1"
 publish = false
 authors = ["Calixte Denizet <cdenizet@mozilla.com>"]
 edition = "2024"
@@ -37,11 +37,11 @@ tree-sitter-c = "=0.24.2"
 # Vendored grammar forks — see ../Cargo.toml for rationale on the
 # `package = ...` alias trick that preserves the `tree_sitter_<lang>`
 # import path while the published crate name is `bca-tree-sitter-<lang>`.
-tree-sitter-tcl = { package = "bca-tree-sitter-tcl", path = "../tree-sitter-tcl", version = "=2.0.0" }
-tree-sitter-preproc = { package = "bca-tree-sitter-preproc", path = "../tree-sitter-preproc", version = "=2.0.0" }
-tree-sitter-ccomment = { package = "bca-tree-sitter-ccomment", path = "../tree-sitter-ccomment", version = "=2.0.0" }
-tree-sitter-mozcpp = { package = "bca-tree-sitter-mozcpp", path = "../tree-sitter-mozcpp", version = "=2.0.0" }
-tree-sitter-mozjs = { package = "bca-tree-sitter-mozjs", path = "../tree-sitter-mozjs", version = "=2.0.0" }
+tree-sitter-tcl = { package = "bca-tree-sitter-tcl", path = "../tree-sitter-tcl", version = "=2.0.1" }
+tree-sitter-preproc = { package = "bca-tree-sitter-preproc", path = "../tree-sitter-preproc", version = "=2.0.1" }
+tree-sitter-ccomment = { package = "bca-tree-sitter-ccomment", path = "../tree-sitter-ccomment", version = "=2.0.1" }
+tree-sitter-mozcpp = { package = "bca-tree-sitter-mozcpp", path = "../tree-sitter-mozcpp", version = "=2.0.1" }
+tree-sitter-mozjs = { package = "bca-tree-sitter-mozjs", path = "../tree-sitter-mozjs", version = "=2.0.1" }
 
 [profile.release]
 debug = "line-tables-only"

man/bca-check.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH BCA-CHECK 1  "big-code-analysis 2.0.0" "big-code-analysis Manual"
+.TH BCA-CHECK 1  "big-code-analysis 2.0.1" "big-code-analysis Manual"
 .SH NAME
 bca\-check \- Check per\-function metrics against thresholds. Exits 2 when any threshold is exceeded; reserve exit 1 for tool errors so CI can distinguish "metric regression" from "tool crashed". `\-\-strict\-exit\-codes` opts into tiered codes (2\-5) that split the violation case by severity
 .SH SYNOPSIS