refactor: rename clawdbot to moltbot with legacy compat

docs/cli/acp.md

@@ -7,7 +7,7 @@ read_when:
 
 # acp
 
-Run the ACP (Agent Client Protocol) bridge that talks to a Clawdbot Gateway.
+Run the ACP (Agent Client Protocol) bridge that talks to a Moltbot Gateway.
 
 This command speaks ACP over stdio for IDEs and forwards prompts to the Gateway
 over WebSocket. It keeps ACP sessions mapped to Gateway session keys.
@@ -15,19 +15,19 @@ over WebSocket. It keeps ACP sessions mapped to Gateway session keys.
 ## Usage
 
 ```bash
-clawdbot acp
+moltbot acp
 
 # Remote Gateway
-clawdbot acp --url wss://gateway-host:18789 --token <token>
+moltbot acp --url wss://gateway-host:18789 --token <token>
 
 # Attach to an existing session key
-clawdbot acp --session agent:main:main
+moltbot acp --session agent:main:main
 
 # Attach by label (must already exist)
-clawdbot acp --session-label "support inbox"
+moltbot acp --session-label "support inbox"
 
 # Reset the session key before the first prompt
-clawdbot acp --session agent:main:main --reset-session
+moltbot acp --session agent:main:main --reset-session
 ```
 
 ## ACP client (debug)
@@ -36,35 +36,35 @@ Use the built-in ACP client to sanity-check the bridge without an IDE.
 It spawns the ACP bridge and lets you type prompts interactively.
 
 ```bash
-clawdbot acp client
+moltbot acp client
 
 # Point the spawned bridge at a remote Gateway
-clawdbot acp client --server-args --url wss://gateway-host:18789 --token <token>
+moltbot acp client --server-args --url wss://gateway-host:18789 --token <token>
 
-# Override the server command (default: clawdbot)
-clawdbot acp client --server "node" --server-args dist/entry.js acp --url ws://127.0.0.1:19001
+# Override the server command (default: moltbot)
+moltbot acp client --server "node" --server-args dist/entry.js acp --url ws://127.0.0.1:19001
 ```
 
 ## How to use this
 
 Use ACP when an IDE (or other client) speaks Agent Client Protocol and you want
-it to drive a Clawdbot Gateway session.
+it to drive a Moltbot Gateway session.
 
 1. Ensure the Gateway is running (local or remote).
 2. Configure the Gateway target (config or flags).
-3. Point your IDE to run `clawdbot acp` over stdio.
+3. Point your IDE to run `moltbot acp` over stdio.
 
 Example config (persisted):
 
 ```bash
-clawdbot config set gateway.remote.url wss://gateway-host:18789
-clawdbot config set gateway.remote.token <token>
+moltbot config set gateway.remote.url wss://gateway-host:18789
+moltbot config set gateway.remote.token <token>
 ```
 
 Example direct run (no config write):
 
 ```bash
-clawdbot acp --url wss://gateway-host:18789 --token <token>
+moltbot acp --url wss://gateway-host:18789 --token <token>
 ```
 
 ## Selecting agents
@@ -74,9 +74,9 @@ ACP does not pick agents directly. It routes by the Gateway session key.
 Use agent-scoped session keys to target a specific agent:
 
 ```bash
-clawdbot acp --session agent:main:main
-clawdbot acp --session agent:design:main
-clawdbot acp --session agent:qa:bug-123
+moltbot acp --session agent:main:main
+moltbot acp --session agent:design:main
+moltbot acp --session agent:qa:bug-123
 ```
 
 Each ACP session maps to a single Gateway session key. One agent can have many
@@ -90,9 +90,9 @@ Add a custom ACP agent in `~/.config/zed/settings.json` (or use Zed’s Settings
 ```json
 {
   "agent_servers": {
-    "Clawdbot ACP": {
+    "Moltbot ACP": {
       "type": "custom",
-      "command": "clawdbot",
+      "command": "moltbot",
       "args": ["acp"],
       "env": {}
     }
@@ -105,9 +105,9 @@ To target a specific Gateway or agent:
 ```json
 {
   "agent_servers": {
-    "Clawdbot ACP": {
+    "Moltbot ACP": {
       "type": "custom",
-      "command": "clawdbot",
+      "command": "moltbot",
       "args": [
         "acp",
         "--url", "wss://gateway-host:18789",
@@ -120,7 +120,7 @@ To target a specific Gateway or agent:
 }
 ```
 
-In Zed, open the Agent panel and select “Clawdbot ACP” to start a thread.
+In Zed, open the Agent panel and select “Moltbot ACP” to start a thread.
 
 ## Session mapping
 
@@ -160,7 +160,7 @@ Learn more about session keys at [/concepts/session](/concepts/session).
 ### `acp client` options
 
 - `--cwd <dir>`: working directory for the ACP session.
-- `--server <command>`: ACP server command (default: `clawdbot`).
+- `--server <command>`: ACP server command (default: `moltbot`).
 - `--server-args <args...>`: extra arguments passed to the ACP server.
 - `--server-verbose`: enable verbose logging on the ACP server.
 - `--verbose, -v`: verbose client logging.