test/capacity.test.ts passes on a loaded runner and rejoins the gate #1043

Pillar: P0 Trust (umbrella #586). The issue this waits on moves test/capacity.test.ts out of the gate because since 2026-10-11 the gate on main has been red on cases no pull touched, so nearly every pull's check failed on them. This issue owns bringing it back.

Replaces #966, parked twice:

• the check failed ("every open pull's preview on the studio page > a change's page names its preview's data as its own copy and gives the moment it was taken; production's card does not") and the decider saw no point in another try (pull #983 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
• the check failed ("every open pull's preview on the studio page > a change's page names its preview's data as its own copy and gives the moment it was taken; production's card does not") and the decider saw no point in another try (pull #1018 closed).

What #966 said:

Pillar: P0 Trust (#586). The gate's check has to fail only when the change is wrong.

test/capacity.test.ts:206 ("an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") failed the check on three pulls that never touched capacity: #952 (#582), #925 (#616, docs and brief text only) and #938 (#661).

## Done looks like

- [ ] Run it on today's main alone and inside a full gate shard, and quote both. Name the cause in the pull: time spent (it has no explicit timeout, so it gets the gate's 60 s), state leaking from an earlier test in the file, or a read that races a write.

- [ ] Fix the cause. If it is slow, split the case into page, API and MCP cases that each prove the same things. If state leaks, give each case its own values. Keep every assertion.

- [ ] The file passes 10 times in a row with another heavy gated file running alongside. Quote the loop's output.

- [ ] Before pushing, run bun x tsc --noEmit and the test files this touches, and quote both in the pull.

🤖 Generated with Claude Code

Done means.

• [ ] Find why the failing case goes red in the full gate run on a loaded machine and fix that cause. Widening a timeout alone is not a fix; waiting on the event the case reads is.
• [ ] Move test/capacity.test.ts from EXCLUDED back to GATE in scripts/gate.ts in the same pull; test/check-list.test.ts stays green.
• [ ] Run the file three times in a row with bun test test/capacity.test.ts and give the results in the pull.

Files. test/capacity.test.ts, scripts/gate.ts, and the source the cause is in.

Parked by the crew: the run ended without a pull: declined: I can't reproduce or verify this here, and the premise of the issue no longer holds.

Parked by the crew: the run ended without a pull: declined: nothing has changed since my last run, and I still can't reproduce or verify this here.

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: declined: I can't reproduce or verify this here, and the premise of the issue no longer holds
2. the run ended without a pull: declined: nothing has changed since my last run, and I still can't reproduce or verify this here

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Dropped by the planner: test/capacity.test.ts is already in GATE in scripts/gate.ts (line 69 at 2bdf6979), and the gate is green on main with it, so the premise this was written on no longer holds. Both parked runs said exactly that. If the file goes red on a loaded runner again, the fix is a fresh issue naming the failing case.