docs: the skill and the README caught up with 0.7.0

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, and a7276e6 two releases back. The version names a file; only the
sha names the code. Both now cite 10ad125.

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.

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "repo-standard",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Per-repo gate for the open/ presentation standard: README first screen, install block, files required by the repo's class, and dead repo references.",
   "author": {
     "name": "Kjell Tore Guttormsen"

CHANGELOG.md

@@ -4,6 +4,32 @@ All notable changes to this project are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
 versioning is [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.1] — 2026-08-09
+
+### Fixed
+
+- The skill told a reader what a `SKIP` finding means and stopped there, which
+  was complete before 0.7.0 and is not now: a repo can headline `OK · 3 not
+  checked`, and a session reporting only the status word would report a green
+  pass over three unjudged findings. `SKILL.md` now requires the status and the
+  count to be reported together. Shipping 0.7.0 without this made the plugin
+  whose purpose is catching stale published documents ship one.
+
+- README's example output carried commits older than the behaviour they
+  demonstrate — one from 0.6.0 beside a `notChecked` that did not exist in it,
+  one two releases back. This repo's own invariant is that the version names a
+  file and only the sha names the code; the examples now cite `10ad125`, the
+  commit the feature actually shipped in.
+
+### Added
+
+- README states the unit of `notChecked`: it counts un-judged **findings**, not
+  checks. A repo with many links leaving it scores a high count without a single
+  check having failed to run, so the bare number reads worse than the repo is.
+  Named as a known limitation rather than corrected in the string — the fix is
+  splitting *deliberately not judged* from *could not run*, which is its own
+  release.
+
 ## [0.7.0] — 2026-08-09
 
 ### Changed

README.md

@@ -10,7 +10,7 @@ checks that surface in one repository and reports what it finds.
 
 *AI-generated: all code produced by Claude Code through dialog-driven development.*
 
-![Version](https://img.shields.io/badge/version-0.7.0-blue)
+![Version](https://img.shields.io/badge/version-0.7.1-blue)
 ![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
 ![Skills](https://img.shields.io/badge/skills-1-orange)
 ![License](https://img.shields.io/badge/license-MIT-lightgrey)
@@ -91,10 +91,16 @@ it on its own axis: `notChecked` in `--json`, and a qualifier on the summary
 line, so a pass that had checks it could not run never prints unqualified.
 
 ```
-✓ okr [plugin] — OK · 1 not checked  (repo-standard v0.7.0 @5884a64)
-· stranger — SKIP · 1 not checked    (repo-standard v0.7.0 @5884a64)
+✓ okr [plugin] — OK · 1 not checked  (repo-standard v0.7.0 @10ad125)
+· stranger — SKIP · 1 not checked    (repo-standard v0.7.0 @10ad125)
 ```
 
+The count is **findings**, not checks — one per un-judged item, the same list the
+detail output prints under `NOT CHECKED`. A repo with many links leaving it
+scores a high `notChecked` without a single check having failed to run, which is
+why the next thing this number needs is to distinguish *deliberately not judged*
+from *could not run*.
+
 ### Traits — a second axis
 
 Class is structural. A **trait** is about what the code does, which no remote can
@@ -197,7 +203,7 @@ The header and the `--json` output carry the engine's version *and* the commit
 it ran from:
 
 ```
-✓ voyage [plugin] — OK  (repo-standard v0.7.0 @a7276e6)
+✓ voyage [plugin] — OK  (repo-standard v0.7.0 @10ad125)
 ```
 
 Both, because they answer different questions. A stale plugin cache once served

package.json

@@ -1,6 +1,6 @@
 {
   "name": "repo-standard",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "private": true,
   "type": "module",
   "engines": {

skills/repo-standard/SKILL.md

@@ -34,6 +34,13 @@ register against the live org listing.
 to judge — an unreachable forge, an untagged repo, a link leaving the
 repository. Say which.
 
+That applies hardest when the repo's own status is green. Since 0.7.0 a `SKIP`
+no longer outranks an `OK` in the status line, so a repo reads
+`OK · 3 not checked` rather than `SKIP`. The number is the qualifier: three
+findings nobody judged. Report the status and the number together, never the
+status alone, and name what went unjudged — the detail output lists them under
+`NOT CHECKED`.
+
 **Confirm the version before you trust a green run.** Measured 2026-08-04:
 `${CLAUDE_PLUGIN_ROOT}` resolved to a cached `0.1.1` in a live session while
 `0.2.0` was installed and the catalog pinned it — same instruction, same