chore: Run pnpm format:fix.

docs/channels/nextcloud-talk.md

@@ -3,19 +3,23 @@ summary: "Nextcloud Talk support status, capabilities, and configuration"
 read_when:
   - Working on Nextcloud Talk channel features
 ---
+
 # Nextcloud Talk (plugin)
 
 Status: supported via plugin (webhook bot). Direct messages, rooms, reactions, and markdown messages are supported.
 
 ## Plugin required
+
 Nextcloud Talk ships as a plugin and is not bundled with the core install.
 
 Install via CLI (npm registry):
+
 ```bash
 openclaw plugins install @openclaw/nextcloud-talk
 ```
 
 Local checkout (when running from a git repo):
+
 ```bash
 openclaw plugins install ./extensions/nextcloud-talk
 ```
@@ -26,18 +30,20 @@ OpenClaw will offer the local install path automatically.
 Details: [Plugins](/plugin)
 
 ## Quick setup (beginner)
-1) Install the Nextcloud Talk plugin.
-2) On your Nextcloud server, create a bot:
+
+1. Install the Nextcloud Talk plugin.
+2. On your Nextcloud server, create a bot:
    ```bash
    ./occ talk:bot:install "OpenClaw" "<shared-secret>" "<webhook-url>" --feature reaction
    ```
-3) Enable the bot in the target room settings.
-4) Configure OpenClaw:
+3. Enable the bot in the target room settings.
+4. Configure OpenClaw:
    - Config: `channels.nextcloud-talk.baseUrl` + `channels.nextcloud-talk.botSecret`
    - Or env: `NEXTCLOUD_TALK_BOT_SECRET` (default account only)
-5) Restart the gateway (or finish onboarding).
+5. Restart the gateway (or finish onboarding).
 
 Minimal config:
+
 ```json5
 {
   channels: {
@@ -45,19 +51,21 @@ Minimal config:
       enabled: true,
       baseUrl: "https://cloud.example.com",
       botSecret: "shared-secret",
-      dmPolicy: "pairing"
-    }
-  }
+      dmPolicy: "pairing",
+    },
+  },
 }
 ```
 
 ## Notes
+
 - Bots cannot initiate DMs. The user must message the bot first.
 - Webhook URL must be reachable by the Gateway; set `webhookPublicUrl` if behind a proxy.
 - Media uploads are not supported by the bot API; media is sent as URLs.
 - The webhook payload does not distinguish DMs vs rooms; set `apiUser` + `apiPassword` to enable room-type lookups (otherwise DMs are treated as rooms).
 
 ## Access control (DMs)
+
 - Default: `channels.nextcloud-talk.dmPolicy = "pairing"`. Unknown senders get a pairing code.
 - Approve via:
   - `openclaw pairing list nextcloud-talk`
@@ -65,35 +73,41 @@ Minimal config:
 - Public DMs: `channels.nextcloud-talk.dmPolicy="open"` plus `channels.nextcloud-talk.allowFrom=["*"]`.
 
 ## Rooms (groups)
+
 - Default: `channels.nextcloud-talk.groupPolicy = "allowlist"` (mention-gated).
 - Allowlist rooms with `channels.nextcloud-talk.rooms`:
+
 ```json5
 {
   channels: {
     "nextcloud-talk": {
       rooms: {
-        "room-token": { requireMention: true }
-      }
-    }
-  }
+        "room-token": { requireMention: true },
+      },
+    },
+  },
 }
 ```
+
 - To allow no rooms, keep the allowlist empty or set `channels.nextcloud-talk.groupPolicy="disabled"`.
 
 ## Capabilities
-| Feature | Status |
-|---------|--------|
-| Direct messages | Supported |
-| Rooms | Supported |
-| Threads | Not supported |
-| Media | URL-only |
-| Reactions | Supported |
+
+| Feature         | Status        |
+| --------------- | ------------- |
+| Direct messages | Supported     |
+| Rooms           | Supported     |
+| Threads         | Not supported |
+| Media           | URL-only      |
+| Reactions       | Supported     |
 | Native commands | Not supported |
 
 ## Configuration reference (Nextcloud Talk)
+
 Full configuration: [Configuration](/gateway/configuration)
 
 Provider options:
+
 - `channels.nextcloud-talk.enabled`: enable/disable channel startup.
 - `channels.nextcloud-talk.baseUrl`: Nextcloud instance URL.
 - `channels.nextcloud-talk.botSecret`: bot shared secret.