chore: Run pnpm format:fix.

docs/plugins/agent-tools.md

@@ -4,6 +4,7 @@ read_when:
   - You want to add a new agent tool in a plugin
   - You need to make a tool opt-in via allowlists
 ---
+
 # Plugin agent tools
 
 OpenClaw plugins can register **agent tools** (JSON‑schema functions) that are exposed
@@ -70,18 +71,19 @@ Enable optional tools in `agents.list[].tools.allow` (or global `tools.allow`):
         id: "main",
         tools: {
           allow: [
-            "workflow_tool",  // specific tool name
-            "workflow",       // plugin id (enables all tools from that plugin)
-            "group:plugins"   // all plugin tools
-          ]
-        }
-      }
-    ]
-  }
+            "workflow_tool", // specific tool name
+            "workflow", // plugin id (enables all tools from that plugin)
+            "group:plugins", // all plugin tools
+          ],
+        },
+      },
+    ],
+  },
 }
 ```
 
 Other config knobs that affect tool availability:
+
 - Allowlists that only name plugin tools are treated as plugin opt-ins; core tools remain
   enabled unless you also include core tools or groups in the allowlist.
 - `tools.profile` / `agents.list[].tools.profile` (base allowlist)

docs/plugins/manifest.md

@@ -4,6 +4,7 @@ read_when:
   - You are building a OpenClaw plugin
   - You need to ship a plugin config schema or debug plugin validation errors
 ---
+
 # Plugin manifest (openclaw.plugin.json)
 
 Every plugin **must** ship a `openclaw.plugin.json` file in the **plugin root**.
@@ -27,10 +28,12 @@ See the full plugin system guide: [Plugins](/plugin).
 ```
 
 Required keys:
+
 - `id` (string): canonical plugin id.
 - `configSchema` (object): JSON Schema for plugin config (inline).
 
 Optional keys:
+
 - `kind` (string): plugin kind (example: `"memory"`).
 - `channels` (array): channel ids registered by this plugin (example: `["matrix"]`).
 - `providers` (array): provider ids registered by this plugin.
@@ -64,4 +67,4 @@ Optional keys:
   discovery + validation.
 - If your plugin depends on native modules, document the build steps and any
   package-manager allowlist requirements (for example, pnpm `allow-build-scripts`
-  + `pnpm rebuild <package>`).
+  - `pnpm rebuild <package>`).

docs/plugins/voice-call.md

@@ -11,12 +11,14 @@ Voice calls for OpenClaw via a plugin. Supports outbound notifications and
 multi-turn conversations with inbound policies.
 
 Current providers:
+
 - `twilio` (Programmable Voice + Media Streams)
 - `telnyx` (Call Control v2)
 - `plivo` (Voice API + XML transfer + GetInput speech)
 - `mock` (dev/no network)
 
 Quick mental model:
+
 - Install plugin
 - Restart Gateway
 - Configure under `plugins.entries.voice-call.config`
@@ -64,18 +66,18 @@ Set config under `plugins.entries.voice-call.config`:
 
           twilio: {
             accountSid: "ACxxxxxxxx",
-            authToken: "..."
+            authToken: "...",
           },
 
           plivo: {
             authId: "MAxxxxxxxxxxxxxxxxxxxx",
-            authToken: "..."
+            authToken: "...",
           },
 
           // Webhook server
           serve: {
             port: 3334,
-            path: "/voice/webhook"
+            path: "/voice/webhook",
           },
 
           // Public exposure (pick one)
@@ -84,21 +86,22 @@ Set config under `plugins.entries.voice-call.config`:
           // tailscale: { mode: "funnel", path: "/voice/webhook" }
 
           outbound: {
-            defaultMode: "notify" // notify | conversation
+            defaultMode: "notify", // notify | conversation
           },
 
           streaming: {
             enabled: true,
-            streamPath: "/voice/stream"
-          }
-        }
-      }
-    }
-  }
+            streamPath: "/voice/stream",
+          },
+        },
+      },
+    },
+  },
 }
 ```
 
 Notes:
+
 - Twilio/Telnyx require a **publicly reachable** webhook URL.
 - Plivo requires a **publicly reachable** webhook URL.
 - `mock` is a local dev provider (no network calls).
@@ -119,13 +122,14 @@ streaming speech on calls. You can override it under the plugin config with the
     provider: "elevenlabs",
     elevenlabs: {
       voiceId: "pMsXgVXv3BLzUgSXRplE",
-      modelId: "eleven_multilingual_v2"
-    }
-  }
+      modelId: "eleven_multilingual_v2",
+    },
+  },
 }
 ```
 
 Notes:
+
 - **Edge TTS is ignored for voice calls** (telephony audio needs PCM; Edge output is unreliable).
 - Core TTS is used when Twilio media streaming is enabled; otherwise calls fall back to provider native voices.
 
@@ -138,9 +142,9 @@ Use core TTS only (no override):
   messages: {
     tts: {
       provider: "openai",
-      openai: { voice: "alloy" }
-    }
-  }
+      openai: { voice: "alloy" },
+    },
+  },
 }
 ```
 
@@ -157,13 +161,13 @@ Override to ElevenLabs just for calls (keep core default elsewhere):
             elevenlabs: {
               apiKey: "elevenlabs_key",
               voiceId: "pMsXgVXv3BLzUgSXRplE",
-              modelId: "eleven_multilingual_v2"
-            }
-          }
-        }
-      }
-    }
-  }
+              modelId: "eleven_multilingual_v2",
+            },
+          },
+        },
+      },
+    },
+  },
 }
 ```
 
@@ -178,13 +182,13 @@ Override only the OpenAI model for calls (deep‑merge example):
           tts: {
             openai: {
               model: "gpt-4o-mini-tts",
-              voice: "marin"
-            }
-          }
-        }
-      }
-    }
-  }
+              voice: "marin",
+            },
+          },
+        },
+      },
+    },
+  },
 }
 ```
 
@@ -196,11 +200,12 @@ Inbound policy defaults to `disabled`. To enable inbound calls, set:
 {
   inboundPolicy: "allowlist",
   allowFrom: ["+15550001234"],
-  inboundGreeting: "Hello! How can I help?"
+  inboundGreeting: "Hello! How can I help?",
 }
 ```
 
 Auto-responses use the agent system. Tune with:
+
 - `responseModel`
 - `responseSystemPrompt`
 - `responseTimeoutMs`
@@ -222,6 +227,7 @@ openclaw voicecall expose --mode funnel
 Tool name: `voice_call`
 
 Actions:
+
 - `initiate_call` (message, to?, mode?)
 - `continue_call` (callId, message)
 - `speak_to_user` (callId, message)

docs/plugins/zalouser.md

@@ -12,9 +12,11 @@ Zalo Personal support for OpenClaw via a plugin, using `zca-cli` to automate a n
 > **Warning:** Unofficial automation may lead to account suspension/ban. Use at your own risk.
 
 ## Naming
+
 Channel id is `zalouser` to make it explicit this automates a **personal Zalo user account** (unofficial). We keep `zalo` reserved for a potential future official Zalo API integration.
 
 ## Where it runs
+
 This plugin runs **inside the Gateway process**.
 
 If you use a remote Gateway, install/configure it on the **machine running the Gateway**, then restart the Gateway.
@@ -39,6 +41,7 @@ cd ./extensions/zalouser && pnpm install
 Restart the Gateway afterwards.
 
 ## Prerequisite: zca-cli
+
 The Gateway machine must have `zca` on `PATH`:
 
 ```bash
@@ -46,6 +49,7 @@ zca --version
 ```
 
 ## Config
+
 Channel config lives under `channels.zalouser` (not `plugins.entries.*`):
 
 ```json5
@@ -53,9 +57,9 @@ Channel config lives under `channels.zalouser` (not `plugins.entries.*`):
   channels: {
     zalouser: {
       enabled: true,
-      dmPolicy: "pairing"
-    }
-  }
+      dmPolicy: "pairing",
+    },
+  },
 }
 ```
 
@@ -70,6 +74,7 @@ openclaw directory peers list --channel zalouser --query "name"
 ```
 
 ## Agent tool
+
 Tool name: `zalouser`
 
 Actions: `send`, `image`, `link`, `friends`, `groups`, `me`, `status`