Skip to content

feat: expose boundary handoff report (layer order, inversions, pitch) - #187

Open
spheceo wants to merge 1 commit into
tscircuit:mainfrom
spheceo:feat/boundary-handoff-report
Open

feat: expose boundary handoff report (layer order, inversions, pitch)#187
spheceo wants to merge 1 commit into
tscircuit:mainfrom
spheceo:feat/boundary-handoff-report

Conversation

@spheceo

@spheceo spheceo commented Sep 7, 2026

Copy link
Copy Markdown

Summary

  • Adds getBoundaryHandoffReport() so callers can read actual boundary exits grouped by physical layer without reverse-engineering a solved SRJ.
  • Reports requested-vs-actual order, pairwise inversions, per-exit deviation, and minimum along-edge pitch.
  • Attaches the report to FanoutSolver.getOutput() as boundaryHandoff. This is a read-only view of existing plans and does not change routing.

This is the small main-based solver primitive requested in #130 (handoff routability as a first-class result), not another stacked experiment-wide fix.

Test plan

  • bun test tests/boundary-handoff-report.test.ts
  • Confirm a DRAM/orbit caller can read output.boundaryHandoff.layers instead of reconstructing exit order from traces

Made with Cursor

Callers were reverse-engineering layer order, inversions, and pitch after a successful solve. Expose that as a read-only report on FanoutSolver output.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Sep 7, 2026

Copy link
Copy Markdown

@spheceo is attempting to deploy a commit to the tscircuit Team on Vercel.

A member of the Team first needs to authorize it.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@spheceo

spheceo commented Sep 7, 2026

Copy link
Copy Markdown
Author

This is the small main-based handoff report primitive from #130, not a stacked experiment-wide fix.

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