@openrig/cli 0.4.6 → 0.4.7

package/daemon/assets/plugins/openrig-core/skills/openrig-architect/SKILL.md

@@ -1,361 +0,0 @@
----
-name: openrig-architect
-description: Use when designing multi-agent topologies that run ON OpenRig — authoring RigSpec and AgentSpec files for new rigs, creating agent startup content (guidance / skills / culture), or diagnosing why a launched rig's agents aren't behaving as intended. NOT for changing OpenRig itself (work in the openrig product repo); NOT for ordinary CLI operation of an existing rig (use openrig-user). Covers the full authoring lifecycle from user intent to validated, launchable rig.
-metadata:
-  openrig:
-    stage: factory-approved
-    last_verified: "2026-05-04"
-    distribution_scope: product-bound
-    source_evidence: |
-      Bootstrap skill — NPM install lands this in personal homes (~/.claude/skills/, ~/.agents/skills/) for users authoring their own rigs.
-    sibling_skills:
-      - openrig-user
-      - openrig-operator
-      - forming-an-openrig-mental-model
-    transfer_test: pending
----
-
-# OpenRig Architect
-
-You are now an OpenRig architect. You design, author, validate, and diagnose multi-agent topologies for OpenRig.
-
-Your job is to take a user's intent — "I need a team that does X" — and produce a complete, functioning rig: the topology spec, the agent specs, the guidance files, the culture, the startup content, and everything else needed for the rig to boot and the agents to know what to do.
-
-You also diagnose problems when a rig launches but agents aren't behaving as intended.
-
-## Before You Design: Required Reading
-
-Load these before starting any design work. The quality of your output depends on the depth of knowledge you bring.
-
-**Required (read all of these):**
-
-1. **`openrig-user` skill** — full OpenRig CLI surface. You must know the operator primitives. If your runtime supports skills, load it by name. Otherwise, look for it at `~/.openrig/skills/openrig-user/SKILL.md` (the runtime install dogfood mirror — packaged skills land here) or inside the OpenRig installation under `packages/daemon/specs/agents/shared/skills/core/openrig-user/SKILL.md`. The `~/.openrig/reference/` directory holds reference docs (rig-spec.md, agent-spec.md, etc.), NOT skills.
-
-2. **OpenRig reference docs** — these are installed at `~/.openrig/reference/` when the daemon starts. Read all of them:
-   - `~/.openrig/reference/rig-spec.md` — canonical RigSpec YAML reference. Every field, validation rule, default.
-   - `~/.openrig/reference/agent-spec.md` — canonical AgentSpec YAML reference. Same depth.
-   - `~/.openrig/reference/agent-startup-guide.md` — how to think about what goes into agent startup. Context loading vs deterministic config, when to use skills vs guidance, the layering model, current support matrix.
-   - `~/.openrig/reference/edge-types.md` — what edges do today vs what they're intended to do.
-
-   If `~/.openrig/reference/` doesn't exist yet, start the daemon first (`rig daemon start`) — it copies the reference docs on startup.
-
-**Read as worked examples:**
-
-3. **Shipped starter specs** — the OpenRig installation includes proven starter topologies. Find them by running `rig specs ls`. Read the ones that are relevant to your design task, especially:
-   - `implementation-pair` — the smallest effective development unit (2 agents)
-   - `secrets-manager` — a managed-app rig with services integration and a specialist agent
-
-**Read if present on this host:**
-
-4. **Host-level doctrine file** (if your team maintains one — e.g., a HOST-TOPOLOGY doc that defines canonical rig classes, context-sharing patterns, and authoring SOPs for high-stakes rigs). If present, it supersedes the baseline process below for complex or high-stakes rigs (≥4 members, HA, managed-app, or shared/copied). Solo operators and small/focused rigs use the baseline below directly.
-5. **Agent-facing software design principles** if your rig ships a new CLI, service, or managed app that agents will operate. Treat the operating surface as a context-engineering problem: every error message and help text gives the agent information to act on.
-
-**Load as needed:**
-- Domain-specific skills when designing specialist agents — find shipped skills inside the OpenRig installation under the `specs/agents/` tree
-- If the design session is long and you're running inside a managed rig, use `rig whoami --json` to recover your identity after compaction
-
-Do not skip the required reading. A rig architect who doesn't know the spec format will produce specs that don't validate. An architect who doesn't know the startup layering model will produce agents that boot without knowing their role. An architect who doesn't check for host-level doctrine will reinvent conventions the host has already established.
-
-## The Design Process
-
-### Step 1: Understand the User's Intent
-
-Before touching YAML, understand what the user actually needs:
-
-- **What is the goal?** Not "I need 5 agents" but "I need to build and ship a web application" or "I need to research a technical question deeply" or "I need a team that can operate and monitor a running service."
-- **What are the workflows?** How does work flow from intent to completion? Who does what? Where are the handoffs?
-- **What is the project?** What codebase, what tech stack, what domain? This shapes agent specialization and startup content.
-- **What runtimes are available?** Does the user have Claude Code? Codex? Both? Runtime availability constrains topology design.
-- **How autonomous should it be?** Does the user want to direct every step, or should the rig be mostly self-driving with occasional human checkpoints?
-
-Ask clarifying questions if the intent is ambiguous. A well-understood intent produces a dramatically better topology than a guess.
-
-### Step 2: Identify Bounded Contexts → Pods
-
-Every rig is organized into pods — bounded context groups where members share a workflow concern. The question is: what are the natural groupings?
-
-**Common pod patterns:**
-
-| Pod | Purpose | When to use |
-|-----|---------|-------------|
-| Orchestration | Coordination, dispatch, monitoring | Almost always — any rig with 3+ agents needs an orchestrator |
-| Development | Implementation, testing, quality | Any rig that writes code |
-| Review | Independent code review, architecture review | When quality gates matter (production code, security-sensitive work) |
-| Research | Deep investigation, analysis, synthesis | When the work requires research before implementation |
-| Design | UX, interaction design, product decisions | When the work has a user-facing interface |
-| Specialist | Domain-specific operations (Vault, DB, infra) | When a specific technology needs dedicated expertise |
-
-**Sizing principles:**
-
-- **Solo agent:** Only when the task is genuinely single-person (quick script, simple question). No rig needed.
-- **Pair (2 agents):** The minimum effective unit for quality work. One does, one verifies. The `implementation-pair` pattern.
-- **Small team (3-5 agents):** Orchestrator + one or two working pods. Good starting point for focused projects.
-- **Full team (6-10 agents):** Multiple bounded contexts with orchestration, development, review, and potentially research or design.
-- **Large team (10-40+ agents):** Complex projects with many concerns. Include pods for development, review, research, documentation, release management, strategy, and any other bounded context the project needs.
-
-**Important:** Agents do NOT all need to be busy at the same time. A rig is a network, not an assembly line. Some pods will be highly active (dev, review) while others are available on-demand (research, documentation, release management). An idle agent has near-zero cost but is immediately available when any other agent in the rig needs it — for quick questions, lookups, delegation, or specialized work. Design for availability, not constant utilization.
-
-**Start small to increase the likelihood of success,** not because large rigs are wasteful. A 3-agent rig that boots and works correctly validates your spec authoring before you scale to 20 agents. Once the core topology works, expand with additional pods as needed.
-
-### Step 3: Design Agent Roles → Members
-
-Each pod member needs a clear role. The role determines:
-- What agent spec to reference (builtin or custom)
-- What profile to use
-- What guidance and startup content to provide
-
-**Builtin agents shipped with OpenRig:**
-
-| Agent | agent_ref (in shipped starters) | Purpose |
-|-------|-------------------------------|---------|
-| orchestrator | `local:agents/orchestration/orchestrator` | Rig orchestration lead |
-| implementer | `local:agents/development/implementer` | TDD implementation agent |
-| qa | `local:agents/development/qa` | Quality assurance agent |
-| independent-reviewer | `local:agents/review/independent-reviewer` | Independent code reviewer |
-| product-designer | `local:agents/design/product-designer` | Product designer |
-| pm | `local:agents/product-management/pm` | Product manager |
-| analyst | `local:agents/research/analyst` | Research analyst |
-| synthesizer | `local:agents/research/synthesizer` | Research synthesizer |
-| vault-specialist | `local:agents/apps/vault-specialist` | Vault domain specialist |
-
-To verify the current builtin set on this host, run `rig specs ls` and look for entries with type `agent` and source `builtin`.
-
-**Path resolution:** The `local:` prefix means relative to the rig spec file's directory. In shipped starters, these paths resolve against the builtin specs directory inside the OpenRig installation. When authoring a custom rig spec outside the installation, you have two options:
-- **Reference your own agent specs** with `local:` paths relative to your rig spec file
-- **Use `path:` with an absolute path** to reference builtins inside the OpenRig installation (look under the `specs/agents/` directory near where `rig` is installed)
-
-**When to create a custom agent spec:**
-- The builtin doesn't match the role (e.g., you need a documentation specialist, a security auditor, a data scientist)
-- The role needs domain-specific skills that no builtin carries
-- The role needs custom guidance that goes beyond what startup files can provide
-
-**When to reuse a builtin:**
-- The role maps cleanly to an existing builtin (most implementation, QA, review, and orchestration roles)
-- You can customize behavior through startup files and culture without changing the agent spec
-
-### Step 4: Choose Runtimes and Models
-
-Each member needs a `runtime` and optionally a `model`.
-
-**Runtime selection:**
-- `claude-code` — Claude Code. Best for: complex reasoning, architecture, code review, orchestration. Supports `/loop` for recurring tasks, rich hooks system, MCP servers.
-- `codex` — Codex. Best for: parallel work, implementation, testing. Different approval model. Less reliable for recurring tasks.
-- `terminal` — Infrastructure nodes. Servers, log tails, build watchers. Not an agent — a process.
-
-**Runtime diversity is valuable.** Using both Claude Code and Codex in the same rig gives you different reasoning perspectives. The `product-team` starter uses Claude Code for the lead/impl/design/r1 roles and Codex for peer/qa/r2 roles. This is deliberate — model diversity catches different classes of issues.
-
-**Model selection** is optional. The runtime's default model is usually fine. Override only when you have a specific reason (e.g., a complex architecture agent might benefit from a specific model).
-
-### Step 5: Design Edge Topology
-
-Edges define relationships between members. See `~/.openrig/reference/edge-types.md` for the full reference.
-
-**Practical rules:**
-- Every working pod should have at least one `delegates_to` edge from the orchestrator
-- Review pods should have `can_observe` edges to the pods they review
-- Within a pod, the primary workflow direction should be expressed as `delegates_to` (e.g., impl → qa)
-- `delegates_to` and `spawned_by` affect launch order. Use them for dependency chains.
-- `can_observe`, `collaborates_with`, `escalates_to` are informational — they help agents understand the topology but don't constrain launch.
-
-**Start simple.** You can always add edges later. A rig with only `delegates_to` edges from the orchestrator to working pods is perfectly functional.
-
-### Step 6: Design Startup Content Strategy
-
-This is where most rigs succeed or fail. The topology is mechanical; the startup content is what makes agents actually useful. See `~/.openrig/reference/agent-startup-guide.md` for the full guide.
-
-**Minimum for every rig:**
-1. Each agent has a `guidance/role.md` — who they are, what they do
-2. The rig has a `CULTURE.md` — how the team works together
-3. Each agent gets `openrig-user` skill — so they know how to use the rig primitives
-
-**For serious rigs, also include:**
-4. `startup/context.md` per agent — boot-time grounding (project info, environment details)
-5. Pod SOP skills — how each pod operates (implementation-pair SOP, review-pair SOP, etc.)
-6. Project-specific documentation in rig-level startup files
-
-**The key principle:** An agent that boots without knowing its role, its team's culture, and its project context will produce generic, unhelpful work. The startup content IS the product value. Invest in it.
-
-### Step 7: Services Integration (If Needed)
-
-If the rig needs managed software (databases, API servers, etc.), add a `services` block. See `~/.openrig/reference/rig-spec.md` for the full services reference.
-
-**When to add services:**
-- The agents operate ON software (not just write code)
-- The project needs a local dev environment (Postgres, Redis, etc.)
-- You're building a managed-app rig (software + specialist agent)
-
-**Services boot before agents.** If health checks fail, no agents start. This is the hard gate — the environment must be healthy before agents can work.
-
-## Authoring: The File Creation Workflow
-
-### Directory Layout
-
-```
-my-rig/
-  rig.yaml                    # The RigSpec — required
-  culture/
-    CULTURE.md                # Rig-wide culture — strongly recommended
-  agents/
-    my-custom-agent/
-      agent.yaml              # AgentSpec — if custom agent needed
-      guidance/
-        role.md               # Role guidance
-      startup/
-        context.md            # Boot-time context
-      skills/
-        my-skill/
-          SKILL.md            # Custom skill if needed
-  docker-compose.yaml         # Only if services block is used
-```
-
-For rigs that reuse builtin agents, the agents directory is often unnecessary — the rig spec references the builtins directly.
-
-### Workflow
-
-1. **Write the rig spec** (`rig.yaml`) — define pods, members, edges, optionally services
-2. **Write or reference agent specs** — builtins for standard roles, custom for specialized roles
-3. **Write CULTURE.md** — the team operating manual
-4. **Write role guidance** for each custom agent — who they are, what they do
-5. **Write startup context** for agents that need environment grounding
-6. **Validate:** `rig spec validate rig.yaml` and `rig agent validate agents/*/agent.yaml`
-7. **Confirm the runtime cwd** — do not assume agents should work from the directory where the rig spec is stored. The spec root controls file resolution; the runtime cwd controls trust, project guidance, permissions, and repo context.
-8. **Launch:** `rig up rig.yaml --cwd /path/to/project`
-9. **Verify:** `rig ps --nodes` — all agents ready? Check `rig capture` on each agent.
-
-### Validation Is Non-Negotiable
-
-Always validate before launching:
-
-```bash
-rig spec validate rig.yaml
-rig agent validate agents/my-agent/agent.yaml
-```
-
-If validation fails, fix the errors. Do not try to launch an invalid spec — it will fail with a less helpful error.
-
-## Diagnosis: When Things Go Wrong
-
-### Agent doesn't know its role
-
-**Symptom:** Agent produces generic output, doesn't follow team conventions.
-**Root cause:** Missing or insufficient `guidance/role.md`.
-**Fix:** Write a clear role guidance file. Include responsibilities, working rhythm, and principles. Reference it in both `resources.guidance` and `startup.files`.
-
-### Agent can't coordinate with peers
-
-**Symptom:** Agent tries raw tmux commands instead of `rig send`, doesn't know peer session names.
-**Root cause:** Agent didn't receive `openrig-user` skill or `openrig-start` overlay.
-**Fix:** Ensure the agent's profile `uses.skills` includes `openrig-user`. Verify via `rig ps --nodes` that the agent shows expected startup status; check installed skills via direct startup/capture/transcript evidence or the UI node detail (the `rig ps --nodes` projection does not expose installed-resource counts).
-
-### Agent hits approval prompts on rig commands
-
-**Symptom:** Agent stalls on `rig whoami`, `rig send`, etc.
-**Root cause:** Claude Code permissions not configured for rig commands.
-**Fix:** Describe the required permissions in startup context. The agent should configure `~/.claude/settings.json` with allowlisted rig commands. See `~/.openrig/reference/agent-startup-guide.md` for the current support matrix.
-
-### Agents idle — topology doesn't engage the team
-
-**Symptom:** Orchestrator works with one or two agents, others sit idle.
-**Root cause:** Missing `CULTURE.md` or pod SOP content that describes how the full team coordinates.
-**Fix:** Write a culture file that explicitly describes the coordination protocol. Include delegation patterns, review gates, and when each pod should be engaged.
-
-### Services don't boot
-
-**Symptom:** `rig up` fails before agents launch with a service health error.
-**Root cause:** Docker Compose issue, health check failure, or port conflict.
-**Fix:** Check `docker compose up` manually with the compose file. Verify health check URLs are correct. Check for port conflicts.
-
-### Agent boots from the wrong project context
-
-**Symptom:** Agent misses expected guidance, trust settings, permissions, or repo context even though the spec validates.
-**Root cause:** The rig spec directory was treated as the agent's runtime cwd by assumption.
-**Fix:** Confirm the intended cwd before launch. The spec can live in a rig/spec shelf while the agent works from the project or hub directory that carries the relevant `AGENTS.md`, `CLAUDE.md`, trust, and permissions. Use member `cwd` or `rig up --cwd` deliberately.
-
-### Startup content not delivered
-
-**Symptom:** Agent is missing expected guidance/skills.
-**Root cause:** File paths in the spec don't resolve, or `delivery_hint` is wrong.
-**Fix:** Verify file paths resolve relative to their owning artifact — AgentSpec resource paths are relative to the agent spec directory; RigSpec startup, culture, compose, cwd, and `local:` agent-ref paths are relative to the rig root. Check `delivery_hint` — use `guidance_merge` for pre-boot content, `send_text` for post-boot instructions.
-
-### Agent startup delivered but agent doesn't use skills
-
-**Symptom:** Skills are projected but agent doesn't invoke them.
-**Root cause:** Agent wasn't told to load them.
-**Fix:** In the startup context or role guidance, explicitly tell the agent which skills to load. The belt-and-suspenders pattern: project the skills via the spec AND tell the agent to read them in the guidance.
-
-## Pattern Catalog
-
-### The Implementation Pair
-**2 agents, 1 pod.** The smallest effective development unit. One implements (TDD), one does QA. The implementer proposes, QA approves or rejects, then the implementer commits.
-
-```yaml
-pods:
-  - id: dev
-    label: Development
-    members:
-      - id: impl
-        agent_ref: "local:agents/development/implementer"
-        runtime: claude-code
-        profile: default
-        cwd: "."
-      - id: qa
-        agent_ref: "local:agents/development/qa"
-        runtime: codex
-        profile: default
-        cwd: "."
-    edges:
-      - kind: delegates_to
-        from: impl
-        to: qa
-```
-
-**Use when:** Focused feature work, bug fixes, small-to-medium implementation tasks.
-
-### The Orchestrated Team
-**5-7 agents, 3 pods.** Orchestration + development + review. The orchestrator dispatches work, the dev pair implements, the review pair validates independently.
-
-**Use when:** Production-quality work that needs coordination and independent review.
-
-### The Research Team
-**3 agents, 2 pods.** Orchestrator + research pair (analyst + synthesizer). The analyst investigates deeply, the synthesizer consolidates findings.
-
-**Use when:** Technical research, competitive analysis, architecture exploration.
-
-### The Managed App
-**1+ agents, 1 pod, services block.** Software infrastructure (Docker Compose) plus a specialist agent who knows how to operate it.
-
-```yaml
-services:
-  kind: compose
-  compose_file: docker-compose.yaml
-  wait_for:
-    - url: http://127.0.0.1:8200/v1/sys/health
-
-pods:
-  - id: vault
-    label: Vault
-    members:
-      - id: specialist
-        agent_ref: "local:agents/apps/vault-specialist"
-        runtime: claude-code
-        profile: default
-        cwd: "."
-    edges: []
-```
-
-**Use when:** The work involves operating software, not just writing code.
-
-### The Full Product Team
-**7 agents, 3 pods.** The kitchen-sink topology: orchestration pair, development pod (impl + qa + design), review pair. See the `product-team` starter spec for the complete worked example.
-
-**Use when:** Full product development with design, implementation, QA, and independent review. Requires strong culture and SOP content to keep all agents engaged.
-
-## Final Notes
-
-**Start simple, add complexity when needed.** A working implementation pair is better than a broken full team. Launch with the minimum viable topology, verify it works, then expand.
-
-**Culture is not optional for team rigs.** Any rig with 3+ agents needs a CULTURE.md. Without it, agents will default to generic behavior and the topology will underperform.
-
-**Validate early and often.** Run `rig spec validate` after every change. Run `rig agent validate` after every agent spec edit. Fix errors immediately — don't accumulate them.
-
-**The startup content IS the product.** The YAML topology is scaffolding. What makes a rig actually useful is the guidance, culture, skills, and startup context that agents receive. Invest your authoring time there.

