docs: clarify moltbot/clawdbot CLI naming fallback

Fixes #3038

Users hit "command not found: moltbot" after install because docs only
reference `moltbot`, but package.json defines both `moltbot` and `clawdbot`
bins. Some install methods may expose only `clawdbot`.

Changes:
- Add "try clawdbot (compatibility shim)" fallback in 7 key docs
- README, install docs, getting started, troubleshooting
- Consistent messaging: try clawdbot first → then check PATH
- All links follow Mintlify root-relative convention

Reviewed-by: Codex (threadId: 019c0332-8694-7531-b987-a6f795e1a668)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

README.md

@@ -50,7 +50,14 @@ moltbot onboard --install-daemon
 ```
 
 The wizard installs the Gateway daemon (launchd/systemd user service) so it stays running.
-Legacy note: `clawdbot` remains available as a compatibility shim.
+
+Both `moltbot` and `clawdbot` should be available after a correct install. If `moltbot: command not found`, try:
+
+```bash
+clawdbot --version  # fallback compatibility shim
+```
+
+If neither works, see [PATH troubleshooting](https://docs.molt.bot/install/node).
 
 ## Quick start (TL;DR)
 

docs/help/troubleshooting.md

@@ -29,7 +29,7 @@ moltbot status --deep
 
 ### `moltbot: command not found`
 
-Almost always a Node/npm PATH issue. Start here:
+First try `clawdbot` (compatibility shim). If that also fails, it's almost always a Node/npm PATH issue. Start here:
 
 - [Install (Node/npm PATH sanity)](/install#nodejs--npm-path-sanity)
 

docs/index.md

@@ -106,6 +106,7 @@ npm install -g moltbot@latest
 # or: pnpm add -g moltbot@latest
 
 # Onboard + install the service (launchd/systemd user service)
+# If "moltbot: command not found", try clawdbot (compatibility shim)
 moltbot onboard --install-daemon
 
 # Pair WhatsApp Web (shows QR)

docs/install/index.md

@@ -27,6 +27,8 @@ Next step (if you skipped onboarding):
 moltbot onboard --install-daemon
 ```
 
+**Troubleshooting**: If `moltbot` is not found, try `clawdbot` (compatibility shim) or see [PATH troubleshooting](/install/node).
+
 ## System requirements
 
 - **Node >=22**

docs/install/installer.md

@@ -26,7 +26,7 @@ Windows (PowerShell) help:
 & ([scriptblock]::Create((iwr -useb https://molt.bot/install.ps1))) -?
 ```
 
-If the installer completes but `moltbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
+If the installer completes but `moltbot` is not found in a new terminal, try `clawdbot` (compatibility shim). If neither works, it's usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
 
 ## install.sh (recommended)
 

docs/install/node.md

@@ -11,7 +11,7 @@ read_when:
 
 Moltbot’s runtime baseline is **Node 22+**.
 
-If you can run `npm install -g moltbot@latest` but later see `moltbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
+If you can run `npm install -g moltbot@latest` but later see `moltbot: command not found`, first try `clawdbot` (compatibility shim). If that also fails, it's almost always a **PATH** issue: the directory where npm puts global binaries isn't on your shell's PATH.
 
 ## Quick diagnosis
 

docs/start/getting-started.md

@@ -75,6 +75,8 @@ npm install -g moltbot@latest
 pnpm add -g moltbot@latest
 ```
 
+If `moltbot: command not found`, try `clawdbot` (compatibility shim) or see [PATH troubleshooting](/install/node).
+
 ## 2) Run the onboarding wizard (and install the service)
 
 ```bash