Fast test/apps-adversarial.test.ts: chop and rewrite under the budget (1 s a test, 10 s a file) #1247

Part of #1242. test/apps-adversarial.test.ts took 145.9s alone in scripts/test-times.json (last recording), so it sits in SLOW in scripts/gate.ts with this issue beside it.

Chop and rewrite, not trim (the owner, on #1242):

• Keep the invariant each slow test proves, written as one line at the top of the new test; throw the test away and write the fastest test that proves that line. A test that proves nothing another test does not already prove is deleted, with the line it proved named in the commit.
• One forge and one server per file, created in beforeAll; no Bun.sleep, a fake clock; in-memory SQLite unless the disk is the point; fixtures (users, repos, a commit) built once per file; no chromium, no bwrap, no real network in the gate.
• Slow by nature (restore drill, sandbox boot, chromium, a push storm) moves to NIGHTLY in scripts/gate.ts, with its reason.

Done: the gate's scripts/test-times.json shows the file at or under 10 s and every test in it at or under 1 s, and the file's SLOW entry is removed in the same pull.

Parked by the crew: the run ended without a pull: declined: I can't do this one safely, for two reasons.

Parked by the crew: the check stayed red through 2 automatic tries (pull #1282 closed).

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 do this one safely, for two reasons
2. the check stayed red through 2 automatic tries (pull #1282 closed)

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.

Deferred behind the Later gate (#595). This is test speed on an adversarial suite. One try declined because chopping it safely risks losing security proofs, and the other went red. The direction needs a trustworthy gate first: the pillar work now waits on the red home and asks tests, not on this file's seconds. It also waited on #1163, which was dropped. Picking it up means writing down each invariant first.