ops-go

# OPS ► MORNING BRIEFING 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`). ## Runtime Context Before executing, load available context: 1. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` - `owner` — use in the greeting header ("Good morning, [owner]") - `timezone` — display all timestamps in this timezone - `default_channels` — which channels to include in unread summary 2. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` - If `action_needed` is not null → surface it before the briefing - Check `whatsapp-bridge` status before including WhatsApp unread counts - Also check bridge liveness: `lsof -i :8080 | grep LISTEN` 3. **WhatsApp pre-check**: Only include WhatsApp data if bridge is running (`lsof -i :8080 | grep LISTEN`). ## CLI/API Reference ### whatsapp-bridge (WhatsApp — mcp**whatsapp**\*) **Bridge health** — check before any WhatsApp operation: - Running: `lsof -i :8080 | grep LISTEN` → proceed - Not running → `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge`, wait 5s | Tool | Params | Output | | ------------------------------ | -------------------...