Timeout smoke can expire before fake Playground command starts

[chubes4]

Bug

The focused runtime smoke playground-command-timeout-smoke can fail before its fake Playground run() implementation is entered.

Reproduction

npm run smoke -- --command=playground-command-timeout-smoke

Observed on Node 25.7.0:

AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

false !== true

at scripts/playground-command-timeout-smoke.ts:47:8

The test gives the entire runtime.execute() path timeoutMs: 25, then requires runCalled === true. Runtime setup can consume that budget before the fake backend's run() callback starts, so the timeout contract assertion passes but the implementation-detail assertion fails.

Expected

The timeout smoke should deterministically test an in-flight command timeout without depending on runtime startup completing within 25 ms.