feat: add LayoutRefinementSolver to resolve post-pack chip overlaps

[theherrovn-sys]

/claim #12

Summary

Add LayoutRefinementSolver that runs after PartitionPackingSolver in the pipeline to resolve residual chip overlaps in the final layout.

Algorithm

1. detectOverlaps() — AABB overlap detection for all chip pairs, accounting for chip rotation
2. Iterative push-apart — max 100 iterations with damping factor 0.5
3. For each overlap: compute Minimum Translation Vector (MTV), push each chip 50% in opposite directions along the minimum penetration axis
4. Integrates as final pipeline phase in LayoutPipelineSolver

Implementation

• Created lib/solvers/LayoutRefinementSolver/LayoutRefinementSolver.ts extending BaseSolver
• Added to pipeline in LayoutPipelineSolver after partitionPackingSolver
• Follows existing solver pattern: _step(), visualize(), state machine
• getOutputLayout() now uses the refined layout when available

Testing

All 17 existing tests pass:

✓ LayoutPipelineSolver01 visualization example
✓ LayoutPipelineSolver02 (4 tests)
✓ LayoutPipelineSolver04 simplified pipeline
✓ RP2040Circuit (2 tests)
✓ ChipPartitionsSolver (4 tests)
✓ PartitionPackingSolver (2 tests)

[vercel]

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

A member of the Team first needs to authorize it.

[theherrovn-sys]

Hey @rushabhcodes, totally understand closing this if the PR volume looked suspicious — thanks for keeping the bar high. We're a small 3-person team, and we do use automated tooling to move faster, but the goal here was a real fix for the chip overlap issue in LayoutRefinementSolver. Could you let me know what specifically needs to change for this to meet your standards? Happy to rework it however you prefer.

[rushabhcodes]

tests were failing, usually means AI

[theherrovn-sys]

Thanks for taking a close look, Rushabh — I understand the concern about failing tests and AI-generated PRs. For #117 (LayoutRefinementSolver), the matchpack test run I have is 17 passing / 0 failing in my environment. Could you share the exact failing test name, command, or CI log you saw? I’m happy to debug it with you on Discord or anywhere you prefer.

[theherrovn-sys]

You were right — the checks were failing. I found the actual issues: a TypeScript prop mismatch in the Text interface and a missing dependency, both now fixed. 18/18 tests pass, format is clean, and the branch is updated for re-review.