test(pipeline7): reproduce srj24 sample 4 topology gap

[ShiboSoftwareDev]

What this reproduces

This adds a reduced srj24 sample 4 fixture that isolates the two topology gaps seen before port-point pathing:

1. a compact pad grid nested inside a larger mixed component is not classified as BGA topology;
2. target regions that can legally accept a via remain single-layer, so the capacity graph has no cross-layer edge.

The test intentionally asserts the current behavior. It does not change production code.

Step visualization

The four frames show the mixed component input, the undetected nested grid, the single-layer target regions, and the resulting missing cross-layer capacity edge.

Verification

• bun test tests/features/topology/srj24-sample4-topology-repro.test.ts --timeout 9999999
• bun run build

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
capacity-node-autorouter	Ready	Preview	Jul 30, 2026 4:20pm

[tscircuitbot]

Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [benchmark.sh args...]
/benchmark-long [benchmark.sh args...]
/benchmark-all

Comment /benchmark to run the default dataset, or append any arguments accepted by ./benchmark.sh.
Comment /benchmark-long for an 8-vCPU run that defaults to 8 workers and has an eight-hour timeout.
Comment exactly /benchmark-all to start separate workflow runs and result comments for the default dataset plus srj18, srj19, srj20, srj21, and srj23.

Everything after /benchmark or /benchmark-long is safely forwarded to ./benchmark.sh, except --profile-solvers, which enables profile comparison tables.
Examples: /benchmark --dataset 18 --sample-timeout 2000s, /benchmark --pipeline 7 --scenario-limit 20, /benchmark all 20 --concurrency 8, 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.