@openrig/cli 0.6.7 → 0.6.8

package/README.md

@@ -22,11 +22,11 @@ Not setting this up today? Get the next walkthrough and occasional OpenRig updat
 
 Requires Node.js 22 or 24 and tmux, on macOS or Linux. On Linux, the distribution's own Node.js can be older (Ubuntu 24.04's is 18); install a supported version with [nvm](https://github.com/nvm-sh/nvm) (`nvm install 22`) or NodeSource. On a Mac with Apple silicon, use Node.js 22 ([compatibility history](docs/releases/v0.5.15.md#known-compatibility-limitation)). On Windows, use WSL2, the Windows route OpenRig supports; native Windows isn't supported. OpenRig's automated tests don't run on WSL2 yet; see [one user's working setup](docs/reference/getting-started.md#wsl2-a-reported-working-setup). Launching a rig writes provider hooks and workspace trust settings. Before running the commands below, read [what OpenRig changes on your machine](#what-openrig-changes-on-your-machine) and back up the relevant files.
 
-**One command.** This runs OpenRig's install script from the `v0.6.7` release. It checks Node.js and npm, installs the latest published `@openrig/cli` with `npm install -g`, runs the Node.js and SQLite check, then runs `rig setup --dry-run` and `rig setup`. The first line prints that plan and changes nothing:
+**One command.** This runs OpenRig's install script from the `v0.6.8` release. It checks Node.js and npm, installs the latest published `@openrig/cli` with `npm install -g`, runs the Node.js and SQLite check, then runs `rig setup --dry-run` and `rig setup`. The first line prints that plan and changes nothing:
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.7/scripts/install.sh | sh -s -- --dry-run
-curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.7/scripts/install.sh | sh
+curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.8/scripts/install.sh | sh -s -- --dry-run
+curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.8/scripts/install.sh | sh
 ```
 
 If a provider isn't signed in yet, the last step reports `FAILED [4/4]`, and `rig setup` lists the sign-in under "Some steps need attention". If the only remaining failures are provider sign-ins, the install steps finished; sign in to each selected provider as below and continue.
@@ -107,7 +107,9 @@ recommends one of three, and fits it to the providers you have.
 
 As shipped, `starter` uses both Claude Code and Codex. With only one of them, ask
 the kernel operator to adapt it: it writes a copy of the team for your providers
-under the same name. `first-project` is starter's old name and still starts it,
+under the same name. [The naming guide](docs/reference/topology-naming.md) explains
+how their pods and roles grow and how to name your own team. `first-project` is
+starter's old name and still starts it,
 unless you already have a rig named `first-project` or `starter`: then it refuses
 and names the `rig up <name> --existing` command that brings that rig back.
 Show the selected runtime, configured model and command before launch; confirm the

package/daemon/assets/plugins/openrig-core/skills/messaging-the-human/SKILL.md

@@ -92,6 +92,12 @@ the human (a pending human decision, or a row parked on the human), since a
 reply in that thread would answer the decision. In every such case the
 `--verify` result says `threaded: false` with the reason.
 
+To answer a reply the human typed inside one of your threads, `--reply-to` the
+row their reply landed as. The update posts in that thread unless one of the
+cases above applies, and `--verify` reports it the same way. A message the
+human started at the top level of the channel has no thread yet, so the answer
+posts as a new message.
+
 A **decision** with a few clear choices can carry `--human-questions-file <path>`:
 a JSON array of 1–4 questions, each
 `{"id", "question", "options": [{"id", "label", "recommended"?}]}` with 2–4

package/daemon/context-packs/help/manifest.yaml

@@ -1,6 +1,6 @@
 # Agent help: the single troubleshooting and escalation guide (docs/reference/help.md).
 name: help
-version: "0.6.7"
+version: "0.6.8"
 taxonomy: world
 purpose: "What an agent does when its user says OpenRig isn't working: diagnose, fix within permissions, verify, and escalate to OpenRig support."
 files:

package/daemon/context-packs/onboarding-width/manifest.yaml

@@ -1,6 +1,6 @@
 # Public capability and source-map width for the default onboarding walk.
 name: onboarding-width
-version: "0.6.7"
+version: "0.6.8"
 taxonomy: world
 purpose: "The public capability map and source map referenced by the default onboarding walk."
 files:

package/daemon/context-packs/onboarding-width/public-what-you-can-do.md

@@ -11,7 +11,7 @@ not know exists.** So the point of what follows is not skill. It is recognition:
 lands, something rhymes, and you go check instead of building.
 
 Eighty-seven top-level verbs ship (capability canon refreshed through
-`capability-delta-v0.6.7`). This marker describes the pack's teaching, not publication or live
+`capability-delta-v0.6.8`). This marker describes the pack's teaching, not publication or live
 adoption. Read this once for shape, and let it make you suspicious that a thing already exists.
 Model-divergence proclamations are live product (trust them; pins use canonical
 model IDs).
@@ -157,7 +157,10 @@ unseen — which makes messages the one delivery channel that never gets skipped
   It needs the `reactions:read` scope and the `reaction_added` event (reinstall the app);
   `rig slack verify` warns when the scope is missing. A long ask is posted in numbered thread parts; one that
   still can't be posted comes back to the asking seat as a `slack-undeliverable` task. Replies
-  sent with “Also send to #channel” reach the seat like any other thread reply.
+  sent with “Also send to #channel” reach the seat like any other thread reply. A person's reply
+  inside a thread OpenRig opened is answered in that thread: answer with `rig queue create
+  --human-intent update --reply-to <the inbound reply's row>`; a top-level message is answered
+  top-level.
 
 ## Making work outlive you
 
@@ -223,7 +226,10 @@ relay is a reason to inspect the available routing, not to surrender judgment to
 
 - **`rig workflow specs`** — what can be started here, and which are shipped versus authored by
   this rig.
-- **`rig workflow validate`** — will this spec instantiate at all, before a run finds out for you.
+- **`rig workflow validate`** — will this spec instantiate at all, before a run finds out for you. A
+  step with no allowed exit that can finish it or route onward is reported as `step_cannot_finish`.
+  An allowed mapped exit is valid; in a dependency graph, `handoff` can finish a sink without a next
+  step.
 - **`rig workflow compile <mission>`** / **`instantiate-lifecycle`** — derive one executable graph
   from `project.yaml` → `mission.yaml` → `slice.yaml`, inspect it without writing, then start an
   eligible graph with an opaque replay key. Typed acceptance candidate, verdict, and evidence
@@ -314,7 +320,9 @@ fresh, since a web tool's cached copy can be older. The built-in shelf also hold
 `research`, `pm`, `secrets-manager` and `kernel`. Older names are gone: `adversarial-review`,
 `research-team` and `pm-team` became `code-review`, `research` and `pm` with no alias, and
 `first-project-claude`, `first-project-mixed`, `conveyor`, `demo`, `implementation-pair` and
-`product-team` were removed. Verify prerequisites (Node 22 or 24) and actual runtime readiness
+`product-team` were removed. When authoring a new team, read
+`docs/reference/topology-naming.md`: name the rig for its purpose, pods for domains,
+and members for their roles. Verify prerequisites (Node 22 or 24) and actual runtime readiness
 before work. The starter's Codex model `gpt-6-astra` needs a Codex newer than 0.145; when a Codex
 seat reports that, the operator offers to update Codex and restart that seat. Existing Herdr/cmux
 terminals can present the managed team through `rig terminal open`.
@@ -333,7 +341,8 @@ not have to tear one down to change it, and you rarely have to start from nothin
   best-effort snapshot, not a record of what was interrupted. With `--host`, a remote teardown
   that reports errors exits 2.
 - **`rig launch <rig> [seat]`** — one seat is down; start just that one, without disturbing the
-  rest.
+  rest. Add `--plan` to preview it first, locally or with `--host`; a plan is never sent to a
+  daemon older than 0.5.9, which would ignore it and launch.
 - **`rig seat launch <seat> --fresh --reason <why>`** — deliberately create a blank occupant for
   exactly one existing seat. It uses no resume, fork, rebuild, snapshot, or restore packet;
   siblings and durable work stay put, and unmanaged ambiguity refuses.
@@ -463,7 +472,8 @@ version, from checking the environment to a useful report to the OpenRig team.
   skill covers writing and reading the map; `claude-compact-in-place` no longer ships. After a
   managed compaction, refocus waits for the restore request, which names the `refocusing` skill
   (the daemon installs it globally); three failed refocus attempts in a row for one occupant post
-  one issue to the stream.
+  one issue to the stream. The turn boundary, restore request and read-depth audit reach a seat
+  that stays quiet after `/compact`; they don't wait for its next turn.
 - **Know what compaction costs before you reach for it.** On some runtimes what comes back has
   enough context left to believe it knows everything and not enough to actually know anything — and
   **the compacted agent is the only one who knows it happened**, while every other seat keeps
@@ -550,8 +560,12 @@ scheme, and nothing downstream can see it.
   require `--project`. World packs named in `project.yaml`'s `install.worlds`
   are listed after the System World; read each with `rig context get <ref>`.
   `context profile` and `context work-install` both accept `--runtime claude-code` (alias
-  `claude`) or `codex`; explicit invalid values refuse before projection. This does not rename
-  every other command's runtime vocabulary.
+  `claude`) or `codex`; explicit invalid values refuse before projection. This does not rename every
+  other command's runtime vocabulary. A catalog skill with uncommitted content blocks only itself:
+  it is skipped and named (`catalog_skill_skipped`, or `selected_skill_skipped` with its selector).
+  With `--runtime`, work-install reports selected skips with exit 1. It inspects by default;
+  `--apply-skills` projects the remaining clean skills while keeping any previously projected copy
+  of the skipped skill. Commit or restore that skill's folder, then apply the projection again.
 - **`rig context show` / `sync` / `rm`** — what is inside a context pack before you prime a seat
   with it, and how to make the library catch up when you edit one. `sync` also finds a workspace
   pack created after the daemon started; a daemon restart is no longer needed.
