Nicolas Le Cam 976a1d7630 docs(config): scope the exclude_commands coverage claim to what is peeled ...

`configuration.md` said an excluded tool "is covered however it is invoked".
The stated limits then covered only tools without their own filter, and exactness
— leaving three invocation forms of *filtered* tools promised but not delivered.

Scope the sentence to the wrapper, interpreter and path spellings that are
actually peeled, and table the three that are not, each with its cause:

- `head -20 f` / `tail -n 5 f` — the line-range fast path returns before the
  exclusion is consulted (#2823); `head f` is excluded normally
- `gradlew.bat build` / `mvnw.cmd test` — path stripping splits on `/`, so a
  `.bat`/`.cmd` spelling never reduces to the tool name (#3617)
- `golangci run ./...` — `golangci run` is one of the rule's own aliases and is
  kept whole, so it misses a `golangci-lint` entry

Each row verified against a build on `develop` at e533c40, including the
documented workaround: `["golangci"]` excludes the alias form but not
`golangci-lint run`, so both entries are needed.

Docs only, no behaviour change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-01 12:42:04 +02:00

..

configuration.md

docs(config): scope the exclude_commands coverage claim to what is peeled

2026-09-01 12:42:04 +02:00

installation.md

docs: scope savings claims to bash output and document the estimator

2026-07-22 18:33:54 +02:00

quick-start.md

docs: revert internal and low-value files, drop the two-estimator table

2026-07-22 19:02:16 +02:00

supported-agents.md

fix(vibe): address PR review — exit code contract, tests, telemetry, docs

2026-08-05 13:55:09 +02:00