chore: rename project to clawdbot

docs/agent.md

@@ -6,13 +6,13 @@ read_when:
 <!-- {% raw %} -->
 # Agent Runtime 🤖
 
-CLAWDIS runs a single embedded agent runtime derived from **p-mono** (internal name: **p**).
+CLAWDBOT runs a single embedded agent runtime derived from **p-mono** (internal name: **p**).
 
 ## Workspace (required)
 
-You must set an agent home directory via `agent.workspace`. CLAWDIS uses this as the agent’s **only** working directory (`cwd`) for tools and context.
+You must set an agent home directory via `agent.workspace`. CLAWDBOT uses this as the agent’s **only** working directory (`cwd`) for tools and context.
 
-Recommended: use `clawdis setup` to create `~/.clawdis/clawdis.json` if missing and initialize the workspace files.
+Recommended: use `clawdbot setup` to create `~/.clawdbot/clawdbot.json` if missing and initialize the workspace files.
 
 If `agent.sandbox` is enabled, non-main sessions can override this with
 per-session workspaces under `agent.sandbox.workspaceRoot` (see
@@ -20,7 +20,7 @@ per-session workspaces under `agent.sandbox.workspaceRoot` (see
 
 ## Bootstrap files (injected)
 
-Inside `agent.workspace`, CLAWDIS expects these user-editable files:
+Inside `agent.workspace`, CLAWDBOT expects these user-editable files:
 - `AGENTS.md` — operating instructions + “memory”
 - `SOUL.md` — persona, boundaries, tone
 - `TOOLS.md` — user-maintained tool notes (e.g. `imsg`, `sag`, conventions)
@@ -28,9 +28,9 @@ Inside `agent.workspace`, CLAWDIS expects these user-editable files:
 - `IDENTITY.md` — agent name/vibe/emoji
 - `USER.md` — user profile + preferred address
 
-On the first turn of a new session, CLAWDIS injects the contents of these files directly into the agent context.
+On the first turn of a new session, CLAWDBOT injects the contents of these files directly into the agent context.
 
-If a file is missing, CLAWDIS injects a single “missing file” marker line (and `clawdis setup` will create a safe default template).
+If a file is missing, CLAWDBOT injects a single “missing file” marker line (and `clawdbot setup` will create a safe default template).
 
 ## Built-in tools (internal)
 
@@ -38,16 +38,16 @@ p’s embedded core tools (read/bash/edit/write and related internals) are defin
 
 ## Skills
 
-Clawdis loads skills from three locations (workspace wins on name conflict):
+Clawdbot loads skills from three locations (workspace wins on name conflict):
 - Bundled (shipped with the install)
-- Managed/local: `~/.clawdis/skills`
+- Managed/local: `~/.clawdbot/skills`
 - Workspace: `<workspace>/skills`
 
 Skills can be gated by config/env (see `skills` in `docs/configuration.md`).
 
 ## p-mono integration
 
-Clawdis reuses pieces of the p-mono codebase (models/tools), but **session management, discovery, and tool wiring are Clawdis-owned**.
+Clawdbot reuses pieces of the p-mono codebase (models/tools), but **session management, discovery, and tool wiring are Clawdbot-owned**.
 
 - No p-coding agent runtime.
 - No `~/.pi/agent` or `<workspace>/.pi` settings are consulted.
@@ -61,15 +61,15 @@ Apply these notes **only** when the user is Peter Steinberger at steipete.
 - Peter travels between **Vienna** and **London**; there are two networks bridged via **Tailscale**.
 - For debugging, connect to the Mac Studio (London) or MacBook Pro (primary).
 - There is also an **M1 MacBook Pro** on the Vienna tailnet you can use to access the Vienna network.
-- Nodes can be accessed via the `clawdis` binary (`pnpm clawdis` in `~/Projects/clawdis`).
-- See also `skills/clawdis*` for node/browser/canvas/cron usage.
+- Nodes can be accessed via the `clawdbot` binary (`pnpm clawdbot` in `~/Projects/clawdbot`).
+- See also `skills/clawdbot*` for node/browser/canvas/cron usage.
 
 ## Sessions
 
 Session transcripts are stored as JSONL at:
-- `~/.clawdis/sessions/<SessionId>.jsonl`
+- `~/.clawdbot/sessions/<SessionId>.jsonl`
 
-The session ID is stable and chosen by CLAWDIS.
+The session ID is stable and chosen by CLAWDBOT.
 Legacy Pi/Tau session folders are **not** read.
 
 ## Steering while streaming