Windows detached-entry launch can time out in CI #3688

Problem

The Windows unit job can time out launching a detached entry through PowerShell in the bracket/smart-quote path case. This failed PR #3687, whose changes are limited to benchmark export and website presentation.

Evidence

• Failed Windows job, head f90d832.
• packages/stim-cli/src/__tests__/detached-entry.test.ts: the Windows launcher starts an entry from a path with brackets and a smart quote.
• Command timed out after 10000ms: powershell.exe -NoProfile -NonInteractive -Command ... [System.Diagnostics.Process]::Start($start) | Out-Null, ETIMEDOUT, SIGTERM.
• The test and launcher are unchanged by that PR and still present on refreshed origin/main 9b34ea5. Searches for open Windows launcher timeout and detached-entry issues found no match.

Cause

Unknown. The reported timeout is in the PowerShell launcher process, before detached-entry completion can be checked. One CI failure is insufficient to distinguish runner contention from a launcher hang.

Fix idea

Capture launcher startup and child-process timing on Windows, then preserve the real launch assertion while removing sensitivity to runner startup variance. Do not treat a timed-out launch as a successful test.