chore: rename project to clawdbot

docs/mac/peekaboo.md

@@ -1,26 +1,26 @@
 ---
-summary: "Plan for integrating Peekaboo automation into Clawdis via PeekabooBridge (socket-based TCC broker)"
+summary: "Plan for integrating Peekaboo automation into Clawdbot via PeekabooBridge (socket-based TCC broker)"
 read_when:
-  - Hosting PeekabooBridge in Clawdis.app
+  - Hosting PeekabooBridge in Clawdbot.app
   - Integrating Peekaboo as a submodule
   - Changing PeekabooBridge protocol/paths
 ---
-# Peekaboo Bridge in Clawdis (macOS UI automation broker)
+# Peekaboo Bridge in Clawdbot (macOS UI automation broker)
 
 ## TL;DR
 - **Peekaboo removed its XPC helper** and now exposes privileged automation via a **UNIX domain socket bridge** (`PeekabooBridge` / `PeekabooBridgeHost`, socket name `bridge.sock`).
-- Clawdis integrates by **optionally hosting the same bridge** inside **Clawdis.app** (user-toggleable). The primary client is the **`peekaboo` CLI** (installed via npm); Clawdis does not need its own `ui …` CLI surface.
-- For **visualizations**, we keep them in **Peekaboo.app** (best UX); Clawdis stays a thin broker host. No visualizer toggle in Clawdis.
+- Clawdbot integrates by **optionally hosting the same bridge** inside **Clawdbot.app** (user-toggleable). The primary client is the **`peekaboo` CLI** (installed via npm); Clawdbot does not need its own `ui …` CLI surface.
+- For **visualizations**, we keep them in **Peekaboo.app** (best UX); Clawdbot stays a thin broker host. No visualizer toggle in Clawdbot.
 
 Non-goals:
 - No auto-launching Peekaboo.app.
-- No onboarding deep links from the automation endpoint (Clawdis onboarding already handles permissions).
-- No AI provider/agent runtime dependencies in Clawdis (avoid pulling Tachikoma/MCP into the Clawdis app/CLI).
+- No onboarding deep links from the automation endpoint (Clawdbot onboarding already handles permissions).
+- No AI provider/agent runtime dependencies in Clawdbot (avoid pulling Tachikoma/MCP into the Clawdbot app/CLI).
 
 ## Big refactor (Dec 2025): XPC → Bridge
-Peekaboo’s privileged execution moved from “CLI → XPC helper” to “CLI → socket bridge host”. For Clawdis this is a win:
+Peekaboo’s privileged execution moved from “CLI → XPC helper” to “CLI → socket bridge host”. For Clawdbot this is a win:
 - It matches the existing “local socket + codesign checks” approach.
-- It lets us piggyback on **either** Peekaboo.app’s permissions **or** Clawdis.app’s permissions (whichever is running).
+- It lets us piggyback on **either** Peekaboo.app’s permissions **or** Clawdbot.app’s permissions (whichever is running).
 - It avoids “two apps with two TCC bubbles” unless needed.
 
 Reference (Peekaboo submodule): `docs/bridge-host.md`.
@@ -30,23 +30,23 @@ Reference (Peekaboo submodule): `docs/bridge-host.md`.
 - **Bridge hosts** (provide TCC-backed automation):
   - **Peekaboo.app** (preferred; also provides visualizations + controls)
   - **Claude.app** (secondary; lets `peekaboo` reuse Claude Desktop’s granted permissions)
-  - **Clawdis.app** (secondary; “thin host” only)
+  - **Clawdbot.app** (secondary; “thin host” only)
 - **Bridge clients** (trigger single actions):
   - `peekaboo …` (preferred; humans + agents)
-  - Optional: Clawdis/Node shells out to `peekaboo` when it needs UI automation/capture
+  - Optional: Clawdbot/Node shells out to `peekaboo` when it needs UI automation/capture
 
 ### Host discovery (client-side)
 Order is deliberate:
 1. Peekaboo.app host (full UX)
 2. Claude.app host (piggyback on Claude Desktop permissions)
-3. Clawdis.app host (piggyback on Clawdis permissions)
+3. Clawdbot.app host (piggyback on Clawdbot permissions)
 
 Socket paths (convention; exact paths must match Peekaboo):
 - Peekaboo: `~/Library/Application Support/Peekaboo/bridge.sock`
 - Claude: `~/Library/Application Support/Claude/bridge.sock`
-- Clawdis: `~/Library/Application Support/clawdis/bridge.sock`
+- Clawdbot: `~/Library/Application Support/clawdbot/bridge.sock`
 
