test/studio-changes.test.ts runs under 10 s #3584

test/studio-changes.test.ts already runs under the 10 s target, so the only change is the recorded time in scripts/test-times.json. I did not touch the test file, so no test was removed or weakened.

• Measured: all 26 tests pass in about 2.2 s. I ran the file ten times in a row and every run was green, between 2.23 s and 2.57 s. The slowest single test takes 0.23 s. I ran this in my sandbox, not on the vxrail.
• Why it is already fast: the file builds one forge and one git fixture in beforeAll and tears them down in afterAll. It has no sleeps, timers or Date.now waits, so there was nothing left to fake or cut.
• Recorded time: scripts/test-times.json listed this file at 31.8 s, which no longer matches. It now says 2.3 s.
• Production code: none changed.

To try it, run bun test test/studio-changes.test.ts.

🤖 Generated with Claude Code

Closes #3575

test/studio-changes.test.ts already runs under the 10 s target, so the only change is the recorded time in scripts/test-times.json. I did not touch the test file, so no test was removed or weakened.

• Measured: all 26 tests pass in about 2.2 s. I ran the file ten times in a row and every run was green, between 2.23 s and 2.57 s. The slowest single test takes 0.23 s. I ran this in my sandbox, not on the vxrail.
• Why it is already fast: the file builds one forge and one git fixture in beforeAll and tears them down in afterAll. It has no sleeps, timers or Date.now waits, so there was nothing left to fake or cut.
• Recorded time: scripts/test-times.json listed this file at 31.8 s, which no longer matches. It now says 2.3 s.
• Production code: none changed.

To try it, run bun test test/studio-changes.test.ts.

🤖 Generated with Claude Code

test/studio-changes.test.ts already runs in about 2.2 s, so this pull only corrects the time recorded for it and adds a header comment.

• Time: all 26 tests pass in about 2.2 s, and the slowest test takes 0.23 s. Ten runs in a row were green. I measured this in my sandbox, not on the vxrail.
• Why it is fast: the file builds one forge and one git fixture in beforeAll, and nothing in it waits on a clock or sleeps. There was nothing left to fake or cut.
• Record: scripts/test-times.json listed the file at 31.8 s. It now says 2.3 s.
• Header comment: my first push changed only scripts/test-times.json. The check's impact map found no tests for that file and failed with "name the test files to run". I added a comment to the test file saying why it is fast, so the check now selects and runs it. This is the only change to the test file.
• Coverage: no test was removed or weakened, so every behaviour the file proves is still proved. No production code changed.

To try it, run bun test test/studio-changes.test.ts.

🤖 Generated with Claude Code

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

• test/studio-changes.test.ts: I kept this branch's 2.3. That is the point of the pull, and main's 31.8 is the old slow figure. After the merge the file still runs in 2.29 s (26 tests pass).
• test/studio-door.test.ts: I took main's 2.1. This branch still had a stale 34.2 for it.

I only ran test/studio-changes.test.ts after the merge, not the full suite, because the forge runs the whole check on the push.