@@ -771,6 +785,9 @@ your circumstances is configuration, and the ones that are not, another agent ca
   it attaches to the existing kernel terminal; Ctrl-b then d detaches, and no missing
   seat or terminal is implicitly launched. Explain the failure and help with the
   chosen fallback. Plain `rig tui` remains a separate dashboard.
+  On an empty command line every typed command reaches the line whole and `j`/`k` move the
+  selection; the footer toggle is `F`, and a selected Scopes view's mini-requirements and
+  narrative keys are `M` and `N`.
   Open the instance row for one continuous cross-rig agent table with pod separators and material
   `RECENT` transitions; drill into a rig, mission, slice, or agent without losing the owning
   identity. Use the mission's workflow/packet view and Specs purpose/source to understand work.

package/daemon/context-packs/reference/getting-started.md

@@ -105,11 +105,11 @@ OpenRig view and the handoff to the operator as one procedure. From 0.6.7, OpenR
 script will do and changes nothing:
 
 ```sh
-curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.7/scripts/install.sh | sh -s -- --dry-run
+curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.8/scripts/install.sh | sh -s -- --dry-run
 ```
 
 The same command without `--dry-run`,
-`curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.7/scripts/install.sh | sh`, installs the
+`curl -fsSL https://raw.githubusercontent.com/mvschwarz/openrig/v0.6.8/scripts/install.sh | sh`, installs the
 latest published `@openrig/cli` with `npm install -g`,
 runs the Node.js and SQLite check, then `rig setup --dry-run` and `rig setup`. `rig setup` checks both Claude Code and
 Codex and may install a missing one, as described below. A failed step prints

