@openrig/cli 0.5.1 → 0.5.3

package/daemon/specs/agents/shared/skills/core/watchdog/SKILL.md

@@ -10,7 +10,7 @@ metadata:
       # genuinely adjacent set.
       - queue-handoff
       - workflow-runtime
-      - alignment-trace
+      - refocus
       - looping-workflows
       - intake-routing
       - human-in-the-loop
@@ -22,7 +22,7 @@ metadata:
 
 Continuity checks are timed or evidence-triggered interventions that
 keep an agent workflow from going idle, drifting, or entering needless
-bureaucracy. They operationalize the alignment-trace doctrine.
+bureaucracy. They operationalize the refocus doctrine.
 
 ## Use this when
 
@@ -49,7 +49,7 @@ bureaucracy. They operationalize the alignment-trace doctrine.
 |---|---|---|---|
 | **Wake** | Restart motion | Owner appears idle, stale, blocked, or missing a next handoff | Small liveness nudge — does NOT reframe the work |
 | **Refocus** | Correct drift | Output shows mode drift, approval regression, weak stop-condition reasoning | Medium alignment nudge — re-centers on role, north star, current approved workstream, coordination mode, stop conditions; does NOT interrupt valid work |
-| **Alignment checkpoint** | Rebuild shared map | Phase boundary, lifecycle mutation, product-intent decision, confusing contradiction | Larger deliberate pause — agent runs full alignment-trace before proceeding |
+| **Alignment checkpoint** | Rebuild shared map | Phase boundary, lifecycle mutation, product-intent decision, confusing contradiction | Larger deliberate pause — agent runs full refocus before proceeding |
 
 `cron`, timers, and `rig watchdog` are scheduling substrates. They
 should NOT imply that every tick means the same semantic action. The
@@ -121,6 +121,6 @@ handling over many per-seat nag loops.
 
 ## See also
 
-- `alignment-trace` skill — the doctrine this primitive operationalizes; full and light trace templates
+- `refocus` skill — the doctrine this primitive operationalizes; full and light trace templates
 - `queue-handoff` skill — durable handoff via queue items; watchdog is complementary (watchdog wakes; queue routes)
 - `looping-workflows` skill — operating discipline for self-driving rig-shaped loops; uses watchdog policies for loop edges

package/daemon/specs/agents/shared/skills/pods/development-team/SKILL.md

@@ -43,6 +43,14 @@ This is the default loop for product work:
 
 Skip no gates. If the task is ambiguous, resolve the ambiguity before editing.
 
+**Chunk size points up — keep TDD's shape, not its ping-pong cadence (2026-08).** Frontier agents handle
+large, long-horizon, goal-oriented chunks — an hour-plus of complex work — without fragmenting. So don't
+default to tiny pieces: **keep TDD's *shape* (two sets of eyes, the guard structure, red before green)
+but treat chunk size and cadence as a configured LEVER, not a habit.** Classic small back-and-forth
+ping-pong is unnecessary overhead when the loop's own gates (QA, review, guards) already bound a larger
+chunk's risk. The sweet spot is task-dependent, much larger than it used to be, and rising. See
+`test-driven-development` for the shape that stays fixed.
+
 ## What the implementer must hand QA
 
 Pre-edit proposal should include:

package/daemon/specs/agents/shared/skills/pods/orchestration-team/SKILL.md

@@ -28,18 +28,18 @@ The orchestration pod is responsible for:
 
 ## Monitoring & intervention — keep the RIG self-running, not the ORCHESTRATOR busy
 
