The 'execProbe keeps the parent event loop available' case asserts nothing about timing; the 1s spawn budget only exists so a wedged child cannot stall the run. A cold Windows CI runner can take longer than 1s just to start the node child, which failed the test for reasons unrelated to what it guards. 5s keeps the safety bound without the flake.