Connect net labels to existing same-net traces - #893
Draft
Sang-it wants to merge 9 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sang-it
force-pushed
the
feat/net-label-same-net-trace-recovery-v2
branch
from
August 25, 2026 22:41
1844aba to
678a34a
Compare
Sang-it
force-pushed
the
feat/net-label-same-net-trace-recovery-v2
branch
from
August 26, 2026 19:01
6b02428 to
1adc10c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mainNetLabelToSameNetTraceSolveras the final pipeline stagey+labelsyvalue on each global netmainSafety checks
Candidates must share a non-ground global net and schematic section. Branch continuations must be aligned within 0.15 units; standalone ports must be within 5 units of existing copper. The solver rejects non-axis-aligned routes, restricted-centerline crossings, collisions, cross-net intersections, unintended same-net overlaps, and paths through rendered labels. Protected labels are reserved before recovery so other branches can join their traces without removing the visible label or its port connector.
Verification
bun test(215 pass, 4 skip)bunx tsc --noEmitbun run format:checkgit diff --checkbun run debug:pipeline tests/assets/example51.json --out /tmp/schematic-trace-debug-example51-net01-connected --stop-after netLabelToSameNetTraceSolver --svgSupersedes #869.