obstacle_map.resolve_hole_clearance (#616) reads the board's declared
min_hole_clearance for add_drill_hole_obstacles and
plane_obstacle_builder, and its docstring names the engines it does NOT
cover: plane_region_connector (taps / region joins / reconnects),
pcb_modification, and placement/fanout_clearance still hardcode
NPTH_TO_TRACK_CLEARANCE. On a board declaring above 0.20 those paths route
into a band check_drc now flags (measured on neo6502: 0.2263 mm against a
declared 0.25). The helper exists and is cached; each site is a one-expression
change, best made engine-by-engine with a pinning test per engine.
obstacle_map.resolve_hole_clearance(#616) reads the board's declaredmin_hole_clearanceforadd_drill_hole_obstaclesandplane_obstacle_builder, and its docstring names the engines it does NOTcover:
plane_region_connector(taps / region joins / reconnects),pcb_modification, andplacement/fanout_clearancestill hardcodeNPTH_TO_TRACK_CLEARANCE. On a board declaring above 0.20 those paths routeinto a band
check_drcnow flags (measured on neo6502: 0.2263 mm against adeclared 0.25). The helper exists and is cached; each site is a one-expression
change, best made engine-by-engine with a pinning test per engine.