use optimized tiny hypergraph for rv1106 routing

[mohan-bee]

Motivation

Removed from the board-improvement stack: the replay skips path search, so this PR does not demonstrate a board improvement. TinyHypergraph performance should be evaluated separately.

Pin TinyHypergraph #181 on the shared RV1106 repro. This optimizes blocker search without intentionally changing route selection. The full path-search run reached a solved result with 239 traces and 36 relaxed DRC errors, matching the replay count. Bun reported the 30-minute CLI timeout at the final asynchronous snapshot check, so full-run image equality is not yet verified; the displayed image is the checkpoint replay. Further full-run checking was stopped after downstream CI exposed result differences.

Before: 36	After: 36

[vercel]

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

Project	Deployment	Actions	Updated
capacity-node-autorouter	Ready	Preview	Sep 10, 2026 2:57pm UTC

[tscircuitbot]

Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [benchmark.sh args...]
/benchmark-long [benchmark.sh args...]
/benchmark-all [benchmark.sh args except --dataset]
/benchmark --same-machine
/benchmark-all --same-machine
/profile --dataset 18

Comment /benchmark to compare current main and the PR head sequentially on the same 8-vCPU Blacksmith runner using the default dataset, or append any arguments accepted by ./benchmark.sh. Same-machine comparison is enabled by default, except for --pipeline 9net, which uses its dedicated cold/hot benchmark workflow.
Comment /benchmark-long for an 8-vCPU run that defaults to 8 workers and has an eight-hour timeout.
Comment /benchmark-all to start separate workflow runs and result comments for dataset01 and dataset18. You may append benchmark arguments such as --pipeline 9; --dataset is not accepted because the command selects both datasets.
Append --same-machine to /benchmark-long or /benchmark-all to compare current main and the PR head sequentially on the same 8-vCPU Blacksmith runner.
Comment /profile --dataset 18 to compare direct Pipeline 7 stage-time percentages between current main and the PR head sequentially on one Blacksmith runner.

Everything after /benchmark, /benchmark-long, or /benchmark-all is safely forwarded to ./benchmark.sh, except --profile-solvers, which enables profile comparison tables, and --same-machine, which enables the paired runner.
Examples: /benchmark --dataset 18 --sample-timeout 2000s, /benchmark --pipeline 10 --dataset 29, /benchmark --pipeline 10 --dataset 29 --sample 1, /benchmark --pipeline 7 --limit 20, /benchmark all 20 --concurrency 8, /benchmark --same-machine, /benchmark-all --pipeline 9 --same-machine, and /benchmark-long --dataset 18.

Use /update-snapshots (or /us) to run BUN_UPDATE_SNAPSHOTS=1 bun test --timeout 120_000 on the PR branch and auto-commit snapshot updates.
Use /usf to read recent failed test files, update and verify their exact CI test shards, and auto-commit only their snapshots. It uses the configured fast benchmark runner by default; use /usf --ubuntu-latest for GitHub-hosted x64 CI parity.

Any PR whose title contains [BENCHMARK TEST] will automatically run one default-dataset benchmark on PR updates; it does not post a PR result comment.