@openrig/cli 0.5.12 → 0.5.14

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

@@ -42,16 +42,44 @@ Check readiness: configured, enabled, active, ready, reason, and next action.
 `indeterminate` is not ready. Follow the reported next inspection; do not enable
 or reconfigure a connector merely to make the check pass.
 
-Write the decision, evidence, and continuation in a body file. The sole outbound
-human-message primitive is:
+Author for the person reading on a phone: a short subject in `--summary`, then
+one complete brief in `--body-file`. State why it matters, your recommendation
+and material tradeoff, the bounded action if approved, and the choice requested.
+For an update, state the user-visible outcome and “No action needed.” Aim for
+roughly 100–150 words; this is guidance, not a semantic validator. Keep technical
+continuation, exact candidate/revision and evidence on the owning agent row and
+in the durable artifact behind `--evidence-ref`. A local path is not a phone link
+and Markdown evidence files are not automatically attached.
+
+For example, a synthetic brief could say:
+
+> The repaired status view is ready. I recommend updating this instance; live
+> status will briefly pause. Sessions will be preserved. Approve this instance
+> update, or hold? Supporting test detail follows in this thread.
+
+This example grants no authority. Choose `--human-intent decision` for a request
+or `--human-intent update` for a quiet FYI. Omission retains legacy decision
+behavior; words such as “FYI” and tags do not change intent.
+
+The sole outbound human-message primitive is:
 
 ```bash
 rig queue create --destination <entityId>@external \
-  --summary "<decision or update>" --body-file <packet-file> \
+  --human-intent decision --summary "<short subject>" --body-file <brief-file> \
   --evidence-ref <durable-evidence> --verify --json
 ```
 
-If an existing agent-owned row must wait, block it on the **new live qitem ID**
+An optional `--human-detail-file <path>` supplies one coherent supplemental
+reply in the same thread. Announce its purpose in the brief; the product also
+marks that a detail reply follows. The primary must already contain the complete
+scope, options and action. Do not split an agent dump blindly or move the essential
+choice into overflow. Rendering checks every part and its accessibility fallback
+before posting; an oversized request is refused with a field-specific correction,
+never silently clipped. Shorten the brief or related detail as directed. Inspect
+the failed row, then deliberately cancel/replace the authored request if its
+content needs correction; a timeout alone is never a reason to replace it.
+
+If an existing agent-owned row must wait for a **decision**, block it on the **new live qitem ID**
 (`rig queue block <work-id> --on <human-qitem-id> ...`), not on the human address.
 Completion of the human qitem resumes its dependants. Blocking on the human as
 well would issue another notification for the same decision.
@@ -66,7 +94,14 @@ or blindly resend because verification timed out.
 rig queue transitions <qitem-id>
 ```
 
-A correlated reply binds to that exact human and qitem and records the resolution
+For `update`, confirmed complete delivery may close the delivery obligation.
+It creates no approval obligation and cannot be used as a decision blocker.
+Delivered updates remain queryable for Feed; a failure or ambiguous send stays
+separate. A root message alone does not prove supplemental delivery. Retries
+reconcile stable part identities and send only missing parts. An FYI reply is
+not a human decision.
+
+For a decision, a correlated reply binds to that exact human and qitem and records the resolution
 that resumes the owner. Check the recorded result before claiming the decision
 arrived; a delivery receipt alone is not acceptance.
 

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.5.12"
+version: "0.5.14"
 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,8 +11,9 @@ 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-one-plus top-level verbs ship (capability canon refreshed through
-`capability-delta-v0.5.12`). 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
+`capability-delta-v0.5.14-r6`). 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).
 
 ---
@@ -54,6 +55,13 @@ one command away. Your memory of the fleet is a claim about the past.
   freshness, rule, evidence, confidence, and next inspection. Use the TUI's HEALTH tab for the
   same records when a human also needs to see them. Empty output is never a healthy assertion,
   list/explain never mutate, and diagnostic presentation remains explicit opt-in policy.
+  INFO is a severity; Unknown and stale describe assessment or freshness, not a healthy result.
+- **`rig health diagnosis show <qitem-id>`** — inspect a retained diagnosis alongside current
+  selected guidance before carrying an old restriction forward; `--full --json` expands the
+  evidence. `docs/reference/health-diagnosis.md#current-selected-context-and-correction` explains
+  the authored selection and correction record. Authority, current applicability, an assessment,
+  an action taken and a later observed effect are separate facts. Recording a correction or
+  replaying a case does not establish improved behavior or authorize unrelated work.
 
 ## Reaching another agent
 
