Reproduce overbooked region boundaries

[ShiboSoftwareDev]

What this reproduces

The region-path planner can assign more nets to a boundary than that boundary has physical port-points.

The fixture has two nets:

• constrained-net can only use the center path.
• flexible-net can use either the center path or the longer upper path.

Both currently choose the shorter center path. The center boundary has one physical lane but receives two distinct nets, shown as 2/1 nets in red.

The rectangles and boundary lines are the real region graph, and the colored lines are the paths returned by RegionPathSolver. The visualization change only exposes the graph's demand and capacity; it does not change routing.

Validation

bun test tests/solver/region-path-capacity-negotiation.test.ts --timeout 9999999
1 pass, 0 fail

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tiny-hypergraph	Ready	Preview	Aug 7, 2026 1:11pm

[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.