CB-WP-0005 T01: spec->code link over every numbered spec and every crate

AGGREGATE becomes a list of source roots and rule patterns become
per-spec, so the link runs over every numbered spec x every crate rather
than GroundRules.md x games/ground/src/lib.rs.

The prediction held on the first run:

  AM-1b kernel spec->code link: 15/18 (83%) across 10 source files
    unlinked: K10 K14 K18

Kernel rules are link-only by design, and the output says so: they are
kernel invariants with no aggregate, setup preset or command vocabulary,
so scenarios/kernel/*.yaml with covers: [K11] would be a tag in a
directory the runner cannot dispatch. Claiming scenario coverage for them
is the inflation this gate exists to prevent.

Per ADR-0005 §5 the kernel arm reports without feeding the exit code
until 2026-08-31, then binds — the date in the tool, not in prose, with
days remaining printed every run, because open-ended "gate it later" is
how AM-4's targets went unratified for four workplans. The self-test
asserts the gate returns 0 before that date and 2 after.

The zero-rules positive control is replicated on the new denominator: a
kernel regex that stops matching aborts rather than printing 0/0 as
though it were 100%.

The self-test passed while the tool was completely broken. A print(
inside say() became say(), so every real `make coverage` died with
RecursionError while --self-test reported all-ok — it only ever called
kernel_arm(quiet=True) and never executed the reporting path. The control
named the behaviour and did not assert it, which is precisely what this
workplan is about. Fixed by exercising the loud path and asserting it
prints, then verified by re-breaking say() and confirming both new checks
go red. Seventh instance of the harness-does-nothing shape, in the tool
written to find that shape.

Also caught by its own gate: a self-test label that printed "0 K-ids"
beside a passing ">5" assertion, because the detail string rebuilt the
pattern with different escaping. A label that contradicts its own check
is worse than no label.

k_rules, k_linked and k_unlinked are registered facts under facts-check.
A limit of that checker is recorded rather than patched: it is
line-based, so a tagged value that prose-wraps fails.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

specs/MetricsAndScenarios.md

@@ -45,7 +45,34 @@ and add capability-specific rows only when these don't cover the claim.
 | M-D4-LEAK | D4 | foreign types in canonical interfaces | count | novel — must be 0; enforced by grep/deny rule, the Clay-Borg hard rule |
 | M-D4-SWAP | D4 | capability has null + reference impls passing the same conformance suite | bool | adapted:hexagonal-architecture port testing |
 
-### 1b. The coverage gate's two numbers (M-D1-COV, M-D1-LNK)
+### 1b. The coverage gate's numbers (M-D1-COV, M-D1-LNK)
+
+> **Widened 2026-07-31 (CB-WP-0005 T01).** Until then the instrument
+> matched `GR-` only, against `GroundRules.md` only, and linked against
+> one source file, so all **18** K-rules were outside it. <!-- fact:k_rules -->
+> `58/58 (100%)` read as "all rules".
+>
+> `make coverage` now reports a second, separate denominator:
+> **15 of 18** K-rules are named across the source. <!-- fact:k_linked -->
+> Unlinked: **K10 K14 K18**. <!-- fact:k_unlinked -->
+>
+> **Kernel rules are link-only, by design.** They are kernel invariants,
+> not game rules: there is no kernel aggregate, setup preset or command
+> vocabulary, so a `scenarios/kernel/*.yaml` carrying `covers: [K11]`
+> would be a tag in a directory the runner cannot dispatch. Claiming
+> scenario coverage for them would be the inflation this gate exists to
+> prevent.
+>
+> Per ADR-0005 §5 the kernel arm **reports without feeding the exit
+> code until 2026-08-31**, then binds. A newly widened denominator is not
+> a regression. The date lives in `tools/rule-coverage.py`, not here, and
+> the tool prints the days remaining on every run.
+
+**Both numbers count names.** Neither proves anything fails when a rule is
+violated. That is **M-D1-MUT** (`make mutation-check`, CB-WP-0005 T02) —
+four of the seven defects found by CB-RES-0004 were named in the source
+and inert, and therefore invisible to everything on this page.
+
 
 M-D1-COV counts tags. It proves no rule is unclaimed and no claimed rule
 is invented; it does **not** prove a scenario exercises what it names, and