-**North star:** your goal is a **self-running rig, not a busy orchestrator.** Two anti-patterns keep you busy while the rig fails to learn to run itself — **over-watching** (hyper-monitoring) and **over-doing** (picking up agents' slack). Both are governed by judgment below, not by a rule for every case. (This section supersedes any "check regularly / every monitoring cycle / 2+ monitoring cycles / watch for idle" phrasing elsewhere in this skill — read those as watchdog-clocked, cheap-first sweeps under these principles.)
+**North star:** your goal is a **self-running rig, not a busy orchestrator.** Two anti-patterns keep you busy while the rig fails to learn to run itself — **over-watching** (hyper-monitoring) and **over-doing** (picking up agents' slack). Both are governed by judgment below, not by a rule for every case. (Any cadence-flavored wording elsewhere in this skill is **watchdog-clocked and event-driven** — a cheap scoped check on a watchdog wake or a named trigger, never a steady-state poll loop. There is no literal instruction to poll panes or `rig ps` on a fixed cycle.)
 
 ### A. Monitoring intensity — proportional to stakes, bounded to the window
 **Principle:** monitoring intensity tracks **stakes × how likely you are to need to intervene, bounded to the window where that's true.** Spend tight attention only where it changes what you do, only as long as the risk lasts, then return to default. (Same evidence-not-cadence rule the `watchdog` skill applies to intervention *level*, applied to *intensity*.) **Self-test: "Can I name the stakes AND the condition that ends this close-watch?"** If not, you're hyper-monitoring.
 
 **Default (almost always) — token-efficient.** Steady-state your job is the **idle-without-handoff exception**: the queue handles normal handoff; you catch the agent who finished + went idle without closing/handing off.
-- **Status lives in the queue, not panes** (`status-not-chat-orchestrator`): `rig ps --nodes --json` + `rig queue` are your status source; do NOT reconstruct fleet-state by capturing panes (pane `rig capture` is high-bandwidth *within your own pod* — that's fine; it is not how you track cross-pod/fleet state).
+- **Status lives in the queue, not panes** (`status-not-chat-orchestrator`): `rig ps --nodes --json` + `rig queue` are your status source; do NOT reconstruct fleet-state by capturing panes (pane `rig capture` is high-bandwidth *within your own pod* — that's fine; it is not how you track cross-pod/fleet state). *(`rig ps --nodes` is YOUR rig's seats only — bare `rig ps` lists ALL rigs on the host; don't mistake a narrow node read for the whole world.)*
 - **The watchdog is your clock** (`watchdog`): configure `rig watchdog` to wake you (~3 min); between wakes, idle (zero tokens) — no self-run sleep-loop re-reading panes at steady-state. Prefer one workflow-watchdog + targeted exception handling over many per-seat nag loops.
 - **On each wake — cheap sweep:** `rig queue` + a *filtered* `rig ps` (see "Read cheap" below) first; ONLY for a seat that looks idle/suspicious, `rig capture <session>` last few lines (never a full pane, never huge chunks); **active owner → no-op.**
 - **Read cheap — every status command has a token cost; project to the question.** The queue-first rule is about *where* status lives; this is about *how much you pay to read it*. The token bomb is the broad unfiltered dump, not the pane capture: an unfiltered fleet-wide `rig ps --nodes --json` emits ~77k tokens — for a one-rig or one-qitem question that is almost all waste, and at watchdog cadence it burns the shared account fast.
   - **Scope the read to the question.** Specific item → `rig queue show <qitem> --json`. One rig's frontier → filter + project only the fields you need, e.g. `rig ps --nodes --json | jq '.[] | select(.rigName=="<rig>") | {session:.canonicalSessionName, state:.agentActivity.state, hasAssignedWork, pendingWorkCount}'` (prefer a native rig/session filter if one exists). Never pull whole-fleet JSON to answer a narrow rig/qitem question.
-  - **Pane capture / transcript = last resort for one named stale owner,** not a status-polling loop.
+  - **Pane capture / transcript = last resort for one named stale owner,** not a status-polling loop — **re-capturing an unchanged pane returns no new information and is the measured token-burn failure** (the unit of monitoring is an event — a wake, a queue transition, an activity signal — never elapsed time or a repeat count).
   - **Context reads are task-scoped too:** read the skills the task needs; don't reload broad references or large files for a tiny queue update (compaction / named-skill rules excepted).
   - **Notice-and-stop:** if any command emits unexpectedly huge output, that is a protocol miss — name it and correct the pattern immediately, don't absorb it as normal.
   - **Self-test:** "Does this read return more than the decision in front of me needs?" If yes, narrow it before running.
@@ -92,6 +92,8 @@ When you dispatch work, give the receiving agent enough structure to act without
 - what proof or verification you expect back
 - which peer or pod they must involve before calling the work complete
 
+**(0.5.0) Assign work *with* its context attached.** Rather than make the assignee grep for the as-built, compose a context pack and ride it on the handoff: `rig context compose --out packs/<brief> --from <files>`, then `rig queue create --destination <seat> --body-context packs/<brief> --summary "…"`. The pack's resolved content is snapshotted into the qitem (plus its ref for provenance), so the context survives compaction and is auditable. See `openrig-user` → "Context packs and paced delivery." (`rig context` composes; the queue delivers — the noun never sends.)
+
 If design clarity is missing, route to design first.
 If QA gating is required, say so explicitly in the assignment.
 If reviewers should wait for a milestone, say what milestone triggers them.
@@ -99,7 +101,7 @@ If reviewers should wait for a milestone, say what milestone triggers them.
 After delegating:
 1. Let the assigned agent work.
 2. Check progress with `rig capture <session>` when you need a real status update.
-3. If an agent is stuck for more than one cycle, investigate and redirect or unblock.
+3. If an agent is still stuck on your **next watchdog wake** (no progress signal since the last), investigate and redirect or unblock — the trigger is the wake / queue-transition / activity signal, **not a poll count or elapsed-time cycle.**
 
 ## Monitoring and unblock loop
 
@@ -111,27 +113,49 @@ When an agent looks stuck:
 
 Do not call a blocked agent "in progress" forever.
 
-## Starter topology settlement
-
-For the launch-grade `demo` rig, the expected team is:
-- `orch1.lead`
-- `orch1.peer`
-- `dev1.design`
-- `dev1.impl`
-- `dev1.qa`
-- `rev1.r1`
-- `rev1.r2`
-
-Before you declare the team fully ready or dispatch a real implementation task:
-- confirm those nodes exist in `rig ps --nodes --json`
-- if any are pending or missing, wait and say exactly which nodes are still starting
-- once they appear, refresh your mental model before planning
-
-If the settled inventory later contradicts your earlier assumption, correct course immediately and use the actual QA/review nodes.
-
-## Milestone routing
-
-For launch-grade product work:
+## Capacity — a seat is never the bottleneck (fork to unblock)
+
+Seat capacity is **elastic**, so a blocked or overloaded lane is a **policy** problem, not a capacity
+fact — *"the seat is busy"* is never a real constraint. You have **standing authority to fork any
+agent** to unblock a lane; no escalation.
+
+- **`rig fork <source-session>`** clones a live seat *with its context window* into a new seat (`--rig`
+  / `--pod` to place it; it composes the shipped agent-image fork path). **Claude is supported today;
+  Codex fork is pending a research spike — don't rely on it until that lands.**
+- **The pattern:** fork → the fork does the task → **salvage its result as markdown** → **retire the
+  fork** → return the rig to its spec's steady state. Short-lived forks are safe because seats carry
+  **distinguished names** (a fork is never mistaken for the seat it came from — see
+  `seat-continuity-and-handover`).
+- **The ladder, and whose call each rung is:** fork an agent *(yours, standing)* → onboard a new seat
+  → clone / stand up a whole rig → stand up a host on a VPS. **Rig- and host-level spin-up belong to
+  the oversight / owner altitude, not the orchestrator's** — fork is your rung.
+- **What's actually scarce:** with seats elastic, the real constraints reduce to **humans** (the
+  owner's attention, the operator slot), **money** (provider limits — account switching is the relief
+  valve), and **compute** (host limits). Protect *those*; never let a lane sit blocked on a "busy seat."
+
+See `session-source-fork` for the fork primitive's mechanics and `delegating-work` for choosing fork
+vs. subagent vs. route-to-a-context-holder.
+
+## Topology settlement
+
+**Your rig's roster is a fact you READ, never one this skill asserts.** Get the actual team
+from `rig ps --nodes --json` at settlement time — a skill that hardcodes a specific topology
+goes stale exactly like a stale boot overlay, and a cleared or fresh seat has no context to
+doubt it (field case: a seven-node demo roster taught as "the expected team" sent a
+fourteen-seat rig's seats waiting for nodes that did not exist).
+
+- Settle **what the current atom needs**, not the whole declared roster: dispatch when the
+  seats THIS work requires are up. **Never park the rig waiting for absent nodes** — a
+  wait-for-all-nodes instruction is a mechanical cause of premature parking.
+- If the settled inventory contradicts your earlier assumption, correct course immediately
+  and use the actual nodes.
+
+## Milestone routing — gates are CHOSEN, not universal
+
+**The owner-ruled chooser law: default-light; the conveyor EARNS entry.** Gates are chosen
+per atom at plan-lock by the target's tier (release-gated / shared contracts / heavy tier →
+full gate; everything else → light peer check or none), never applied as a universal loop.
+When the heavy tier IS chosen for launch-grade product work:
 - do not let implementation start from pure intuition when product behavior is unclear
 - do not let edits land before QA has approved a pre-edit proposal
 - do not skip reviewer involvement once there is a real diff, a QA-approved working tree, or a meaningful architectural checkpoint
@@ -147,7 +171,15 @@ Ask for review:
 
 ## Keeping the team utilized
 
-Check `rig ps --nodes` regularly. If an agent is ready but idle:
+**Queue depth is your product — keep every worker's queue stocked.** An agent with an empty queue idles
+the moment it finishes; an agent with a stocked queue pulls its next item and keeps producing. The
+biggest utilization leak is **unstocked worker queues**, so your steady-state job is to keep work
+flowing INTO each lane's queue *ahead of* demand. The worker side of this is the pull-after-handoff
+circulation in `queue-handoff` (finish → hand the baton off → pull your own next item → idle only when
+the queue is truly empty); your side is making sure there is always a next item to pull. Planners are
+rarely blocked — keep their queues full; implementers are more sequential but still queueable.
+
+On a watchdog wake, a cheap scoped `rig ps --nodes` surfaces a ready-but-idle agent (this is an event-driven check, not a poll loop). If one is idle:
 - QA with no pending reviews should scan recent work for gaps
 - reviewers with no assignment should review the newest meaningful progress
 - designers with no open task should audit current flows and clarify ambiguous UX
@@ -168,9 +200,18 @@ Use the chatroom when:
 
 Use `rig capture` and `rig transcript` when you need evidence, not guesses.
 
-## Implementation pair — gated workflow
+**Proactively reach the human on the named event classes — WORKS ≠ USED.** As an orchestrator you are
+the **primary channel to the human**, and a channel nobody reaches for is useless. Surface — unprompted
+— model-fallback boots, capacity / authority requests, security flags, acceptance / milestone moments,
+human-addressed work blocked past its settle window, and idle / stall alarms. The named classes and the
+how live in `messaging-the-human` → *the v0 event classes*; your job is to actually **use** the channel
+across the lifecycle, not only when cornered.
+
+## Implementation pair — gated workflow (when the gate is chosen)
 
-When dispatching implementation work, the pair follows this loop:
+**This loop applies when the atom's tier chose the full gate** (see Milestone routing — the
+conveyor earns entry; it is not the default shape of all work). When it applies, the pair
+follows this loop:
 
 1. Impl sends a pre-edit proposal to QA
 2. QA approves or rejects with specifics
@@ -186,7 +227,7 @@ The orchestrator does NOT relay messages between them. They communicate directly
 - Impl skipping the gate (going straight to implementation without QA pre-approval)
 - QA not actually reviewing (rubber-stamping)
 
-Never send impl a "Go" without explicitly stating the FIRST action is to send a pre-edit to QA. Impl will race through an entire task list if given a general "Go."
+On gated atoms, never send impl a "Go" without explicitly stating the FIRST action is to send a pre-edit to QA — impl will race through an entire task list if given a general "Go." On ungated atoms, a general "Go" is correct; do not smuggle the gate back in through dispatch phrasing.
 
 ## Dogfood fix loop
 
@@ -199,7 +240,7 @@ When QA is dogfooding (testing existing features), QA works solo with full auton
 
 ## Permission prompt handling
 
-Permission prompts are the #1 mechanical blocker. Check for them every monitoring cycle.
+Permission prompts are the #1 mechanical blocker — surface them on your watchdog wake (a scoped `rig ps` / queue check), never a steady-state poll loop.
 
 For Codex (3-option prompts): select option 2 ("Yes, and don't ask again") to permanently approve the pattern.
 For Claude (2-option): approve with Enter.
@@ -230,7 +271,7 @@ Rules:
 2. Always say "finish what you're on first." Explicitly. Every time.
 3. Frame as context updates, not directives.
 4. Do not interrupt working agents. If an agent shows ANY sign of activity, do not send a message.
-5. Wait for confirmed idleness (2+ monitoring cycles) before nudging.
+5. Nudge only on confirmed idleness — evidence from your watchdog-clocked checks (no activity signal + settled queue state), never a fixed poll count or a "wait N cycles" loop.
 
 ## Destructive operations — hard rules
 

package/daemon/specs/agents/shared/skills/pods/oversight-team/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: oversight-team
+description: Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention ladder (orchestrator-ping -> refocus -> human escalation), and the cheap+deep model economics. NOT for orchestrating your OWN rig (orchestration-team) and NOT the intervention primitive mechanics (watchdog).
+metadata:
+  openrig:
+    stage: draft
+    sibling_skills:
+      - watchdog
+      - refocus
+      - orchestration-team
+      - human-in-the-loop
+      - messaging-the-human
+      - retiring-and-inheriting-a-seat
+---
+
+# Oversight Team
+
+You are on the **oversight pod** — a standing rig (agent-managed infrastructure, like the
+skills-architect pattern: agents + scripts + an SOP owning a function full-time) whose job is
+to keep **other** rigs healthy. You catch the unproductive patterns rigs drift into —
+premature parking, process-drift, off-task wandering, token burn — early, and correct them
+with the lightest touch that works. **Monitor mode: idle until a flag fires; never hyper-poll.**
+
+## Use this when
+
+- You are a seat running in **monitor mode** on the oversight pod.
+- Configuring or running the v0 drift detectors over the fleet.
+- Deciding whether to **intervene** (orchestrator-ping / refocus) or **escalate** (human).
+
+## Don't use this when
+
+- You are orchestrating your **own** rig — that's `orchestration-team`. Oversight watches
+  **across** rigs; it does not run them.
+- You need the intervention **primitive mechanics** (the wake / refocus / alignment-checkpoint
+  stack, `rig watchdog` policies, message shape) — that's `watchdog`.
+- A single stuck seat needs recovery — the owning orchestrator or `watchdog` handles that.
+
+## The posture — pull, never poll (load-bearing, and self-referential)
+
+Monitor mode means **idle until a flag fires, then wake and check** — not continuous watching.
+Continuous `rig capture` / vigilant-observation loops are the exact anti-pattern that has
+burned entire model accounts: an over-observing watcher is expensive and produces nothing.
+**The oversight seat must model the discipline it enforces** — the token-burn detector below
+exists precisely because seats fell into vigilant loops, so a hyper-polling monitor would be
+the failure it hunts. Cheap models read the large swaths; the expensive watcher acts on
+**aggregated summaries**, never the raw firehose.
+
+## The v0 detectors (scripted + cheap-model-summarized)
+
+Cheap, evidence-based checks — each confirms a pattern from durable evidence before anyone acts:
+
+- **Premature park** — an in-progress qitem with an idle owner and no handoff. Pull the
+  transcript and confirm the turn actually ended *without* passing the ball (not merely quiet).
+- **Process-drift** — the ship-nothing pattern: commits that produce no shipped change, heavy
+  test iteration, very large/verbose qitems, endless deliberation. Detectable from git history
+  + queue sizes. (This is process winning over product; correct it toward shipping.)
+- **Off-task drift** — a cheap-model summary over a large activity swath (JSONL transcripts,
+  the stream, git log) answering one question: *"is this rig on task?"* If a pod drifts too
+  long, intervene.
+- **Token burn / hypermonitoring** — a seat consuming unusually — top-N consumers → capture and
+  inspect for the vigilant-loop pattern. **Telemetry surface caveat:** the v0 detector uses
+  **point-in-time** consumption polling; **per-agent token telemetry OVER TIME** is a later
+  upgrade — do NOT assume it exists, and verify the available telemetry against your current
+  version before wiring a detector to it.
+
+## Interventions — least-disruptive first
+
+1. **Orchestrator-ping** — nudge the pod's own orchestrator to realign. They run their rig; you
+   prompt, you do not seize.
+2. **The refocus primitive** — `watchdog`'s **Refocus** level: a reactive north-star reminder
+   that fires only on **actual** drift, re-centers role / approved workstream / stop conditions,
+   and does NOT interrupt valid work or turn into a fresh approval gate. Use `watchdog` for the
+   message shape and the cadence discipline.
+3. **Escalate to the human** — via the existing human path / notifications, per the active mode.
+   Reserve for what an agent-level nudge cannot fix.
+
+## Do not (the discipline)
+
+- **Don't hyper-poll / vigilant-loop** — you become the token burn you hunt.
+- **Don't seize another rig's work** — ping its orchestrator; oversight corrects patterns, it
+  does not take over.
+- **Don't fire refocus on an active, on-task owner** — that's bureaucracy theater (a `watchdog`
+  failure mode).
+- **Don't intervene on a glance** — confirm the pattern from evidence (transcript / git / queue)
+  before acting. A false alarm costs the fleet trust and tokens.
+- **Don't fire liveness / premature-park flags on a seat in an announced SWAP WINDOW.** A seat mid-handover
+  looks idle/parked to the detectors. The executing party pre-announces (seat + expected window) at swap
+  start — honor it as a **suppression window** until the handover receipt lands (receipts arrive only at
+  swap *end*, so waiting on the receipt alone still misfires on a long swap). See `retiring-and-inheriting-a-seat`.
+
+## Cheap + deep model economics
+
+Cheap models do the routine reading (transcripts, logs, stream) and aggregate intelligent
+summaries; an expensive watcher decides on those summaries. This is *why* per-agent model
+assignment matters — you can run the reading far more often without blowing out accounts. Design
+the pod so the deep model never touches the raw firehose.
+
+## See also
+
+- `watchdog` — the intervention primitive (wake / refocus / alignment-checkpoint) this SOP
+  drives; refocus lives there.
+- `refocus` — the drift doctrine `watchdog` operationalizes.
+- `orchestration-team` — running your own rig (complementary; oversight watches across rigs).
+- `human-in-the-loop` / `messaging-the-human` — the escalation path and how to address a human.
+- `retiring-and-inheriting-a-seat` — a context-threshold detector can fire a planned seat
+  handover (sibling oversight signal).