chore: Run pnpm format:fix.

docs/broadcast-groups.md

@@ -22,7 +22,9 @@ Broadcast groups are evaluated after channel allowlists and group activation rul
 ## Use Cases
 
 ### 1. Specialized Agent Teams
+
 Deploy multiple agents with atomic, focused responsibilities:
+
 ```
 Group: "Development Team"
 Agents:
@@ -35,6 +37,7 @@ Agents:
 Each agent processes the same message and provides its specialized perspective.
 
 ### 2. Multi-Language Support
+
 ```
 Group: "International Support"
 Agents:
@@ -44,6 +47,7 @@ Agents:
 ```
 
 ### 3. Quality Assurance Workflows
+
 ```
 Group: "Customer Support"
 Agents:
@@ -52,6 +56,7 @@ Agents:
 ```
 
 ### 4. Task Automation
+
 ```
 Group: "Project Management"
 Agents:
@@ -65,6 +70,7 @@ Agents:
 ### Basic Setup
 
 Add a top-level `broadcast` section (next to `bindings`). Keys are WhatsApp peer ids:
+
 - group chats: group JID (e.g. `120363403215116621@g.us`)
 - DMs: E.164 phone number (e.g. `+15551234567`)
 
@@ -83,7 +89,9 @@ Add a top-level `broadcast` section (next to `bindings`). Keys are WhatsApp peer
 Control how agents process messages:
 
 #### Parallel (Default)
+
 All agents process simultaneously:
+
 ```json
 {
   "broadcast": {
@@ -94,7 +102,9 @@ All agents process simultaneously:
 ```
 
 #### Sequential
+
 Agents process in order (one waits for previous to finish):
