docs(hooks): cite run-standards.sh blocks by name, not by line number

[twistedmelonman]

Fixes the inconsistency caught by the merge reviewer on #347 and filed as #348: pre-commit/config.yaml cited run-standards.sh:157-161 while lint-yamllint.sh and its test cited 147-150, for the same upstream code.

Both were right, against different revisions

147-150 was correct before smartwatermelon/github-workflows#172 added the canonical shellcheck block above it. 157-161 was correct after. The loop now begins at line 158 — so the citation moved twice within a day, once while this very session was working on it.

That is the real finding, and #348 named it precisely: "a stale line-number citation is the kind of label that reads as authoritative while resolving to the wrong code." It is the same class of defect as a pinned SHA with a stale # v3 comment — the label keeps looking correct long after it stops resolving.

Fix

All five citations now name the block rather than its coordinates — "the yamllint config block in run-standards.sh". That does not drift when unrelated code is inserted above, and unlike a line number it is greppable in the upstream checkout.

The markdownlint citation at config.yaml:154 had already drifted the same way — 193-197 now lands on the block's header comment rather than the merge logic it claims to cite — so it is corrected in the same pass rather than left to be rediscovered.

Verification

Comments only, no behaviour change. Test suite still 8/8. shellcheck -S info clean under the newly-merged canonical standards/shellcheckrc (with a known-bad gate confirming shellcheck actually ran) — this is the first dotfiles change linted against that config since #172 landed.

Closes #348.

https://claude.ai/code/session_011awg91UvzUos9YoXHJ2e8B

[claude]

All changes are comment-only: stale line-number references replaced with descriptive prose. No executable code, conditions, data paths, or error handling were touched.

VERDICT: PASS