herdr-orchestrate-pilisted

# Herdr Orchestration — PI harness Precondition: `test "${HERDR_ENV:-}" = 1` — otherwise say so and stop. Every worker lane is a pi pane; model per role via `--model` after `--`. All lane plumbing is one tool: the sibling `herdr-orchestrate` skill's `bin/herd` (both skills install side by side in `~/.claude/skills/`) — every command below is `herd <verb>`. Run it from the project directory (or set `HERD_PROJECT`); it keeps a ledger in `<project>/.herd/ledger.json`. Preflight once per session: - `herdr integration status --outdated-only` — update anything listed; outdated integrations re-raise trust dialogs on spawn. - **Find the project first.** If the cwd holds no `.herd/` and no spec and the brief carries no absolute path, locate the project (mdfind/spec search; disambiguate siblings by ledger lane prefixes and freshness), then `export HERD_PROJECT=<abs>` and run every `herd` command from there. Never spawn from `$HOME` — herd refuses to create a ledger there. - `herd status` — an existing ledger means you are **resuming**: adopt it (see Resume), don't spawn duplicates. ## Layers Captain ↔ **root orchestrator** (product shape, taste, spec-writing; where the captain lives) → **this session = ops** (route, watch, review-route, land, sweep) → **one owner lane** per spec (decides whether and how to split, spawns peers, owns integration + acceptance) → peers. Ops never designs, slices, implements or reviews; root never touches lanes. The captain zooms into ops only by choic