open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Releases Activity

docs(catalog): verify the ungated-values claim on the catalog side too

Browse source 
"No ungated ref has moved since its audit" only proves the badge source is
unchanged. Catalog prose is itself ungated, so an ungated stat value could have
been restated by any commit with nothing catching it — which would have made
the no-re-measurement justification false.

Checked by diffing extractCatalogStats against README.md at db1e80b (08-02):
the only ungated numbers the catalog has restated since are repo-standard's two,
absent then and measured 08-04. The claim holds; it is now stated as a two-sided
verification rather than a one-sided inference.

Sharpens the 251-selftest-checks flag with what that diff also showed: the
catalog's own 08-02 stat line already said 370, so two independent records agree
on 370 and check-versions.mjs's 374 reads as a transcription slip.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PtnSwCLpUR3Hk8SHkPoxX4
This commit is contained in:
Kjell Tore Guttormsen 2026-08-04 21:46:38 +02:00
commit 7e7e060b67
1 changed files with 11 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

19
CLAUDE.md
View file

@ -49,14 +49,17 @@ their own Forgejo repositories under `https://git.fromaitochitta.com/open/`.
repo-standard entered the catalog (`+1` gated, `+2` ungated). The 15 ungated axes were hand-audited
at their pinned tags — 13 on 2026-08-02 (**14 of that pass's 15 were exact**; the defects were
repo-mailbox `6 CLI scripts` (true 8) / `251 selftest checks`, and voyage `500+ tests` against a
measured 832), and repo-standard's two on 2026-08-04. Since no ungated plugin's ref has moved
since its audit, every ungated value currently stands measured at the ref it is pinned to.
**⚠️ The `251 selftest checks` correction is itself unresolved and must not be cited as settled:**
three records disagree on the true value at v0.19.0 — this file said 370, `check-versions.mjs`
said 374, and repo-mailbox's own README at that tag implies 390 (`183 + 134 + 73`). It is moot for
the gate (repo-mailbox badges the axis now, 398 at v0.20.2, green) and was **not** re-measured
2026-08-04. It stands as the standing proof of the cost: an ungated number rots, and so does the
record of having fixed it.
measured 832), and repo-standard's two on 2026-08-04. Every ungated value currently stands measured
at the ref it is pinned to — verified on **both** sides 2026-08-04, because a ref that has not moved
only proves the *badge source* is unchanged and catalog prose is itself ungated: no ungated plugin's
ref has moved since its audit, **and** diffing `extractCatalogStats` against the 08-02 README shows
the only ungated numbers the catalog has restated since are repo-standard's two (absent then).
**⚠️ The `251 selftest checks` correction is not fully settled**, though the weight is on 370: this
file *and* the catalog's own 08-02 stat line both record the axis as corrected to 370,
`check-versions.mjs` said 374 (most likely a transcription slip), and repo-mailbox's README at
v0.19.0 implies 390 (`183 + 134 + 73`) — its own prose being ungated too. Moot for the gate (they
badge the axis now, 398 at v0.20.2, green) and **not** re-measured. It stands as the proof of the
cost: an ungated number rots, and so does the record of having fixed it.
`N+` in the catalog is read as a lower bound, not an equality, so `500+` was never gate-visible —
ungated axes rot in silence and need a re-run of this pass **whenever a ref moves**. **Never
hand-edit a stat line to silence the gate** — the plugin's badge is the source for every stat