test: allow telemetry probes more time on Windows

[sean0407]

Summary

• Raise the telemetry probe child-process timeout from 15 seconds to 60 seconds.
• Keep the probe's existing behavior and assertions unchanged.

Issue #176 includes clean-clone Windows reproductions, with one probe taking 32.9 seconds under cold transpilation and parallel test load. The 15-second timeout terminates it before it can emit output.

Verification: git diff --check passed.

Closes #176

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-10T12:55:26.862474Z	8d8d103	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[BigDataDZ]

Independent verification on native Windows 10 (zh-CN, cp936), with the same one-line change applied (timeout: 15000 -> 60000 in captureRuntime) - byte-identical to this PR's patch, which I had also staged locally while preparing the #176 follow-up; I am not opening a competing PR.

npx tsx --import ./tests/setup.ts --test tests/telemetry.test.ts: 3/3 pass. The attribution probe took 55.7 s under a cold, post-checkout run - well past the old 15 s timeout and close enough to 60 s that the new budget is needed headroom, not generosity. Opt-out probe 33.4 s, zero-sample probe 7.8 s.

The change touches only the child-process timeout and leaves every assertion intact, so warm-cache ubuntu CI is unaffected as described. Good to merge from the issue reporter's side.