ops-inbox

# OPS ► INBOX ZERO Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). ## ⚠️ WHATSAPP TRANSPORT — MCP ONLY, NEVER `wacli` For **all** WhatsApp operations in this skill (list chats, read messages, search contacts, send replies, archive chats), use the `mcp__whatsapp__*` tool family backed by the whatsmeow (Go) whatsapp-bridge — upstream `lharries/whatsapp-mcp`. (Earlier docs misnamed this as "Baileys" — Baileys is the Node.js WhatsApp library; this bridge uses `go.mau.fi/whatsmeow`.) > **Server name.** `mcp__whatsapp__*` is the single-account default. Installs with more than one account > register one server per account (`whatsapp-nl`, `whatsapp-us`, `whatsapp-personal`, `whatsapp-work`, ...) > and have no plain `mcp__whatsapp__*` at all. `whatsapp-cos` is not an account — do not send on it. > Resolve the real name from the available tools before the first call, and when several accounts exist, > scan each one separately and keep the results labelled by account. See CLAUDE.md / ops-rules Rule 8. **NEVER call the legacy `wacli` CLI** (`wacli chats list`, `wacli messages list`, `wacli send`, `wacli doctor`, `wacli history backfill`, etc). The wacli store and keepalive daemon are deprecated for this skill. If you find yourself reaching for any `wacli ...` shell command, s...