chore: rename project to clawdbot

docs/mac/child-process.md

@@ -3,17 +3,17 @@ summary: "Running the gateway as a child process of the macOS app and why"
 read_when:
   - Integrating the mac app with the gateway lifecycle
 ---
-# Clawdis gateway as a child process of the macOS app
+# Clawdbot gateway as a child process of the macOS app
 
 Date: 2025-12-06 · Status: draft · Owner: steipete
 
 Note (2025-12-19): the current implementation prefers a **launchd LaunchAgent** that runs the **bundled bun-compiled gateway**. This doc remains as an alternative mode for tighter coupling to the UI.
 
 ## Goal
-Run the Node-based Clawdis/clawdis gateway as a direct child of the LSUIElement app (instead of a launchd agent) while keeping all TCC-sensitive work inside the Swift app/broker layer and wiring the existing “Clawdis Active” toggle to start/stop the child.
+Run the Node-based Clawdbot/clawdbot gateway as a direct child of the LSUIElement app (instead of a launchd agent) while keeping all TCC-sensitive work inside the Swift app/broker layer and wiring the existing “Clawdbot Active” toggle to start/stop the child.
 
 ## When to prefer the child-process mode
-- You want gateway lifetime strictly coupled to the menu-bar app (dies when the app quits) and controlled by the “Clawdis Active” toggle without touching launchd.
+- You want gateway lifetime strictly coupled to the menu-bar app (dies when the app quits) and controlled by the “Clawdbot Active” toggle without touching launchd.
 - You’re okay giving up login persistence/auto-restart that launchd provides, or you’ll add your own backoff loop.
 - You want simpler log capture and supervision inside the app (no external plist or user-visible LaunchAgent).
 
@@ -34,11 +34,11 @@ Run the Node-based Clawdis/clawdis gateway as a direct child of the LSUIElement
 ## Process manager design (Swift Subprocess)
 - Add a small `GatewayProcessManager` (Swift) that owns:
   - `execution: Execution?` from `Swift Subprocess` to track the child.
-  - `start(config)` called when “Clawdis Active” flips ON:
-    - binary: host Node running the bundled gateway under `Clawdis.app/Contents/Resources/Gateway/`
-    - args: current clawdis entrypoint and flags
-    - cwd/env: point to `~/.clawdis` as today; inject the expanded PATH so Homebrew Node resolves under launchd
-    - output: stream stdout/stderr to `/tmp/clawdis-gateway.log` (cap buffer via Subprocess OutputLimits)
+  - `start(config)` called when “Clawdbot Active” flips ON:
+    - binary: host Node running the bundled gateway under `Clawdbot.app/Contents/Resources/Gateway/`
+    - args: current clawdbot entrypoint and flags
+    - cwd/env: point to `~/.clawdbot` as today; inject the expanded PATH so Homebrew Node resolves under launchd
+    - output: stream stdout/stderr to `/tmp/clawdbot-gateway.log` (cap buffer via Subprocess OutputLimits)
     - restart: optional linear/backoff restart if exit was non-zero and Active is still true
   - `stop()` called when Active flips OFF or app terminates: cancel the execution and `waitUntilExit`.
 - Wire SwiftUI toggle:
@@ -52,14 +52,14 @@ Run the Node-based Clawdis/clawdis gateway as a direct child of the LSUIElement
 - Host runtime should not call TCC APIs directly; keep privileged work inside the app/broker.
 
 ## Logging and observability
-- Stream child stdout/stderr to `/tmp/clawdis-gateway.log`; surface the last N lines in the Debug tab.
+- Stream child stdout/stderr to `/tmp/clawdbot-gateway.log`; surface the last N lines in the Debug tab.
 - Emit a user notification (via existing NotificationManager) on crash/exit while Active is true.
 - Add a lightweight heartbeat from Node → app (e.g., ping over stdout) so the app can show status in the menu.
 
 ## Failure/edge cases
 - App crash/quit kills the gateway. Decide if that is acceptable for the deployment tier; otherwise, stick with launchd for production and keep child-process for dev/experiments.
 - If the gateway exits repeatedly, back off (e.g., 1s/2s/5s/10s) and give up after N attempts with a menu warning.
-- Respect the existing pause semantics: when paused, the broker should return `ok=false, "clawdis paused"`; the gateway should avoid calling privileged routes while paused.
+- Respect the existing pause semantics: when paused, the broker should return `ok=false, "clawdbot paused"`; the gateway should avoid calling privileged routes while paused.
 
 ## Open questions / follow-ups
 - Do we need dual-mode (launchd for prod, child for dev)? If yes, gate via a setting or build flag.
@@ -68,5 +68,5 @@ Run the Node-based Clawdis/clawdis gateway as a direct child of the LSUIElement
 
 ## Decision snapshot (current recommendation)
 - Keep all TCC surfaces in the Swift app/broker (node commands + PeekabooBridgeHost).
-- Implement `GatewayProcessManager` with Swift Subprocess to start/stop the gateway on the “Clawdis Active” toggle.
+- Implement `GatewayProcessManager` with Swift Subprocess to start/stop the gateway on the “Clawdbot Active” toggle.
 - Maintain the launchd path as a fallback for uptime/login persistence until child-mode proves stable.