open/repo-standard
1
0
Fork 0
Code Issues Releases 2 Activity

docs: correct test count from 103 to 111

Browse source 
npm test currently reports 111, not 103 — the number went stale as
tests were added. Caught by catalog's coord message after measuring
the v0.2.2 tag directly (git-archive extraction, not the worktree).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WB6C8cJLHo3PF2BLPVb5qt
This commit is contained in:
Kjell Tore Guttormsen 2026-08-04 21:53:58 +02:00
commit ca81db549c
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
CLAUDE.md
View file

@ -77,7 +77,7 @@ would recreate, in data, exactly the drift this plugin exists to remove.
## Commands
```bash
npm test # 103 tests
npm test # 111 tests
node scripts/repo-standard-check.mjs --dir "$PWD" # gate one repo
node scripts/repo-standard-check.mjs --offline # no network call
node scripts/repo-standard-check.mjs --json # machine output

2
README.md
View file

@ -167,7 +167,7 @@ without that, a raw scan turns three dead names into about twenty.
npm test
```
103 tests over the pure classifiers. The reference fixtures are measured false
111 tests over the pure classifiers. The reference fixtures are measured false
positives, each with its expected verdict — the six that produced the
three-outcome reference rule, plus the noise sources found by running the gate
against a real repository: regexes inside code spans that are markdown links to