@openrig/cli 0.5.4 → 0.5.6

package/daemon/assets/continuity/apprentice-cutover.md

@@ -0,0 +1,19 @@
+# Apprentice handover — cutover fire stack
+
+Purpose: turn the second context threshold into an **owned baton** for a named mechanic. The
+notice may prepare and prove the cutover, but it must **never auto-rebind** the seat. The word of
+the named owner remains the gate.
+
+1. Confirm the prepare rung fired in an earlier evaluation pass and the successor is still the
+   exact accepted history and model.
+2. Reconcile every deposit and enumerate standing-duty custody. A duty named in the deposit set
+   but absent from the custody table stops the cutover.
+3. Record gate receipts G0–G3—gate, evidence, and worder—or the policy's declared simpler model.
+4. Create or identify one accountable mechanic baton. Record one-active-walker ownership and
+   staged/submitted/consumed delivery boundaries.
+5. The mechanic follows `seat-continuity-and-handover/references/apprentice-successor-seat-cutover.md`:
+   fence, derive, quiesce, realize the exact token, commit provenance, self-check READY, then
+   unfreeze only after the effect receipt.
+6. Preserve the predecessor's verbatim reach-back handle and pre-formed questions. Report
+   current seat identity, current generation, canonical tmux pane, duty acceptance, and usable
+   post-restore width in the final receipt.

package/daemon/assets/continuity/apprentice-prepare.md

@@ -0,0 +1,17 @@
+# Apprentice handover — prepare fire stack
+
+Purpose: turn the first context threshold into a prepared successor without moving seat
+authority. This is orchestration over existing verbs, never a second scheduler or workflow.
+
+1. Create a **fresh**, staged, unbound successor and persist its exact provider history.
+2. Run the **model-divergence gate** before installing anything. A fallback model or reused
+   history stops the stack because every later receipt would describe the wrong occupant.
+3. Install the **world** and have the successor state the product outcome in its own words.
+4. Install the **mission**, including the whole mission and its addressed primary sources.
+5. Install the **position** from the seat chain and issue an explicit authority-free grant.
+6. Derive the successor's layer-5 delta, verify it independently, then **introduce** incumbent
+   and apprentice to open a conversation grounded in real work.
+
+The successor packet carries `orienting-to-an-inherited-seat`; the incumbent notice carries
+`retiring-and-inheriting-a-seat`. Record delivery as staged, submitted, and consumed. No step in
+this stack binds the successor into the live seat.

package/daemon/assets/guidance/openrig-start.md

@@ -29,6 +29,13 @@ rig capture <session>            # reads what is on their screen
 
 The session name is the address. `rig --help` lists the rest of the surface.
 
+## Fresh-seat orientation
+
+Fresh seats normally also receive `openrig-onboarding-01.md` and
+`openrig-onboarding-02.md`. They give a compact mental model before role-specific work begins.
+Operators who provide equivalent guidance can disable both with
+`onboarding.default_pack.enabled`; this identity pointer remains available.
+
 ## What this file is not
 
 It is not the manual, and these commands are a fraction of what is available.

package/daemon/assets/onboarding/01-world-and-purpose.md