-No auto-launch: if a host isn’t reachable, the command fails with a clear error (start Peekaboo.app, Claude.app, or Clawdis.app).
+No auto-launch: if a host isn’t reachable, the command fails with a clear error (start Peekaboo.app, Claude.app, or Clawdbot.app).
 
 Override (debugging): set `PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock`.
 
@@ -58,22 +58,22 @@ Override (debugging): set `PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock`.
 ## Dependency strategy (submodule)
 Integrate Peekaboo via git submodule (nested submodules are OK).
 
-Path in Clawdis repo:
+Path in Clawdbot repo:
 - `./Peekaboo` (Swabble-style; keep stable so SwiftPM path deps don’t churn).
 
-What Clawdis should use:
+What Clawdbot should use:
 - **Client side**: `PeekabooBridge` (socket client + protocol models).
-- **Host side (Clawdis.app)**: `PeekabooBridgeHost` + the minimal Peekaboo services needed to implement operations.
+- **Host side (Clawdbot.app)**: `PeekabooBridgeHost` + the minimal Peekaboo services needed to implement operations.
 
-What Clawdis should *not* embed:
+What Clawdbot should *not* embed:
 - **Visualizer UI**: keep it in Peekaboo.app for now (toggle + controls live there).
 - **XPC**: don’t reintroduce helper targets; use the bridge.
 
 ## IPC / CLI surface
-### No `clawdis ui …`
-We avoid a parallel “Clawdis UI automation CLI”. Instead:
+### No `clawdbot ui …`
+We avoid a parallel “Clawdbot UI automation CLI”. Instead:
 - `peekaboo` is the user/agent-facing CLI surface for automation and capture.
-- Clawdis.app can host PeekabooBridge as a **thin TCC broker** so Peekaboo can piggyback on Clawdis permissions when Peekaboo.app isn’t running.
+- Clawdbot.app can host PeekabooBridge as a **thin TCC broker** so Peekaboo can piggyback on Clawdbot permissions when Peekaboo.app isn’t running.
 
 ### Diagnostics
 Use Peekaboo’s built-in diagnostics to see which host would be used:
@@ -94,7 +94,7 @@ Standardize for the CLI (agent-friendly): **top-left origin per screen**.
 
 Proposed request shape:
 - Requests accept `screenIndex` + `{x, y}` in that screen’s local coordinate space.
-- Clawdis.app converts to global CG coordinates using `NSScreen.screens[screenIndex].frame.origin`.
+- Clawdbot.app converts to global CG coordinates using `NSScreen.screens[screenIndex].frame.origin`.
 - Responses should echo both:
   - The resolved `screenIndex`
   - The local `{x, y}` and bounds
@@ -136,15 +136,15 @@ Practical flow (agent-friendly):
 
 ## Visualizer integration
 Keep visualizations in **Peekaboo.app** for now.
-- Clawdis hosts the bridge, but does not render overlays.
+- Clawdbot hosts the bridge, but does not render overlays.
 - Any “visualizer enabled/disabled” setting is controlled in Peekaboo.app.
 
 ## Screenshots (legacy → Peekaboo takeover)
-Clawdis should not grow a separate screenshot CLI surface.
+Clawdbot should not grow a separate screenshot CLI surface.
 
 Migration plan:
 - Use `peekaboo capture …` / `peekaboo see …` (returns a file path, default temp directory).
-- Once Clawdis’ legacy screenshot plumbing is replaced, remove it cleanly (no aliases).
+- Once Clawdbot’ legacy screenshot plumbing is replaced, remove it cleanly (no aliases).
 
 ## Permissions behavior
 If required permissions are missing:
@@ -164,7 +164,7 @@ Debug-only escape hatch (development convenience):
 
 ## Next integration steps (after this doc)
 1. Add Peekaboo as a git submodule (nested submodules OK).
-2. Host `PeekabooBridgeHost` inside Clawdis.app behind a single setting (“Enable Peekaboo Bridge”, default on).
-3. Ensure Clawdis hosts the bridge at `~/Library/Application Support/clawdis/bridge.sock` and speaks the PeekabooBridge JSON protocol.
-4. Validate with `peekaboo bridge status --verbose` that Peekaboo can select Clawdis as the fallback host (no auto-launch).
+2. Host `PeekabooBridgeHost` inside Clawdbot.app behind a single setting (“Enable Peekaboo Bridge”, default on).
+3. Ensure Clawdbot hosts the bridge at `~/Library/Application Support/clawdbot/bridge.sock` and speaks the PeekabooBridge JSON protocol.
+4. Validate with `peekaboo bridge status --verbose` that Peekaboo can select Clawdbot as the fallback host (no auto-launch).
 5. Keep all protocol decisions aligned with Peekaboo (coordinate system, element IDs, snapshot scoping, error envelopes).