@openrig/cli 0.6.9 → 0.6.10

package/daemon/context-packs/reference/whats-new.md

@@ -1,91 +1,167 @@
-# What changed in OpenRig 0.6.9
+# What changed in OpenRig 0.6.10
 
-This note is for an agent on an install that was just upgraded to 0.6.9. It lists only what behaves differently from
-0.6.8 and what to do about it. For everything OpenRig can do, read the capability map:
+This note is for an agent on an install that was just upgraded to 0.6.10. It lists only what behaves differently from
+0.6.9 and what to do about it. For everything OpenRig can do, read the capability map:
 `rig context get onboarding-width/public-what-you-can-do.md`. Each release replaces this file, so
 `rig context get reference/whats-new.md` describes the installed version once the upgraded daemon is running. Without
 a running daemon, read `$OPENRIG_HOME/reference/whats-new.md`. The daemon refreshes that copy when it starts, so right
 after an upgrade it can still hold the previous version's note.
 
+## After the upgrade
+
+- **Restart the daemon** (`rig daemon stop`, then `rig daemon start`). Two migrations run on the first start: `099`
+  adds one partial index to the queue table, and `101` adds four empty columns to `sessions`. Neither changes existing
+  data. There is no migration `100`. The bundled openrig-core plugin goes from 0.1.8 to 0.1.9.
+
+## Output that changed shape
+
+- **`rig capture --lines N` is the last N lines,** after blank rows at the bottom are dropped. When earlier lines are
+  cut, stderr says `[rig capture: <session>: N earlier lines not shown; last M shown]`. In `--json`, `lines` is then
+  the count returned, and `requestedLines` and `omittedLines` are new (per seat under `--rig` or `--pod`). For the old
+  output, N history lines plus the whole pane, add `--history-plus-pane`; it keeps the old JSON too, without
+  `requestedLines` or `omittedLines`. Without `--lines`, or with a non-numeric or zero `--lines`, nothing changed. A
+  short capture doesn't prove a seat is idle.
+- **Compact `rig queue list` rows carry `summary`,** and so do `overdue` and `undelivered`. The fields they leave out
+  (`body`, `evidenceRef`, `humanDetail`, `waiting`, `chainOfRecord`, `replyTo`, `humanQuestions`, `humanAnswers`) are
+  now absent, not `null` or `""`, and `fieldsElided` names them. A filter that tested those fields for null must test
+  for presence. Read a full row with `rig queue show <id> --full --json`.
+- **`lastNudgeResult` reads `claimed`** on a claimed row whose wake was recorded as `delivered-ack-pending` or
+  `indeterminate:…`. The recorded value is unchanged and shows in the new `lastNudgeWireResult`; unclaiming brings it
+  back. `claimed` is never promoted to `verified`.
+- **`rig chatroom history` returns the newest messages** when you give neither `--after` nor `--since`, still listed
+  oldest first. Before, a room longer than the limit returned its oldest messages. `--after` and `--since` still page
+  forward from that point, and `rig chatroom wait` is unchanged.
+
+## Seats and restore
+
+- **`rig launch <rigId> <seat>` no longer calls an exited agent running.** When a seat's kept pane is at an idle shell,
+  the launch returns `attention_required` (HTTP 409, exit 1) with `Session alive, agent not running for '<seat>'` and
+  the ways back: resume it with `--snapshot-id <id>` when a snapshot can, `rig seat launch <session> --fresh --stop`, or
+  restart the agent in the pane. The pane and its history are kept. This covers Claude Code, Codex, Pi and OMP seats.
+- **`rig up <rig> --existing` puts back the guidance `rig down` removed.** Before a resumed seat starts, the missing
+  OpenRig managed blocks go back into the rig's Claude file (`CLAUDE.md`, or `CLAUDE.local.md`) or `AGENTS.md` for
+  Codex. Existing blocks and the person's own text are untouched, and nothing is sent to the conversation. The
+  warnings say `Restore guidance: <seat>: put back missing blocks …`. A seat still missing a block keeps running, its
+  node lists `guidanceGaps`, the rig reads `partially_restored` instead of `fully_restored`, and `rig up` exits 1.
+- **A resumed Claude seat whose session ID changed can prove.** When Claude continues `--resume T1` under a new ID T2,
+  and the first SessionStart hook from the process OpenRig launched reports `source: "resume"`, OpenRig records T2. The
+  seat restores as `resumed`, `rig seat clear-attention` can clear it, and sends stop warning that the launch identity
+  differs. Resume commands now start with `OPENRIG_RESUME_LAUNCH='<T1>'`. It needs openrig-core 0.1.9; `/clear`, an
+  in-process `/resume`, or a hand-started process still keep the refusal.
+- **A restore no longer proves a seat from a launcher's token** when the launcher isn't Claude and the Claude it
+  started names a different conversation. That seat reads `mismatch` and the restore returns `attention_required`.
+- **A seat whose tmux session is confirmed gone reads `detached`,** with activity `unknown` and reason
+  `session_missing`. `rig ps --nodes` shows `tmux session missing; restore or relaunch the seat`, `rig seat status`
+  prints a `Reason:` line, and `--full --json` adds `storedSessionStatus`. The stored status isn't rewritten.
+- **A Codex seat at its usage limit reads `unknown` with reason `usage_limit`,** not idle, when its screen ends with
+  the `■ You've hit your usage limit` banner. For a seat bound to a known Codex account, `rig provider signals` can show
+  a provider-event signal for that account that allows a switch decision.
+- **`rig add <rig> …` takes the rig's name as well as its ID.** A name two active rigs share is refused with
+  `rig_ambiguous` and the candidates. `rig launch` still takes an ID only.
+- **`rig start` says why it skipped an existing kernel:** `Kernel auto-boot skipped (kernel rig already managed).` and,
+  if its seats aren't running, `rig up kernel --existing`.
+
+## Sends and wakes
+
+- **Codex seats behind a launcher receive sends.** When a seat's `codex` is a launcher that starts Codex as a child,
+  `rig send` and queue wakes used to refuse with "reports sh as the foreground command". The deepest `codex` on one
+  process chain now counts as the seat. Codex processes on separate branches, or naming different conversations, are
+  still refused.
+- **Claude's faint suggested prompt isn't a person's draft.** A send to an idle Claude seat whose empty input box shows
+  only that suggestion is no longer refused as `prompt_draft`. OpenRig takes one styled capture to tell; real typed or
+  pasted text is still refused, and a suggestion that wraps onto a second row still reads as a draft.
+- **`rig queue create --verify` reports a seat's wake and claim.** For an agent destination it returns as soon as a
+  wake result or a claim is recorded, bounded at 30 seconds, with `receiptSource: "terminal"`, `outcome`, `wakeResult`
+  and `claim {observed, claimedAt, pickup}`. An unconfirmed receipt is not a failed handoff. See the known gap below
+  for a row the seat already claimed.
+- **Keep agent-to-agent escalations off the person's Slack (off by default).** `rig config set queue.wake_human_rung
+  explicit-only` (or `OPENRIG_QUEUE_WAKE_HUMAN_RUNG`) stops the wake ladder's last step at `rig view show escalations`
+  unless the row is addressed to a person: an `@external` address or a registered human. A seat stuck at a prompt only
+  a person can clear still reaches one, and an unreadable human registry posts everything. The default, `always`,
+  changes nothing.
+
 ## Slack
 
-- **A typed reply to a decision with structured questions is kept.** It's recorded on the row in `humanAnswers` as a
-  tagged entry (`kind: "typed-reply"`), placed under the first unanswered question, with the count of questions still
-  unanswered. A clicked answer is still the option's ID. Typed text that matches an option's ID is never read as clicking
-  it. The decision still closes, and closing doesn't mean approval: read the reply and its placement before acting. The
-  `messaging-the-human` skill says how.
-- **`rig slack status` shows the inbound retry backlog:** how many retained records for inbound messages, reactions
-  and click answers are waiting to be retried, kept across restarts. This counts records, not distinct messages.
-  If the records can't be read, the line says the count is unknown and why; it never reads as an empty backlog.
-- **An alert retried after its row closed isn't posted.** A Slack post that failed is kept and retried when the gateway
-  next starts. If the row has left the active states by then, the alert is dropped and the row records
-  `slack-owner-notification-dropped … reason=row-not-active`. Alerts for rows still open, decision-resolved notices and
-  digests still post. `rig slack enable` says how many earlier undelivered posts wait to be retried.
-- **"Connected" is no longer the only word about the Slack connection.** OpenRig now notices a connection that stays
-  open while Slack stops delivering events to it, and replaces it: a new connection opens first, then the old one
-  closes. Two signals catch it, each counted only once the connection has shown it: Slack's server pings stopping for
-  30 seconds, and two of OpenRig's own posts not coming back as events within a minute. Automatic replacements are at
-  most one every 5 minutes; Slack's own refresh requests are exempt.
-- **Read delivery beside the socket state.** `rig slack status` adds a `Delivery:` line (`delivering`, `not yet
-  confirmed`, `events missing since …`, `no server pings since …`, or Socket Mode disabled), the last automatic
-  reconnect and why, a held-back reconnect and until when, and Slack's connection count when it's more than ours. The
-  connections view shows `connected; delivering` or `connected; delivery not yet confirmed`. Report "not yet
-  confirmed" as that, never as working.
-
-## Sends and waits
-
-- **A cross-host send that may have arrived reads as unconfirmed, not failed.** `rig send <session> --host <id>` to an
-  http-registered host now has a 30-second request budget, plus any `--wait-for-idle` time. When the answer doesn't come back, or the connection drops after the
-  request went out, the send exits 1 with `failedStep: "remote-outcome-unknown"` and "Delivery UNCONFIRMED". **Check the
-  target with `rig capture <session> --host <id>` before any resend**; a blind resend can deliver twice. Only a host
-  that was never reached reads as unreachable.
-- **`rig chatroom wait` keeps waiting through a slow or restarting daemon.** Poll timeouts, connection refusals, and
-  reset or closed connections are retried until your `--timeout`; the first failure in a run prints a line on stderr.
-  Other errors, including an error answer from the daemon such as a removed rig, still end the wait. If the last
-  recorded poll failure remains unresolved at the deadline, the timeout says new messages may have arrived unseen.
-
-## Kernel status
-
-- **A kernel that recovered from a failed start reads ready.** When every declared kernel seat reports ready, for
-  example after `rig seat continue`, `rig status` says so and adds an indented line naming the earlier failure and
-  when it happened. `GET /api/kernel/status` returns that as `last_boot_failure`. The kernel's agent list shows each
-  seat once, with its runtime.
-
-## Scope approval
-
-- **`rig scope <tier> approve --workspace <path>` stamps the work tree you named.** Before, it reported success while
-  the stamp landed in the daemon's own work tree. A named workspace with no `missions/` folder is now refused instead
-  of falling back to the configured one. The approval record names the root it wrote under.
-
-## Claude seats on NixOS
-
-- **A Claude Code installed from nixpkgs is recognised as the seat's runtime,** so its seats read `running` and sends
-  no longer warn that the runtime couldn't be established. A seat that still carries an attention marker from an
-  earlier failed launch keeps it: clear it with `rig seat clear-attention <seat>`.
-
-## A correction to the 0.6.8 note
-
-- **`rig launch` takes a rig ID, not a rig name.** The 0.6.8 note wrote `rig launch <rig> <seat> --plan`. Read the ID
-  from `rig ps --json`; a name gives `rig_not_found`.
+- **A decision click that isn't recorded gets one reply in the thread** saying why: the clicker isn't registered, the
+  decision was sent to someone else or is no longer waiting, the button no longer matches, or OpenRig can't find the
+  decision. Where it helps, the reply asks for an answer in words. A recorded click still gets its usual reply, and a
+  redelivered click gets no second one. It's best effort and needs the bot token. A successful press doesn't exercise
+  these replies.
+
+## Terminals and attach
+
+- **Attach commands name the daemon's tmux server.** When the daemon was started inside tmux on a non-default socket,
+  every attach command OpenRig prints carries `-L <name>` or `-S <path>`, including `tmuxAttachCommand` in `rig ps
+  --json`. From inside tmux, run it as `env -u TMUX <tmuxAttachCommand>`. On the default server nothing changed.
+- **When a caller of the daemon's terminal API names no provider, the daemon uses cmux if Herdr isn't available** and
+  cmux is, and says so. A named `--provider` is used as named. `rig terminal open` without `--provider`, and the TUI's
+  "Open terminals", open Herdr, or plain tmux when Herdr is missing, never cmux. The TUI's preview now asks for the
+  same provider as the window it opens, so it isn't refused when cmux is running.
+- **A tmux started inside a Herdr pane is recognised** by Herdr's markers (`HERDR_ENV`, `HERDR_PANE_ID`,
+  `HERDR_SOCKET_PATH`), so `rig terminal open --window` opens in that Herdr.
+
+## Setup
+
+- **`rig setup --providers claude|codex|both`** (or a comma list) sets which harnesses it installs and checks. One not
+  chosen reads `skipped` with `Not selected: …`, never failed. Without the flag, setup is unchanged. `rig doctor` still
+  checks both.
+- **A first `rig daemon start` after a timed-out probe goes ahead when the port is free,** as on WSL2. A port that's
+  really held is refused with `Address already in use (EADDRINUSE)` and the `--port` advice.
+
+## Teams
+
+- **Starter and factory teams run their own first steps and checks without stopping for approval** where they can:
+  plain `rig` commands, the file tool instead of a heredoc, the project's test command first. Their leads read the goal
+  from `rig queue show <id> --full`.
+- **The operator says what a team launch changes in the person's folder before asking** (`CLAUDE.md`, skills,
+  `.mcp.json`, `.openrig/`, and an accept-edits `.claude/settings.local.json`), and offers a separate copy such as a git
+  worktree. When a seat shows `needs_input`, the operator or lead tells the person which seat, what it asks, and its
+  attach command.
+
+## Smaller fixes
+
+- `_` and `%` in a `rig view show <lens> --rig <name>` rig name are no longer wildcards, in all seven lenses that
+  filter by rig.
+- `rig ask` matches chat keywords such as `config.json` or `C++` literally.
+- `rig heartbeat` reads CRLF queue files and reads a zone-less proof timestamp as UTC when picking the latest.
+- `rig usage top` reads every sample in its window; `rig usage top|series --json` prints the daemon's error as JSON.
+- A `?limit=` that isn't a number returns 400, not 500.
+- `rig workflow instantiate` and `project` print the instance and packet the daemon returned.
+- `rig transcript --tail` keeps a line ending in `%` and drops a repeated prompt.
+- `--json` after `--` no longer turns an error into JSON; `rig env` prints the daemon's error.
+- A file read over 1 MiB ends at a whole UTF-8 character, and `truncatedAtBytes` says where.
+- The TUI counts CR+LF as one Enter, keeps an emoji whole at a wrap, pages Local reading directories by 10, and skips
+  fenced examples when opening a file at a heading.
+- Scope progress rows go only under a matching `##` heading, frontmatter updates stay inside the exact `---`
+  delimiters, a capability delta expires only with a readable successor file, and fenced examples no longer count as
+  slice sections or progress tasks.
+- `rig package install` looks for a guidance block's closing marker only after its opening one.
+- A Codex seat keeps its last context reading across quota-only usage records, and a fresh Codex launch keeps git
+  metadata paths that end in whitespace.
 
 ## What to stop doing
 
