test/prompts.test.ts and test/snapshot-destination.test.ts pass in any order and run in the gate #11100

test/prompts.test.ts and test/snapshot-destination.test.ts now pass in any order, and both are off the scripts/gate.ts EXCLUDED list.

bun scripts/flake-hunt.ts admit gave ten green randomized runs for each file. bun scripts/gate.ts exits 0 and bun x tsc --noEmit is clean. I did not run the rest of the suite.

The sandbox denies connections to 127.0.0.1:1, and the snapshot-destination runs print that denial. The suite still passes. The test that exercises the connection failure is built to expect exactly that.

• test/snapshot-destination.test.ts: a beforeEach forgets any sealed destination, so each test starts with nothing saved. The "service follows a saved or cleared destination" test now saves its own destination first. Before, it relied on the precedence test having saved one.
• test/prompts.test.ts: the file was one story across 15 tests. Each test now gets a fresh app, server, routine, fake Instagram and clock, and builds the state it reads.

- New helpers connect(at), reelOne() and firstTell() set up the connected account and the first told Reel. - Where a test used to depend on earlier tests having made issues #1–#3, its expectations are renumbered to its own story. "Fetch now" and "token refresh" are examples, and the issue count in the refusals test is one lower. - In "Fetch now", I backdate the token to the day before the run so that no refresh is due. Without that, the refresh call gets in the way of the call list the test checks. - The "no Reel at all" test now sets up its own previous Reel before the empty one.

I did not change any production code.

Closes #11097

test/prompts.test.ts and test/snapshot-destination.test.ts now pass in any order, and both are off the scripts/gate.ts EXCLUDED list.

bun scripts/flake-hunt.ts admit gave ten green randomized runs for each file. bun scripts/gate.ts exits 0 and bun x tsc --noEmit is clean. I did not run the rest of the suite.

The sandbox denies connections to 127.0.0.1:1, and the snapshot-destination runs print that denial. The suite still passes. The test that exercises the connection failure is built to expect exactly that.

• test/snapshot-destination.test.ts: a beforeEach forgets any sealed destination, so each test starts with nothing saved. The "service follows a saved or cleared destination" test now saves its own destination first. Before, it relied on the precedence test having saved one.
• test/prompts.test.ts: the file was one story across 15 tests. Each test now gets a fresh app, server, routine, fake Instagram and clock, and builds the state it reads.

- New helpers connect(at), reelOne() and firstTell() set up the connected account and the first told Reel. - Where a test used to depend on earlier tests having made issues #1–#3, its expectations are renumbered to its own story. "Fetch now" and "token refresh" are examples, and the issue count in the refusals test is one lower. - In "Fetch now", I backdate the token to the day before the run so that no refresh is due. Without that, the refresh call gets in the way of the call list the test checks. - The "no Reel at all" test now sets up its own previous Reel before the empty one.

I did not change any production code.

I merged main into the branch and pushed it, so #11100 should merge cleanly again.

The only conflict was in scripts/gate.ts. main had rewritten the EXCLUDED reasons for test/prompts.test.ts and test/snapshot-destination.test.ts and moved the neighbouring entries. I kept main's other entries and deleted both of those files' entries, since this pull fixes the tests those entries excused.

Checks after the merge:

• bun scripts/gate.ts exits 0.
• bun x tsc --noEmit is clean.
• The two test files together give 30 pass, 0 fail under --randomize. The sandbox again denied connections to 127.0.0.1:1, as it did before; the tests still pass.

I did not re-run the ten-run flake-hunt admit.

I dropped the four #261 entries, you were right, and pushed. The earlier merge conflict resolution had brought them back; my fault.

I took main's scripts/gate.ts as it stands after #11099 and deleted only the two #11097 entries. The diff against main is now those ten deleted lines in gate.ts plus the two test files.

At this head, after merging the newest main:

• Flake-hunt: bun scripts/flake-hunt.ts admit is 10/10 green, random order, under load, for both test/prompts.test.ts and test/snapshot-destination.test.ts.
• Gate and types: bun scripts/gate.ts exits 0 and bun x tsc --noEmit is clean.
• Sandbox noise: the sandbox denies connections to 127.0.0.1:1, which the snapshot-destination tests try on purpose, and the tests still pass.