@openrig/cli 0.5.11 → 0.5.12

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Mike Schwarz
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/daemon/assets/plugins/openrig-core/skills/agent-operated-software/SKILL.md

@@ -72,10 +72,13 @@ Consumers fail closed on the shared proof. A filename or exit code is not conten
 
 ## Build with an agent SDLC
 
-Map work onto **intent -> plan -> spec -> build -> verify -> review -> QA -> done**. The human supplies
-steering, judgment, taste, and the call on irreversible ambiguity; agents perform and coordinate the
-technical work. Locks freeze the agreed spec and accepted delivery so multiple seats can work without
-guessing whether the target moved.
+Select the rigor required by the outcome and the project's policy. Scope relationships,
+attributed evidence-backed item judgment, and genuinely distinct higher judgment have separate
+owners. One item judgment derives its upstream readiness; agents do not synchronize parent
+checkboxes, queue tags, or status prose. Capture alone is not acceptance, and readiness does not
+publish or advance a workflow. Use `openrig-operating-model` and `rig proof --help` for the
+supported judgment, correction, and read path. Keep historical locks and evidence addressable.
+The human supplies steering, taste, and decisions the project's authority reserves for them.
 
 For studio applications, the running product is usually the best iteration surface. A separate mockup
 earns its cost only when it resolves a real design uncertainty that the running app cannot expose as

package/daemon/assets/plugins/openrig-core/skills/openrig-operating-model/SKILL.md

@@ -16,9 +16,8 @@ metadata:
 
 **Canonical term: the Operating Model.** How an OpenRig topology organizes every
 kind of context so that any agent — cold, fresh, or five generations in — can
-find what it needs and knows where to write what it learns. Everything below
-runs on **markdown files, scripts, and conventions only**; the `rig` verbs that
-formalize pieces of it are conveniences, never dependencies.
+find what it needs and knows where to write what it learns. Authored context stays in addressed Markdown and manifests. Supported writers
+record semantic judgments; their read models remain rebuildable from those artifacts.
 
 This skill owns the structure: trees, chains, tracing, and placement of authored
 knowledge. Resolve installed context through its current library addresses and
@@ -91,7 +90,8 @@ its body. Alongside it sit three files with different jobs and different writers
 | `SPEC.md` | the node — `intent:` composes, body specifies | the node's owner |
 | `NOTES.md` | **LIVED** — what actually happened doing it, in the doer's own words | whoever is doing it |
 | `PROOF.md` | evidence the thing does what was intended | the prover |
-| `PROGRESS.md` | authored acceptance checklist — each checkbox is a stored mark; roll-ups above those marks are derived | the scope's owner and provers |
+| `PROGRESS.md` | authored narrative and historical checklist marks; current proof readiness is derived from attributed judgments | the scope's owner and provers |
+| `proof/judgments/` | retained item judgment receipts written by `rig proof judge` | judges selected by the owning proof policy |
 
 **A scaffold may create `NOTES.md` and its starter instructions; its lived entries are never
 generated or projected.** It is the work tree's lived file, the way `LEARNED.md` is the topology
@@ -104,14 +104,31 @@ content addressable; use `NOTES.md` for the chain because its name works at ever
 | Level | `SPEC.md` — frontmatter `intent:` (why) + body (what must be built) | progress | kept true by |
 |---|---|---|---|
 | project | `intent:` only — stable, changes at real pivots | derived roll-up | the project's PM |