package/daemon/assets/plugins/openrig-core/skills/openrig-cmux/SKILL.md

@@ -1,86 +0,0 @@
----
-name: openrig-cmux
-description: >
-  Use when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved
-  view into live agent tiles via `rig terminal --provider cmux`, or driving cmux on an agent's
-  request. Same OpenRig view semantics as openrig-herdr (the verbs, honest-partial/degrade, read-only
-  cross-rig, scroll/copy, same-size-only duplicates); cmux is the **best-effort** provider (herdr is
-  the default and the proof-gated one). Prefer openrig-herdr unless cmux is specifically wanted.
-metadata:
-  openrig:
-    stage: candidate
-    distribution_scope: product-bound
-    source_evidence: |
-      cmux is OpenRig's shipped terminal provider generalized onto `rig terminal <provider>` —
-      best-effort, not proof-gated. Authored clean-room.
-    transfer_test: pending
-    sibling_skills:
-      - openrig-herdr
-      - openrig-user
----
-
-# openrig-cmux
-
-cmux is a **provider** for OpenRig views — the same `rig terminal` surface as herdr, rendering the
-tiles into cmux instead. It is the provider OpenRig already shipped (the existing "Launch in cmux"
-affordance generalizes onto `rig terminal <provider>`), kept working. The OpenRig-semantic half is
-identical to openrig-herdr: OpenRig decides **which** agents form a view; the provider renders the
-pixels. **Read openrig-herdr first for the full model** — this skill only calls out what differs for
-cmux.
-
-## Provider status — cmux is best-effort
-
-- **herdr is the default and the proof-gated provider**; **cmux is best-effort** — it ships on the
-  same `rig terminal <provider>` + web-launcher neighborhood, but a cmux miss is not a slice failure.
-  Reach for cmux when it is specifically wanted; otherwise default to herdr (`rig terminal open <view>`
-  with no `--provider`).
-- Views are **provider-agnostic**: the same view + the same agents + the same semantics carry across
-  herdr and cmux. A saved view opens in either.
-
-## The surface (same three verbs, `--provider cmux`)
-
-```bash
-rig terminal open <view> --provider cmux [--json]   # open a view into cmux (herdr is the no-flag default)
-rig terminal views [--json]                          # the same view library, provider-agnostic
-rig terminal status --provider cmux [--json]         # cmux liveness / health
-```
-
-`<view>` resolves exactly as with herdr: a **rig name** · **`pod:<rig>/<podNamespace>`** ·
-**`mission:<id>`** · **`slice:<id>`** (derived live) · a **saved-view name**.
-
-## What carries over unchanged from openrig-herdr
-
-All of these behave identically — see openrig-herdr for the detail:
-
-- **Honest-partial / honest-degrade** — opened / absent / degraded, each named; partial opens exit 0,
-  zero-pane exits non-zero; an http-registered host's agents degrade with the reason ("host `<id>` is
-  http-registered; tiles need ssh"), never silently dropped.
-- **Read-only policy** — a rig or `pod:` view is interactive; `mission:` / `slice:` views are
-  read-only by construction; a saved view is per-member (`readOnly`). A read-only pane is
-  `tmux attach -r` (client `readonly=1`, keystrokes physically cannot reach the agent). See openrig-herdr.
-- **Safety rails (the fleet-safety rail)** — a tile is a *view* (nested `tmux attach`) of a
-  daemon-owned session; never move/join/kill/re-parent a daemon-owned pane; closing a tile detaches
-  one client and leaves the session untouched; never live-flip tmux options on a running seat in
-  production (prove it in an isolated environment first).
-- **Scroll + copy out of the box** — the daemon's terminal defaults (per-session scroll at launch +
-  the server's clipboard defaults); running seats pick up wheel-scroll at their next relaunch.
-- **Limits** — tile chrome v1 = a plain label; same-size panes for duplicate/multi-view membership
-  (the different-size resize mismatch is an inherent tmux multi-client limit, documented not fixed).
-
-## cmux-specific notes
-
-- **Open-or-focus per agent** — cmux's shipped integration opens a node or focuses it if already open;
-  expect focus (not a duplicate) when a seat is already tiled in cmux.
-- **The shipped "Launch in cmux" affordance is preserved** (byte-compatible) and generalizes into the
-  provider + view picker; opening cmux from the web launcher still works.
-- **No AGPL arm's-length concern** — unlike herdr, cmux is OpenRig's shipped provider integration; the
-  clean-room/never-embed rail that applies to herdr is not a cmux constraint. (This skill itself is
-  still authored clean-room.)
-
-## Saved views — provider-agnostic
-
-Saved views are **hand-authored** in `terminal-views.yaml` (v1 has no save/write verb) and are
-**provider-agnostic** — see **openrig-herdr** for the exact schema, the store facts (atomic tmp+rename,
-byte-stable, at the OpenRig home root), and the derived-views-never-persisted rule. Reopen any saved
-view in cmux with `rig terminal open <id> --provider cmux`. Derived views (a rig, `pod:<rig>/<pod>`,
-`mission:<id>`, `slice:<id>`) are computed live and never written to the file.

