test/studio-runs.test.ts runs under 10 s #3596

test/studio-runs.test.ts already runs under 10 s on current main, so the only change is the stale number in scripts/test-times.json: 29.3 s becomes 2.5 s.

• Timing: I ran the file ten times in a row. All 38 tests passed every time, in 2.3–2.7 s. The slowest single test took 0.30 s.
• Waits: The file has no sleep or setTimeout calls.
• No test code touched: No test was deleted or changed, so everything the file proved before it still proves. I didn't touch any production code.
• Measured here, not on the vxrail: The timings come from this sandbox, not the vxrail. The forge's check will show how the file does there. The two socket-based suites are skipped here and run on the forge's check.

To try it: bun test test/studio-runs.test.ts.

🤖 Generated with Claude Code

Closes #3578

test/studio-runs.test.ts already runs under 10 s on current main, so the only change is the stale number in scripts/test-times.json: 29.3 s becomes 2.5 s.

• Timing: I ran the file ten times in a row. All 38 tests passed every time, in 2.3–2.7 s. The slowest single test took 0.30 s.
• Waits: The file has no sleep or setTimeout calls.
• No test code touched: No test was deleted or changed, so everything the file proved before it still proves. I didn't touch any production code.
• Measured here, not on the vxrail: The timings come from this sandbox, not the vxrail. The forge's check will show how the file does there. The two socket-based suites are skipped here and run on the forge's check.

To try it: bun test test/studio-runs.test.ts.

🤖 Generated with Claude Code

test/studio-runs.test.ts already runs in about 2.5 s on main, well under the 10 s target, so I only updated the stale number in scripts/test-times.json (29.3 s to 2.5 s).

• Timing: I ran the file ten times in a row. All 38 tests passed each time, in 2.3–2.7 s, and the slowest single test took 0.30 s. It has no sleep or setTimeout calls. These are sandbox timings, not the vxrail's.
• Coverage: No test was deleted or changed, so nothing the file proved is lost. I touched no production code.
• Why the first push failed: The check's fast tier picks tests from the changed files, and a change to scripts/test-times.json alone selects none, so it exited with "name the test files to run". I added a one-line note about the runtime to the header comment of test/studio-runs.test.ts, so the push now touches that file. I did not change the selector.
• After the fix: I re-ran the file once (it passed in 2.49 s) and pushed. I have not seen the forge's result for the new push.

To try it: bun test test/studio-runs.test.ts.

🤖 Generated with Claude Code

I merged main into the branch and pushed it. The only conflict was scripts/test-times.json.

• Resolution: test/studio-runs.test.ts stays at 2.5 s, the figure this pull records. I took main's newer numbers for the two neighbouring entries: studio-door at 2.1 s and studio-search at 2.3 s.
• Checks run: the file still parses as JSON, and test/studio-runs.test.ts passes (38 tests, about 2.4 s). I did not run the rest of the suite here; the forge's check runs it on this push.
• Not touched: main still lists studio-runs at 29.3 s, which is the stale figure this pull corrects.