Summary

Add a debug/diagnostic mode to the Control UI that surfaces connection logs and errors in the browser, without persisting anything to device storage after the tab/app is closed.

Motivation

When the gateway WS connection fails (e.g. auth error, device identity issue, network problem), the UI currently shows a brief error string with no context. Diagnosing the issue requires SSH access to the server to tail logs — not feasible for non-technical users or remote clients.

Proposed Behavior

• Toggle in the UI (e.g. a button in the connection/settings panel) that enables verbose logging for the current session
• Captures: WS connection lifecycle events, handshake frames, error codes/details, gateway close codes and reasons
• Log is ephemeral: stored only in memory (or sessionStorage at most), never written to localStorage or IndexedDB, cleared on tab close
• Display as a scrollable overlay/drawer with copy-to-clipboard for sharing with support
• Could also include gateway-side logs streamed via logs.tail once connected (if connection succeeds)

Notes

• Particularly useful for diagnosing LAN/remote connection failures before auth is established
• The pre-auth phase (challenge, device identity, pairing) is currently a complete black box to end users