chore: Run pnpm format:fix.

docs/concepts/architecture.md

@@ -3,6 +3,7 @@ summary: "WebSocket gateway architecture, components, and client flows"
 read_when:
   - Working on gateway protocol, clients, or transports
 ---
+
 # Gateway architecture
 
 Last updated: 2026-01-22
@@ -22,26 +23,31 @@ Last updated: 2026-01-22
 ## Components and flows
 
 ### Gateway (daemon)
+
 - Maintains provider connections.
 - Exposes a typed WS API (requests, responses, server‑push events).
 - Validates inbound frames against JSON Schema.
 - Emits events like `agent`, `chat`, `presence`, `health`, `heartbeat`, `cron`.
 
 ### Clients (mac app / CLI / web admin)
+
 - One WS connection per client.
 - Send requests (`health`, `status`, `send`, `agent`, `system-presence`).
 - Subscribe to events (`tick`, `agent`, `presence`, `shutdown`).
 
 ### Nodes (macOS / iOS / Android / headless)
+
 - Connect to the **same WS server** with `role: node`.
 - Provide a device identity in `connect`; pairing is **device‑based** (role `node`) and
   approval lives in the device pairing store.
 - Expose commands like `canvas.*`, `camera.*`, `screen.record`, `location.get`.
 
 Protocol details:
+
 - [Gateway protocol](/gateway/protocol)
 
 ### WebChat
+
 - Static UI that uses the Gateway WS API for chat history and sends.
 - In remote setups, connects through the same SSH/Tailscale tunnel as other
   clients.