package/daemon/context-packs/reference/instance-layout.md

@@ -79,6 +79,11 @@ Missing or malformed selections fail; absence is never inferred as disablement.
 `rig context work-install --json` reports the effective state, source, manifest,
 context selectors, and skills. With `--runtime`, its managed skill loadout then
 combines System World, topology, and Project World selectors with provenance.
+The catalog is a Git checkout. A skill folder with uncommitted or untracked content is
+skipped by itself and named. With `--runtime`, work-install reports selected skips with
+exit 1. It inspects by default; `--apply-skills` projects the remaining clean skills while
+keeping any previously projected copy of the skipped skill. An uncommitted change directly
+in the catalog root, such as `catalog.yaml`, still makes the whole catalog unavailable.
 
 For a pre-0.5.9 home, use the `openrig-upgrade` skill's
 `migrate-telemetry-state-0.5.9.mjs` helper as an Agent-Operated Migration. Its

package/daemon/context-packs/reference/manifest.yaml

@@ -1,7 +1,7 @@
 # Reference guides the help pack links to, loaded one file or section at a time by address
 # (rig context get reference/<file>#<section>). Each file is a symlink to docs/reference/.
 name: reference
-version: "0.6.7"
+version: "0.6.8"
 taxonomy: world
 purpose: "Version-matched reference guides the help guide links to. Load a single file or section by address; don't load the whole pack."
 files:

package/daemon/context-packs/reference/rig-spec.md

@@ -8,6 +8,9 @@ This is the canonical reference for the pod-aware RigSpec YAML format. Every fie
 
 ---
 
+For choosing IDs, see [naming rigs, pods and seats](topology-naming.md). Keep the same
+logical names in edges, startup instructions, workflow targets and runtime presets.
+
 ## Minimal Valid Example
 
 ```yaml
@@ -18,7 +21,7 @@ pods:
   - id: dev
     label: Development
     members:
-      - id: impl
+      - id: build
         agent_ref: "local:agents/impl"
         profile: default
         runtime: claude-code
@@ -105,7 +108,7 @@ pods:
           required: true
       actions: []
     members:
-      - id: impl
+      - id: build
         agent_ref: "local:agents/impl"
         profile: default
         runtime: claude-code
@@ -131,7 +134,7 @@ pods:
         cwd: "."
     edges:
       - kind: delegates_to
-        from: impl
+        from: build
         to: qa
 
   - id: rev
@@ -152,13 +155,13 @@ pods:
 edges:
   - kind: delegates_to
     from: orch.lead
-    to: dev.impl
+    to: dev.build
   - kind: delegates_to
     from: orch.peer
     to: dev.qa
   - kind: can_observe
     from: rev.r1
-    to: dev.impl
+    to: dev.build
   - kind: can_observe
     from: rev.r2
     to: dev.qa
@@ -453,7 +456,7 @@ The canonical session name is derived from the pod ID, member ID, and rig name:
 {podId}-{memberId}@{rigName}
 ```
 
-Example: pod `dev`, member `impl`, rig `my-team` → session `dev-impl@my-team`
+Example: pod `dev`, member `build`, rig `my-team` → session `dev-build@my-team`
 
 Pod and member IDs cannot contain `@` because the first `@` separates their portion
 of the session address from the rig name. Rig names may still contain `@`.
