New tools/verify_rules.py is billed as per-board manufacturability verification but fails open: if router analyze fails or returns no nets, the width loop skips every trace and prints 0 below required width instead of not checked; it checks file existence, not return codes, and never clears last run's report JSONs, so a failed route can be scored against an old board's report, and main() always exits 0 even with illegal DRC or failed RF/thermal validators.