ops-deploy

# OPS ► DEPLOY STATUS 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` - `timezone` — display all deploy timestamps in the correct timezone 2. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` - Check `infra-monitor` status — if not running, note that ECS data may be stale 3. **Secrets**: AWS and Vercel credentials required. ### Secret Resolution - AWS: check `$AWS_PROFILE` / `$AWS_ACCESS_KEY_ID` → `doppler secrets get AWS_ACCESS_KEY_ID --plain` → vault query cmd from prefs - Vercel token: check `$VERCEL_TOKEN` → `doppler secrets get VERCEL_TOKEN --plain` → vault ## CLI/API Reference ### aws CLI | Command | Usage | Output | | --------------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------- | | `aws ecs list-clusters --output json` | All ECS clusters...