docs(status): add diagnostics commands

docs/gateway/troubleshooting.md

@@ -11,6 +11,24 @@ Start with the FAQ’s [First 60 seconds](/start/faq#first-60-seconds-if-somethi
 
 Provider-specific shortcuts: [/providers/troubleshooting](/providers/troubleshooting)
 
+## Status & Diagnostics
+
+Quick triage commands (in order):
+
+| Command | What it tells you | When to use it |
+|---|---|---|
+| `clawdbot status` | Local summary: OS + update, gateway reachability/mode, daemon, agents/sessions, provider config state | First check, quick overview |
+| `clawdbot status --all` | Full local diagnosis (read-only, pasteable, safe-ish) incl. log tail | When you need to share a debug report |
+| `clawdbot status --deep` | Runs local provider probes (WhatsApp connect + Telegram/Discord APIs) | When “configured” doesn’t mean “working” |
+| `clawdbot gateway status` | Gateway discovery + reachability (local + remote targets) | When you suspect you’re probing the wrong gateway |
+| `clawdbot providers status --probe` | Asks the running gateway for provider status (and optionally probes) | When gateway is reachable but providers misbehave |
+| `clawdbot daemon status` | Supervisor state (launchd/systemd/schtasks), runtime PID/exit, last gateway error | When the daemon “looks loaded” but nothing runs |
+| `clawdbot logs --follow` | Live logs (best signal for runtime issues) | When you need the actual failure reason |
+
+**Sharing output:** prefer `clawdbot status --all` (it redacts tokens). If you paste `clawdbot status`, consider setting `CLAWDBOT_SHOW_SECRETS=0` first (token previews).
+
+See also: [Health checks](/gateway/health) and [Logging](/logging).
+
 ## Common Issues
 
 ### Service Installed but Nothing is Running