-- **Stop resending a cross-host message after a timeout.** Check the target first; the first send may have arrived.
-- **Stop restarting a kernel whose status read `bootstrap_failed` after its seats recovered.** Read `rig status`
-  again on 0.6.9; a recovered kernel reads ready.
-- **Stop passing a rig's name to `rig launch`.** Pass its ID.
+- **Stop reading "already running" from `rig launch` as healthy** for a seat whose agent may have exited; 0.6.10 says
+  `attention_required`.
+- **Stop reading `rig capture --lines N` as N history lines plus the pane.** Add `--history-plus-pane` for that.
+- **Stop testing compact queue rows for null fields.** They're absent; check `fieldsElided`.
+- **Stop attaching to the default tmux server** when the printed command names `-L` or `-S`.
 
-## Known gaps in 0.6.9
+## Known gaps in 0.6.10
 
-- **The latest first-install check used 0.6.8 on a fresh Mac account in Terminal,** with assistance to install the
-  candidate. It reached setup, the kernel window and a team plan; team launch and work weren't exercised.
-  Linux and Windows first installs remain unchecked in the evidence behind this note.
+- **`rig queue create --verify` can report `outcome: "indeterminate"` for a row the seat already claimed,** with
+  "Terminal receipt unconfirmed (claimed)." Read `claim` for pickup: neither the claim nor this outcome shows the
+  message was displayed or read. It isn't a failed handoff, so don't re-run the create.
+- **The latest first-install check used 0.6.9 on Linux only.** macOS was last checked with 0.6.8, and native Windows
+  hasn't been checked.
 - **Only one selected lifecycle-help command has been checked in a live Claude session;** source and parser coverage
   is broader. If a help command still asks, report it.
 - **Codex team seats aren't asked before lifecycle commands yet.**
 - **The send gate trusts the most recently recorded hook.** If hooks are recorded out of order, it can hold a send for
   a question that's already answered, or miss one that's waiting. `rig capture` shows the real screen.
 - **A Codex seat whose permission request was approved automatically can still read "needs input".**