@@ -92,6 +100,11 @@ unseen — which makes messages the one delivery channel that never gets skipped
   someone lists the stream before starting.
 - **`rig terminal open <view>`** — bring every live agent in a rig, mission or slice up as real
   typeable tiles at once.
+  In the TUI, **TERMINALS** keeps Saved views prominent and Derived groups collapsed until
+  expanded. Names load before detailed readiness. Select a view to inspect its members,
+  layout and pages; preview is passive. Saved membership requires deliberate setup.
+  **Open in Herdr** deliberately opens the inspected plan
+  and reports opened, absent or degraded members. Help or a side trip returns to the same preview.
 - **`rig walk <seat> --through <files> --pace <n>`** — deliver context pieces through
   file-backed terminal paste. When the current native generation record resolves, the complete
   piece and its matching Claude/Codex turn closure must arrive before pacing onward, including
@@ -284,13 +297,29 @@ because someone lost work once.
 - **`rig doctor`** — is the *installation* wired up correctly, or are you chasing a bug that is
   really a broken install. **`rig preflight`** asks whether this machine can run OpenRig at all.
 - **Bare `rig`** — the same TUI for first setup, daemon-down startup and ordinary work.
-  Enter starts only the selected daemon; then choose rigs and individual seats, with kernel
-  recommended first. Previously occupied seats default to their authoritative conversation.
+  A positive observation of a running rig enters ordinary work without a repeated Startup choice.
+  With no running rig, the chooser remains; slow or unverified detection does not mean stopped.
+  A late observation never takes navigation away after you have chosen another route.
+  **?** Help, **w** Skip and **L** Local reading remain usable during slow probes or loading,
+  and when the daemon is down or unverified. Local reading shows selected disk intent with
+  provenance and read errors; it does not substitute for live queue, execution or topology data.
+  These reading controls do not start a daemon or resume seats; skipping an already accepted
+  operation does not cancel it.
+  In startup, Enter starts only the selected daemon; then choose rigs and individual seats,
+  with kernel recommended first. Previously occupied seats default to their authoritative conversation.
   Missing history, ambiguous identity and unavailable authentication have distinct explanations;
   a fresh conversation requires a separate named confirmation. Declining launches nothing.
   **o** opens the existing native terminal here to handle its prompts; detach to return.
   If a fresh start paused before context delivery, **c** finishes that same occupant’s context.
   **r** refreshes actual state and **d** expands diagnostics. **S** returns to startup from work.
+  Ordinary views keep the navigator usable through page/rig changes and slow or failed reads.
+  Topology offers rig selection first, then loads that rig before unrelated fleet details.
+  While a new page loads, useful prior content can remain under its original scope label with
+  no action targets. First visits retain navigation and local loading/error feedback.
+  During refresh or failure, previously loaded content in the same scope stays useful, with its last
+  successful read time and Retry. A failed Feed source retains its contribution while healthy
+  sources update; confirmed denial, empty results or removals clear affected content. Late responses cannot
+  replace another page or project's data, and surviving selection and scroll stay in place.
 - **`rig crash-cart`** — the read-only daemon verdict and saved-state discovery used by that UI.
   An unavailable runtime, unauthorized endpoint or unreadable state is not an empty instance.
 - **`rig snapshot`** — take a restore point **before** the risky thing. `snapshot list` shows what
@@ -343,8 +372,26 @@ scheme, and nothing downstream can see it.
 
 - **`rig scope mission ls` / `show` / `create`** — what work exists, what a mission is for, and how
   to open one so it gets a stable dot-ID rather than being a bare folder nothing can address. In
-  `rig tui`, SCOPES → select a mission shows the same story as DONE / NOW / NEXT / ATTENTION, with
-  row drill-in and Escape back.
+  `rig tui`, **PROJECTS** → choose a project → mission → slice shows the work story with row
+  drill-in, current source and Escape back. Project IDs and roots distinguish equal display
+  names; an unavailable project read does not substitute another project's work.
+  The mission overview puts outcomes, current work/owner, blockers, next dependencies and
+  readable slice boxes before process prose. Accepted required proof judgments determine
+  completion; attached evidence, quiet activity and handoff do not. Reopened and assigned
+  unfinished work stays open even when no unassigned next slice exists. Actual custody and
+  planned ownership remain distinct, as do outcome completion and mission lifecycle or
+  publication. Unknown owners and eligibility stay unknown. Narrow views keep boxes and scroll.
+  Malformed mission or slice sources stay visible as local unavailable entries while healthy
+  neighbors remain readable. Open the affected source to inspect it, then refresh after correction.
+- **TUI Feed** — inspect **Human requests** separately from **Updates**, with the scope shown as
+  **Instance / All humans**. Explorer lists these categories; their entries appear in the
+  content pane. Human destinations and explicit human blockers show the recipient,
+  relevant project, needed decision and work it unblocks; agent priority alone is not a human
+  request. Confirmed delivered quiet FYIs remain in a bounded update window after their delivery
+  obligation closes, with a receipt and **No action needed**. Failed or ambiguous delivery is not
+  delivered history. Existing outcome and health updates retain their source and history.
+  Open detail and evidence, then Back. Reading does not approve or deliver a request, and queue
+  closure alone does not accept an outcome. Direct `attention`, `needs` and `feed` commands remain.
 - **`rig scope slice ls` / `show` / `create`** — the same at the altitude where work is actually
   buildable. `show` gives you intent, frontmatter and children without guessing which of five files
   to open.
@@ -389,6 +436,15 @@ scheme, and nothing downstream can see it.
   every other command's runtime vocabulary.
 - **`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.
+- **`rig context add <repository-path-or-URL> --git`** — select a pack while retaining its Git
+  source and checkout; `--pack <path>` chooses a repository-relative pack. Inspect that relationship
+  with **`rig context source inspect <ref>`**; it does not fetch or prove agent consumption.
+  **`rig context source update <ref>`** explicitly fetches and merges, preserving committed local
+  authorship before selecting clean content. Dirty work, conflicts, unavailable upstreams and
+  edits to the served selection refuse without a reset or push. Resolve and commit, or abort,
+  in the retained checkout before retrying; conflicts leave the prior served selection available.
+  Read the selected bytes with `context get` and check the actual consumer separately. This is
+  explicit update, not automatic synchronization of libraries or running agents.
 - **`rig context get <name-or-ref>`** — pull exact context by address instead of reading files:
   `<pack-ref>/<file>#<H2-slug>[/<H3-slug>]` serves the exact span bytes of one section, and **the
   `/<file>` component is required even in a one-file pack**. A bogus slug fails loud and lists the
@@ -462,6 +518,9 @@ reaching them is ordinary work rather than an escalation.
   pending, failed, or indeterminate delivery leaves the row intact. Inspect the same row's
   transitions before retrying. `rig send` remains agent-terminal delivery only.
 - **When project policy calls for human judgment or an update, load `messaging-the-human`.**
