Add same-net trace segment alignment

[trigga6006]

/claim #29
/claim #34

Summary

• Add a final TraceCleanupSolver phase that aligns nearby overlapping internal H/V segments sharing the same globalConnNetId.
• Preserve endpoint-only segments so pin anchors do not drift.
• Reject candidate alignments that would introduce intersections with different-net traces.
• Add focused regression tests for same-net alignment, different-net no-op, endpoint preservation, and collision rejection.

This covers both:

• New Phase To combine same-net trace segments that are close together #29: combine same-net trace segments that are close together
• Merge same-net trace lines that are close together (make at the same Y or same X) #34: merge same-net trace lines close together onto the same Y or same X

Verification

• bun test tests\solvers\TraceCleanupSolver\alignNearbySameNetSegments.test.ts tests\examples\example29.test.ts tests\examples\example34.test.ts
• bun test
• bunx tsc --noEmit
• bun run build
• git diff --check

Note: bun run format:check failed locally on the repo-wide baseline CRLF/LF formatting mismatch across existing files; touched files were formatted with Biome directly. Remote CI format-check passes on this PR.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
schematic-trace-solver	Ready	Preview, Comment	May 26, 2026 10:45pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 44d4e912d9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Prevent same-net alignment from routing through obstacles

This acceptance path only verifies orthogonality and intersectsDifferentNet, so the new alignment phase can move a segment through chip/box obstacles (and other non-trace blockers) without being rejected. Earlier cleanup passes explicitly validate against static obstacle rectangles and label bounds, but this phase omits those checks entirely; in a layout where two same-net segments are close on opposite sides of a component, the shorter one can be snapped across the component and still be accepted.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Reject self-intersecting candidate paths before applying

Checking only isOrthogonalPath is insufficient here: an orthogonal path can still self-intersect after moving an internal segment. Because the subsequent collision filter skips traces with the same mspPairId, the candidate is never tested against non-adjacent segments of its own trace, so a zig-zag trace can be transformed into a self-crossing polyline and committed.

Useful? React with 👍 / 👎.