@openrig/cli 0.6.0 → 0.6.2

package/daemon/context-packs/skills/applying-a-permission-policy/SKILL.md

@@ -1,12 +1,13 @@
 ---
 name: applying-a-permission-policy
 description: >-
-  Use when a user asks an agent to configure OpenRig command permissions, reduce
-  repeated native approval prompts, or apply a selected rig/seat permission policy.
+  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.
 metadata:
   openrig:
     stage: established
-    docs_checked: "2026-09-25"
+    docs_checked: "2026-09-29"
     verification_status: "Verify the installed harness version and effective settings; a rule-parser result is not a native permission test."
 ---
 
@@ -17,10 +18,40 @@ OpenRig operating posture, native command rules, sandbox access and launch flags
 are separate controls. A command rule grants execution capability, not authority
 to invent tasks, publish work or change another host.
 
+## Ask once before team launch
+
+Reuse an existing explicit choice for these harnesses and this scope from the
+user's onboarding context; do not ask again. Existing rules are configuration,
+not evidence of consent to expand their scope. Preserve them without expansion.
+If the choice is unknown, briefly explain:
+
+> This allows the whole `rig` command family, including starting/stopping agents,
+> changing OpenRig configuration and launching processes. It is not global YOLO
+> or permission to invent work. The scope is your personal settings for this
+> project unless you explicitly choose your user-wide sessions instead.
+>
+> Allow your agents to run OpenRig commands without repeated permission prompts?
+> **Yes — recommended** / **No — keep prompts**
+
+- **Yes:** require an actual affirmative answer, then apply the procedure below
+  at that scope for the selected harnesses. Never substitute user-wide rules
+  when project rules are unsupported. Native restrictions still apply.
+- **No:** leave permission settings unchanged and continue with existing prompts.
+- **No answer:** make no settings change, infer no consent and continue with
+  existing prompts. Do not keep asking during this setup.
+
+Remember an explicit Yes or No in the existing onboarding/project context the
+agent already reads: choice, harnesses and scope. For Yes, record the exact files
+and entries added, any pre-existing equivalents, and the loading/verification
+result. Do not add a preference service or native configuration key. No answer
+is not a remembered No. Offer broader permissive operation only as a separate
+explicit opt-in; the setup question does not select a builtin policy or mode.
+
 ## Choose the intended scope
 
-Use an existing explicit choice; otherwise explain these options and ask which
-the user wants. Do not ask again for routine steps already authorized.
+Outside the setup question above, use an existing explicit choice; otherwise
+explain these options and ask which the user wants. Do not reopen the menu after
+an answered setup question or ask again for routine steps already authorized.
 
 | Choice | What the agent configures |
 | --- | --- |
@@ -47,7 +78,14 @@ execution, an entire interpreter or a generic shell wrapper.
    hooks, auth, MCP, model settings and unrelated values. An allow must not erase
    a stricter rule or managed requirement. Report a real conflict instead of
    silently bypassing it.
+   Check both bare and actual absolute command spellings: a restriction on one
+   may not match the other. If a new allowance would evade a stricter restriction,
+   leave that addition unapplied and report the conflict; do not switch spellings
+   to bypass it.
 4. Back up touched files and merge only authorized additions, avoiding duplicates.
