docs: refresh gateway overview mirrors

docs/gateway/index.md

@@ -308,7 +308,9 @@ Defaults include isolated state/config and base gateway port `19001`.
 - `hello-ok.features.methods` / `events` are a conservative discovery list, not
   a generated dump of every callable helper route.
 - Requests: `req(method, params)` → `res(ok/payload|error)`.
-- Common events: `connect.challenge`, `agent`, `chat`, `presence`, `tick`, `health`, `heartbeat`, `shutdown`.
+- Common events include `connect.challenge`, `agent`, `chat`,
+  `session.message`, `session.tool`, `sessions.changed`, `presence`, `tick`,
+  `health`, `heartbeat`, pairing/approval lifecycle events, and `shutdown`.
 
 Agent runs are two-stage:
 

docs/nodes/index.md

@@ -11,7 +11,8 @@ title: "Nodes"
 
 A **node** is a companion device (macOS/iOS/Android/headless) that connects to the Gateway **WebSocket** (same port as operators) with `role: "node"` and exposes a command surface (e.g. `canvas.*`, `camera.*`, `device.*`, `notifications.*`, `system.*`) via `node.invoke`. Protocol details: [Gateway protocol](/gateway/protocol).
 
-Legacy transport: [Bridge protocol](/gateway/bridge-protocol) (TCP JSONL; deprecated/removed for current nodes).
+Legacy transport: [Bridge protocol](/gateway/bridge-protocol) (TCP JSONL;
+historical only for current nodes).
 
 macOS can also run in **node mode**: the menubar app connects to the Gateway’s WS server and exposes its local canvas/camera commands as a node (so `openclaw nodes …` works against this Mac).
 

docs/tools/capability-cookbook.md

@@ -56,7 +56,7 @@ Core:
 - request/response types
 - provider registry + resolution
 - fallback behavior
-- config schema and labels/help
+- config schema plus propagated `title` / `description` docs metadata
 - runtime helper surface
 
 Vendor plugin:

docs/web/index.md

@@ -71,7 +71,8 @@ Open:
 }
 ```
 
-Then start the gateway (token required for non-loopback binds):
+Then start the gateway (this non-loopback example uses shared-secret token
+auth):
 
 ```bash
 openclaw gateway