docs(readme): trim the badge row to five, recolor the selftest count
repo-standard's presentation check flagged two WARNs. Both land on the badge row, and one of them collides with a decision made yesterday. BADGE-STATIC-CLAIM: green is CI idiom for "passing", and this repo has no CI by design (a stated non-goal — the forge has no runner). Linking the badge to a real run is therefore impossible, but DROPPING it is not free either: the catalog's stat-mirror gate is per-axis and badge-gated, so an unbadged axis is skipped silently and the number it protects can rot again (measured 6 and 251 against a true 8 and 398). The badge stays and turns blue, which reads as a count rather than a pass state. The catalog parser splits label/value/color and ignores the color, so the gate is unaffected. BADGE-COUNT: seven badges, past the point a row reads as clutter. Five of them are load-bearing — version is ERROR-gated by the catalog, and hooks/skills/CLI scripts/selftest checks are the four axes it mirrors. Platform and License are not: the first restates the opening line, the second restates the License section that already links LICENSE. Dropping those two lands exactly on five without ungating anything. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015bWgoaf46fu6DagYQyDVR5
This commit is contained in:
parent
cbcd236050
commit
ddc978d4c1
1 changed files with 1 additions and 3 deletions
|
|
@ -11,12 +11,10 @@ Session A in repo X leaves a message for repo Y; the next session in repo Y gets
|
|||
*AI-generated: all code produced by Claude Code through dialog-driven development.*
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue