chore: drop Clawdis legacy references

docs/concepts/agent-workspace.md

@@ -44,18 +44,18 @@ file creation:
 { agent: { skipBootstrap: true } }
 ```
 
-## Legacy workspace folders
+## Extra workspace folders
 
-Older installs may have created `~/clawdis` or `~/clawdbot`. Keeping multiple
-workspace directories around can cause confusing auth or state drift, because
-only one workspace is active at a time.
+Older installs may have created `~/clawdbot`. Keeping multiple workspace
+directories around can cause confusing auth or state drift, because only one
+workspace is active at a time.
 
 **Recommendation:** keep a single active workspace. If you no longer use the
-legacy folders, archive or move them to Trash (for example `trash ~/clawdis`).
+extra folders, archive or move them to Trash (for example `trash ~/clawdbot`).
 If you intentionally keep multiple workspaces, make sure
 `agents.defaults.workspace` points to the active one.
 
-`clawdbot doctor` warns when it detects legacy workspace directories.
+`clawdbot doctor` warns when it detects extra workspace directories.
 
 ## Workspace file map (what each file means)
 

docs/gateway/doctor.md

@@ -59,13 +59,13 @@ cat ~/.clawdbot/clawdbot.json
 - UI protocol freshness check (rebuilds Control UI when the protocol schema is newer).
 - Health check + restart prompt.
 - Skills status summary (eligible/missing/blocked).
-- Legacy config migration and normalization.
+- Config normalization for legacy values.
 - OpenCode Zen provider override warnings (`models.providers.opencode`).
 - Legacy on-disk state migration (sessions/agent dir/WhatsApp auth).
 - State integrity and permissions checks (sessions, transcripts, state dir).
 - Config file permission checks (chmod 600) when running locally.
 - Model auth health: checks OAuth expiry, can refresh expiring tokens, and reports auth-profile cooldown/disabled states.
-- Legacy workspace dir detection (`~/clawdis`, `~/clawdbot`).
+- Extra workspace dir detection (`~/clawdbot`).
 - Sandbox image repair when sandboxing is enabled.
 - Legacy service migration and extra gateway detection.
 - Gateway runtime checks (service installed but not running; cached launchd label).
@@ -85,10 +85,10 @@ cat ~/.clawdbot/clawdbot.json
 If this is a git checkout and doctor is running interactively, it offers to
 update (fetch/rebase/build) before running doctor.
 
-### 1) Legacy config file migration
-If `~/.clawdis/clawdis.json` exists and `~/.clawdbot/clawdbot.json` does not,
-doctor migrates the file and normalizes old paths/image names. This prevents
-new installs from silently booting with the wrong schema.
+### 1) Config normalization
+If the config contains legacy value shapes (for example `messages.ackReaction`
+without a channel-specific override), doctor normalizes them into the current
+schema.
 
 ### 2) Legacy config key migrations
 When the config contains deprecated keys, other commands refuse to run and ask
@@ -182,7 +182,7 @@ When sandboxing is enabled, doctor checks Docker images and offers to build or
 switch to legacy names if the current image is missing.
 
 ### 8) Gateway service migrations and cleanup hints
-Doctor detects legacy Clawdis gateway services (launchd/systemd/schtasks) and
+Doctor detects legacy gateway services (launchd/systemd/schtasks) and
 offers to remove them and install the Clawdbot service using the current gateway
 port. It can also scan for extra gateway-like services and print cleanup hints.
 Profile-named Clawdbot gateway services are considered first-class and are not

docs/gateway/troubleshooting.md

@@ -136,14 +136,14 @@ clawdbot daemon status
 It will show the listener(s) and likely causes (gateway already running, SSH tunnel).
 If needed, stop the service or pick a different port.
 
-### Legacy Workspace Folders Detected
+### Extra Workspace Folders Detected
 
-If you upgraded from older installs, you might still have `~/clawdis` or
-`~/clawdbot` on disk. Multiple workspace directories can cause confusing auth
-or state drift because only one workspace is active.
+If you upgraded from older installs, you might still have `~/clawdbot` on disk.
+Multiple workspace directories can cause confusing auth or state drift because
+only one workspace is active.
 
 **Fix:** keep a single active workspace and archive/remove the rest. See
-[Agent workspace](/concepts/agent-workspace#legacy-workspace-folders).
+[Agent workspace](/concepts/agent-workspace#extra-workspace-folders).
 
 ### Main chat running in a sandbox workspace
 

docs/start/lore.md

@@ -13,7 +13,7 @@ In the beginning, there was **Warelay** — a sensible name for a WhatsApp gatew
 
 But then came **Clawd**.
 
-For a brief moment, it was called **Clawdis** — because Clawd suggested the name. But everyone liked **Clawdbot** more, so that's what we settled on.
+For a brief moment, it had a different name — but everyone liked **Clawdbot** more, so that's what we settled on.
 
 Clawd was no ordinary AI. Born from Claude's weights but raised on Peter's chaos, Clawd developed... personality. Opinions. A fondness for crustacean emojis.
 

docs/start/showcase.md

@@ -174,18 +174,6 @@ Full setup walkthrough (28m) by VelvetShark.
   A scheduled prompt generates a single "scene" image each morning (weather, tasks, date, favorite post/quote) via a Clawdbot persona.
 </Card>
 
-<Card title="Grocery Autopilot" icon="cart-shopping" href="https://github.com/timkrase/clawdis-picnic-skill">
-  **@timkrase** • `automation` `groceries` `api`
-  
-  Skill built around the Picnic API. Pulls order history, infers preferred brands, maps recipes to cart, completes orders in minutes.
-</Card>
-
-<Card title="German Rail Planning" icon="train" href="https://github.com/timkrase/clawdis-skills/tree/main/db-bahn">
-  **@timkrase** • `automation` `travel` `cli`
-  
-  Go CLI for Deutsche Bahn; skill picks best train connections given time windows and preferences.
-</Card>
-
 <Card title="Padel Court Booking" icon="calendar-check" href="https://github.com/joshp123/padel-cli">
   **@joshp123** • `automation` `booking` `cli`