What
The #meta-block anchor is referenced by 3 consumers across the plugin instruction files, but no host heading exists that yields that slug — the fragment is dangling (file-existence link tests pass; fragment resolution is untested).
Surfaced during the wake/idle ordering-hardening PREPARE sweep (anchor/cross-ref inventory over pact-plugin/**/*.md), where it was ruled out-of-scope drift (pre-existing, not co-located with the edited sections).
Fix sketch
Either:
- Add the missing host heading (e.g.
### META-BLOCK) at the canonical META-BLOCK definition site in protocols/pact-completion-authority.md — NOTE: that file is a byte-compared extract; the heading must land in the same commit in its pact-protocols.md SSOT region (scripts/verify-protocol-extracts.sh gates it), or
- Re-point the 3 referrers at an existing heading's slug.
Option 1 preferred: the referrers' intent is "the META-BLOCK rule", which deserves a stable anchor.
Acceptance criteria
What
The
#meta-blockanchor is referenced by 3 consumers across the plugin instruction files, but no host heading exists that yields that slug — the fragment is dangling (file-existence link tests pass; fragment resolution is untested).Surfaced during the wake/idle ordering-hardening PREPARE sweep (anchor/cross-ref inventory over
pact-plugin/**/*.md), where it was ruled out-of-scope drift (pre-existing, not co-located with the edited sections).Fix sketch
Either:
### META-BLOCK) at the canonical META-BLOCK definition site inprotocols/pact-completion-authority.md— NOTE: that file is a byte-compared extract; the heading must land in the same commit in itspact-protocols.mdSSOT region (scripts/verify-protocol-extracts.shgates it), orOption 1 preferred: the referrers' intent is "the META-BLOCK rule", which deserves a stable anchor.
Acceptance criteria
#meta-block(or the replacement slug) resolves to a real heading in every referring file's targettests/test_wake_ordering_pinned.pystyle so the anchor cannot silently dangle again