test: reproduce intermediate-layer graph guidance release

[ShiboSoftwareDev]

Problem

Stacked on #146. A six-layer route starts on z0 and ends on z5. Its ordinary multilayer region exposes one legal z5 exit and dead-end exits on z1–z4.

The intermediate exits are slightly closer to the goal in XY. The current heuristic therefore guides the route to the correct region, then turns off after leaving z0 and chooses those wrong-layer exits. The bounded search fails.

Fixture and snapshot

This changes the existing fixture only. The top frame shows the six-layer topology. The bottom frame shows the failed bounded search after it enters intermediate-layer dead ends instead of continuing to z5.

The test failure and SVG were produced in GitHub Actions. Nothing was run locally.

[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 9:17pm

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