@@ -482,13 +485,13 @@ Edges within a pod use **unqualified member IDs** (just the member `id`, not `po
 pods:
   - id: dev
     members:
-      - id: impl
+      - id: build
         # ...
       - id: qa
         # ...
     edges:
       - kind: delegates_to
-        from: impl      # NOT dev.impl
+        from: build     # NOT dev.build
         to: qa          # NOT dev.qa
 ```
 
@@ -502,7 +505,7 @@ Edges between pods use **fully-qualified `pod.member` IDs**:
 edges:
   - kind: delegates_to
     from: orch.lead     # pod.member format
-    to: dev.impl        # pod.member format
+    to: dev.build       # pod.member format
 ```
 
 Cross-pod edges must reference different pods. An edge where both `from` and `to` are in the same pod is a validation error — use pod-local edges instead.

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

@@ -1,128 +1,90 @@
-# What changed in OpenRig 0.6.7
+# What changed in OpenRig 0.6.8
 
-This note is for an agent on an install that was just upgraded to 0.6.7. It lists only what behaves differently from
-0.6.6 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.8. It lists only what behaves differently from
+0.6.7 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.
 
-## The OpenRig view is now the handoff
-
-- **Open the view as the step after install or start; don't wait to be asked.** Say you're opening it, run
-  `rig terminal open saved:kernel --window`, then tell the person where it opened. Don't ask "Open the OpenRig view
-  now?", don't wait for a phrase like "show me my agents", and don't finish by printing a command for them to copy. The
-  same command brings their agents back later.
-- **The layout follows the person's terminal width.** On a narrow terminal the operator gets the first tab. On a wide
-  one the dashboard and operator sit side by side and the advisor has its own tab. Inside herdr it opens a focused
-  `openrig kernel` space. A `kernel` view the person saved themselves still wins.
-- **It opens where the caller is.** Terminal gets a window and Ghostty a tab. From Claude Desktop, iTerm or VS Code on a
-  Mac it opens a new Ghostty or Terminal window, and macOS may ask to allow it: mention that clicking Allow is fine only
-  in that case. Over SSH, in CI or with no display, it returns a definite no-window result with the reason. Relay the
-  `run:` command it prints exactly, or give `env -u TMUX tmux attach-session -t '=<canonicalSessionName>'` for the
-  operator.
-- **`rig terminal open <view>` opens a window by default.** Pass `--provider herdr` or `--provider cmux` only to add
-  tiles to a workspace that's already visible. With `--json`, `reusedWorkspace` and `opened: []` mean an existing view
-  was reused, which is success.
-- **The TUI's action is now "Open terminals ▸"** (it was `term ▸`). It opens a desktop window through the same
-  launcher, so the TUI must run on the daemon's desktop.
-- **The `rigs` skill is installed for the person's own agent.** The daemon writes it to `~/.claude/skills/rigs` and
-  `~/.agents/skills/rigs` and refreshes it on every upgrade. It now triggers on any mention of OpenRig, rigs or a team
-  of coding agents. A copy added earlier with skills.sh is left alone and never refreshed.
-
-## Installing and setting up
-
-- **Show the install preview first.** The published install command has a `--dry-run` preview
-  (`rig context get reference/getting-started.md` has both forms). Run the install when the person agrees. If the only
-  failures left are provider sign-ins, have them sign in and continue at "Start the kernel".
-- **If your own harness refuses a tool call while installing,** say so and show the refusal: Claude Code's auto mode can
-  deny calls as well as approve them. Let the person review it in their harness or run that step themselves. A refused
-  call doesn't prove the OpenRig command failed.
-- **`rig setup` installs herdr by default** on macOS and Linux; `--no-herdr` declines it. On a Mac, ask once about
-  Ghostty and on yes rerun `rig setup --ghostty`, keeping `--no-herdr` if it was chosen. Setup no longer installs cmux,
-  and an existing cmux still works. In `--json` output the `cmux_install` step is gone and `herdr_install` and
-  `ghostty_install` appear.
-- **`rig doctor` checks Claude and Codex installs, and a login or configured provider credential,** the way setup does.
-  It exits 1 when either harness is missing or has neither, including one the person doesn't use, so ignore a failure
-  on an unused harness. A pass means a login or configured provider credential is available locally, not that a
-  provider accepts the credential or that an agent can work; no provider request or agent work is tested.
-- **When setting up permissions,** recommend keeping the team default and offer remembered allowances only if the
-  person wants fewer prompts. People slowed by prompts can be pointed to the workshop listing.
-- **Windows users go through WSL2.** For Pi seats there, offer either credential route; a global Pi login still isn't
-  shared with managed seats.
-
-## Fewer prompts
-
-- **In Claude team seats, help on lifecycle commands runs without a prompt.** `rig down --help` and `-h` forms run;
-  the lifecycle actions themselves still ask. Pipelines, command substitutions, redirects and heredocs aren't allowed
-  automatically.
-- **The kernel operator's Claude session runs routine inspection without prompts:** Python, command lookup, `cd`, text
-  helpers and WebFetch. Compound commands and redirects still go to Claude's own permission check.
-- **Managed Codex seats no longer stop at the update menu on start.** Updating Codex is the operator's job: if a Codex
-  seat says its model needs a newer Codex, offer to update Codex and restart that seat, without stopping the team. If a
-  Codex seat shows a model-switch menu near a rate limit, ask the person; don't change the team's model.
-
-## Messages, wakes and Slack
-
-- **A send or wake no longer answers a question that's waiting for a person.** It's refused with
-  `target_needs_input`, and the reason ends `; latest hook, pane unrecognized` when the screen can't be read, even if
-  the hook is minutes old. Read the seat with `rig capture` and get the question answered by whoever should answer it.
-  Don't retry the send.
-- **Slack can post to a channel per rig or seat:** `rig slack channel-map list`, `set <match> <channel>` and
-  `remove <match>`. After a change, invite the app to each channel, run `rig slack verify`, then `rig slack disable`
-  and `rig slack enable` (or restart the daemon). Thread replies still reach the seat in any channel.
-- **A reaction on any part of a Slack ask reaches the seat that asked,** as a task tagged `human-reaction`. Treat it as
-  a signal to interpret, not an answer; the ask stays open. An existing app needs the `reactions:read` scope, the
-  `reaction_added` event and a reinstall, and `rig slack verify` warns when the scope is missing.
-- **A long Slack ask is posted in parts.** If it still can't be posted, you get a task `<ask id>-undeliverable`, tagged
-  `slack-undeliverable`: shorten the ask or link a file for the long part, and send it as a new ask.
-- **Replies sent with "Also send to #channel" now arrive** at the seat that asked, like any other thread reply.
-
-## Running teams
-
-- **`rig down` prints what each agent seemed to be doing before it stops them,** on one stderr line, or "unknown". It's
-  a best-effort snapshot, not a record of what was interrupted. `rig down --host` now exits 2 when the remote teardown
-  reports errors.
-- **Before a handover or compaction, write the seat's recap** with
-  `rig context recap-write --rig <rig> --seat <seat> --file <draft.md>`, not a file tool, so earlier recaps are kept.
-  `rig seat handover <seat>` now works on the same seat again and again; a seat left half-handed-over recovers by
-  running it again.
-- **After a managed compaction, read the `refocusing` skill and consume the current topology and work traces
-  delivered with the restore.** Don't rerun them just to duplicate the delivery; name a missing trace. For a new trace
-  outside that context, use the skill's one-command form. The daemon now installs the skill globally.
-- **The built-in starter and factory leads publish their team's roster** at first start, so `rig roster list` and
-  `rig roster find <topic>` know those teams.
-- **Claiming a parked queue item clears its `blocked_on`.** To park it again on the same gate, run
-  `rig queue update <id> --state blocked` without `--blocked-on`: it reuses the previous gate. Add the usual wake when
-  one is required.
-- **A periodic reminder first fires one interval after you register it,** not immediately.
-- **Workflows:** `rig workflow run` and `rig workflow watch` exit 3 for an aborted instance. When a step that was sent
-  back completes again, the steps that depend on it run again too, including ones that had passed.
-- **Sharing teams:** `rig bundle create` and `rig up <link>` name the bundle after `rig.yaml`'s `name`, and
-  `rig bundle check` names the file in each finding. Submissions go to `mvschwarz/openrig-registry`. The bundle safety
-  check always runs, even with `--skip-version-check --force`.
-- **`rig context add <url> --git` retrieves shallowly by default:** the initial retrieval fetches only the current
-  commit, and a server that refuses shallow retrieval falls back to a full clone with a warning. Use
-  `rig context source update` for later revisions.
-- **Values that used to fail quietly are refused:** a bad `rig chatroom history --since` (fix the value; the room isn't
-  empty) and a `--wake-after` such as `7d` (use hours, for example `168h`).
-- **Pi seats print a `[pi-runner] seat …:` line at start** saying whether a credential was found and, if not, how to
-  fix it. A MiniMax model gets `MINIMAX_API_KEY` when that name is in `recovery.provider_auth_env_allowlist`.
-- **`agents.advisor_session` defaults to the kernel's advisor seat.**
+## Skills from the managed catalog
+
+- **A skill with uncommitted changes in the catalog now blocks only itself.** Before, one edited skill made the whole
+  catalog unavailable to work-install, launch and restore preflight. Now that skill is skipped and named, and the
+  remaining clean skills stay available for projection.
+- **Read the warning, don't retry.** `catalog_skill_skipped` names a skill nobody selected; `selected_skill_skipped`
+  names the selector and the folder. The fix is to commit or restore that folder's content in the catalog, then run the
+  projection again.
+- **A selected skipped skill makes the inspection commands exit 1.** `rig context work-install --runtime <runtime>`
+  and `rig skill loadout --runtime <runtime>` inspect by default. Use `--apply-skills` with work-install or `--apply`
+  with skill loadout to project the remaining clean skills. Read the warnings and projection result; exit 1 alone does
+  not say whether files were changed. With `--json`, skipped skills are in `skillLoadout.skipped` or
+  `loadout.skipped`, respectively.
+- **A seat keeps the copy it already has** of a skipped skill, unchanged. After the catalog change is committed or
+  restored, the next applied projection can refresh it. No seat receives the skipped skill's uncommitted files, and
+  launch only warns about the skip.
+- **An uncommitted `catalog.yaml` still makes the whole catalog unavailable,** because it changes every selection.
+
+## Launch plans
+
+- **`rig launch <rig> <seat> --plan` previews one seat's launch** without launching it, locally or with `--host`. Use
+  it before starting a single seat, as `--seats … --plan` already allowed for several.
+- **A plan is never sent to a daemon older than 0.5.9,** which would ignore the flag and launch. If `rig launch --plan`
+  refuses for that reason, restart or upgrade that daemon. If it exits non-zero saying the daemon may have acted, check
+  `rig ps --nodes -A` before retrying.
+
+## Slack
+
+- **Answer a person's thread reply in that thread.** When someone replies inside a thread OpenRig opened, answer with
+  `rig queue create --human-intent update --reply-to <the inbound reply's row>`, and the answer posts in that thread.
+  A top-level message is still answered top-level.
+- **A short rate limit is waited out.** When Slack asks for a pause of 10 seconds or less, OpenRig waits and retries the
+  post once. A longer pause is still left to the usual retry of retained messages.
+
+## Managed compaction
+
+- **A quiet seat is restored after `/compact`.** The turn boundary, the restore request and the read-depth
+  audit now reach a Claude seat that takes no turn after compacting. Before, they waited for the seat's next turn,
+  so a seat with nothing to do could sit unrestored. Each stage still waits until the seat's screen shows it idle.
+
+## Workflows
+
+- **Validate before you run.** `rig workflow validate` reports `step_cannot_finish` when no allowed exit can finish a
+  step or route onward, and such a workflow cannot be instantiated. Allow `done` or an exit with a route onward. In a
+  dependency graph, `handoff` can also finish a sink without a next step. A spec that validated on 0.6.7 may need a
+  correction.
+
+## The TUI
+
+- **Type whole commands on an empty command line.** The footer toggle is now `F`, and in a selected Scopes view the
+  mini-requirements and narrative keys are `M` and `N`, so `find`, `feed`, `mission`, `narrative` and `needs` reach the
+  command line intact.
+- **`j` and `k` move the selection down and up** when the command line is empty. With text on the line they're ordinary
+  letters.
+
+## Smaller changes
+
+- **A Claude seat launched with `--remote-control`** confirms its identity instead of staying "identity not confirmed".
+- **`rig down` still saves its recovery snapshot** when finding one seat's resume details fails.
+- **A wake for a handed-off task shows its summary** on one line, so read it to see what the task is for.
+- **`rig scope audit` accepts slice folders numbered 100 and above.** `rig proof add --file` keeps a leading UTF-8
+  byte-order mark.
+- **Building from source no longer needs POSIX shell tools** for the CLI and TUI output. It hasn't been run on Windows
+  yet; WSL2 is still the way to run OpenRig there.
+- **A topology naming reference** explains how to name a team's pods and seats: `rig context get
+  reference/topology-naming.md`.
 
 ## What to stop doing
 
-- **Stop asking whether to open the OpenRig view, or waiting for a phrase.** Open it after install or start.
-- **Stop using `--provider herdr` for the first view,** and stop pre-warning about macOS prompts from Terminal or
-  Ghostty.
-- **Stop suggesting `--skip-version-check --force` to get past a bundle pre-check failure.** The check always runs.
-- **Stop retrying a send refused with `target_needs_input`.** Get the question answered instead.
-- **Stop telling people to untick "Also send to #channel" when they answer in Slack.** Those replies now arrive.
+- **Stop treating a non-zero work-install exit as proof that nothing changed.** Read the skipped-skill warnings and
+  projection result. Inspection alone changes no skill files; an applied projection can update clean skills while
+  reporting a skipped one.
+- **Stop scripting around the TUI's single-letter keys.** Type the command whole.
+- **Stop assuming a workflow that validated on 0.6.7 can finish.** Validate it again on 0.6.8.
 
-## Known gaps in 0.6.7
+## Known gaps in 0.6.8
 
-- **Not yet checked on a real machine:** opening the view from Claude Desktop, and the plain-tmux layout without herdr.
-  The full first install from nothing and a Linux run come after this release.
+- **Not yet checked on a real machine:** the full first install from nothing, on Mac, Linux and Windows.
 - **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.**

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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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.7"
+version: "0.6.8"
 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/SKILL.md

@@ -92,6 +92,12 @@ the human (a pending human decision, or a row parked on the human), since a
 reply in that thread would answer the decision. In every such case the
 `--verify` result says `threaded: false` with the reason.
 
+To answer a reply the human typed inside one of your threads, `--reply-to` the
+row their reply landed as. The update posts in that thread unless one of the
+cases above applies, and `--verify` reports it the same way. A message the
+human started at the top level of the channel has no thread yet, so the answer
+posts as a new message.
+
 A **decision** with a few clear choices can carry `--human-questions-file <path>`:
 a JSON array of 1–4 questions, each
 `{"id", "question", "options": [{"id", "label", "recommended"?}]}` with 2–4

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.7"
+version: "0.6.8"
 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: