OpenClaw Gateway as alternative backend (memory, tools, multi-model)

Summary Clicky is amazing as a screen-aware voice companion — the cursor overlay, push-to-talk, and POINT system are genuinely next-level UX. But right now it's a stateless Claude wrapper: no memory between sessions, no tools, no persistent context. I'd like to propose adding OpenClaw (https://github.com/openclaw/openclaw) Gateway as an optional alternative backend — so Clicky can talk to a full personal AI agent instead of vanilla Claude. What is OpenClaw? OpenClaw is an open-source (MIT) self-hosted AI gateway that connects agents to messaging surfaces (WhatsApp, Telegram, Slack, Discord, etc.). It provides: • Persistent memory — workspace files, conversation history across sessions • Tool use — browser control, code execution, file system, git, cron jobs • Multi-model — Claude, GPT, Gemini, and others via a single gateway • Built-in TTS — ElevenLabs already integrated (reusable for Clicky) • Skills system — extensible agent capabilities It exposes a WebSocket Protocol (v3) that native apps already use (macOS menu bar app, iOS/Android nodes). Proposed Architecture Clicky (Swift) ←→ WS Protocol v3 ←→ OpenClaw Gateway ←→ Agent (memory + tools + skills) The key idea: replace the Cloudflare Worker proxy with a direct WebSocket connection to OpenClaw Gateway. The Worker becomes optional (standalone fallback mode). Changes in Clicky: 1. New OpenClawClient.swift — WebSocket client implementing Gateway Protocol v3 (connect, challenge/auth, chat.send, event streaming) 2. Re...