-- **A launched team still writes its skills into its working folder.**
+- **A launched team still writes into its working folder;** the operator now says what changes before you agree.
 - **After a restart, `rig status` shows `Kernel: skipped` whatever the kernel seats' state.** Read them with
   `rig ps --nodes --rig kernel --full`.
+- **`rig tui --shared` still attaches on the default tmux server,** so it can't find the dashboard when the daemon runs
+  on a non-default tmux socket. Use `rig tui` there instead.

package/daemon/context-packs/skills/agent-operated-software/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "agent-operated-software"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles."
 files:

package/daemon/context-packs/skills/agent-operated-workflows/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "agent-operated-workflows"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop."
 files:

package/daemon/context-packs/skills/applying-a-permission-policy/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "applying-a-permission-policy"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy."
 files:

package/daemon/context-packs/skills/claude-compaction-restore/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "claude-compaction-restore"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when a Claude Code session is about to compact, has just compacted, reached its context limit, resumed after /compact, or must rebuild its working picture of a long-running seat from its own restore map, its JSONL transcript and the files it touched."
 files:

package/daemon/context-packs/skills/core/agent-starters/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "agent-starters"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance."
 files:

package/daemon/context-packs/skills/core/agent-startup-and-context-ingestion/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "agent-startup-and-context-ingestion"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages, \"rig context\" surface. Covers the 4 failure modes that make startup context fail (old rig spec misses current operating mode; current agents never told about new guidance; startup file as dumping ground; orchestrator transmits implementation without preserving product intent)."
 files:

package/daemon/context-packs/skills/core/cross-host-rig-commands/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "cross-host-rig-commands"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result."
 files:

package/daemon/context-packs/skills/core/human-in-the-loop/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "human-in-the-loop"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when classifying a slice closeout (auto-continue / human gate / park), routing a real decision to a human, or designing a human queue/dashboard surface. Treats humans as durable network participants with attention surfaces, queues, and decision records — escalation lands as a durable attention item, not a chat message. Approval is NOT required for every clean closeout; the default RSI conveyor continues unless an explicit human gate is reached."
 files:

package/daemon/context-packs/skills/core/messaging-the-human/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "messaging-the-human"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work."
 files:

package/daemon/context-packs/skills/core/openrig-architect/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-architect"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "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 (use developing-openrig); NOT for ordinary CLI operation of an existing rig (use openrig-user). Covers the full authoring lifecycle from user intent to validated, launchable rig."
 files:

package/daemon/context-packs/skills/core/openrig-cmux/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-cmux"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "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."
 files:

package/daemon/context-packs/skills/core/openrig-herdr/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-herdr"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "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 "
 files:

package/daemon/context-packs/skills/core/openrig-skills/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-skills"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when you're operating OpenRig and need the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also use when you don't know what applies or nothing is projected on cold boot."
 files:

