hermes - 💡(How to fix) Fix Desktop: Electron renderer crash loop on remote gateway connection (v0.15.1)

Bug: Desktop remote gateway renderer crash loop

Version: v0.15.1 (commit 79bfddd)
OS: Windows 10/11 (corporate laptop)
Remote: Linux VPS running Hermes gateway on :9119

Symptoms

When Hermes Desktop is configured to connect to a remote gateway, it enters an infinite crash/restart loop:

1. HTTP health check passes: [boot] Remote Hermes backend is ready
2. Immediately after: [bootstrap] reset requested by renderer; clearing latched failure
3. Renderer restarts, reconnects, crashes again — loop forever

The local backend mode works fine.

Reproduction

1. In Hermes Desktop → Settings → Remote Gateway
2. Enter any valid remote URL (tested with HTTPS, HTTP, and SSH tunnel to localhost)
3. Click "Save and reconnect"
4. Observe boot loop

What we tested

• HTTPS (https://hermes.asassi.cloud) → crash loop
• HTTP (http://hermes.asassi.cloud) → crash loop
• SSH tunnel (http://127.0.0.1:9119 via ssh -L) → crash loop
• Tailscale IP (http://100.88.100.86:9119) → crash loop

All remote modes fail identically. The network/connectivity is not the issue — the HTTP check succeeds in every case.

Log evidence

[hermes] [boot] Connecting to remote Hermes backend at https://hermes.asassi.cloud
[hermes] [boot] Remote Hermes backend is ready                    ← HTTP OK
[hermes] [renderer console] Blocked call to navigator.vibrate...  ← renderer
[hermes] [bootstrap] reset requested by renderer; clearing latched failure  ← CRASH
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Connecting to remote Hermes backend at https://hermes.asassi.cloud
[hermes] [boot] Remote Hermes backend is ready                    ← HTTP OK again
[hermes] [bootstrap] reset requested by renderer; clearing latched failure  ← CRASH again
...

Also noted: earlier local backend failures were caused by missing python-dotenv module (auto-fixed by bootstrap reinstall). That is separate.

Additional context

• No WebSocket attempt reaches the server — the renderer crashes before establishing the WSS connection
• Server logs show zero incoming WebSocket connections during these attempts
• This appears to be an Electron/Chromium renderer crash, not a network issue

Full desktop log available on request (2,448 lines covering multiple boot cycles).