Rule text alone cannot guarantee enforcement because developers can still misinterpret or bypass the intent without mechanical checks. The FVC 32 false‑ship pattern demonstrates this by allowing a branch to be reported as pushed successfully while it never actually appears on the remote origin. The FVC 34 footer‑not‑fenced pattern shows how a usage block can slip outside a code fence, undermining the kit’s formatting requirements. The new tools—align‑check.sh, verify‑push.sh, and check‑footer.sh—automatically validate alignment, confirm that pushes reach the origin, and enforce that footers are properly fenced, thereby closing both gaps.