refactor: centralize typing mode signals

docs/concepts/group-messages.md

@@ -71,3 +71,4 @@ Only the owner number (from `whatsapp.allowFrom`, or the bot’s own E.164 when
 - Heartbeats are intentionally skipped for groups to avoid noisy broadcasts.
 - Echo suppression uses the combined batch string; if you send identical text twice without mentions, only the first will get a response.
 - Session store entries will appear as `agent:<agentId>:whatsapp:group:<jid>` in the session store (`~/.clawdbot/agents/<agentId>/sessions/sessions.json` by default); a missing entry just means the group hasn’t triggered a run yet.
+- Typing indicators in groups follow `agent.typingMode` (default: `message` when unmentioned).

docs/concepts/typing-indicators.md

@@ -39,10 +39,11 @@ Order of “how early it fires”:
 }
 ```
 
-You can override the refresh cadence per session:
+You can override mode or cadence per session:
 ```json5
 {
   session: {
+    typingMode: "message",
     typingIntervalSeconds: 4
   }
 }
@@ -51,8 +52,8 @@ You can override the refresh cadence per session:
 ## 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; if the model doesn’t emit
-  reasoning deltas, typing won’t start.
+- `thinking` only fires if the run streams reasoning (`reasoningLevel: "stream"`).
+  If the model doesn’t emit reasoning deltas, typing won’t start.
 - Heartbeats never show typing, regardless of mode.
 - `typingIntervalSeconds` controls the **refresh cadence**, not the start time.
   The default is 6 seconds.