chore: Run pnpm format:fix.

docs/gateway/pairing.md

@@ -5,6 +5,7 @@ read_when:
   - Adding CLI flows for approving remote nodes
   - Extending gateway protocol with node management
 ---
+
 # Gateway-owned pairing (Option B)
 
 In Gateway-owned pairing, the **Gateway** is the source of truth for which nodes
@@ -47,10 +48,12 @@ openclaw nodes rename --node <id|name|ip> --name "Living Room iPad"
 ## API surface (gateway protocol)
 
 Events:
+
 - `node.pair.requested` — emitted when a new pending request is created.
 - `node.pair.resolved` — emitted when a request is approved/rejected/expired.
 
 Methods:
+
 - `node.pair.request` — create or reuse a pending request.
 - `node.pair.list` — list pending + paired nodes.
 - `node.pair.approve` — approve a pending request (issues token).
@@ -58,6 +61,7 @@ Methods:
 - `node.pair.verify` — verify `{ nodeId, token }`.
 
 Notes:
+
 - `node.pair.request` is idempotent per node: repeated calls return the same
   pending request.
 - Approval **always** generates a fresh token; no token is ever returned from
@@ -67,6 +71,7 @@ Notes:
 ## Auto-approval (macOS app)
 
 The macOS app can optionally attempt a **silent approval** when:
+
 - the request is marked `silent`, and
 - the app can verify an SSH connection to the gateway host using the same user.
 
@@ -82,6 +87,7 @@ Pairing state is stored under the Gateway state directory (default `~/.openclaw`
 If you override `OPENCLAW_STATE_DIR`, the `nodes/` folder moves with it.
 
 Security notes:
+
 - Tokens are secrets; treat `paired.json` as sensitive.
 - Rotating a token requires re-approval (or deleting the node entry).