[FIX] REVIEWED-131: build PENDING-165 (d) as an allowlist, then (b) narrowly

(d) — governance-drift-check.py now DECLARES the contents of ~/dotfiles/git/hooks
(README.md, pre-commit) and reports anything unexpected or declared-but-missing.
Tracked-ness is never consulted, and that is the correction: the filed form tested
"neither tracked nor pre-commit", and 066a47a was TRACKED for four weeks, so it
would have been silent throughout the only occurrence that did damage. Asserted
structurally, not in prose — a control checks that scan_hooks' code names contain
neither "git" nor "subprocess".

(b) — .gitignore for the four git-lfs shim names. DELIBERATELY NARROW: a blanket
git/hooks/* + allowlist would silently prevent committing a new legitimate hook,
which would work locally, never reach the repo, and be invisible to (d) because
(d) reads the filesystem and not the index. Verified the pair composes: a planted
shim yields 0 entries in git status AND is reported UNEXPECTED by the check.

⚠ And a fifth self-referential instrument event, in the fix for that very class.
The five new controls were appended after failed_controls is computed (702 vs
846): all ran, none counted, tally still read 48/48, and a failure among them
would have printed NOTHING. The check against blind checks was blind to itself.
Caught by comparing the printed tally to the number of controls added. Moved above
the report block (53/53) and verified by breaking one deliberately and confirming
it prints INSTRUMENT NOT VERIFIED and names itself.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NvZAKSf9aqratbqHbU9LK5

claude/memory/session-ledger-2026-08-26.md

@@ -40,6 +40,16 @@ type: feedback
   ignoring them would hide the pollution instead of surfacing it. ⚠ Care did not prevent the
   second occurrence; I had cleaned the first one two hours earlier.
 
+- 2026-08-26T~night — ⚠ **FIFTH self-referential instrument event, and it was in the fix
+  for the class.** The new hook-allowlist controls were appended AFTER `failed_controls` is
+  computed (line 702 vs 846), so all five ran, none was counted — the tally still read
+  `48/48` — and **a failure among them would have printed nothing.** I built the check
+  against *blind checks* with a check blind to itself, in the same hour, immediately after
+  the jurist caught the previous blindness in the same item. Caught only because I compared
+  the printed tally against the number of controls I knew I had added. Fixed by moving the
+  section above the report block (`53/53`), then **verified by deliberately breaking one new
+  control and confirming it now prints INSTRUMENT NOT VERIFIED and names itself.**
+
 ## What held
 
 - Ran `thread-query.py` on the actual thread and reported the **null honestly** (689 candidates,