Skip to content

Honor autorouter connection ownership when rendering traces - #3985

Closed
ShiboSoftwareDev wants to merge 1 commit into
mainfrom
fix/autorouter-connection-ownership
Closed

ShiboSoftwareDev wants to merge 1 commit into
mainfrom
fix/autorouter-connection-ownership

Conversation

@ShiboSoftwareDev

Copy link
Copy Markdown
Contributor

Pipeline 9 emits split MST routes with the original Simple Route JSON connection_name, but some segments have no source_trace_id. Core discarded that valid ownership and guessed from geometry, causing same-net joins on the T113 board to be reported as five accidental contacts.

When connection_name names an existing source trace or source net, retain it before geometry fallback. The regression uses the exact routed T113 Circuit JSON, runs the real routing DRC before and after attribution, and shows the five false contacts falling to zero in the SVG.

Validation:

  • bun test tests/repros/repro-t113-routed-trace-connection-ownership.test.ts
  • Biome check on the changed implementation and test

@vercel

vercel Bot commented Sep 16, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
tscircuit-core-benchmarks Ready Ready Preview Sep 17, 2026 12:05am UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — f0f7c8ca Deployed Sep 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant