Bug: crypto.randomUUID is not a function when accessing Web GUI over plain HTTP (LAN/phone)

[TYBLHQY]

Bug: crypto.randomUUID is not a function when accessing the Web GUI over plain HTTP on another device

Environment: @deepseek-ai/dsh 0.1.0-rc.6, accessed from a phone on the same LAN at http://<lan-ip>:<port> (plain HTTP, non-localhost).

Symptom: The page loads but shows no conversation/model data, with crypto.randomUUID is not a function in the console.

Root cause: crypto.randomUUID is only exposed in a secure context (HTTPS or localhost). On a plain-HTTP LAN origin the API is absent. The production RPC client mints its request ids here:

• packages/host/apiproxy/src/fetch/client.ts → mintRpcId() → RpcId(crypto.randomUUID())

Note: the browser-safe replacement already exists in the repo — packages/client/connection/src/client/random-uuid.ts → randomUuid(), which uses crypto.getRandomValues() (available on insecure origins) and is already used by the connection client's other paths (rpc.ts, fixture.ts). It just isn't wired into mintRpcId().

Suggested fix: use randomUuid() in mintRpcId() (and, for consistency, the browser draft-attachment id in the conversation UI) instead of crypto.randomUUID().

Happy to submit a PR if it helps — this blocks LAN/mobile access to the Web GUI.

[naipi11]

Confirmed on rc.7: the fetch client still calls crypto.randomUUID(), which is unavailable on a plain-HTTP LAN origin. As a temporary workaround, open the UI through HTTPS with a certificate trusted by the device (or use localhost); please do not edit installed files. Reusing the existing browser-safe randomUuid() helper looks like the appropriate upstream fix.