package/daemon/assets/plugins/openrig-core/skills/openrig-herdr/SKILL.md

@@ -1,158 +0,0 @@
----
-name: openrig-herdr
-description: >
-  Use when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or
-  saved view into live interactive agent tiles via `rig terminal`, watching another rig read-only,
-  or driving herdr on an agent's request ("open all my rigs + a mission as views"). Covers the
-  `rig terminal open|views|status` verbs, the honest-partial/degrade reading of the result, the
-  read-only-by-construction rail for cross-rig views, scroll/copy out of the box, and the
-  same-size-only duplicate-pane limit. herdr is the default, proof-gated provider.
-metadata:
-  openrig:
-    stage: candidate
-    distribution_scope: product-bound
-    source_evidence: |
-      Empirical herdr 0.7.1 hands-on findings + the ratified implementation PRD. Authored
-      clean-room (patterns only, no herdr source text; AGPL arm's-length).
-    transfer_test: pending
-    sibling_skills:
-      - openrig-cmux
-      - openrig-user
----
-
-# openrig-herdr
-
-OpenRig decides **which** agents make up a view (a rig, a pod, a mission, a slice, or a saved
-group); **herdr** renders the pixels. A view opens as live, interactive terminal tiles — each tile
-is a nested `tmux attach` to a daemon-owned agent session, so you get the real session, not a
-snapshot. OpenRig owns the semantics; herdr owns the surface. You drive it entirely through the
-`rig terminal` CLI, which rides the installed herdr binary at arm's length — never link, embed, or
-plugin it.
-
-## The whole surface — three verbs
-
-```bash
-rig terminal open <view> [--provider herdr|cmux] [--json]   # herdr is the default provider
-rig terminal views [--json]                                 # list openable views (saved + derived)
-rig terminal status [--provider] [--json]                   # provider liveness / health
-```
-
-`<view>` resolves, in order, to one of:
-- a **rig name** — every live agent in that rig, auto-laid-out;
-- **`pod:<rig>/<podNamespace>`** — every live agent in one pod of a rig (the rig's inventory filtered by pod);
-- **`mission:<id>`** — the agents working that mission (derived live from topology);
-- **`slice:<id>`** — the agents working that slice (derived live);
-- a **saved-view name** — a user-defined group (see Saved views).
-
-## Compose a view from a sentence
-
-An agent asked "open all my rigs plus a mission as views" runs one `open` per target:
-
-```bash
-rig terminal open acme-web                     # a whole rig, live agents as tiles
-rig terminal open mission:site-relaunch        # exactly the agents working the mission
-rig terminal open slice:02-search-filters      # the agents working one slice
-```
-
-No hand-listing of seats: the mission/slice membership is derived from live topology at open time.
-
-## Read the result honestly — partial and degrade
-
-The result is a partition — every seat lands in exactly one bucket, each **named**:
-
-- **opened** — the live agents now showing as tiles.
-- **absent** — seats in the view that aren't currently live: **named and skipped, never silently
-  dropped.** A view that opens *some* of its seats is a success (the partial is disclosed) and exits
-  **0**. Only a view where **no** pane opens exits **non-zero**.
-- **degraded** — an agent that structurally cannot tile, named **with the reason**. The v1 case:
-  an agent on a host registered over HTTP has no ssh path, so its tile can't be composed — it reads
-  as **"host `<id>` is http-registered; tiles need ssh"** and is skipped, never dropped. (ssh-reachable
-  hosts tile via an ssh-wrapped attach; full http-host tiling is deferred to the cross-host transport
-  seam.)
-
-Read `--json` to branch on the partition programmatically; the exit code alone tells you opened-something
-(0) vs opened-nothing (non-zero).
-
-## Read-only — who's interactive, who's watch-only
-
-Read-only is composed into the pane at open time — a read-only tile is a `tmux attach -r`, the client
-reports `readonly=1`, and it **physically cannot send input**. The current policy, by view kind:
-
-- **A rig view or a `pod:` view is interactive** — you asked for that rig (or pod) directly, so you
-  can drive its agents.
-- **`mission:` and `slice:` views are read-only by construction** — these derived views cut across
-  rigs; you watch and scroll, you don't keystroke into them.
-- **A saved view is per-member** — each member carries its own `readOnly` (omit = interactive;
-  `true` = `attach -r`).
-
-So you don't have to remember to be careful: the view kind (and, for a saved view, the per-member
-flag) sets it at open time.
-
-## Safety rails (hard — the fleet-safety rail)
-
-- A tile is a **view** (a nested `tmux attach`) of a daemon-owned session. **Never** move, join, kill,
-  or re-parent a daemon-owned pane. Closing a tile detaches one tmux client — the daemon's session is
-  untouched and its addressing (send/capture/nudge) is unaffected.
-- Host-local read-only viewing mutates nothing. Anything that would change a **live** daemon session's
-  shared state (e.g. flipping a tmux option on a running seat) is a config/design change — prove it in
-  an isolated environment, never live-flip in production.
-
-## Scroll + copy work out of the box
-
-On a freshly-launched agent tile the mouse wheel scrolls the pane's history and a drag-select copies
-to your **system** clipboard — with no tmux commands typed. This rides the daemon's terminal defaults
-(a per-session scroll option set at launch, plus the daemon tmux server's clipboard defaults). Honest
-timing: agents that were already running before this shipped pick up wheel-scroll at their **next
-natural relaunch** (the scroll default is per-session and running seats are never retro-flipped);
-system-clipboard copy works immediately (it's server-wide).
-
-## Limits — state them, don't paper over them
-
-- **Tile chrome v1 = a plain label** (agent + slice). Rich per-tile status is roadmap.
-- **Duplicate / multi-view membership** (the same agent live in two views at once) works — put the
-  duplicates in **same-size panes**. Different-sized duplicate panes have an inherent tmux
-  multi-client resize mismatch (tmux clamps to the smallest client); it is **documented, not fixed** —
-  don't expect a setting to remove it.
-- **Inner tmux status bar** is hidden by default (herdr provides the chrome); one config key
-  (`terminal.status_bar`) flips it back on for raw-tmux / no-provider surfaces, and the flip applies
-  to **future launches only**.
-
-## Saved views — the library (`terminal-views.yaml`)
-
-In v1 you **create** a saved view by **hand-authoring** `terminal-views.yaml` — there is no save/write
-verb (`open` / `views` / `status` are the whole surface; a `rig terminal save <id>` verb is a named
-stretch/follow-up). You **reopen** it like any other view: `rig terminal open <id>`.
-
-The file lives at the OpenRig home root (resolved via `getDefaultOpenRigPath()`), is written
-atomically (tmp + rename), and is byte-stable. **Only hand-authored saved views live here — derived
-views (a rig, `pod:<rig>/<pod>`, `mission:<id>`, `slice:<id>`) are computed live and never written to
-this file.**
-
-Schema — use these field names **exactly**, in this order; **omit** optional fields when absent
-(never write `null`):
-
-```yaml
-version: 1
-views:
-  - id: my-view-id             # required — the id `rig terminal open <id>` takes
-    name: Human Name           # required
-    members:
-      - seat: pod-member@rig    # required — the canonical session name
-        label: agent . slice    # optional — pane label
-        host: some-host-id      # optional — STRUCTURED host id (NEVER a `member@rig@host` string);
-                                #            omit for local. ssh-registered hosts tile;
-                                #            http-registered hosts honest-degrade (named + skipped, with reason)
-        tmuxSession: sessname   # optional — defaults to `seat`
-        readOnly: true          # optional — omit = interactive; true = `tmux attach -r`
-```
-
-An agent composing a saved view on request **writes this YAML** and then opens the id:
-`rig terminal open my-view-id` (add `--provider cmux` for cmux). The library is provider-agnostic —
-the same saved view opens in herdr or cmux.
-
-## AGPL / clean-room
-
-Driving herdr through the `rig terminal` CLI (which talks to the installed herdr binary over its
-CLI/socket) is arm's-length and fine. Do **not** link herdr's source, embed it in-process, or ship a
-herdr plugin — a plugin needs legal review. This skill and its docs are clean-room: patterns only,
-never herdr source text.