Hardware Testing Rack can now put each board's design rule checking (DRC) policy into its generated KiCad project. A board definition chooses whether a named layout check is an error, a warning, or ignored, and the generator writes that choice into the board's .kicad_pro file for KiCad to enforce.
The defensive behavior matters more than the configuration option. The generator always treats dangling tracks and vias, the plated holes that connect copper layers, as errors. It also stops if a board names a check that the project file doesn't contain or supplies an unknown severity. KiCad would otherwise skip an unrecognized setting without saying so, leaving a team to believe a rule ran when it did not.
No board in the repository uses the new override yet, so this is infrastructure rather than proof that the policy catches a product defect. Even so, it gives generated boards a reviewable test policy instead of relying on whichever settings happen to be open on an engineer's workstation. The first team to adopt it should change one rule deliberately and archive KiCad's report in continuous integration, proving both the pass and failure paths.