Apps-Engine Deno runtime sendRequest can hang forever because it has no response timeout

Description:

In messenger.ts, the sendRequest function creates a responsePromise that waits indefinitely for a response:${request.id} event on RPCResponseObserver. If the Deno subprocess never returns a response, the promise remains pending and the caller is blocked. Additionally, the request id is generated using Math.random(), which is not ideal for unique IDs.

Expected behavior:

sendRequest should reject after a reasonable timeout and clean up the event listener, so pending requests cannot leak or hang the process forever.

Suggested fix:

Race the response promise against a setTimeout promise.
Remove the event listener in both the success/timeout cases.
Consider replacing the Math.random() id with crypto.randomUUID() or a sequential/counter-based id.

Start in messenger.ts at sendRequest, then trace RPCResponseObserver and the response:${request.id} listener. Confirm how requests and responses are matched before defining the timeout and cleanup behavior; done means an unanswered request rejects after a reasonable timeout, successful responses still resolve, and listeners do not remain pending.