feat: Add SameNetTraceMergeSolver for issue #29

[Wong789]

/claim #29

Summary

This PR implements a new pipeline phase (SameNetTraceMergeSolver) that combines same-net trace segments that are close together, as described in issue #29.

Changes

1. New Solver: lib/solvers/SameNetTraceMergeSolver/SameNetTraceMergeSolver.ts

   • Identifies parallel segments (same direction, within GAP_THRESHOLD of 0.15)
   • Merges segments that share the same mspPairId
   • Runs as a new phase after raceCleanupSolver

2. Pipeline Integration: Updated SchematicTracePipelineSolver.ts

   • Added sameNetTraceMergeSolver step after raceCleanupSolver
   • The solver processes traces after cleanup and before final label placement

3. Tests: lib/solvers/SameNetTraceMergeSolver/SameNetTraceMergeSolver.test.ts

   • Tests for merging parallel same-net traces within gap threshold
   • Tests ensuring different nets are not merged

How It Works

The solver:

1. Extracts segments from all traces
2. Groups parallel segments (horizontal or vertical) that are within GAP_THRESHOLD (0.15)
3. For segments that share the same mspPairId, combines them into a single longer segment
4. Returns the merged trace set

Bounty

This PR claims the ** bounty** for issue #29 (New Phase To combine same-net trace segments that are close together).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
schematic-trace-solver	Error		Apr 18, 2026 6:03am

[Wong789]

Hi @seveibar, my Vercel preview deployment seems to be failing (dpl_HgCtUaNweHs5cxoJ8pcmKbLRMaPg). I don't have access to the Vercel dashboard to check the logs. Could you help investigate, or is there anything I can do from my side to fix this? Thank you!