Queue duplicate congested port route solves

[0hmX]

Summary

This PR changes DuplicateCongestedPortSolver from a synchronous setup-time helper into a normal step-driven solver.

The solver's job is to find ports that multiple independently routed connections all want to use, then duplicate those congested ports so the full route has more local choices. Before this change, it did that detection by solving every single-route problem synchronously during setup. That worked as a utility, but it made the solver hard to compose inside a larger pipeline: there was no useful progress, no active child solver to visualize, and failures could happen outside the usual solver state.

This PR keeps the same high-level behavior, but makes the work observable and schedulable.

What Changed

• Load the serialized hypergraph during setup, then queue one TinyHyperGraphSolver child per route.
• Step one child route solver at a time through activeSubSolver.
• Accumulate port-use counts as route children finish, then duplicate congested ports after all route checks complete.
• Report setup and child-route failures through normal failed, error, and failedSubSolvers state.
• Expose progress and stats for the duplicate-port route scan.
• Delegate visualization to the active child solver while it is running, then show the duplicated source and duplicate ports after completion.
• Add tests for queued progress and setup-error reporting.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tiny-hypergraph	Ready	Preview, Comment	Jun 24, 2026 4:14pm

[tscircuitbot]

Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [benchmark.sh args...]
/benchmark --dataset <hg07|srj18> --limit <n> --solver <core|poly> --families <default|default+deep|all> --concurrency <n|auto>

Everything after /benchmark is forwarded directly to ./benchmark.sh.
The result comment shows the matching dataset from the latest stored main-branch benchmark artifact beside the PR run; main is not rerun for each PR benchmark request.

Examples:

• /benchmark -> hg07, all samples, core solver
• /benchmark --dataset srj18 --limit 20 -> first 20 srj18 samples
• /benchmark --dataset srj18 --concurrency auto -> srj18 samples with runner CPU-count concurrency
• /benchmark --sample sample002 -> one hg07 sample
• /benchmark --limit 20 --solver poly -> first 20 hg07 samples with the poly solver
• /benchmark --limit 40 --families default+deep -> first 40 hg07 samples with deeper candidate families

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