fix(check-versions): mirror stats against the pinned ref, not the working tree [skip-docs]
Found live minutes after shippingfc95cbd: llm-security went ERROR on scanners (23 vs 22) and tests (2013 vs 2034). The catalog was RIGHT and the gate was wrong. llm-security had committed past its v7.8.3 tag without bumping the version, and the gate was reading the sibling working tree — but the catalog documents what INSTALLS, and `ref: v7.8.3` still installs 23/2013. Stat badges are now read with `git show <ref>:README.md`, falling back to the working tree only when the ref cannot be read (a ref resolving to nothing is already its own ERROR, so the fallback cannot hide a dangling ref). The version-badge check is unchanged and still reads the working tree: that one is about the plugin's internal consistency, not about what the catalog promises. This also corrects a stat I got wrong infc95cbd. I had moved config-audit from 1410 to 1441 tests off the working tree; at the pinned v5.13.0 the badge says 1398. 1441 is unreleased. The catalog now says 1398 — what installs. [skip-docs]: CLAUDE.md carries the rule and the "check `git show <ref>:README.md` before believing the working tree" instruction; README.md changes by one number because the gate was wrong about it. Tests 117 -> 120 (+3, all regression). Gate green at 11 OK / 0 WARN / 0 ERROR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RDSiMcgLMpEETwtkc86Nym
This commit is contained in:
parent
c6c82b358e
commit
780f86ec9f
4 changed files with 63 additions and 6 deletions
|
|
@ -47,3 +47,9 @@ their own Forgejo repositories under `https://git.fromaitochitta.com/open/`.
|
|||
(repo-mailbox's read `6 CLI scripts` / `251 selftest checks` against a true 8 / 374). `N+` in the
|
||||
catalog is read as a lower bound, not an equality. **Never hand-edit a stat line to silence the
|
||||
gate** — the plugin's badge is the source for every stat number; fix the catalog to match it.
|
||||
- **The stat mirror reads the plugin README AT THE PINNED `ref`, never the sibling working tree.**
|
||||
The catalog documents what *installs*, and that is the tag. A plugin that commits past its tag
|
||||
without bumping its version — measured 2026-08-02 on both llm-security (scanners 23→22, tests
|
||||
2013→2034) and config-audit (tests 1398→1441) — would otherwise make the gate demand that the
|
||||
catalog restate unreleased numbers, which is exactly backwards. **When the gate flags a stat,
|
||||
check `git show <ref>:README.md` in the plugin repo before believing the working tree.**
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue