test(ipc): Drop wall-clock timing from the daemon start test

[4ndreello]

tests/ipc-daemon-start.test.ts checked that ensureDaemonStarted resolves within 50 ms of the socket accepting connections, using real sockets and wall-clock time. The code polls every 25 ms, so a loaded runner blows the budget while the code is correct: on #106 it failed on Node 26 with expected 238 to be less than or equal to 50, and passed on Node 24 in the same run.

The test now runs on fake timers with fs.existsSync and net.createConnection stubbed. The first probe fails, the daemon is spawned once, readiness flips, and the call has to settle within 50 fake ms. Nothing in src/daemon/ipc.ts changes.

Tests

• npx vitest run tests/ipc-daemon-start.test.ts: 3 passed, five runs in a row
• Mutation probes on a scratch copy of src/daemon/ipc.ts, all killed: poll interval raised to 51 ms, raised to 100 ms, readiness result ignored

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud