chore: Run pnpm format:fix.

docs/channels/location.md

@@ -8,15 +8,18 @@ read_when:
 # Channel location parsing
 
 OpenClaw normalizes shared locations from chat channels into:
+
 - human-readable text appended to the inbound body, and
 - structured fields in the auto-reply context payload.
 
 Currently supported:
+
 - **Telegram** (location pins + venues + live locations)
 - **WhatsApp** (locationMessage + liveLocationMessage)
 - **Matrix** (`m.location` with `geo_uri`)
 
 ## Text formatting
+
 Locations are rendered as friendly lines without brackets:
 
 - Pin:
@@ -27,13 +30,16 @@ Locations are rendered as friendly lines without brackets:
   - `🛰 Live location: 48.858844, 2.294351 ±12m`
 
 If the channel includes a caption/comment, it is appended on the next line:
+
 ```
 📍 48.858844, 2.294351 ±12m
 Meet here
 ```
 
 ## Context fields
+
 When a location is present, these fields are added to `ctx`:
+
 - `LocationLat` (number)
 - `LocationLon` (number)
 - `LocationAccuracy` (number, meters; optional)
@@ -43,6 +49,7 @@ When a location is present, these fields are added to `ctx`:
 - `LocationIsLive` (boolean)
 
 ## Channel notes
+
 - **Telegram**: venues map to `LocationName/LocationAddress`; live locations use `live_period`.
 - **WhatsApp**: `locationMessage.comment` and `liveLocationMessage.caption` are appended as the caption line.
 - **Matrix**: `geo_uri` is parsed as a pin location; altitude is ignored and `LocationIsLive` is always false.