fix(trigger): require names for trigger creation

docs/chat-commands.md

@@ -16,7 +16,7 @@ These commands work inside chat channels and interactive agent sessions:
 | `/dream-restore` | List recent Dream memory versions |
 | `/dream-restore <sha>` | Restore memory to the state before a specific change |
 | `/skill` | List enabled skills and their descriptions |
-| `/trigger` | Create a local external trigger for the current chat/session |
+| `/trigger` | Show external trigger usage |
 | `/trigger <name>` | Create a named local external trigger for the current chat/session |
 | `/pairing` | List pending pairing requests |
 | `/pairing approve <code>` | Approve a pairing code |
@@ -59,8 +59,9 @@ Preset names come from the top-level `modelPresets` config. Switching is runtime
 
 ## External Triggers
 
-Use `/trigger` when a local script or another service should be able to send a
-message into the current chat/session later.
+Use `/trigger <name>` when a local script or another service should be able to
+send a message into the current chat/session later. A name is required; plain
+`/trigger` only shows the usage hint.
 
 Create the trigger from the chat where future messages should arrive:
 

docs/cli-reference.md

@@ -13,7 +13,7 @@ Use this page when you know what you want to run and need the command shape. For
 | Send one test message | `nanobot agent -m "Hello!"` | First proof that install, config, provider, model, and workspace all work |
 | Chat in the terminal | `nanobot agent` | Interactive local chat; exit with `exit`, `/exit`, `:q`, or `Ctrl+D` |
 | Use WebUI or chat apps | `nanobot gateway` | Keep this terminal running, or use `nanobot gateway --background` |
-| Deliver a local external trigger | `nanobot trigger <id> "message"` | Created first with `/trigger` in the target chat/session |
+| Deliver a local external trigger | `nanobot trigger <id> "message"` | Created first with `/trigger <name>` in the target chat/session |
 | Serve an OpenAI-compatible API | `nanobot serve` | Starts `/v1/chat/completions`, `/v1/models`, and `/health` |
 | Check chat channel setup | `nanobot channels status` | Useful before starting `nanobot gateway` |
 | Log in to QR/OAuth-style channels | `nanobot channels login <channel>` | Used by channels such as WhatsApp and WeChat |
@@ -126,7 +126,7 @@ The bundled WebUI is served by the WebSocket channel, usually on port `8765`, no
 ## Local Triggers
 
 `nanobot trigger` delivers one local message to a trigger that was created from
-a chat/session with `/trigger [name]`.
+a chat/session with `/trigger <name>`.
 
 ```bash
 nanobot trigger trg_8K4P2Q9X "Review PR #4502"

docs/concepts.md

@@ -144,7 +144,7 @@ protected heartbeat system job. They run as scheduled turns in their origin
 chat/session and normally deliver the result back to that channel.
 
 External triggers are also session-bound, but they do not have their own
-schedule. Create one from the target chat with `/trigger [name]`, then call
+schedule. Create one from the target chat with `/trigger <name>`, then call
 `nanobot trigger <id> "<message>"` when a local script or external service wants
 nanobot to respond in that session. Webhook servers, third-party auth, and
 event-to-message formatting stay outside nanobot.

docs/webui.md

@@ -125,7 +125,7 @@ There are two user-facing automation types:
 
 - Scheduled automations, created by the agent's cron tool, run at a time,
   interval, or cron expression.
-- External triggers, created with `/trigger [name]`, run when you call a local
+- External triggers, created with `/trigger <name>`, run when you call a local
   command such as `nanobot trigger trg_8K4P2Q9X "Review PR #4502"`.
 
 If a GitHub webhook, CI system, or another service should wake nanobot up, keep