chore: rename project to clawdbot

docs/mac/canvas.md

@@ -12,7 +12,7 @@ Status: draft spec · Date: 2025-12-12
 
 Note: for iOS/Android nodes that should render agent-edited HTML/CSS/JS over the network, prefer the Gateway `canvasHost` (serves `~/clawd/canvas` over LAN/tailnet with live reload). A2UI is also **hosted by the Gateway** over HTTP. This doc focuses on the macOS in-app canvas panel. See `docs/configuration.md`.
 
-Clawdis can embed an agent-controlled “visual workspace” panel (“Canvas”) inside the macOS app using `WKWebView`, served via a **custom URL scheme** (no loopback HTTP port required).
+Clawdbot can embed an agent-controlled “visual workspace” panel (“Canvas”) inside the macOS app using `WKWebView`, served via a **custom URL scheme** (no loopback HTTP port required).
 
 This is designed for:
 - Agent-written HTML/CSS/JS on disk (per-session directory).
@@ -32,12 +32,12 @@ If a Canvas page truly needs “real web” semantics (CORS, fetch to loopback e
 ## URL ↔ directory mapping
 
 The Canvas scheme is:
-- `clawdis-canvas://<session>/<path>`
+- `clawdbot-canvas://<session>/<path>`
 
 Routing model:
-- `clawdis-canvas://main/` → `<canvasRoot>/main/index.html` (or `index.htm`)
-- `clawdis-canvas://main/yolo` → `<canvasRoot>/main/yolo/index.html` (or `index.htm`)
-- `clawdis-canvas://main/assets/app.css` → `<canvasRoot>/main/assets/app.css`
+- `clawdbot-canvas://main/` → `<canvasRoot>/main/index.html` (or `index.htm`)
+- `clawdbot-canvas://main/yolo` → `<canvasRoot>/main/yolo/index.html` (or `index.htm`)
+- `clawdbot-canvas://main/assets/app.css` → `<canvasRoot>/main/assets/app.css`
 
 Directory listings are not served.
 
@@ -47,9 +47,9 @@ This is a visual placeholder only (no A2UI renderer).
 ### Suggested on-disk location
 
 Store Canvas state under the app support directory:
-- `~/Library/Application Support/Clawdis/canvas/<session>/…`
+- `~/Library/Application Support/Clawdbot/canvas/<session>/…`
 
-This keeps it alongside other app-owned state and avoids mixing with `~/.clawdis/` gateway config.
+This keeps it alongside other app-owned state and avoids mixing with `~/.clawdbot/` gateway config.
 
 ## Panel behavior (agent-controlled)
 
@@ -78,34 +78,34 @@ Canvas is exposed via the Gateway **node bridge**, so the agent can:
 - Capture a snapshot image of the current canvas view.
 - Optionally set panel placement (screen `x/y` + `width/height`) when showing/navigating.
 
-This should be modeled after `WebChatManager`/`WebChatSwiftUIWindowController` but targeting `clawdis-canvas://…` URLs.
+This should be modeled after `WebChatManager`/`WebChatSwiftUIWindowController` but targeting `clawdbot-canvas://…` URLs.
 
 Related:
-- For “invoke the agent again from UI” flows, prefer the macOS deep link scheme (`clawdis://agent?...`) so *any* UI surface (Canvas, WebChat, native views) can trigger a new agent run. See `docs/clawdis-mac.md`.
+- For “invoke the agent again from UI” flows, prefer the macOS deep link scheme (`clawdbot://agent?...`) so *any* UI surface (Canvas, WebChat, native views) can trigger a new agent run. See `docs/clawdbot-mac.md`.
 
 ## Agent commands (current)
 
-Use the main `clawdis` CLI; it invokes canvas commands via `node.invoke`.
+Use the main `clawdbot` CLI; it invokes canvas commands via `node.invoke`.
 
-- `clawdis canvas present [--node <id>] [--target <...>] [--x/--y/--width/--height]`
+- `clawdbot canvas present [--node <id>] [--target <...>] [--x/--y/--width/--height]`
   - Local targets map into the session directory via the custom scheme (directory targets resolve `index.html|index.htm`).
   - If `/` has no index file, Canvas shows the built-in scaffold page and returns `status: "welcome"`.
-- `clawdis canvas hide [--node <id>]`
-- `clawdis canvas eval --js <code> [--node <id>]`
-- `clawdis canvas snapshot [--node <id>]`
+- `clawdbot canvas hide [--node <id>]`
+- `clawdbot canvas eval --js <code> [--node <id>]`
+- `clawdbot canvas snapshot [--node <id>]`
 
 ### Canvas A2UI
 
 Canvas A2UI is hosted by the **Gateway canvas host** at:
 
 ```
-http://<gateway-host>:18793/__clawdis__/a2ui/
+http://<gateway-host>:18793/__clawdbot__/a2ui/
 ```
 
 The macOS app simply renders that page in the Canvas panel. The agent can drive it with JSONL **server→client protocol messages** (one JSON object per line):
 
-- `clawdis canvas a2ui push --jsonl <path> [--node <id>]`
-- `clawdis canvas a2ui reset [--node <id>]`
+- `clawdbot canvas a2ui push --jsonl <path> [--node <id>]`
+- `clawdbot canvas a2ui reset [--node <id>]`
 
 `push` expects a JSONL file where **each line is a single JSON object** (parsed and forwarded to the in-page A2UI renderer).
 
@@ -117,31 +117,31 @@ cat > /tmp/a2ui-v0.8.jsonl <<'EOF'
 {"beginRendering":{"surfaceId":"main","root":"root"}}
 EOF
 
-clawdis canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node <id>
+clawdbot canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node <id>
 ```
 
 Notes:
 - This does **not** support the A2UI v0.9 examples using `createSurface`.
 - A2UI **fails** if the Gateway canvas host is unreachable (no local fallback).
 - `canvas a2ui push` validates JSONL (line numbers on errors) and rejects v0.9 payloads.
-- Quick smoke: `clawdis canvas a2ui push --text "Hello from A2UI"` renders a minimal v0.8 view.
+- Quick smoke: `clawdbot canvas a2ui push --text "Hello from A2UI"` renders a minimal v0.8 view.
 
 ## Triggering agent runs from Canvas (deep links)
 
 Canvas can trigger new agent runs via the macOS app deep-link scheme:
-- `clawdis://agent?...`
+- `clawdbot://agent?...`
 
-This is intentionally separate from `clawdis-canvas://…` (which is only for serving local Canvas files into the `WKWebView`).
+This is intentionally separate from `clawdbot-canvas://…` (which is only for serving local Canvas files into the `WKWebView`).
 
 Suggested patterns:
-- HTML: render links/buttons that navigate to `clawdis://agent?message=...`.
-- JS: set `window.location.href = 'clawdis://agent?...'` for “run this now” actions.
+- HTML: render links/buttons that navigate to `clawdbot://agent?message=...`.
+- JS: set `window.location.href = 'clawdbot://agent?...'` for “run this now” actions.
 
 Implementation note (important):
-- In `WKWebView`, intercept `clawdis://…` navigations in `WKNavigationDelegate` and forward them to the app, e.g. by calling `DeepLinkHandler.shared.handle(url:)` and returning `.cancel` for the navigation.
+- In `WKWebView`, intercept `clawdbot://…` navigations in `WKNavigationDelegate` and forward them to the app, e.g. by calling `DeepLinkHandler.shared.handle(url:)` and returning `.cancel` for the navigation.
 
 Safety:
-- Deep links (`clawdis://agent?...`) are always enabled.
+- Deep links (`clawdbot://agent?...`) are always enabled.
 - Without a `key` query param, the app will prompt for confirmation before invoking the agent.
 - With a valid `key`, the run is unattended (no prompt). For Canvas-originated actions, the app injects an internal key automatically.
 
@@ -149,7 +149,7 @@ Safety:
 
 Recommended defaults:
 - `WKWebsiteDataStore.nonPersistent()` for Canvas (ephemeral).
-- Navigation policy: allow only `clawdis-canvas://…` (and optionally `about:blank`); open `http/https` externally.
+- Navigation policy: allow only `clawdbot-canvas://…` (and optionally `about:blank`); open `http/https` externally.
 - Scheme handler must prevent directory traversal: resolved file paths must stay under `<canvasRoot>/<session>/`.
 - Disable or tightly scope any JS bridge; prefer query-string/bootstrap config over `window.webkit.messageHandlers` for sensitive data.
 
@@ -157,5 +157,5 @@ Recommended defaults:
 
 Suggested debugging hooks:
 - Enable Web Inspector for Canvas builds (same approach as WebChat).
-- Log scheme requests + resolution decisions to OSLog (subsystem `com.clawdis`, category `Canvas`).
+- Log scheme requests + resolution decisions to OSLog (subsystem `com.clawdbot`, category `Canvas`).
 - Provide a “copy canvas dir” action in debug settings to quickly reveal the session directory in Finder.