Reproduce greedy final-route single-layer crossing

[ShiboSoftwareDev]

Summary

• reproduce greedy final timeout routing accepting two interleaving routes in a one-layer region
• record both the invalid accepted state and a staged before/after SVG snapshot

Root cause context

The normal solver rejects this transition as non-finite, but the emergency greedy final router currently bypasses the base transition evaluation.

The SVG intentionally shows the second route changing from a pending dashed path to accepted copper crossing the first route.

Validation

• bun test ./tests/solver/greedy-final-route-single-layer-crossing.test.ts
• bun run typecheck

This is the reproduction base for a stacked root fix.

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