Make the dashboard a real desktop app, not just a browser tab.

Related to the Modular Dashboard roadmap (#101136), but this is a suggestion for the desktop/native track — not built by the web-ui series.

Problem

The Control UI is a browser SPA, but operators running their business through it want a native desktop window — a real control hub, not another browser tab competing with everything else. The roadmap's deep-links and approval flows also want OS-level integration (link handling, notifications) that a browser tab can't give them.

What this adds

• A native desktop window (Electron/Tauri) hosting the Control UI.
• OS-level deep-link handling, pairing with the deep-linkable URLs item.
• Tray icon and a global hotkey to summon the dashboard.
• Native OS notifications for approvals.

How it'd be built

This is a packaging effort, not a rewrite: the Control UI is already a pure gateway-client SPA, so a native shell can host it as-is behind a webview, wiring OS deep-links and notifications into the existing gateway event stream. The web-ui roadmap deliberately does not build this — it belongs to the desktop/native track.

References

• Linux/Windows Clawdbot Apps #75 — native desktop apps.
• [Bug]: Origin validation fails for custom URL schemes (tauri://, electron://) #46520 — tauri/electron origin handling.

Desktop / native track — not a web-ui build item.