The version probe was a bare subprocess.run with a 10s timeout while the
registry probe already had run_pi_registry_command's 45s timeout and three
attempts for concurrent-Pi stalls. Under CI queue load the bare probe is the
step that times out: pipelines 2808-2810 and 2819-2820 all failed at
test_pi_carve_out_resolves_to_real_unshadowed_builtins with
'pi --version timed out after 10 seconds' on unrelated (including docs-only)
heads, while 2814/2816 passed between them. Reusing the existing runner gives
the version probe the same bounded retries and the same probe/infra failure
labeling; behavior on a version mismatch or nonzero exit is unchanged.
fred