Reroute component-to-component traces around avoidable label-trace crossings

[MustafaMulla29]

Root cause

Component-to-component traces are routed before generated net-label connectors are added to the pipeline. A later connector can therefore cross an already-routed component trace even when that component trace has an equally short clean corridor.

Crossings between two generated label connectors are valid and remain unchanged.

Solution

• track generated connector IDs explicitly instead of matching trace ID strings
• retain provenance for traces produced by the original component-routing pass
• after connectors exist, inspect only crossings between a fixed generated connector and an eligible component trace
• reuse the existing generatePerpendicularTraceDetours routing primitive, extended with optional bounds so an attached label and its connector form one obstacle
• accept only candidates that are no longer than the original route, preserve the turn budget, and avoid components, text, foreign labels, coincident traces, and all foreign-trace intersections

The previous standalone 331-line candidate generator has been removed. The cleanup now uses a compact coordinator around the existing routing primitive.

Result

• the wireless-mouse component trace takes the available collision-free corridor
• generated connectors never move
• label-to-label crossings remain allowed
• routes without an equally short safe alternative remain unchanged
• exactly one visual snapshot changes

Verification

• focused coverage for a clean component route, an allowed label-to-label crossing, and rejection of a longer detour
• wireless-mouse and TI power-output repro snapshots
• bun test --timeout 20000 — 297 passed, 4 skipped, 0 failed
• bunx tsc --noEmit
• bun run format
• git diff --check

[vercel]

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

Project	Deployment	Actions	Updated
schematic-trace-solver	Ready	Preview	Sep 2, 2026 5:24am UTC

[imrishabh18]

Don't use string matching hack's

[tscircuitbot]

---

Thank you for your contribution! 🎉

PR Rating: ⭐⭐⭐
Impact: Major

Track your contributions and see the leaderboard at: tscircuit Contribution Tracker

---