+   Recognize equivalent existing entries (including Claude's legacy `Bash(rig:*)`);
+   leave their markers untouched. Reapplying the same choice must be a no-op when
+   the required entries already exist, including no timestamp-only rewrite.
    The agent performs these edits; hand-editing is an option, not a required user
    chore. Apply the selected scope without another conversational permission round.
    Native enforcement still applies.
@@ -60,8 +98,15 @@ execution, an entire interpreter or a generic shell wrapper.
    not destructive probes. Report effective settings and remaining prompts.
    A parser match alone does not establish native behavior.
 
-For rollback, remove only this setup's additions, preserving later unrelated
-edits. Builtin policy specs remain read-only; customize in user space.
+Give the user this short undo: **“Undo the OpenRig command allowances added by
+this setup; keep my other rules.”** The agent removes only the recorded entries
+from their exact files, preserving pre-existing rules and subsequent edits.
+For Codex remove those `prefix_rule` entries; for Claude remove those
+`permissions.allow` entries. Delete a newly created rules file only if it still
+contains solely this setup's additions. Never restore the entire backup over
+later changes. Record the changed choice in the same context and verify native
+reloading/revocation; other pre-existing allowances may still permit `rig`.
+Builtin policy specs remain read-only; customize in user space.
 
 ## Codex command rules
 
@@ -103,8 +148,10 @@ codex execpolicy check --pretty --rules /absolute/path/to/openrig.rules -- print
 ```
 
 Inspect matches, not only exit status; repeat `--rules` for other effective
-files. A matching `prompt` or `forbidden` overrides allow. Verify rule loading
-in the target conversation after the required reload. For project-only scope,
+files. A matching `prompt` or `forbidden` overrides allow. The official procedure
+loads `.rules` at session startup; a file edit alone does not reload this turn.
+Preserve the conversation and use an authorized supported resume when needed,
+then verify loading in the target conversation. For project-only scope,
 confirm the layer is active there and absent from an unrelated project's active
 layers. An evaluator given an explicit `--rules` file proves matching, not that
 scope or automatic loading. Existing user-wide rules may already permit the
@@ -134,7 +181,9 @@ Current syntax uses ` *` for a command family; `Bash(rig:*)` is also supported.
 Narrower examples are `Bash(rig ps *)` and `Bash(rig queue list *)`.
 Preserve `deny`/`ask` entries and `defaultMode`; do not add `Bash(*)` or switch
 to bypass to resolve a mismatch. Inspect native `/permissions` and verify the
-actual command spelling.
+actual command spelling. A bare rule does not cover every absolute invocation:
+derive the actual executable and, after the stricter-rule check above, add its
+exact `Bash(/actual/path/to/rig *)` spelling if needed. Do not use a path wildcard.
 
 Choose scope using the [settings reference](https://code.claude.com/docs/en/settings):
 `.claude/settings.local.json` for personal project settings,
@@ -143,6 +192,9 @@ Choose scope using the [settings reference](https://code.claude.com/docs/en/sett
 Confirm the effective project root, especially for worktrees. Keep personal
 settings out of commits. Managed restrictions and sandbox/network controls
 still apply; a Bash allow is not a general network policy.
+Current Claude settings documentation describes live reload of permission
+edits. Confirm the rule's source in `/permissions` and repeated harmless calls
+in the target conversation; do not claim prompt behavior from JSON validity.
 
 ## Existing policies and broader modes
 
@@ -154,9 +206,10 @@ is unavailable, explain the remaining choice instead of selecting broader access
 
 For explicitly chosen broader operation, inspect
 `rig policy current --spec <user-owned-rig.yaml>` and the compatible getting-started guide's **Opt-in permissive
-operation** section. OpenRig's Codex `builtin:yolo` supplies `-s danger-full-access`;
-it does not itself select `approval_policy` and replaces a named
-`codex_config_profile` argument. Claude's corresponding launch flag is
+operation** section. OpenRig's Codex `builtin:yolo` supplies
+`-s danger-full-access -a never` and replaces a named `codex_config_profile`
+argument. The legacy environment-only YOLO path selects only the sandbox.
+Claude's corresponding launch flag is
 `--dangerously-skip-permissions`. Neither a resource `profile: default` nor OpenRig
 operating posture is a native permission policy. Do not change shipped defaults
 or assume editing a launch spec changes an existing seat.

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

@@ -1,10 +1,10 @@
 # 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.0"
+version: "0.6.2"
 taxonomy: "skills"
-purpose: "Use when a user asks an agent to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy."
+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:
   - path: "SKILL.md"
     role: "instruction"
-    summary: "Use when a user asks an agent to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy."
+    summary: "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."

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.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when a Claude Code session has just compacted, is about to compact, reached context limit, resumed after /compact, or needs to rebuild its working mental model from Claude JSONL transcripts and touched files."
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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 openrig-builder); 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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/SKILL.md

@@ -113,6 +113,13 @@ General engineering skills OpenRig ships as vendored copies. Open when the task
 - **frontend-design** — designing frontend / UI.
 - **dogfood** — web-QA / dogfooding a shipped UI.
 
+## When OpenRig itself misbehaves
+
+Run `rig context get help`: the one help guide for your installed version, from symptom to next step, known problems,
+and a useful report to the OpenRig team if you are still stuck. If `rig` won't run, read
+`daemon/docs/reference/help.md` inside the installed `@openrig/cli` package, or https://www.openrig.dev/help/agents
+(the same text).
+
 ## Need more than what ships here?
 
 This index covers the **shipped** surface. A dev host carries far more (factory, architecture, PM-craft, studio skills) reached through the host's own routers/codemaps — if you're on a builder host and need something not listed above, that deeper routing is the next hop, not a wall. (Host-scale routing is the subject of the context-routing architecture doc; at product scale, this one file is the whole map.)

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

@@ -37,6 +37,31 @@ read [references/worked-example.md](references/worked-example.md). Installed cop
 `rig context get skills/core/openrig-software-factory/references/worked-example.md`.
 A roadmap, YAML file or wake does not execute work or authorize a new outcome.
 
+## Choose the first project's providers
+
+Ask which working account(s) the user wants: Claude Code, Codex, or both. Reuse
+an explicit choice and recommend the account they already have working. Use
+`first-project-claude` (two Claude), `first-project` (two Codex), or
+`first-project-mixed` (Claude owner, Codex checker). All share the same task and
+owner/checker culture. Check only selected CLIs/logins; request `claude auth login`
+or `codex login` once when that selected login is missing. No credential copying,
+unused provider prerequisite or silent model/provider fallback.
+
+Read the compatible getting-started guide's **Choose your providers** and
+**Kernel startup stays automatic** sections before launch. The choice selects
+the two project agents. Kernel auto-boot independently uses available
+authenticated accounts, so it may use both even when the project uses one.
+Do not add an unused-provider login gate or manual kernel setup to this path.
+An instance-wide provider restriction is a separate request. Preserve an
+existing kernel and working user rigs.
+
+Show the chosen recipe, resolved runtimes/models and exact
+`rig up <starter> --cwd . --plan` / `rig up <starter> --cwd .` commands. Codex seats
+retain `gpt-6-astra`; Claude seats use the configured native default without an
+OpenRig model override. Confirm that model with the user and its availability;
+verify the native session's actual model before consequential work. Use the
+chosen rig name in owner/checker addresses throughout the same task and return.
+
 ## Establish the working agreement
 
 Read the repository instructions, current work and desired user-visible result.
@@ -51,12 +76,18 @@ model turns, but delivered wakes and resumed work **can spend tokens**. Prefer
 an event-driven wait to frequent empty reminders. Wakes cannot answer a user
 question, clear a permission prompt or guarantee progress.
 
-**Choose permissions before launching or assigning work.** Offer ordinary prompts,
-persistent rules for selected commands, or deliberately broader access. Follow
-[Applying a permission policy](#find-the-compatible-permission-guide) to perform
-the user's choice and verify it in the target conversation. Preserve restrictions
-and unrelated settings. A whole `rig` allowance covers every verb, not just reads;
-it does not grant new product authority or change everyone else's defaults.
+**Ask once before launching or assigning work:** “Allow your agents to run
+OpenRig commands without repeated permission prompts?” **Yes — recommended** /
+**No — keep prompts**. Reuse an existing explicit choice for this scope. Explain
+that this covers all `rig` verbs, including starting/stopping agents and changing
+configuration, at personal project scope unless the user explicitly chooses
+user-wide sessions. It is not global YOLO or permission to invent work.
+On an actual Yes, follow [Applying a permission policy](#find-the-compatible-permission-guide)
+to add existing native rules, preserve stricter/unrelated settings, and verify
+the target conversation. No or no answer leaves settings alone and continues
+with existing prompts. Remember the explicit choice and exact additions in the
+existing onboarding context; “Undo the OpenRig command allowances added by this
+setup” removes only those additions. Broader access remains a separate opt-in.
 
 Keep purpose, acceptance, decisions and evidence in existing project files.
 Deliver selected context and obtain each seat's scope reaction; retrieval alone

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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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/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.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when changing a rig while it is alive — `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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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/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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 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.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication."
 files:

package/daemon/context-packs/skills/pm/context-builder/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: "context-builder"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered."
 files:

package/daemon/context-packs/skills/pm/exec-summary/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: "exec-summary"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document."
 files:

package/daemon/context-packs/skills/pm/office-hours/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: "office-hours"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "YC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions."
 files:

package/daemon/context-packs/skills/pm/plan-review/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: "plan-review"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Multi-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early."
 files:

package/daemon/context-packs/skills/pm/requirements-writer/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: "requirements-writer"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies."
 files:

package/daemon/context-packs/skills/pm/ui-mockup/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: "ui-mockup"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing."
 files:

package/daemon/context-packs/skills/pods/development-team/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: "development-team"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when a development pod begins or hands off implementation, QA, or design work."
 files:

package/daemon/context-packs/skills/pods/orchestration-team/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: "orchestration-team"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when coordinating assignments, selected review boundaries, or blocked work across a rig."
 files:

package/daemon/context-packs/skills/pods/oversight-team/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: "oversight-team"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention ladder (orchestrator-ping -> refocus -> human escalation), and the cheap+deep model economics. NOT for orchestrating your OWN rig (orchestration-team) and NOT the intervention primi"
 files:

package/daemon/context-packs/skills/pods/review-team/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: "review-team"
-version: "0.6.0"
+version: "0.6.2"
 taxonomy: "skills"
 purpose: "Use when assigned a review or when an authored review boundary is reached."
 files: