chore: rename project to clawdbot

docs/setup.md

@@ -1,5 +1,5 @@
 ---
-summary: "Setup guide: keep your Clawdis setup tailored while staying up-to-date"
+summary: "Setup guide: keep your Clawdbot setup tailored while staying up-to-date"
 read_when:
   - Setting up a new machine
   - You want “latest + greatest” without breaking your personal setup
@@ -10,7 +10,7 @@ read_when:
 Last updated: 2026-01-01
 
 ## TL;DR
-- **Tailoring lives outside the repo:** `~/clawd` (workspace) + `~/.clawdis/clawdis.json` (config).
+- **Tailoring lives outside the repo:** `~/clawd` (workspace) + `~/.clawdbot/clawdbot.json` (config).
 - **Stable workflow:** install the macOS app; let it run the bundled Gateway.
 - **Bleeding edge workflow:** run the Gateway yourself via `pnpm gateway:watch`, then point the macOS app at it using **Debug Settings → Gateway → Attach only**.
 
@@ -23,40 +23,40 @@ Last updated: 2026-01-01
 
 If you want “100% tailored to me” *and* easy updates, keep your customization in:
 
-- **Config:** `~/.clawdis/clawdis.json` (JSON/JSON5-ish)
+- **Config:** `~/.clawdbot/clawdbot.json` (JSON/JSON5-ish)
 - **Workspace:** `~/clawd` (skills, prompts, memories; make it a private git repo)
 
 Bootstrap once:
 
 ```bash
-clawdis setup
+clawdbot setup
 ```
 
 From inside this repo, use the local CLI entry:
 
 ```bash
-pnpm clawdis setup
+pnpm clawdbot setup
 ```
 
 ## Stable workflow (macOS app first)
 
-1) Install + launch **Clawdis.app** (menu bar).
+1) Install + launch **Clawdbot.app** (menu bar).
 2) Complete the onboarding/permissions checklist (TCC prompts).
 3) Ensure Gateway is **Local** and running (the app manages it).
 4) Link surfaces (example: WhatsApp):
 
 ```bash
-clawdis login
+clawdbot login
 ```
 
 5) Sanity check:
 
 ```bash
-clawdis health
+clawdbot health
 ```
 
 If onboarding is still WIP/broken on your build:
-- Run `clawdis setup`, then `clawdis login`, then start the Gateway manually (`clawdis gateway`).
+- Run `clawdbot setup`, then `clawdbot login`, then start the Gateway manually (`clawdbot gateway`).
 
 ## Bleeding edge workflow (Gateway in a terminal)
 
@@ -81,7 +81,7 @@ pnpm gateway:watch
 
 ### 2) Point the macOS app at your running Gateway
 
-In **Clawdis.app**:
+In **Clawdbot.app**:
 
 - Connection Mode: **Local**
 - Settings → **Debug Settings** → **Gateway** → enable **Attach only**
@@ -94,19 +94,19 @@ This makes the app **only connect to an already-running gateway** and **never sp
 - Or via CLI:
 
 ```bash
-pnpm clawdis health
+pnpm clawdbot health
 ```
 
 ### Common footguns
 - **Attach only enabled, but nothing is running:** app shows “Attach-only enabled; no gateway to attach”.
 - **Wrong port:** Gateway WS defaults to `ws://127.0.0.1:18789`; keep app + CLI on the same port.
 - **Where state lives:**
-  - Credentials: `~/.clawdis/credentials/`
-  - Sessions/logs: `~/.clawdis/sessions/`
+  - Credentials: `~/.clawdbot/credentials/`
+  - Sessions/logs: `~/.clawdbot/sessions/`
 
 ## Updating (without wrecking your setup)
 
-- Keep `~/clawd` and `~/.clawdis/` as “your stuff”; don’t put personal prompts/config into the `clawdis` repo.
+- Keep `~/clawd` and `~/.clawdbot/` as “your stuff”; don’t put personal prompts/config into the `clawdbot` repo.
 - Updating source: `git pull` + `pnpm install` (when lockfile changed) + keep using `pnpm gateway:watch`.
 
 ## Related docs
@@ -115,4 +115,4 @@ pnpm clawdis health
 - `docs/configuration.md` (config schema + examples)
 - `docs/discord.md` and `docs/telegram.md` (reply tags + replyToMode settings)
 - `docs/clawd.md` (personal assistant setup)
-- `docs/clawdis-mac.md` (macOS app behavior; gateway lifecycle + “Attach only”)
+- `docs/clawdbot-mac.md` (macOS app behavior; gateway lifecycle + “Attach only”)