docs: expand logging guidance

docs/gateway/troubleshooting.md

@@ -33,6 +33,19 @@ Doctor/daemon will show runtime state (PID/last exit) and log hints.
 - Linux systemd (if installed): `journalctl --user -u clawdbot-gateway.service -n 200 --no-pager`
 - Windows: `schtasks /Query /TN "Clawdbot Gateway" /V /FO LIST`
 
+**Enable more logging:**
+- Bump file log detail (persisted JSONL):
+  ```json
+  { "logging": { "level": "debug" } }
+  ```
+- Bump console verbosity (TTY output only):
+  ```json
+  { "logging": { "consoleLevel": "debug", "consoleStyle": "pretty" } }
+  ```
+- Quick tip: `--verbose` affects **console** output only. File logs remain controlled by `logging.level`.
+
+See [/logging](/logging) for a full overview of formats, config, and access.
+
 ### Service Environment (PATH + runtime)
 
 The gateway daemon runs with a **minimal PATH** to avoid shell/manager cruft:

docs/start/faq.md

@@ -33,10 +33,14 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
    Asks the running gateway for a full snapshot (WS-only). See [Health](/gateway/health).
 
 5) **Tail the latest log**
+   ```bash
+   clawdbot logs --follow
+   ```
+   If RPC is down, fall back to:
    ```bash
    tail -f "$(ls -t /tmp/clawdbot/clawdbot-*.log | head -1)"
    ```
-   File logs are separate from service logs; see [Logging](/gateway/logging) and [Troubleshooting](/gateway/troubleshooting).
+   File logs are separate from service logs; see [Logging](/logging) and [Troubleshooting](/gateway/troubleshooting).
 
 ## What is Clawdbot?