JSON Bug Report: long trace instead of netlabel

[mohan-bee]

Solver input JSON attachment

_board#1332 _-SchematicTracePipelineSolver-solver-input.json

Notes

No response

[tscircuitbot]

Created or updated #671 for this JSON bug report.

Report id: bug-report-20260716T144856Z

[DPS0340]

Root-caused and fixed in #702: LongDistancePairSolver was bridging distant pins on labeled rails (V3_3/GND) with 9-13 unit bus traces even though MspConnectionPairSolver had deliberately left them label-connected (beyond maxMspPairDistance). Labeled nets with >2 pins now cap long-distance neighbor candidates at maxMspPairDistance, so distant rail pins keep their net labels. Regression test with this board's input included.