Fallback
gstack's PR gate now runs every paid check when its import scan fails
A failed import scan in gstack's pull request gate used to count as no consumers, so nothing ran. Now it restores the full gate, and labels the file to fix.
Shadow map
Every PR plan now previews a tighter case map, without changing what runs
Each plan now carries a shadow line: the checks a tighter map would run, counting only what each case executes. It changes nothing yet. Replayed over ten days of failed runs, it kept every failing case.
Fixes
Three smaller fixes
bun and node scripts count as code, so 41 files reach the paid cases that use them1.91.129.0bun run test:health leads with cost per merged PR1.91.129.0Extensionless bun and node scripts now get scanned, so forty-one files reach the checks that use them. The free suite's timing seeds refresh themselves weekly. And test health leads with cost per merged PR.
Your CI
Does your own CI run everything when it can't tell what a change touches?
docs/TESTING_INTERNALS.mdexercised-path map, PR paid-lane fallbackThe testing internals doc in the gstack repo covers the shadow map and the fallback rules. So, does your own CI run everything when it can't tell what a change touches?















