Double the test timeout on Windows CI runners

[HelloThisWorld]

Summary

The post-merge main run failed on Windows/node 20 with a single 30s test timeout — resume.test.ts > recovers each intermediate phase — while 1,647 of 1,648 tests passed (failing job). Nothing is functionally wrong: that test is the git-heaviest in the suite (five separate git-initialized fixtures plus a snapshot per resume — roughly fifty blocking execFileSync git spawns inside one budget), Windows process spawn costs several times more than Linux, and the second vitest worker now runs the subprocess-heavy v1.2 driver suites concurrently. The run''s aggregate Windows test time was 1,102s versus ~160s on Ubuntu — the test''s long-standing margin inside 30s is simply gone on that runner.

A timeout is a slowness budget, not a correctness assertion, and the config already documents this class ("slow CI runners regularly exceed the 5s default"). The budget doubles to 60s scoped exactly to where the slowness lives — CI AND win32 — and stays 30s for Linux, macOS, and every local run, so real hangs still fail fast where machines are fast. Scoping it globally for Windows CI (rather than a per-test override) protects every borderline git-heavy test instead of whack-a-moling the current slowest one.

For the reviewer''s context, this is the third distinct Windows-CI failure mode since v1.2 landed, each with a different root cause and fix: the forks-pool IPC timeout (fixed by the threads pool), the bundle-verifier partial-line race (fixed in #15), and now a genuine slowness-budget shortfall. No onTaskUpdate error and no verifier failure occurred in this run — those fixes hold.

Checklist

• pnpm lint, pnpm typecheck, and pnpm test pass locally — config-only change; the affected file (tests/orchestration/resume.test.ts) passes locally, and the full suite was green on this tree at the Fix flaky bundle verifier: stop parsing partial stdout lines #15 merge
• pnpm check:public-contracts passes — no contract touched
• Documentation updated for any user-visible behavior change — none (test config only)
• CHANGELOG entry added for any user-visible change — none
• Everything is in English (code, comments, docs, commit messages)
• No employer or client proprietary content — examples and fixtures are synthetic
• No credentials, tokens, or secret values anywhere in the diff, fixtures, or recorded test output