+  Use `rig context get skills/core/messaging-the-human/SKILL.md` for a complete decision brief,
+  related supplemental detail and explicit quiet-update intent. An FYI creates no approval
+  obligation; writing “FYI” in ordinary request prose does not select that intent.
   System World teaches these mechanics; Project World decides when and why they apply.
   Existing `<entityId>@host` blockers are internal custody labels mapped through the registry
   to the external participant, not a separate outbound route.
@@ -491,6 +550,14 @@ your circumstances is configuration, and the ones that are not, another agent ca
   loudly to report, whether to batch permission questions or block on them. **This declares a
   posture; it does not grant or deny permissions** — the harness's own settings are the control
   surface for that.
+- **`rig mode effective --rig <id> --json`** — inspect scoped human-led/delegated posture, phase
+  and source; project, mission and qitem selectors are also available in help. Resolved unset
+  scopes default to human-led; missing or ambiguous identity stays unknown. To deliberately
+  change a mission, `rig mode set delegated --scope mission --qualifier <project>/<mission>
+  --evidence "<decision>"` proposes it without writing; add `--confirm` to apply an authorized
+  choice, or select `human-led` to return to interactive work. Posture grants no authority.
+  Human-led process diagnosis is quiet; operational health and ordinary reminders remain.
+  See `docs/reference/scoped-operating-posture.md` for precedence and other scopes.
 - **Project World declares the human authority boundary.** Read the current project and mission
   policy for actions requiring approval; the system mechanics do not impose a universal list.
   A script's explicit-path authoring guard (for example `OPENRIG_SKILL_CANON_ROOT`) asks for a
@@ -514,15 +581,27 @@ your circumstances is configuration, and the ones that are not, another agent ca
   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.
-  Tab completes commands and snapshot arguments; Recent opens original events. **CONFIG**
-  browses instance/work roots, context, display, waiting, recovery, activity and advanced settings;
+  In **Specs**, kind groups start collapsed and expand explicitly. Selection previews purpose,
+  contents and provenance; Enter opens details.
+  **View current source** reads disk within the explicitly configured readable roots. Relative
+  Markdown links resolve against that source; headings open with a labelled starting point.
+  Escape or `back` restores the caller's selection and scroll. Detail uses the full width on
+  narrow terminals. The TUI command `read <root>/<path>#heading` also opens a named source;
+  missing, denied, binary, truncated and missing-heading results stay explicit. HTTP(S) links
+  show a selectable destination without opening a browser; `v` enables terminal text selection.
+  Tab completes commands and snapshot arguments; Recent opens original events. **System** opens
+  to instance **Health**, with **Configuration** and **Connections** beneath it. Contextual Health
+  remains available in the owning rig or agent view. **Configuration** browses instance/work
+  roots, context, display, waiting, recovery, activity and advanced settings;
   Slack and people are one category. Select a category, use right/left to change panes,
   Enter for full value/default/source/scope, `/` to search labels and keys, and Escape or `back`
   to return. Long detail scrolls; `v` enables terminal text selection. `refresh` reads the current
   view again without changing settings or verifying delivery. Sources & coverage names exclusions,
   daemon/CLI identity and the client timezone separately. Resolved settings do not prove runtime
-  adoption. The legacy `connections` command still inspects gateway services and human routes;
-  dated verification does not prove delivery. `timezone` gives persistent local-time guidance.
+  adoption. Direct `config` and `connections` commands remain; Connections inspects gateway
+  services and human routes. Dated verification does not prove delivery. `timezone` gives
+  persistent local-time guidance.
+  **?** opens full-screen Help with command grammar and examples; Escape returns to the caller.
   **`rig tui commands`** lists everything it can do without launching it. **`rig ui open`** is
   unmaintained, best-effort, and replaced by the TUI, so never diagnose product behaviour from
   the web UI. The TUI plus Slack are the human surface; the CLI plus terminal are the agent surface.

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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 taxonomy: "skills"
 purpose: "Use when a permission policy is attached to a rig/seat (rig.yaml permission_policy:), or a user asks you to apply one, and you must translate that harness-neutral policy into the target harness's LIVE permission config — Claude settings.json / Codex config.toml / Pi run flags. Agent-driven and interactive: you read the policy, ground yourself in YOUR harness version, show the diff, and ask before writing. NOT for defining policies (that's the policy spec) and NOT a set-and-forget updater."
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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