-| mission | `intent:` and proportional mission-level specification; organizes slices | authored checklist marks; roll-up derived | the mission's PM |
-| slice | `intent:` and the concrete slice specification | authored checklist marks; roll-up derived | the slice's owner |
-| proof item | *(inherits)* | **the checkbox — the stored acceptance mark** | the prover |
-
-**Progress checklists:** Checkbox items stored in a mission or slice
-`PROGRESS.md` are authored acceptance marks. In-process task tracking stays in the agent's own todo
-tool. Everything that rolls those marks up above the managed checklist is derived at render time,
-so authored checklists and the never-author-a-derived-roll-up rule are the same model.
+| mission | `intent:` and proportional mission-level specification; organizes slices | derived child readiness; distinct outcome judgment | the mission's PM |
+| slice | `intent:` and the concrete slice specification | derived proof readiness | the slice's owner |
+| proof item | authored promise in the proof contract | attributed evidence-backed judgment on that revision | the selected judge |
+
+**Current acceptance:** Scope relationships and policy are authored in manifests; an item
+judgment is recorded once against its promise, evidence and policy revision. Slice, mission
+and project readiness derive upward. A distinct outcome or publication decision remains its
+own authority. Queue ownership and generic `done` are custody facts, not proof acceptance.
+Historical checkbox marks stay readable without acquiring current item authority.
+
+Use `rig proof --help` for the supported write/read path. The project owner selects
+`proofPolicy.judges` in `project.yaml`, `mission.yaml` or `slice.yaml` (nearest wins),
+using exact actor addresses. There is no implicit fixed-role review conveyor.
+`rig proof judge mission/slices/slice#1 --verdict accept --reason 'Observed the outcome' --evidence proof/result.md`
+resolves the item identity, revision, evidence digests and retry identity. Evidence may be
+an existing legacy artifact or a non-code outcome. A patch-equivalent subject also names
+its actual comparison/adoption receipt with `--comparison`; the agent owns that judgment.
+`rig proof show` returns the current basis and retained receipt; it does not publish anything.
+
+Correct with `reject`, or `withdraw` when prior acceptance no longer stands. History stays
+in the addressed proof home. A repeated request returns its original receipt and current
+readiness; `--replace` deliberately reaffirms an old identical judgment after a correction.
+Changed promises, policy or evidence require a current judgment. Explicit optional
+`<!-- proof-item: stable-id -->` markers preserve identity across wording edits; the
+product otherwise derives identity from the full promise and reports ambiguity.
 
 **Intent composes; the body does not.** The trace reads the `intent:` FIELD at every altitude, so
 four levels unfurl as four sentences rather than four documents. The body is read only when you
@@ -125,17 +142,11 @@ real information, never silently skipped.
 **Legacy `README.md` nodes stay valid indefinitely** — the resolver prefers `SPEC.md` and falls
 back, so nothing is forced to migrate and dormant missions need no attention.
 
