docs: expand es and pt-BR docs trees

docs/es/help/index.md

@@ -0,0 +1,21 @@
+---
+summary: "Help hub: common fixes, install sanity, and where to look when something breaks"
+read_when:
+  - You’re new and want the “what do I click/run” guide
+  - Something broke and you want the fastest path to a fix
+title: "Help"
+---
+
+# Help
+
+If you want a quick “get unstuck” flow, start here:
+
+- **Troubleshooting:** [Start here](/help/troubleshooting)
+- **Install sanity (Node/npm/PATH):** [Install](/install#nodejs--npm-path-sanity)
+- **Gateway issues:** [Gateway troubleshooting](/gateway/troubleshooting)
+- **Logs:** [Logging](/logging) and [Gateway logging](/gateway/logging)
+- **Repairs:** [Doctor](/gateway/doctor)
+
+If you’re looking for conceptual questions (not “something broke”):
+
+- [FAQ (concepts)](/help/faq)

docs/es/help/troubleshooting.md

@@ -0,0 +1,98 @@
+---
+summary: "Troubleshooting hub: symptoms → checks → fixes"
+read_when:
+  - You see an error and want the fix path
+  - The installer says “success” but the CLI doesn’t work
+title: "Troubleshooting"
+---
+
+# Troubleshooting
+
+## First 60 seconds
+
+Run these in order:
+
+```bash
+openclaw status
+openclaw status --all
+openclaw gateway probe
+openclaw logs --follow
+openclaw doctor
+```
+
+If the gateway is reachable, deep probes:
+
+```bash
+openclaw status --deep
+```
+
+## Common “it broke” cases
+
+### `openclaw: command not found`
+
+Almost always a Node/npm PATH issue. Start here:
+
+- [Install (Node/npm PATH sanity)](/install#nodejs--npm-path-sanity)
+
+### Installer fails (or you need full logs)
+
+Re-run the installer in verbose mode to see the full trace and npm output:
+
+```bash
+curl -fsSL https://openclaw.ai/install.sh | bash -s -- --verbose
+```
+
+For beta installs:
+
+```bash
+curl -fsSL https://openclaw.ai/install.sh | bash -s -- --beta --verbose
+```
+
+You can also set `OPENCLAW_VERBOSE=1` instead of the flag.
+
+### Gateway “unauthorized”, can’t connect, or keeps reconnecting
+
+- [Gateway troubleshooting](/gateway/troubleshooting)
+- [Gateway authentication](/gateway/authentication)
+
+### Control UI fails on HTTP (device identity required)
+
+- [Gateway troubleshooting](/gateway/troubleshooting)
+- [Control UI](/web/control-ui#insecure-http)
+
+### `docs.openclaw.ai` shows an SSL error (Comcast/Xfinity)
+
+Some Comcast/Xfinity connections block `docs.openclaw.ai` via Xfinity Advanced Security.
+Disable Advanced Security or add `docs.openclaw.ai` to the allowlist, then retry.
+
+- Xfinity Advanced Security help: https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security
+- Quick sanity checks: try a mobile hotspot or VPN to confirm it’s ISP-level filtering
+
+### Service says running, but RPC probe fails
+
+- [Gateway troubleshooting](/gateway/troubleshooting)
+- [Background process / service](/gateway/background-process)
+
+### Model/auth failures (rate limit, billing, “all models failed”)
+
+- [Models](/cli/models)
+- [OAuth / auth concepts](/concepts/oauth)
+
+### `/model` says `model not allowed`
+
+This usually means `agents.defaults.models` is configured as an allowlist. When it’s non-empty,
+only those provider/model keys can be selected.
+
+- Check the allowlist: `openclaw config get agents.defaults.models`
+- Add the model you want (or clear the allowlist) and retry `/model`
+- Use `/models` to browse the allowed providers/models
+
+### When filing an issue
+
+Paste a safe report:
+
+```bash
+openclaw status --all
+```
+
+If you can, include the relevant log tail from `openclaw logs --follow`.