@@ -42,16 +42,44 @@ Check readiness: configured, enabled, active, ready, reason, and next action.
 `indeterminate` is not ready. Follow the reported next inspection; do not enable
 or reconfigure a connector merely to make the check pass.
 
-Write the decision, evidence, and continuation in a body file. The sole outbound
-human-message primitive is:
+Author for the person reading on a phone: a short subject in `--summary`, then
+one complete brief in `--body-file`. State why it matters, your recommendation
+and material tradeoff, the bounded action if approved, and the choice requested.
+For an update, state the user-visible outcome and “No action needed.” Aim for
+roughly 100–150 words; this is guidance, not a semantic validator. Keep technical
+continuation, exact candidate/revision and evidence on the owning agent row and
+in the durable artifact behind `--evidence-ref`. A local path is not a phone link
+and Markdown evidence files are not automatically attached.
+
+For example, a synthetic brief could say:
+
+> The repaired status view is ready. I recommend updating this instance; live
+> status will briefly pause. Sessions will be preserved. Approve this instance
+> update, or hold? Supporting test detail follows in this thread.
+
+This example grants no authority. Choose `--human-intent decision` for a request
+or `--human-intent update` for a quiet FYI. Omission retains legacy decision
+behavior; words such as “FYI” and tags do not change intent.
+
+The sole outbound human-message primitive is:
 
 ```bash
 rig queue create --destination <entityId>@external \
-  --summary "<decision or update>" --body-file <packet-file> \
+  --human-intent decision --summary "<short subject>" --body-file <brief-file> \
   --evidence-ref <durable-evidence> --verify --json
 ```
 
-If an existing agent-owned row must wait, block it on the **new live qitem ID**
+An optional `--human-detail-file <path>` supplies one coherent supplemental
+reply in the same thread. Announce its purpose in the brief; the product also
+marks that a detail reply follows. The primary must already contain the complete
+scope, options and action. Do not split an agent dump blindly or move the essential
+choice into overflow. Rendering checks every part and its accessibility fallback
+before posting; an oversized request is refused with a field-specific correction,
+never silently clipped. Shorten the brief or related detail as directed. Inspect
+the failed row, then deliberately cancel/replace the authored request if its
+content needs correction; a timeout alone is never a reason to replace it.
+
+If an existing agent-owned row must wait for a **decision**, block it on the **new live qitem ID**
 (`rig queue block <work-id> --on <human-qitem-id> ...`), not on the human address.
 Completion of the human qitem resumes its dependants. Blocking on the human as
 well would issue another notification for the same decision.
@@ -66,7 +94,14 @@ or blindly resend because verification timed out.
 rig queue transitions <qitem-id>
 ```
 
-A correlated reply binds to that exact human and qitem and records the resolution
+For `update`, confirmed complete delivery may close the delivery obligation.
+It creates no approval obligation and cannot be used as a decision blocker.
+Delivered updates remain queryable for Feed; a failure or ambiguous send stays
+separate. A root message alone does not prove supplemental delivery. Retries
+reconcile stable part identities and send only missing parts. An FYI reply is
+not a human decision.
+
+For a decision, a correlated reply binds to that exact human and qitem and records the resolution
 that resumes the owner. Check the recorded result before claiming the decision
 arrived; a delivery receipt alone is not acceptance.
 

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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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-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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 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.5.12"
+version: "0.5.14"
 taxonomy: "skills"
 purpose: "Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication."
 files: