rule-observance: report which clauses have a program behind them (Refs #2622)

[gHashTag]

Read LOOP-RULES.md properly instead of the three clauses a regex could reach, and checked every one that can be checked at all [measured]:

clause	enforced by	observed
R1 — cost output format	the tool itself	yes
R5 — a tool whose number reaches a report is committed	loop-tools-tracked.sh	yes (it refused my new command until git add)
R6 — the seal certifies identity, not correctness	tri loop-rules	yes, stated in its own output
R10 — an absent check is not a passing check	check_pr_branch_filters.py	yes
R15 — six categories, unchanged ≠ "could not compare"	diffbin, at runtime	yes
R0 — tick ledger at cron_tracking/	nothing	has never existed anywhere
R11 — branch prefix w699-<topic>	nothing	0 of 30
R11 — provenance tag on a number	nothing	1 of 25

The split is total. Not "mostly".

R15 makes the point about its own enforcement:

"The set must be asserted to partition the corpus at runtime; claiming it in a docstring is not a check."

diffbin.py:458 sums the six categories against the file total and errors on mismatch. The rule anticipated that a rule about categories, kept only in prose, would drift — and the three clauses at zero are the ones that took their own advice least.

So this is not carelessness by anyone. A rule kept in a document is a wish; a rule kept in a program is a rule, and this file holds both kinds under one heading, indistinguishable to a reader and equally sealed by a checksum that certifies neither.

Suggested to the owner in #2622 as a fourth option: mark each clause with what enforces it, so a clause with an empty column is visibly a wish rather than silently one.

Still reports, still does not gate. §105.

Refs #2622

[github-actions]

📓 NotebookLM Notebook linked to this PR

• Notebook ID: b83263109fb055dc
• URL: https://notebooklm.google.com/notebook/b83263109fb055dc

This notebook contains session context, decisions, and artifacts for this work.

[github-actions]

PR Dashboard

Generated at: 2026-08-23 22:53:48 UTC

• rule-observance: report which clauses have a program behind them (Refs #2622) #2625 rule-observance: report which clauses have a program behind them (Refs #2622) | Created: 2026-08-23 | Updated: 2026-08-23 | 17 failing / 22 total
• Unbreak FPGA CI and correct two unbacked hardware claims #2081 Unbreak FPGA CI and correct two unbacked hardware claims | Created: 2026-08-11 | Updated: 2026-08-20 | 5 failing / 27 total

Summary

Status	Count
Total Open PRs	2
PRs with Failing Checks	1
PRs with All Checks Green	1
READY	0
FAILING	1
PENDING	0

Seal Status

• ⚠️ STALE -- sha256(compiler.rs)=e6333575ec10 != manifest seal=87e5cbd3ad94.
  The committed NMSE numbers were certified against an older compiler.rs.
  Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).