feat: merge same-net collinear trace segments

[singhaditya21]

Summary

Fixes #34

/claim #34

• Added mergeCollinearTraces() in lib/utils/mergeCollinearTraces.ts that groups SolvedTracePath traces by globalConnNetId, finds horizontal/vertical segments sharing the same constant coordinate, and merges overlapping or adjacent 1-D intervals into a single longer segment.
• Integrated the function into SchematicTracePipelineSolver.getOutput() so callers automatically receive deduplicated traces without any pipeline restructuring.
• Added 8 unit tests covering overlapping horizontal segments, adjacent (touching) segments, vertical segments, three-way merges, multi-segment traces, cross-net isolation, and an end-to-end integration scenario.

How it works

The algorithm:

1. Groups all input traces by globalConnNetId.
2. Extracts every axis-aligned segment from each trace.
3. Buckets horizontal segments by Y-coordinate and vertical segments by X-coordinate.
4. Within each bucket, sorts by the interval start and greedily merges overlapping/adjacent intervals.
5. The "winning" trace absorbs the extended interval; the "absorbed" trace is either fully removed or trimmed to its non-overlapping portion.
6. Repeats until no further merges are possible.

Test plan

• bun test tests/functions/mergeCollinearTraces.test.ts — all 8 new tests pass
• bunx tsc --noEmit — no type errors
• bun test — all 79 pre-existing tests still pass (4 pre-existing skips; 1 unrelated pre-existing failure in an untracked file from another branch)

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
schematic-trace-solver	Ready	Preview, Comment	Jun 26, 2026 4:42pm

[singhaditya21]

Friendly nudge 🙂 — CI is green and this is mergeable whenever you have a moment. Happy to rebase or address any feedback if it helps. Thanks for the great project!