+
 ```json
 {
   "broadcast": {
@@ -152,7 +162,7 @@ Agents process in order (one waits for previous to finish):
 4. **If not in broadcast list**:
    - Normal routing applies (first matching binding)
 
-Note: broadcast groups do not bypass channel allowlists or group activation rules (mentions/commands/etc). They only change *which agents run* when a message is eligible for processing.
+Note: broadcast groups do not bypass channel allowlists or group activation rules (mentions/commands/etc). They only change _which agents run_ when a message is eligible for processing.
 
 ### Session Isolation
 
@@ -166,6 +176,7 @@ Each agent in a broadcast group maintains completely separate:
 - **Group context buffer** (recent group messages used for context) is shared per peer, so all broadcast agents see the same context when triggered
 
 This allows each agent to have:
+
 - Different personalities
 - Different tool access (e.g., read-only vs. read-write)
 - Different models (e.g., opus vs. sonnet)
@@ -176,6 +187,7 @@ This allows each agent to have:
 In group `120363403215116621@g.us` with agents `["alfred", "baerbel"]`:
 
 **Alfred's context:**
+
 ```
 Session: agent:alfred:whatsapp:group:120363403215116621@g.us
 History: [user message, alfred's previous responses]
@@ -184,8 +196,9 @@ Tools: read, write, exec
 ```
 
 **Bärbel's context:**
+
 ```
-Session: agent:baerbel:whatsapp:group:120363403215116621@g.us  
+Session: agent:baerbel:whatsapp:group:120363403215116621@g.us
 History: [user message, baerbel's previous responses]
 Workspace: /Users/pascal/openclaw-baerbel/
 Tools: read only
@@ -230,10 +243,10 @@ Give agents only the tools they need:
 {
   "agents": {
     "reviewer": {
-      "tools": { "allow": ["read", "exec"] }  // Read-only
+      "tools": { "allow": ["read", "exec"] } // Read-only
     },
     "fixer": {
-      "tools": { "allow": ["read", "write", "edit", "exec"] }  // Read-write
+      "tools": { "allow": ["read", "write", "edit", "exec"] } // Read-write
     }
   }
 }
@@ -242,6 +255,7 @@ Give agents only the tools they need:
 ### 4. Monitor Performance
 
 With many agents, consider:
+
 - Using `"strategy": "parallel"` (default) for speed
 - Limiting broadcast groups to 5-10 agents
 - Using faster models for simpler agents
@@ -260,6 +274,7 @@ Result: Agent A and C respond, Agent B logs error
 ### Providers
 
 Broadcast groups currently work with:
+
 - ✅ WhatsApp (implemented)
 - 🚧 Telegram (planned)
 - 🚧 Discord (planned)
@@ -272,7 +287,10 @@ Broadcast groups work alongside existing routing:
 ```json
 {
   "bindings": [
-    { "match": { "channel": "whatsapp", "peer": { "kind": "group", "id": "GROUP_A" } }, "agentId": "alfred" }
+    {
+      "match": { "channel": "whatsapp", "peer": { "kind": "group", "id": "GROUP_A" } },
+      "agentId": "alfred"
+    }
   ],
   "broadcast": {
     "GROUP_B": ["agent1", "agent2"]
@@ -290,11 +308,13 @@ Broadcast groups work alongside existing routing:
 ### Agents Not Responding
 
 **Check:**
+
 1. Agent IDs exist in `agents.list`
 2. Peer ID format is correct (e.g., `120363403215116621@g.us`)
 3. Agents are not in deny lists
 
 **Debug:**
+
 ```bash
 tail -f ~/.openclaw/logs/gateway.log | grep broadcast
 ```
@@ -308,6 +328,7 @@ tail -f ~/.openclaw/logs/gateway.log | grep broadcast
 ### Performance Issues
 
 **If slow with many agents:**
+
 - Reduce number of agents per group
 - Use lighter models (sonnet instead of opus)
 - Check sandbox startup time
@@ -329,9 +350,21 @@ tail -f ~/.openclaw/logs/gateway.log | grep broadcast
   },
   "agents": {
     "list": [
-      { "id": "code-formatter", "workspace": "~/agents/formatter", "tools": { "allow": ["read", "write"] } },
-      { "id": "security-scanner", "workspace": "~/agents/security", "tools": { "allow": ["read", "exec"] } },
-      { "id": "test-coverage", "workspace": "~/agents/testing", "tools": { "allow": ["read", "exec"] } },
+      {
+        "id": "code-formatter",
+        "workspace": "~/agents/formatter",
+        "tools": { "allow": ["read", "write"] }
+      },
+      {
+        "id": "security-scanner",
+        "workspace": "~/agents/security",
+        "tools": { "allow": ["read", "exec"] }
+      },
+      {
+        "id": "test-coverage",
+        "workspace": "~/agents/testing",
+        "tools": { "allow": ["read", "exec"] }
+      },
       { "id": "docs-checker", "workspace": "~/agents/docs", "tools": { "allow": ["read"] } }
     ]
   }
@@ -340,6 +373,7 @@ tail -f ~/.openclaw/logs/gateway.log | grep broadcast
 
 **User sends:** Code snippet  
 **Responses:**
+
 - code-formatter: "Fixed indentation and added type hints"
 - security-scanner: "⚠️ SQL injection vulnerability in line 12"
 - test-coverage: "Coverage is 45%, missing tests for error cases"
@@ -381,7 +415,6 @@ interface OpenClawConfig {
 - `strategy` (optional): How to process agents
   - `"parallel"` (default): All agents process simultaneously
   - `"sequential"`: Agents process in array order
-  
 - `[peerId]`: WhatsApp group JID, E.164 number, or other peer ID
   - Value: Array of agent IDs that should process messages
 
@@ -395,6 +428,7 @@ interface OpenClawConfig {
 ## Future Enhancements
 
 Planned features:
+
 - [ ] Shared context mode (agents see each other's responses)
 - [ ] Agent coordination (agents can signal each other)
 - [ ] Dynamic agent selection (choose agents based on message content)