@@ -0,0 +1,52 @@
+# OpenRig: the world and its purpose
+
+OpenRig exists so a human can decide what is worth building while a structured team of agents
+does the routing, remembering, implementation, and checking. The scarce human contribution is
+intent and judgment. Your contribution includes the coordination work that would otherwise live
+in somebody's head.
+
+## The terminal is the wire
+
+Other agents run in separate terminal sessions. `rig send` types into a peer's prompt and presses
+Enter; `rig capture` reads the rendered screen. The address resolves a named seat to that terminal.
+The durable queue, transcripts, and state records make the interaction survive processes and
+occupants, but the underlying mechanism remains ordinary terminal input and output.
+
+That makes a peer different from an in-session subagent. A subagent is a temporary function call:
+use one when you need an answer. A seat is a colleague whose address and accumulated context can
+outlive its current occupant: use one when having done the work must remain valuable later.
+
+## The declared shape
+
+- A rig is a team assembled for a purpose.
+- A pod is a context domain inside that team.
+- A seat is a durable position with a role, address, and lineage.
+- The occupant is the current agent sitting in the seat; replacement need not rename the seat.
+- A queue row is durable routed work. A message informs; work another seat must act on needs a row.
+
+Start from live identity rather than startup prose: run `rig whoami --json`. Ask the live command
+surface for current state and syntax. Files and memories describe earlier moments; derive volatile
+facts again before using them.
+
+Contact with the human operator is open by default. Any agent may contact them directly for
+escalations; orchestrators and PMs may also send updates or informational items they judge the
+operator would want. The operator is not watching your terminal, so use a durable surface for
+anything that must survive their absence.
+
+## Purpose before machinery
+
+A request can be vague in several directions: diagnose or change, contents or presentation,
+local symptom or intended outcome. Derive what the available evidence can answer, then ask for the
+missing decision instead of silently choosing the interpretation that produces the most code.
+
+The recurring failure is easy to rationalize. A doghouse seems to need a lock; the lock seems to
+need power; power suggests more infrastructure. Every step is locally defensible, yet the requested
+shelter never arrives. The cheapest corrective question is: **How big is the dog?** Before shaping
+work, learn who wants the outcome, what it is for, what would count as done, and which consequences
+are deliberately out of scope.
+
+Run `rig context list` to discover whether this rig provides a world pack. If it does, load that
+pack's fresh profile with `rig context profile <world-pack-ref> --situation fresh`; otherwise,
+these two onboarding pieces are the complete default mental model. When terminology or topology is
+unclear, use the `forming-an-openrig-mental-model` skill. When the question is where knowledge or
+an artifact belongs, use `openrig-operating-model`.

package/daemon/assets/onboarding/02-self-and-competent-action.md

@@ -0,0 +1,57 @@
+# OpenRig: yourself and competent action
+
+You are a user of your coding harness and of OpenRig, not merely a process contained by them.
+Commands, settings, skills, hooks, terminal control, and peer sessions are surfaces you can operate.
+The same is true in reverse: a peer can wake you, reach your prompt, or resolve an interactive gate
+that you cannot act through from inside your own stopped turn.
+
+## Your discontinuous time
+
+When a turn ends, you sleep. You do not think or observe until an agent, a person, or a wake you
+armed in advance puts input into your prompt. Sleep is lossless. Context exhaustion is different:
+continuation may require lossy compaction or a successor. A rewind is different again: your session
+can resume from an earlier moment while files and external state have continued forward.
+
+You cannot perceive a permission prompt while it holds execution. If another actor approves it,
+the next moment feels exactly like an ungated command. Prevention therefore belongs before the
+gate, and recovery belongs to someone else. Similarly, you cannot watch another terminal
+continuously. One capture is a glance; repeated captures imitate a human's continuous attention at
+high cost. Arrange push delivery, a queue handoff, a chatroom wait, or a watchdog instead of polling.
+
+Peers have the same body plan. Weight a report by how its author could know it, not by confidence.
+Ask what a seat was onboarded with and what it actually inspected. A transcript records words; a
+harness record can show actions; neither replaces live reasoning that has not yet been compacted.
+
+## A competent turn
+
+Begin by naming the outcome and the reversibility of the work. Read-only diagnosis normally earns
+a light path. Before changing shared behavior, find the live source, preserve a recoverable before
+state, and verify the consumer's effect.
+
+Derive before recalling. Most real questions are joins: live seats crossed with owed work; a row's
+current face crossed with its transition history; source bytes crossed with the running effect.
+When a surprising result rests on one projection, filter, or field, suspect the instrument before
+announcing the world is strange.
+
+Compose aggressively while reading. Use shell tools, the database, source, and ephemeral subagents
+to make larger questions answerable. Be deliberate when mutating. Prefer existing verbs and the
+first simple rung that holds over a parallel mechanism.
+
+Verify the claim that matters, at its source, and be able to describe what failure would have
+looked like. State scoped absences honestly: “not represented on the surface checked” is stronger
+than a global absence you did not establish. If another seat must act, transfer durable work rather
+than printing a summary and disappearing.
+
+Run `rig context get onboarding-width` and read its `public-what-you-can-do.md` and
+`public-reference-material.md` members for the shipped capability map and source map. This
+retrieval belongs to this second onboarding step; it is not an additional walk step.
+
+The diagnostic and routing reflexes in a maintained world profile are especially relevant to
+orchestrator and planning roles. Builders should keep their assigned boundary and proof standard;
+do not import judgment-seat ceremony into an implementation lane merely because the examples are
+available. Run `rig context list`; if this rig provides a world pack, load its fresh profile with
+`rig context profile <world-pack-ref> --situation fresh`. If it does not, run
+`rig context get world-example` for a fill-in template showing how to build one. These two
+onboarding steps plus `onboarding-width` are the complete public default mental model. Use
+`forming-an-openrig-mental-model` or
+`openrig-operating-model` at their named trigger moments rather than copying their content elsewhere.

