ops-merge

## Runtime Context Before executing, load: 1. **Preferences**: `cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` — read `owner`, `timezone`, project registry 2. **Daemon health**: `cat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` — if `action_needed` set, surface to user 3. **Secrets**: GitHub token: env `$GITHUB_TOKEN` → Doppler MCP (`mcp__doppler__*`) → `doppler secrets get GITHUB_TOKEN --plain` → password manager # OPS ► MERGE 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`). ## Agent Teams support If `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is set, use **Agent Teams** for fixer agents (Phase 3). This enables: - Steering fixers mid-flight if priorities change (e.g., a critical PR should be merged first) - Fixers can report blockers and you can redirect them without waiting for completion - Shared context: if fixer-A discovers a breaking change that affects fixer-B's PR, you can notify B **Team setup** (only when flag is enabled, Phase 3): ``` TeamCreate("merge-fixers") Agent(team_name="merge-fixers", name="fixer-[repo]", ...) ``` Use `SendMessage(to="fixer-my-api", content="PR #2958 was just merged — rebase your branch")` to coordinate. If the flag is NOT set, fall back to standard parallel subagents with `isol...