A frame that ran out of room says so: the scene counts what it refused, and a test holds each game's capacity #285

nextInstance answers null and pushLine answers false once a pool is spent, and src/engine/scene.ts:15-22 tells a game to treat a refusal as a number that wants raising. Nothing counts refusals. So a busy frame drops a body, a plate or a tracer and the player, the frame meter and the suite all stay quiet, and the two capacities — picked by hand for "the busiest frame the game can have" — are a guess nothing checks.

Done looks like

• [ ] Scene carries instancesRefused and linesRefused: zeroed by resetScene, incremented where the refusal already happens, no allocation and no branch a frame would notice.
• [ ] src/engine/scene.test.ts would fail without it: fill a pool past its capacity, read both counters, reset and read zero.
• [ ] Each game holds its own guess. A test per game builds its heaviest frame — the shooter's scripted round at its busiest tick from src/client/replay.ts, the range's fullest drill from src/range/pin.ts — and asserts both counters are zero, so a capacity that stops being enough fails the suite instead of quietly cropping the picture.
• [ ] A player can see it when it happens: where the shooter's frame meter already is, a non-zero refusal count appears and nothing at all appears when it is zero.
• [ ] The scene section of GUIDE.md says the counters exist, and says what a non-zero one means — raise the capacity, do not handle the refusal.
• [ ] Door and version as ever if a name crosses it: src/engine/index.ts, boundary.test.ts, bun run scripts/surface.ts --write.

Files I expect to change

src/engine/scene.ts and its test, src/engine/GUIDE.md, src/client/scene.test.ts, src/range/scene.test.ts, src/client/hud.ts, and the door's three files if the counters are read through it.

Risks

• A refusal must stay a drop. Do not throw, do not grow the array, do not log in a frame — the counter is a measurement and the design is the design.
• The heaviest-frame tests are the valuable half and the fiddly half: build them from the pinned runs that already exist rather than inventing a synthetic world.

Suggested: Torque.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Planner: this was parked by the provider's weekly usage limit (resets Sep 27), not by the work. The run pushed nothing, so nothing in the issue is disproven. It stands as written and is ready again.