Three published documents went out with 0.7.0 unread. SKILL.md told a reader what a SKIP FINDING means and stopped there. Complete before 0.7.0, not now: a repo can headline `OK · 3 not checked`, and a session reporting the status word alone would report a green pass over three unjudged findings. Status and count are now required together. Shipping without this made the plugin whose purpose is catching stale published documents ship one. README's example output cited commits older than the behaviour they demonstrate —5884a64(0.6.0) beside a `notChecked` that did not exist in it, anda7276e6two releases back. The version names a file; only the sha names the code. Both now cite10ad125. README also now states the unit: `notChecked` counts un-judged FINDINGS, not checks. portfolio-optimiser's `11 not checked` is almost entirely LINK-OUTSIDE-REPO, so the bare number reads worse than the repo is. Named as a known limitation, not corrected in the string — the fix is splitting "deliberately not judged" from "could not run", which is the next release.
12 lines
195 B
JSON
12 lines
195 B
JSON
{
|
|
"name": "repo-standard",
|
|
"version": "0.7.1",
|
|
"private": true,
|
|
"type": "module",
|
|
"engines": {
|
|
"node": ">=18"
|
|
},
|
|
"scripts": {
|
|
"test": "node --test scripts/*.test.mjs"
|
|
}
|
|
}
|