rcode-herdr-orchestrationlisted

# rcode-herdr-orchestration ## Overview Run many Claude agents in parallel inside `herdr` (terminal agent multiplexer), monitor them, and merge their work back safely. Two modes: **single-shot** (bounded fan-out, one sitting, merge back done) and **autonomous campaign** (100+ commits across waves with durable backlog and integration branch). Both share the same golden rules and pane mechanics. See `references.md` for the full campaign workflow and deep-dive rules. **Do NOT use for a single quick task** — invoke the work directly without herdr for that. Orchestration overhead (worktrees, panes, monitoring) only pays off across multiple independent agents. --- ## Golden rules (NON-NEGOTIABLE — apply to BOTH modes) 1. **Use `cld`, never `claude`.** `cld` is the alias for `claude --dangerously-skip-permissions`. Send it via `herdr pane send-text` + `send-keys Enter` so the shell alias resolves. Do NOT use `herdr pane run` for `cld`. 2. **If you must invoke `claude` directly** (alias unavailable): pass `--dangerously-skip-permissions` AND run in **interactive mode** (no `-p`/`--print`). A non-interactive `claude -p` call is invisible to herdr. 3. **One git worktree per agent.** Never share a working tree between orchestrated agents. 4. **Work locally, commit locally. Never push to origin or deploy** during an orchestration run unless the user explicitly authorizes it afterward. 5. **The orchestrator NEVER claims a wakeup it cannot fire.** `ScheduleWakeup` onl