Avoid duplicate ports for routes on the same net

[ShiboSoftwareDev]

Problem

The duplicate-port prepass counts routes, but port ownership in the pathing solver is defined by electrical net. Several branches of one net can share a port, so counting each branch creates unnecessary ports and expands the search graph.

Fix

For each port, collect the distinct routeNet IDs seen by the independently solved routes. The number of physical lanes is then based on the number of distinct nets:

• Two different nets still receive two lanes.
• Two routes on the same net use one shared lane.
• No new topology type, threshold, or dataset-specific rule is added.

Visualization

These are the same test and the same snapshot path on the reproduction and fix commits.

Before: route count creates 2 ports	After: net count keeps 1 port

In each image, the upper frame is the one-port input and the lower frame is the real prepass output. Gray circles are topology ports; colored dashed lines are route endpoint hints. The fix removes only the unnecessary second gray center port.

Validation

All tests and snapshots run on GitHub Actions. The exact srj24 sample 4 benchmark is run on the stacked autorouter integration PR.

Stack

Stacked on #141.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tiny-hypergraph	Ready	Preview	Aug 2, 2026 12:00pm

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