herdr-orchestratelisted

# Herdr Orchestration v2 Precondition: `test "${HERDR_ENV:-}" = 1` — otherwise say so and stop. All lane plumbing is one tool: `<this skill dir>/bin/herd` (on PATH or by absolute path) — 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. ## Roles | lane name | kind | takes | | --- | --- | --- | | (this session) | claude | routing, triage, status. NEVER implements or reviews | | `impl-fable[-<slice>]` | claude (Fable, high) | owns a slice as its pseudo-orchestrator: architecture, integration, acceptance — spawns its own Sol/kimi sub-lanes for scoped chunks. Fable typing well-specified code itself is a routing smell | | `impl-sol[-<slice>]` | codex | scoped, well-specified tasks | | `frontend-kimi` | pi (`-- --model moonshotai/kimi-k3:high`) | all UI, any platform (web