@openrig/cli 0.4.4 → 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-operator/SKILL.md

@@ -1,222 +0,0 @@
----
-name: openrig-operator
-description: |
-  Use when debugging host-side OpenRig runtime issues: daemon reachability, Codex permission or writable-root failures, command approval friction, rate limits/account switches, helper cleanup, or topology health confusion. NOT for ordinary CLI operation (use openrig-user) or for changing OpenRig itself (work in the openrig product repo).
-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/).
-      Companion to openrig-user (daily CLI surface) — this skill is host-side troubleshooting.
-    transfer_test: pending
-    sibling_skills:
-      - openrig-user
-      - openrig-architect
-      - forming-an-openrig-mental-model
----
-
-# OpenRig Operator
-
-## Overview
-
-This skill covers host/runtime/operator triage around OpenRig itself.
-Use it when the problem may be the daemon, the shell/runtime surface, or stale helper processes rather than the product workflow you are trying to run.
-
-> **CANONICAL SURFACE NOTE (2026-05-11)** — for durable queue routing while doing
-> operator triage, use `rig queue` (daemon-backed SQLite). `rigx queue` is
-> recovery-only fallback; qitems written there are invisible to daemon-backed
-> reads and should not be used for new substantive work.
-
-## When to Use
-
-Use this skill when you see:
-- `rig whoami --json` returning partial identity
-- `rig ps --nodes --json` failing while some other `rig` commands still work
-- `Sent to ...` plus `Verified: no`
-- repeated unified-exec-process warnings
-- suspicion that stale helper processes are accumulating
-- Codex seats hit `Operation not permitted`, command approval friction, or stale writable roots
-- Codex seats report usage-limit/rate-limit or need a ChatGPT account switch
-
-Do not use this skill for normal product workflow routing, queue handling, or ordinary peer communication. Use `openrig-user` for that.
-
-Do not use this skill to decide how to change OpenRig behavior. Changes
-to the OpenRig product (CLI, daemon, UI, specs) happen in the openrig
-product repo — operate that as a normal software project, not via
-this troubleshooting skill.
-
-## First Checks
-
-Start with the minimum truthful operator read:
-
-```bash
-rig whoami --json
-rig daemon status
-rig ps --nodes --json
-```
-
-Interpret them together, not in isolation:
-- partial `whoami` can mean identity is inferable while daemon-backed surfaces are degraded
-- `daemon status` tells you whether the host daemon is up, not whether every seat can reach it cleanly
-- `ps --nodes --json` is the best machine-readable topology check when it works
-
-## Verification Drift Vs Send Failure
-
-For `rig send`:
-- `Sent to ...` + `Verified: yes` = strong positive delivery evidence
-- `Sent to ...` + `Verified: no` = ambiguous delivery, not automatic failure
-- no `Sent to ...` line or a hard error = send failure
-
-When verification is ambiguous, check:
-- direct reply
-- `rig capture <session>`
-- transcript evidence
-- queue/outbox state if the message asked for a durable handoff
-
-Do not blindly retry until you have checked one of those.
-
-## Unified Exec Warning
-
-If you see:
-
-- `Warning: The maximum number of unified exec processes you can keep open is 60 ...`
-
-treat it first as a host/tooling-layer warning, not as automatic proof that the OpenRig topology is unhealthy.
-
-This warning can coexist with a healthy live topology.
-
-## Safe Process Triage
-
-Inspect the process surface first:
-
-```bash
-ps -axo pid,ppid,command | rg 'tmux send-keys|rig queue create|tmux attach|codex|claude'
-```
-
-Think in layers:
-- host/tooling layer: stale one-shot wrappers, session bookkeeping, helper shells
-- topology layer: live `tmux attach` seats, live `codex` / `claude` runtimes, daemon health
-
-Do not diagnose topology failure from tooling-layer warnings alone.
-
-## Safe Cleanup Boundary
-
-Usually safe to reap when clearly orphaned / one-shot:
-- `tmux send-keys ...`
-- short-lived shell wrappers created only to enqueue or send one message
-
-Do not mass-kill:
-- `tmux attach ...`
-- `codex ...`
-- `claude ...`
-- other long-lived daemon/runtime processes
-
-The point is to remove garbage, not workers.
-
-## Terminal Node Escalation
-
-Use a terminal node when evidence shows a seat-level sandbox/profile cannot perform required host work, but another approved operator surface can. This is an explicit operator lane, not a silent permission bypass.
-
-Good fits:
-- Codex/Claude seat cannot access Tart, SSH, tmux, queue directories, or host files needed for a proof
-- a VM/test-proof or current-host-operator task needs real host capability
-- another seat or terminal/sysadmin node has approved access and can return command evidence
-
-Do not use this lane to bypass repo safety, dirty-worktree boundaries, review gates, or destructive-action approval. If the command would stop live rigs, delete data, reset git state, or mutate VM state beyond the accepted plan, require explicit authorization and record it.
-
-Protocol:
-1. Classify the original failure as seat/profile-specific if possible, not product failure.
-2. Write or cite a packet with objective, lane, exact commands, cwd, expected outputs, stop conditions, and artifact path.
-3. Route to an existing sysadmin/infrastructure/terminal node when available; otherwise provision a named terminal node through the topology/config layer instead of using a hidden ad hoc shell.
-4. Terminal node runs only the packeted commands and returns command log, exit codes, cwd/env notes, and artifacts.
-5. Original agent keeps task ownership and proof classification; terminal node supplies host capability.
-
-Field lesson: if tester sees `Operation not permitted` for Tart/SSH while driver or another approved seat can reach the VM, treat it as permission/profile variance and route a terminal-node/operator remediation before changing product code.
-
-## Codex Permission Policy
-
-Use the `security-and-consequence-boundary-policy` skill for the security model.
-OpenRig gates consequence boundaries, not ordinary work inside the intended boundary.
-
-Treat Codex permissions as two independent layers:
-- command approval rules decide which shell commands can run outside the sandbox
-- filesystem writable roots decide which paths a `workspace-write` seat can mutate
-
-Codex `auto_review`, `--full-auto`, and approval-bypass modes are not normal fleet defaults. They
-can burn quota catastrophically and do not widen filesystem roots for an already-running seat. Full
-access scope with `approvals_reviewer = "user"` is the intended Codex default here.
-
-Claude Code auto permissions are different and are the preferred Claude default on this host when
-the consequence-boundary rules still apply.
-
-Current host policy:
-- default profile is `fleet`
-- `fleet` uses `sandbox_mode = "danger-full-access"`, `approval_policy = "on-request"`, `approvals_reviewer = "user"`
-- top-level `[sandbox_workspace_write].writable_roots` intentionally includes `~/code` and tool dotdirs: `.codex`, `.claude`, `.openrig`, `.agents`, `.config`, `.cache`, `.local`, `.docker`, `.npm`, `.nvm`, `.pnpm-store`
-- `permissions.fleet.filesystem` mirrors those writes and denies `.ssh`, `.gnupg`, and project env files
-- `default.rules` broadly allows `rig` and `rigx`; `rigx` is fully permitted for now because it is the fast-moving config-layer overlay
-- `default.rules` still prompts for destructive/publishing surfaces such as `rm`, `mv`, `chmod`, `git push`, PR mutation, `sudo`, process kills, daemon lifecycle, and destructive Docker/Brew/rig commands
-
-## Codex Account / Usage-Limit Refresh
-
-When Codex seats hit usage limits or need a ChatGPT/OpenAI account rotation, use the focused
-`codex-seat-auth-refresh` skill instead of improvising.
-
-Key reminder: host auth can switch while already-running Codex TUIs keep the old account. Refresh
-only the scoped seats, preserve stable seat names, and record auth-seat registry rows sequentially.
-
-Known failure modes this policy prevents:
-- Codex seats assuming a task is impossible when the real issue is stale launch roots
-- agents creating workaround slices/features for what is actually a sandbox/config problem
-- writing load-bearing canon into `state/`, `/tmp`, or a nearby writable folder because the intended durable path was blocked
-- trusting labels like `full access`; verify actual roots and command policy instead
-- changing `config.toml` and expecting already-running seats to pick it up without restart
-
-When `Operation not permitted` appears:
-1. Identify whether it is command approval, filesystem root, macOS privacy, or stale session.
-2. Check effective roots with `codex -p fleet debug prompt-input <probe-name>`.
-3. Verify with a tiny direct write probe in an allowed target and a negative probe in a protected target such as `.ssh`.
-4. If `config.toml` changed, restart one seat and re-run the probes before fleet rollout.
-5. If the target should be durable and is not writable, stop and escalate; do not invent fallback storage.
-
-Field note: as of Codex CLI `0.125.0`, top-level `[sandbox_workspace_write]` was the shape reflected by `debug prompt-input`; profile-scoped writable roots did not show in the effective prompt. Re-test this if Codex changes.
-
-
-## Durable Write Escalation
-
-If the task requires writing load-bearing knowledge or behavior and the intended target is not writable, stop and escalate. Do not silently write to `state/`, `/tmp`, or a nearby writable folder.
-
-Use the intended durable home for the kind of content:
-- `skills/` (e.g. `~/.claude/skills/`, `~/.agents/skills/`, or your team's
-  shared skill folder) for operating rules and refocus behavior
-- Your team's workstream notebook (field notes, lab experiments, mission
-  packets, etc.) for durable observations and PM canon
-- The product repo for shipped OpenRig daemon/CLI/config/spec/test behavior
-
-A runtime mirror under a rig `state/` path may be used only as a temporary live patch, must be labeled as non-canonical, and must have a canonical sync follow-up.
-
-## Common Mistakes
-
-- treating `Verified: no` as if it proves the message did not land
-- treating the unified-exec warning as if it proves the rig is overloaded
-- killing live seats when only stale helper wrappers needed cleanup
-- concluding "daemon down" from one seat's failure without checking host-level daemon status
-- assuming Codex config changes apply to already-running seats without a restart/probe
-- confusing command approval with filesystem write permission
-- calling a VM or product path broken before comparing another approved seat or terminal-node probe
-- assuming a label like `full access` proves effective write/network capability; verify command approval and filesystem writable-root coverage separately
-
-## Practical Rule
-
-Clean the smallest safe surface that matches the evidence.
-
-If the warning or failure remains after stale-wrapper cleanup, re-check:
-
-```bash
-rig daemon status
-rig ps --nodes --json
-```
-
-If those remain healthy, the residual issue may still be in the host/tool/session layer rather than in OpenRig topology state.