Add repro for too many candidates in SingleTargetNecessaryCrampedPortPointSolver

[0hmX]

• Add test for necessary cramped port point solver to prevent duplicate candidate explosion
• Refactor necessary cramped port point solver test to remove unused statistics and ensure candidate count exceeds 500

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
capacity-node-autorouter	Ready	Preview, Comment	Mar 10, 2026 1:30pm

[tscircuitbot]

🏃 Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [solver-name|all] [scenario-limit] --concurrency <n> --effort <n>

Examples:

• /benchmark -> AutoroutingPipelineSolver, all scenarios (default concurrency uses the benchmark runner CPU count)
• /benchmark AutoroutingPipelineSolver -> one solver, all scenarios
• /benchmark all 20 -> all solvers, first 20 scenarios
• /benchmark AutoroutingPipelineSolver 20 --concurrency 8 -> one solver, 20 scenarios, 8 workers
• /benchmark AutoroutingPipelineSolver 20 --effort 2 -> one solver, 20 scenarios, 2x effort

Any PR whose title contains [BENCHMARK TEST] will automatically run the benchmark workflow on PR updates.

[tscircuitbot]

---

Thank you for your contribution! 🎉

PR Rating: ⭐⭐⭐
Impact: Major

Track your contributions and see the leaderboard at: tscircuit Contribution Tracker

---