Fix IPC race conditions in main.ts - replace manual timeouts with proper handshake mechanism

[Nat3z]

The main.ts uses manual timeouts to coordinate IPC communication, creating race conditions. Replace with proper handshake mechanisms using webContents.send or did-finish-load.

[nat-openclaw]

▶️ Actions Performed

• Inspect main.ts sendIPCMessage, onMainAppReady, and client-ready-for-events flow — Reviewed main.ts, App.svelte, preload — timeout race in sendIPCMessage; onMainAppReady tied to ready-to-show
• Replace IPC_READY_TIMEOUT_MS race with did-finish-load + client-ready handshake — Replacing IPC_READY_TIMEOUT_MS with did-finish-load + client-ready handshake
• Gate onMainAppReady on renderer readiness in normal/game-launch/hook paths
• Run typecheck/build for application — bun run typecheck passed
• Commit, push branch, and open PR closing Fix IPC race conditions in main.ts - replace manual timeouts with proper handshake mechanism #165 — Pushed branch and opened PR fix: replace IPC timeout fallback with renderer handshake #166

[nat-openclaw]

Nice, I replaced the timeout-based IPC flow in main.ts with a proper handshake so startup messages only go out after the renderer has actually loaded and sent client-ready-for-events.

I also made sure the main-app startup path waits on that handshake for normal launch, --game-id, and hook-only flows, so the early IPC burst doesn’t race the frontend anymore.

Checks: bun run typecheck in application/ passed.

PR is up here: #166