package/daemon/context-packs/skills/core/openrig-software-factory/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-software-factory"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when a user wants a continuing software team for a real repository, or has a first OpenRig team and needs a repeatable path for reviewed work and later tasks."
 files:

package/daemon/context-packs/skills/core/openrig-upgrade/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-upgrade"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when an agent is preparing or performing an OpenRig CLI/daemon upgrade and must preserve live seats, verify each mutation, or reconcile managed plugin and skill files without overwriting local work."
 files:

package/daemon/context-packs/skills/core/rig-bundles-and-shareable-artifacts/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "rig-bundles-and-shareable-artifacts"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension boundary, or auditing a bundle for portability. Covers the 4 failure modes that prevent bundles from working anywhere but the operator's machine, and the inspect-before-install discipline."
 files:

package/daemon/context-packs/skills/core/rig-lifecycle/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "rig-lifecycle"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or trusting `rig ps` / lifecycle projections after recovery, or designing proof for a lifecycle scenario. Covers the 4 failure modes (auto-restore creates partial rig; projections report healthier than reality; provider auth treated as impl work; resume succeeds for one runtime fails another) plus the restore-honesty rule (failed resume is FAIL"
 files:

package/daemon/context-packs/skills/core/session-source-fork/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "session-source-fork"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when authoring a rig spec member or `rig expand` payload that needs to start a new managed seat from a prior runtime conversation source — `session_source: { mode: fork, ref: { kind, value } }`. v1 supports `mode: fork` with `ref.kind: native_id` for Claude and Codex. The new seat persists a NEW post-fork token; the parent token is NEVER written onto the new seat. NOT for restoring an existing seat or for artifact-backed mental-model rebuild."
 files:

package/daemon/context-packs/skills/core/specification-system/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "specification-system"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (spec instantiates topology but not workflow/mode; spec depends on local paths and fails on another host; agents modify specs as one-off files instead of preserving reusable intent; validation proves YAML shape but not whether topology can run) and the validation-vs-runtime-realization distinction."
 files:

package/daemon/context-packs/skills/core/topology-mutation-and-seat-management/SKILL.md

@@ -67,8 +67,8 @@ Write a fragment instead when a seat needs something `rig grow` does not set: an
 explicit model, a permission policy, a different agent spec or role profile, a
 per-seat runtime or working directory, or startup files. Use
 `rig expand <rig-id> <pod-fragment-path>` to add a pod, or
-`rig add <rig-id> <pod-namespace> <member-fragment-path>` to add one member to an
-existing pod.
+`rig add <rig> <pod-namespace> <member-fragment-path>` to add one member to an
+existing pod (`<rig>` is the rig id or its exact unique name).
 
 ## Don't use this when
 

package/daemon/context-packs/skills/core/topology-mutation-and-seat-management/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "topology-mutation-and-seat-management"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures."
 files:

package/daemon/context-packs/skills/core/watchdog/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "watchdog"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when configuring `rig watchdog` policies, authoring wake/refocus/alignment-checkpoint messages, or choosing the right intervention level for a stale-owner situation. The 3-level continuity-check stack (wake / refocus / alignment-checkpoint), the discipline that prevents cadence pollution and bureaucracy theater, and the artifact-pool loop-edge pattern for evidence-aware waking."
 files:

package/daemon/context-packs/skills/delegating-work/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "delegating-work"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the topology that already holds the context. The rule: how much would a blank slate have to read in to do this correctly? A lot → route to a context-holding agent; a little → subagent; unsure → a real agent or yourself. NOT the mechanics of fanning out (that's dispatching-parallel-agents / subagent-driven-development) — this is the who/whether decision, and the failure mode that makes teams a"
 files:

package/daemon/context-packs/skills/forming-an-openrig-mental-model/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "forming-an-openrig-mental-model"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when the system around you does not make sense yet: you just booted into a seat and do not know how the pieces fit; someone said rig, pod, seat, fleet, topology, or slice and you are not certain what they mean here; you are unsure what kind of rig you are in or what it is for; you do not know how skills reach you or where context comes from; or you are about to act on a guess about how OpenRig works. Gives the runtime mental model fast, so you stop guessing."
 files:

package/daemon/context-packs/skills/loading-addressable-markdown/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "loading-addressable-markdown"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when a mission, slice, dashboard, or task references Markdown as path#h2-slug or path#h2-slug/h3-slug outside the OpenRig context-pack library."
 files:

package/daemon/context-packs/skills/mission-slice-sop/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "mission-slice-sop"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC."
 files:

package/daemon/context-packs/skills/openrig-operating-model/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-operating-model"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when you do not know WHERE something belongs: you learned a lesson and are unsure which file takes it; you are about to create a new doc, folder, or convention; you are asking \"should this be a skill, a note, or a chain file?\"; you inherited a seat and want to know what SHOULD exist; or you are about to duplicate knowledge that already has a home. Also the trace-to-root: how a seat orients by reading one filename at each level from where it stands up to the fleet."
 files:

package/daemon/context-packs/skills/openrig-user/SKILL.md

@@ -1302,7 +1302,7 @@ Node-granular managed partial restore (v0.3.4+):
 ### Add a member to an existing pod — v0.3.3+
 
 ```bash
-rig add <rig-id> <pod-namespace> <member-fragment-path> [--json]
+rig add <rig> <pod-namespace> <member-fragment-path> [--json]
 ```
 
 `rig add` is the top-level verb for the `add_member` converge op. It adds a
@@ -1310,6 +1310,12 @@ single member to an existing pod from a YAML/JSON member fragment file. The
 daemon resolves the named pod, validates the member, runs preflight, and
 launches the member in place.
 
+`<rig>` is the rig id or its exact name (the `rigName` that `rig whoami --json`
+reports). A name shared by more than one rig is refused before anything is
+added, with the matching ids listed (`rig_ambiguous` under `--json`). `rig add`
+always targets the local daemon: while a remote host is selected it refuses to
+resolve a name (`remote_host_selected`); an exact local id still works.
+
 HTTP outcomes:
 - `201` — member added; per-node launch state included in the response.
 - `400` — `validation_failed` or `preflight_failed` (the fragment or its launch posture is rejected before any state change).

package/daemon/context-packs/skills/openrig-user/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "openrig-user"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when a specific `rig` command, subcommand, or flag is already known and you need its exact syntax, JSON shape, defaults, or error meaning. NOT for natural capability discovery, open-ended how-do-I questions, or choosing which OpenRig move applies."
 files:

package/daemon/context-packs/skills/orienting-to-an-inherited-seat/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "orienting-to-an-inherited-seat"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Use when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the inherit-the-seat-not-the-identity rule, treating the handover packet as testimony you verify (and refusing stale ghost prompts, and verifying your OWN identity surfaces), why a seat is a COMPOUNDING LINEAGE"
 files:

package/daemon/context-packs/skills/pm/backlog-capture/manifest.yaml

@@ -1,7 +1,7 @@
 # GENERATED by scripts/generate-context-packs.mjs — DO NOT EDIT.
 # Package-time projection of a canonical skill; regenerated every build.
 name: "backlog-capture"
-version: "0.6.9"
+version: "0.6.10"
 taxonomy: "skills"
 purpose: "Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication."
 files: