chore: Run pnpm format:fix.

docs/concepts/typing-indicators.md

@@ -3,6 +3,7 @@ summary: "When OpenClaw shows typing indicators and how to tune them"
 read_when:
   - Changing typing indicator behavior or defaults
 ---
+
 # Typing indicators
 
 Typing indicators are sent to the chat channel while a run is active. Use
@@ -10,14 +11,18 @@ Typing indicators are sent to the chat channel while a run is active. Use
 to control **how often** it refreshes.
 
 ## Defaults
+
 When `agents.defaults.typingMode` is **unset**, OpenClaw keeps the legacy behavior:
+
 - **Direct chats**: typing starts immediately once the model loop begins.
 - **Group chats with a mention**: typing starts immediately.
 - **Group chats without a mention**: typing starts only when message text begins streaming.
 - **Heartbeat runs**: typing is disabled.
 
 ## Modes
+
 Set `agents.defaults.typingMode` to one of:
+
 - `never` — no typing indicator, ever.
 - `instant` — start typing **as soon as the model loop begins**, even if the run
   later returns only the silent reply token.
@@ -30,26 +35,29 @@ Order of “how early it fires”:
 `never` → `message` → `thinking` → `instant`
 
 ## Configuration
+
 ```json5
 {
   agent: {
     typingMode: "thinking",
-    typingIntervalSeconds: 6
-  }
+    typingIntervalSeconds: 6,
+  },
 }
 ```
 
 You can override mode or cadence per session:
+
 ```json5
 {
   session: {
     typingMode: "message",
-    typingIntervalSeconds: 4
-  }
+    typingIntervalSeconds: 4,
+  },
 }
 ```
 
 ## Notes
+
 - `message` mode won’t show typing for silent-only replies (e.g. the `NO_REPLY`
   token used to suppress output).
 - `thinking` only fires if the run streams reasoning (`reasoningLevel: "stream"`).