feat: expose boundary handoff report (layer order, inversions, pitch) - #187
Open
spheceo wants to merge 1 commit into
Open
feat: expose boundary handoff report (layer order, inversions, pitch)#187spheceo wants to merge 1 commit into
spheceo wants to merge 1 commit into
Conversation
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>
|
@spheceo is attempting to deploy a commit to the tscircuit Team on Vercel. A member of the Team first needs to authorize it. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Author
|
This is the small main-based handoff report primitive from #130, not a stacked experiment-wide fix. |
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
getBoundaryHandoffReport()so callers can read actual boundary exits grouped by physical layer without reverse-engineering a solved SRJ.FanoutSolver.getOutput()asboundaryHandoff. 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.tsoutput.boundaryHandoff.layersinstead of reconstructing exit order from tracesMade with Cursor