docs(website): update website for project reorganization

- Fix openclaw-migration.md: bridges now exist, web UI exists
- Update intro.md: mention all bridges (Telegram, Discord, WhatsApp)
- Update HomepageFeatures: reflect bridge integrations

Co-authored-by: yiwang <142937+yiwang@users.noreply.github.com>

Author: Copilot

website/docs/intro.md

@@ -14,7 +14,7 @@ LocalGPT is a **local AI assistant with persistent memory, semantic search, and
 - **Desktop App** - Optional native desktop GUI built with egui — chat, sessions, memory browser, and status dashboard. Disable with `--no-default-features` for headless/Docker deployments.
 - **Embedded Web UI** - Browser-based chat interface served directly from the binary
 - **Multi-Provider Support** - Works with Claude CLI, Anthropic API, OpenAI, Ollama, and GLM (Z.AI) — all with full tool calling support
-- **Telegram Bot** - Access LocalGPT from Telegram with full chat, tool use, and memory support — secured with one-time pairing auth
+- **Telegram, Discord & WhatsApp** - Access LocalGPT from Telegram, Discord, or WhatsApp via bridge binaries with full chat, tool use, and memory support — secured with one-time pairing auth
 - **Autonomous Heartbeat** - Daemon mode with scheduled background tasks that run automatically
 - **Skills System** - Extensible skills for specialized tasks
 - **Shell Sandbox** - Kernel-level isolation (Landlock + seccomp + Seatbelt) on every shell command. Zero configuration, enabled by default, graceful degradation. [Not a guarantee](/docs/sandbox#limitations) — defense in depth.

website/docs/openclaw-migration.md

@@ -71,12 +71,12 @@ This preserves your conversation history, session IDs, and CLI session mappings.
 
 ## Key differences
 
-LocalGPT removes several OpenClaw features that were specific to multi-channel or remote operation:
+LocalGPT takes a different approach from OpenClaw in several areas:
 
-- **No remote channels** — Telegram, Discord, Slack, and other integrations are removed (Telegram bot is available as a separate feature)
+- **Bridge-based integrations** — Telegram, Discord, and WhatsApp are supported via standalone bridge binaries in the `bridges/` directory, connected to the daemon via secure IPC (rather than built-in channels)
 - **No plugin/extension system** — LocalGPT uses a simpler skills-based approach
-- **No gateway routing** — single-agent, local-first design
-- **No web UI/Canvas** — CLI and HTTP API only
+- **No gateway routing** — single-agent, local-first design with bridge daemons instead of a multi-channel gateway
+- **Embedded web UI** — browser-based chat interface served directly from the binary, plus an optional desktop GUI (egui)
 - **No subagent spawning** — single "main" agent
 
 Everything else — memory, heartbeat, skills, session management — works the same way.

website/src/components/HomepageFeatures/index.tsx

@@ -31,13 +31,13 @@ const FeatureList: FeatureItem[] = [
     ),
   },
   {
-    title: 'Desktop, Web, CLI & Telegram',
+    title: 'Desktop, Web, CLI & Bridges',
     description: (
       <>
-        Four ways to interact: a full-featured CLI, an optional native desktop
-        GUI (egui), an embedded web UI, and a Telegram bot with one-time pairing
-        auth. Build with <code>--no-default-features</code> for headless
-        Docker/server deployments.
+        Multiple ways to interact: a full-featured CLI, an optional native desktop
+        GUI (egui), an embedded web UI, and bridge integrations for Telegram,
+        Discord, and WhatsApp. Build with <code>--no-default-features</code> for
+        headless Docker/server deployments.
       </>
     ),
   },