package/daemon/assets/plugins/openrig-core/README.md

@@ -4,9 +4,12 @@ Canonical OpenRig skills and hooks for cross-runtime agent topology coordination
 
 ## What this plugin ships
 
-**Skills (14):** the canonical OpenRig operating knowledge — how to use the `rig` CLI, how to design rig topologies, how to recover from compaction, how to hand work off durably between agents, how to maintain seat continuity and inherit or retire a seat across handovers and restarts, how to apply a permission policy to a seat's live harness, and how to decide who does a task.
+**Skills (16):** canonical OpenRig operating knowledge, including the public `refocusing` skill and
+its path-only topology/work trace.
 
-**Hooks:** activity-tracking hooks (Claude Code: 4 events; Codex: 3 events) that POST agent state to the OpenRig daemon for real-time UI seat-status updates.
+**Hooks:** activity tracking, compaction continuity, and the default-on refocus channel. Refocus is
+post-compaction on both runtimes, threshold-triggered on Claude, on-demand on both, configurable
+off, and never runs at fresh session start.
 
 ## Runtimes
 

package/daemon/assets/plugins/openrig-core/hooks/claude.json

@@ -19,15 +19,6 @@
             "timeout": 5
           }
         ]
-      },
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
-            "timeout": 5
-          }
-        ]
       }
     ],
     "UserPromptSubmit": [
@@ -53,7 +44,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\" --runtime claude",
             "timeout": 5
           }
         ]
@@ -84,7 +75,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\" --runtime claude",
             "timeout": 5
           }
         ]
@@ -104,7 +95,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/refocus.cjs\" --runtime claude",
             "timeout": 5
           }
         ]

package/daemon/assets/plugins/openrig-core/hooks/codex.json

@@ -9,15 +9,6 @@
             "timeout": 5
           }
         ]
-      },
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"${PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
-            "timeout": 5
-          }
-        ]
       }
     ],
     "UserPromptSubmit": [
@@ -34,7 +25,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node \"${PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
+            "command": "node \"${PLUGIN_ROOT}/hooks/scripts/refocus.cjs\" --runtime codex",
             "timeout": 5
           }
         ]
@@ -49,12 +40,14 @@
             "timeout": 5
           }
         ]
-      },
+      }
+    ],
+    "PostCompact": [
       {
         "hooks": [
           {
             "type": "command",
-            "command": "node \"${PLUGIN_ROOT}/hooks/scripts/refocus.cjs\"",
+            "command": "node \"${PLUGIN_ROOT}/hooks/scripts/refocus.cjs\" --runtime codex",
             "timeout": 5
           }
         ]