-**PROGRESS stays separate.** Its checklist items are authored stored marks; everything above those
-marks renders from them. Folding a derived roll-up into an authored file is how a stored derivation
-becomes a confident lie.
-
-Two directions on the same trees: intent/values/practice **compose downward**
-(you trace UP to read them); progress **aggregates upward** (never hand-written
-above the stored marks). **And PROGRESS above the managed checklist is a RENDER, not a
-file**: the checkbox is the stored acceptance mark;
-`scripts/compose.py progress` derives the roll-up tree at render time. Keep legacy
-embedded roll-ups as historical records when needed, but derive the current view
-from its marks rather than maintaining another copy by hand.
+**PROGRESS stays separate.** Narrative and legacy marks are retained testimony. For a
+project with selected proof policy, current readiness comes from `rig proof show` and the
+shared existing views, not hand-maintained parent checkboxes or copied status prose.
+`scripts/compose.py progress` remains a legacy checklist renderer; it does not certify
+attributed acceptance. Intent composes downward; proof readiness aggregates upward.
 
 **The axis behind the columns:** every context kind has a *template* half
 (what ships — SOP, the default culture) and a *learned* half (what living

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.11"
+version: "0.5.12"
 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-one-plus top-level verbs ship (capability canon refreshed through
-`capability-delta-v0.5.11`). Read this once for shape, and let it make you suspicious that a thing
+`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
 model IDs).
 
@@ -38,7 +38,10 @@ one command away. Your memory of the fleet is a claim about the past.
   and whether the thing you did an hour ago actually landed.
 - **`rig view list` / `rig view show <lens>`** — named lenses over coordination state: use
   `view show escalations` for owner attention, `view show pickup` for claimed-row state, and
-  `view show execution` for done/now/next. An `INDETERMINATE` cell stays unknown rather than
+  `view show execution` for done/now/next and current authored planning guidance with its
+  source. Mission and wave inspection shows admission and exit guidance; wave/slice details
+  include review decisions. Accepted-core guidance stays separate from full-contract proof,
+  live custody and executable dependencies. An `INDETERMINATE` cell stays unknown rather than
   being filled from memory. **`rig view register`** turns a query you keep re-running into a
   first-class view.
 - **`rig config`** — bare, with no arguments: every key, every current value, and where each came
@@ -152,10 +155,10 @@ you that is still running.
 
 ## Running a pipeline without relaying every step
 
-**Work does not only move because you move it.** A configured workflow routes each step to the next
-owner and wakes them. Where one exists, **you are exception handling, not the engine** — and if you
-find yourself hand-relaying every step, the loop has not been built yet, and building it is usually
-cheaper than being it.
+**A workflow remembers the plan and routes the next action; agents judge the outcome.** Its
+conditions, packets and waits carry decisions across returns. Inspect and revise the selected
+graph when reality changes, preserving completed work and current ownership. Repeated manual
+relay is a reason to inspect the available routing, not to surrender judgment to a fixed pipeline.
 
 - **`rig workflow specs`** — what can be started here, and which are shipped versus authored by
   this rig.
@@ -174,14 +177,50 @@ cheaper than being it.
   Inspect the exact exception occurrence and packet: resolved overdue work is reconciled without
   closing an overdue sibling. Registered-human fallback reports missing or ambiguous selection
   instead of inventing a recipient. Follow the state/error and `workflow show`/`trace` before retrying.
+- **Exception ownership before failure:** `workflow compile` and `workflow validate`
+  expose `exceptionReadiness`; `workflow show` renders it alongside existing exception
+  obligations and their queue/evidence pointers. Defining an ordinary role does not select
+  an exception owner. Follow `selection.source` to the owning `exception_routing.orchestrator_role`
+  field; project profiles own it unless the mission explicitly overrides the graph.
+  Selection, registered identity, genuine capability no-match, intended registered-human
+  fallback, ambiguous human selection and unavailable reads remain distinct. An advisory
+  before failure is not a requirement to keep every future role/model live. A failed read
+  cannot establish no-match or silently route to a human. If human selection is needed,
+  inspect `rig gateway human list --json`; select `workspace.operator_seat_name` when ambiguous.
 - **`rig workflow show` / `trace`** — what this instance is, and every step, actor and exit that
   got it here.
+- **`rig workflow revise <instance>`** — compare the bound graph with current authored
+  inputs before changing a progressed run. Ordinary show and TUI inspection distinguish
+  source-only edits (such as a catalog address) from executable changes. Preview names
+  changed steps, incompatibilities and an exact apply command. Supported revisions preserve
+  completed/live steps, receipts, required obligations and child custody; new work must
+  depend on unfinished work. A changed completed/live contract needs explicit reconsideration:
+  restore it and revise unstarted successors. Revision does not guess a migration or replay
+  accepted consequences. Exception-routing corrections can be adopted for future occurrences;
+  existing exception obligations retain custody. Editing source alone does not change the
+  running owner. Inspect `workflow show` after adoption and inspect each admitted queue row's
+  evidence. Authoritative workflow recovery/completion clears obsolete overdue occurrences;
+  an unresolved sibling stays visible. Closing a queue row alone is not semantic acceptance.
+- **`rig workflow operation <key>`** — recover the committed creation/revision effect after
+  a timeout or disconnected response, even if authored files have since changed. Retain the
+  operation key and repeat only the identical decision. The original receipt and current
+  instance are distinct; a terminal packet is not acceptance.
+  Project profiles and mission extension/override define outer steps; bound slice manifests
+  are not automatically nested execution. Waves are agent planning groups. The current
+  plan's admission, review and integration guidance returns in lifecycle packets and their
+  continuation, alongside the small revision move. Scope creation/move maintains manifest
+  membership; `--depends-on` is advisory build order, while `execution.depends_on` defines
+  executable prerequisites.
 - **`rig workflow continue`** — where you are in a run you have been handed. **It is read-only. It
   does not continue anything**, despite the name — `project` is the advance verb.
 - **`rig workflow route`** — the owner of the current step is gone; move *that step* to a live seat
   without pretending it completed.
-- **`rig workflow resume`** — the instance failed, you fixed the cause, redrive from the broken
-  step rather than re-running what already succeeded.
+- **`rig workflow resume`** — after correcting a failure, redrive its step while retaining
+  completed work. A dependency branch can fail while siblings remain live. Use
+  `--occurrence <failed-qitem-id>` to select that failure (required when several are
+  unresolved); its obsolete exception obligation closes in the redrive transaction,
+  while unresolved siblings stay visible. An identical occurrence/decision retry returns
+  the existing redrive without duplicating work.
 - **`rig workflow run` / `watch` / `list`** — run to completion with an exit code you can act on,
   watch it happen, or see what exists.
 
@@ -244,12 +283,16 @@ because someone lost work once.
   distinct no-op, and a timeout never proves down. Use command help for exact limits and recovery.
 - **`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.
-- **`rig crash-cart`** — the daemon is down or not answering: what was running before it died, and
-  where did the work stop. **NEW in v0.5.2: bare `rig` on a dead daemon opens the crash-cart
-  cockpit, and one Enter restores the whole fleet** — kernel-first, surviving panes ADOPTED live
-  (never clobbered), dead rigs restored from snapshots, non-resumable seats on a scrollable triage
-  list with their exact remediation, mid-run cancel with `c`. It only offers RESTORE on POSITIVE
-  down-evidence (confirmed-down vs cannot-verify are distinct screens).
+- **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.
+  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.
+- **`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
   you actually have and how old the newest is; `--intended-seats` records the topology roster the
   later restore must judge rather than treating every historical node as current.
@@ -327,6 +370,13 @@ scheme, and nothing downstream can see it.
   from the authored SPEC with a named advisory, and `contractSource` in the echo records which
   source actually bound. When someone later asks where the contract items came from, the drop's
   own echo is the answer — not a re-read of the files.
+- **`rig proof judge` / `rig proof show`** — record an attributed judgment on a contract item once,
+  then read derived proof, slice, mission and project readiness. The owning scope selects
+  `proofPolicy.judges` (nearest slice, mission or project policy wins); consult `rig proof --help`
+  for that setup and the item/evidence selectors. Accept, reject or withdraw against readable
+  evidence; corrections preserve history and unrelated judgments without ancestor status edits.
+  Non-code work can name its actual artifact instead of inventing a commit. Evidence capture,
+  policy acceptance, higher outcome judgment and publication remain separate decisions.
 - **`rig workspace doctor` / `validate`** — does the daemon agree with you about where the work
   tree is, and which files are missing the frontmatter their kind requires.
 - **`rig context work-install --project … --mission … --slice … [--deliver]`** — resolves the ordered
@@ -464,9 +514,15 @@ 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. `connections`
-  compares effective config with running services and human bindings, passively; dated
-  verification does not prove delivery. `timezone` gives persistent local-time guidance.
+  Tab completes commands and snapshot arguments; Recent opens original events. **CONFIG**
+  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.
   **`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.
@@ -498,7 +554,7 @@ database. It is one more set of primitives on a machine full of them.
   moving* falls out — which is the actual question behind every "is the rig stuck."
 - **"Is that seat stuck or thinking?"** — the row face answers this now (S04 pickup receipts):
   every list/show projection carries a derived `pickup` state — `working`, `stalled-after-claim`
-  (with its evidence named: claimed N min ago, zero substantive transitions since), `parked`, or
+  (with its evidence named: time since meaningful queue change and current activity confidence), `parked`, or
   `unclaimed` — and `rig view show pickup` lists every claimed row with it. The old by-hand join
   (capture + `claimedAt` arithmetic + `queue transitions`) is RETIRED as a first move; `rig
   capture` remains the second question (is the pane alive), never the state derivation.
@@ -506,9 +562,24 @@ database. It is one more set of primitives on a machine full of them.
   whether or not it has a wake; a strand reads `stalled-after-claim` with named evidence. Wake
   health and fired-but-unconsumed diagnosis come from `rig parked`, not the pickup projection.
   `queue transitions` remains the audit trail for WHAT happened, not the tool for deriving pickup.
-- **"Did that actually land?"** — `queue show` truncates the body and `queue list` can report
-  `bodyBytes=0`; neither means empty. **`sqlite3 "$OPENRIG_DB" "select length(body) …"` is the
-  only answer.** The CLI is a projection; the database is the thing.
+- **"Did that actually land?"** — `rig queue show <qitemId>` gives a bounded preview,
+  original byte size and the exact expansion command. Read the complete original record with
+  `rig queue show <qitemId> --full --json`; a preview or a compact list is not the whole body.
+  Delivery status is separate from content: inspect its receipt before claiming it was consumed.
+- **"What am I waiting on?"** — the queue row's `waiting` view derives its owner, exact blocker
+  and blocker owner, last meaningful change, activity confidence and next backstop from live
+  domain facts. A failed handoff names the delivery ladder before the later unclaimed safety
+  net; its due time is earliest eligibility, with suspension or current recovery disposition
+  shown explicitly. The executing scheduler still checks live state at that time. A working activity observation is not proof of task progress; unknown stays
+  unknown. A repeating wait sends one compact notice per blocker transition, with the existing
+  stuck sweep owning a failed or unconsumed notice after the pickup grace. Real changes use the
+  event path; scheduler reconciliation repairs missed events. A returned result and its dependent
+  resumes share one delivery while retaining their separate rows and receipts.
+  For a workflow waiting on a slice outcome, add `--wait-for-proof <slice-scope>` to
+  `rig workflow project --exit waiting`: it binds the current proof `attention` revision.
+  Proof events invalidate that observation; the authored wait timer repairs a missed event
+  by reading the same current proof source. Inspect `rig workflow project --help` for the
+  required instance, packet and actor arguments; this opt-in does not accept a slice.
 - **"What does this whole corpus say about X?"** — bigger than your window, so do not read it.
   **Fan out**: one region per subagent, N in parallel, each returning a structured report, and you
   read reports rather than sources. **This is the move that beats your own context limit** — it

package/daemon/context-packs/skills/agent-operated-software/SKILL.md

@@ -72,10 +72,13 @@ Consumers fail closed on the shared proof. A filename or exit code is not conten
 
 ## Build with an agent SDLC
 
-Map work onto **intent -> plan -> spec -> build -> verify -> review -> QA -> done**. The human supplies
-steering, judgment, taste, and the call on irreversible ambiguity; agents perform and coordinate the
-technical work. Locks freeze the agreed spec and accepted delivery so multiple seats can work without
-guessing whether the target moved.
+Select the rigor required by the outcome and the project's policy. Scope relationships,
+attributed evidence-backed item judgment, and genuinely distinct higher judgment have separate
+owners. One item judgment derives its upstream readiness; agents do not synchronize parent
+checkboxes, queue tags, or status prose. Capture alone is not acceptance, and readiness does not
+publish or advance a workflow. Use `openrig-operating-model` and `rig proof --help` for the
+supported judgment, correction, and read path. Keep historical locks and evidence addressable.
+The human supplies steering, taste, and decisions the project's authority reserves for them.
 
 For studio applications, the running product is usually the best iteration surface. A separate mockup
 earns its cost only when it resolves a real design uncertainty that the running app cannot expose as

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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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.5.11"
+version: "0.5.12"
 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.11"
+version: "0.5.12"
 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: