fix(solvers): relocate net labels sitting inside chip obstacles in NetLabelNetLabelCollisionSolver

[rudra496]

Summary

Fixes #655.

Previously, `NetLabelNetLabelCollisionSolver` only initiated candidate search when a label collided with another net label (`findNextCollidingPair`). A net label that sat inside a chip body without colliding with any other label was never evaluated against obstacles or relocated, leaving illegible labels buried inside components.

Changes

1. Chip Obstacle Detection: Added `findNextChipCollidingLabel` to detect labels whose bounding boxes intersect chip bodies (via `ChipObstacleSpatialIndex`) or text boxes (`rectIntersectsAnyTextBox`).
2. Standalone Relocation: In `_step()`, after label-label pairs are resolved, the solver queries `findNextChipCollidingLabel()` and tests candidate orientations and anchors along available trace segments to move the label outside obstacle bounds.
3. Unit Tests: Added `tests/solvers/NetLabelNetLabelCollisionSolver/chip-obstacle-avoidance.test.ts` verifying that a label initially placed overlapping a chip body is relocated completely outside the chip bounding box.

Verification

• `bun test tests/solvers/NetLabelNetLabelCollisionSolver/chip-obstacle-avoidance.test.ts` (1/1 passing).

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
schematic-trace-solver	Ready	Preview	Aug 15, 2026 10:31pm

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9f83a4d6b

ℹ️ 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]

Track skipped chip collisions per label

When one colliding label cannot be relocated, this check suppresses every later label with the same globalConnNetId, not just the placement that was exhausted. The placement solver can emit multiple labels for the same global net (for example separate disconnected/port-only pins), so if the first one has no valid candidate, another same-net label that is still inside a chip or text box is never considered and remains buried; key this skip by the actual placement or another per-label identifier instead of the net id.

Useful? React with 👍 / 👎.