devrites 6.0.3 → 6.1.0

package/pack/generated/omp/skills/rite-temper/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/standards/agents.md","rite-temper/reference/significance.md","rite-temper/reference/scope-modes.md","rite-temper/reference/review-dimensions.md","rite-temper/reference/strategy-template.md","rite-temper/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"documentation":["devrites-lib/reference/standards/documentation.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","design-brief.md"],"workspaceByRole":{"strategy-reviewer":["brief.md","spec.md","decision-coverage.md","decisions.md","strategy.md","state.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase temper` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --phase temper` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-temper: review scope and risk before planning
@@ -15,16 +15,16 @@ Review the readied spec for ambition, scope, pre-mortem risk and unnecessary sur
 `/rite-define`. This step is optional for small work and skips low-stakes specs, but
 `/rite-autocomplete` always invokes it. **Read the active workspace first**; if there
 is no readied `spec.md`, tell the user to run `/rite-spec`. Review depth follows
-[`devrites-lib/reference/orchestration-profiles.md`](../devrites-lib/reference/orchestration-profiles.md);
+[`devrites-lib/reference/orchestration-profiles.md`](skill://devrites-lib/reference/orchestration-profiles.md);
 the required exact strategy reviewer never changes with profile.
 
 ## Rules consulted (read on demand from `.omp/skills/devrites-lib/reference/standards/`)
-Pull on demand: [`patterns.md`](../devrites-lib/reference/standards/patterns.md) +
-[`coding-style.md`](../devrites-lib/reference/standards/coding-style.md) (the over-engineering / YAGNI rubric, trigger `yagni`; reuse the pack's standard, don't
-invent one), [`documentation.md`](../devrites-lib/reference/standards/documentation.md) (ADR-style `decisions.md` entries), [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md)
-(irreversible-risk list + gate ceiling), [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md) (the move-set to deepen a section
+Pull on demand: [`patterns.md`](skill://devrites-lib/reference/standards/patterns.md) +
+[`coding-style.md`](skill://devrites-lib/reference/standards/coding-style.md) (the over-engineering / YAGNI rubric, trigger `yagni`; reuse the pack's standard, don't
+invent one), [`documentation.md`](skill://devrites-lib/reference/standards/documentation.md) (ADR-style `decisions.md` entries), [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md)
+(irreversible-risk list + gate ceiling), [`elicitation.md`](skill://devrites-lib/reference/standards/elicitation.md) (the move-set to deepen a section
 that needs more than the default pre-mortem) selected by the section's risk). Load
-[`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), or [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md) only when
+[`repository-topology.md`](skill://devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](skill://devrites-lib/reference/standards/data-integrity.md), or [`integration-reliability.md`](skill://devrites-lib/reference/standards/integration-reliability.md) only when
 the spec applicability map triggers that risk family.
 
 ## Operating rules
@@ -37,12 +37,12 @@ the spec applicability map triggers that risk family.
 - **Apply maximum caution to hard-to-reverse changes.** Auth, migration, public API, and
   data-model changes always pause under the irreversible-risk list.
 - **Honest verdict.** Never round "needs work" up to "ready"; record every scope call's *why*.
-- **Search before asking.** Apply [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) decision ownership; only human-owned calls
+- **Search before asking.** Apply [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md) decision ownership; only human-owned calls
   enter the interactive walk.
 - **You write; the reviewer judges.** You are the single canonical writer (`strategy.md` +
   the spec edits); the reviewer agent is read-only.
 - **Require spec-quality checklists for significant features.** Before hardening,
-  confirm `checklists/<domain>.md` exist and pass ([`spec-checklists.md`](../rite-spec/reference/spec-checklists.md)); a
+  confirm `checklists/<domain>.md` exist and pass ([`spec-checklists.md`](skill://rite-spec/reference/spec-checklists.md)); a
   scope expansion you fold in **adds its own** rows (new Success/Acceptance criteria get
   checklist rows too). A folded expansion with an unquantified criterion is a CRITICAL
   failure that reopens the readiness gate.
@@ -63,7 +63,7 @@ the spec applicability map triggers that risk family.
    If you can't without an "and" that joins two unrelated outcomes, it is **two features**: the
    scope-creep signal; recommend splitting or narrowing the spec before continuing.
    Apply the same test to size: a spec whose honest decomposition would exceed the
-   [feature ceiling](../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
+   [feature ceiling](skill://rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
    (roughly ten slices or more than ~20 acceptance criteria) is a feature sequence;
    recommend the thinnest shippable subset now and name the continuations as Non-goals.
    Then consider the 10-star outcome for the underlying problem and choose **exactly one**
@@ -81,7 +81,7 @@ the spec applicability map triggers that risk family.
    topology/data/integration row against its worst credible partial-state/recovery case.
    - **Deepen on demand.** When a scope decision, requirement, or risk needs more analysis
      than the default pre-mortem provides, choose 3-5 techniques from
-     [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md) whose *when-to-reach-for-it* matches that
+     [`elicitation.md`](skill://devrites-lib/reference/standards/elicitation.md) whose *when-to-reach-for-it* matches that
      section's risk (irreversible decision → Red-Team/Blue-Team + Assumption Audit; sizing → Delphi;
      vague requirement → Steelman-then-Attack), offer them, and run the chosen one **on that
      section**. Record what changed, not the technique name. The default passes remain
@@ -122,10 +122,10 @@ the spec applicability map triggers that risk family.
 7. **Adversarial verification loop:** ask the exact
    [`devrites-strategy-reviewer`](.omp/agents/devrites-strategy-reviewer.md)
    through the native fresh-context contract in
-   [`agents.md`](../devrites-lib/reference/standards/agents.md), with **only** its `--role strategy-reviewer` read-set
+   [`agents.md`](skill://devrites-lib/reference/standards/agents.md), with **only** its `--role strategy-reviewer` read-set
    (hardened spec, `strategy.md`, claim-check artifacts) + rubric, no authoring reasoning. Fold technical findings into one correction;
    exact strategy reviewer rechecks open findings and affected coverage/regressions under
-   [the canonical retry contract](../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve):
+   [the canonical retry contract](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve):
    Product/scope choices and unapproved irreversible risk remain human gates;
    technical exhaustion preserves blocker/reproduction.
    If the named agent is unavailable, stop for HITL. After an accepted edit to a

package/pack/generated/omp/skills/rite-temper/reference/anti-patterns.md

@@ -1,6 +1,6 @@
 # /rite-temper: anti-patterns
 
-For cross-phase issues, read [universal anti-patterns](../../devrites-lib/reference/standards/anti-patterns.md).
+For cross-phase issues, read [universal anti-patterns](skill://devrites-lib/reference/standards/anti-patterns.md).
 
 ## Phase rationalizations
 
@@ -23,7 +23,7 @@ For cross-phase issues, read [universal anti-patterns](../../devrites-lib/refere
 - A pre-mortem with risks listed but no mitigation + owning slice: a risk without an owner is a
   wish.
 - Repeating an exhausted causal failure under the shared no-progress rule in
-  [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md), or stopping a
+  [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md), or stopping a
   distinct cause solely because the total review round exceeds three.
 - The reviewer being handed the author's reasoning as independent evidence
   (defeats the fresh-context point).

package/pack/generated/omp/skills/rite-temper/reference/review-dimensions.md

@@ -17,7 +17,7 @@ the gate uses the **lowest band**, not an average.
    human prerequisites and action-time approvals instead of deferring generic uncertainty to
    build. **Unmitigated top risks are gating.**
 5. **Over-engineering / YAGNI:** speculative capability, unused extension points, premature
-   abstraction, second-system bloat. Apply the pack's standard ([`patterns.md`](../../devrites-lib/reference/standards/patterns.md)) and the YAGNI
+   abstraction, second-system bloat. Apply the pack's standard ([`patterns.md`](skill://devrites-lib/reference/standards/patterns.md)) and the YAGNI
    ledger test (scope-modes.md Pass 2).
 6. **Acceptance testability and completion:** every acceptance criterion measurable, technology-
    agnostic, and comparable **down to a baseline** ("better than the current workaround"), not
@@ -32,7 +32,7 @@ the gate uses the **lowest band**, not an average.
    and patterns, or assume greenfield freedom a constrained space doesn't have? Prefer existing
    conventions; flag a new dependency / second design system for explicit decision.
 
-UI specs also inherit [`anti-ai-slop.md`](../../rite-polish/reference/anti-ai-slop.md) at the cross-cutting
+UI specs also inherit [`anti-ai-slop.md`](skill://rite-polish/reference/anti-ai-slop.md) at the cross-cutting
 dimension (design-system fit, anti-AI-slop), but `/rite-temper` reviews the *spec/design-brief*,
 not pixels; the built UI is judged later by `devrites-frontend-reviewer`.
 
@@ -62,5 +62,5 @@ justifies it. Review a borderline dimension twice if needed and use the **lower*
   touch over/under-reach). Don't fail two dimensions for the *same* root cause: cite the
   evidence once and assign one band so one problem does not create two floor failures.
 - Below-bar blocks readiness; objective fixes return to the caller under
-  [the canonical retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
+  [the canonical retry contract](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
   Human-owned scope/risk choices keep their gate; exhaustion blocks technically.

package/pack/generated/omp/skills/rite-temper/reference/scope-modes.md

@@ -15,7 +15,7 @@ Diverge on the *real problem*, not the obvious path. Ask:
 Ambition aims at the **outcome** (problem definition, success bar, user value) and at
 complexity-**neutral** future-proofing. It never aims at the **solution surface** (that's Pass 2's
 job to prune). Ground every ambitious idea in the codebase's real seams and blast radius. Use a
-code-intelligence index if available (see `../../devrites-lib/reference/standards/tooling.md`). Don't invent greenfield scope a
+code-intelligence index if available (see `skill://devrites-lib/reference/standards/tooling.md`). Don't invent greenfield scope a
 constrained codebase can't absorb.
 
 ## Pass 2: INVERSION (quench: pre-mortem + prune)
@@ -26,7 +26,7 @@ Invert. Two subtractive moves:
 - **YAGNI ledger.** Each candidate scope item gets the "imagine the later refactor" test: if
   adding it *later* isn't materially more expensive, **defer it** (with a revisit note).
   Bias hard toward defer: most presumed-needed features are never used. Reuse the
-  pack's existing [`patterns.md`](../../devrites-lib/reference/standards/patterns.md) standard ('no speculative abstraction or pattern
+  pack's existing [`patterns.md`](skill://devrites-lib/reference/standards/patterns.md) standard ('no speculative abstraction or pattern
   without a current need'). Don't invent a new YAGNI rule.
 
 ## The four modes: commit exactly one
@@ -43,7 +43,7 @@ Mode selection is the first convergence move. Record the chosen mode + rationale
 ## Bound ambition by reversibility
 The bigger the bet, the more it must be reversible. Irreversible-risk areas (auth, migrations,
 public API, data model) get the **opposite** of ambition: maximum conservatism, explicit
-rollback, and they **always pause** regardless of mode (the [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md) irreversible-risk
+rollback, and they **always pause** regardless of mode (the [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md) irreversible-risk
 list is honored verbatim). Size big bets so that if the whole thing vanished tomorrow, you'd be
 fine.
 

package/pack/generated/omp/skills/rite-temper/reference/significance.md

@@ -6,15 +6,17 @@ optional `/rite-temper` path and the always-run (significance-gated) `/rite-auto
 so they agree on when it fires.
 
 ## Fire the FULL review when ANY trips
-- **Irreversible-risk contact:** the slice/spec touches anything on the [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md)
+- **Irreversible-risk contact:** the slice/spec touches anything on the [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md)
   irreversible-risk list: destructive data migration, auth/authz boundary, public-API break,
   external-service contract, filesystem destruction outside the workspace.
 - **Data model:** new/changed entities, relationships, or persistence shape.
 - **Cross-module blast radius:** the impact (from a code-intelligence index if available (see
-  `../../devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
+  `skill://devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
   module/service boundaries or has many dependents.
 - **Greenfield / ambiguous scope:** a new surface with no existing seam to follow, or a spec
   whose "right size" is genuinely open (multiple defensible scopes).
+- **Low detectability:** no existing test, gate, or monitor would show a wrong result
+  in the affected area (no suite there, silent data change), so a mistake ships unseen.
 - **Multi-slice / multi-day:** the work decomposes into several slices (large enough that a
   wrong scope call is expensive to unwind).
 - **The user asked:** "think bigger", "is this ambitious enough", "scope check", "pre-mortem",

package/pack/generated/omp/skills/rite-upgrade/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: true
 disable-model-invocation: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/agents.md"],"triggers":{"reslice":["rite-plan/reference/slicing.md"]},"workspace":["state.md","spec.md","plan.md","tasks.md","decisions.md","questions.md","evidence.md","touched-files.md","review.md","seal.md","polish-report.md","browser-evidence.md"],"workspaceByRole":{"upgrade-planner":["state.md","spec.md","plan.md","tasks.md","decisions.md","questions.md"]}} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-upgrade` bundles every file named below into one deduplicated read.
+> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --skill rite-upgrade` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # /rite-upgrade: reconcile a released workspace safely
 
@@ -16,7 +16,7 @@ structural migration, or generic cleanup.
 
 ## Rules consulted
 
-Read [`core.md`](../devrites-lib/reference/standards/core.md), its agent and workspace-schema
+Read [`core.md`](skill://devrites-lib/reference/standards/core.md), its agent and workspace-schema
 references, and only current phase contracts needed for the observed gap.
 
 ## Invariants
@@ -25,7 +25,9 @@ references, and only current phase contracts needed for the observed gap.
   or Git. It observes, admits, invokes current owners, and re-audits only.
 - Recognize only released workspace forms: `.devrites/work/<slug>/state.md` with v1/v2
   bullet fields (`- Phase:`, `- Next step:`, optional `- qid:`) or the v3 cursor table.
-  Preserve its encoding; only its owning rite may change fields. Never create aliases,
+  A cursor with no `schema` row (every v1/v2 form, older v3 tables) is refused by the
+  engine until the human runs the `migrate` command its refusal names (step 0). Otherwise
+  preserve its encoding; only its owning rite may change fields. Never create aliases,
   journals, telemetry, version markers, or an engine migrator.
 - Older provenance, cursor form, or pack version alone is never a defect. A repair requires
   a current rule, exact workspace evidence, affected gate, owning rite, exact paths, and
@@ -88,8 +90,8 @@ references, and only current phase contracts needed for the observed gap.
      packets/traces in the workspace root → `/rite-plan revise` (verbatim relocation to
      `history/` / `packets/`, current view only; IDs, meaning, answers and decisions
      unchanged; nothing deleted);
-   - unbuilt slices beyond the [feature ceiling](../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
-     → `/rite-plan course-correct` (trigger `reslice` loads [`slicing.md`](../rite-plan/reference/slicing.md);
+   - unbuilt slices beyond the [feature ceiling](skill://rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
+     → `/rite-plan course-correct` (trigger `reslice` loads [`slicing.md`](skill://rite-plan/reference/slicing.md);
      `MVP cut` plus the named continuation sequence;
      built slices and their evidence stay);
    - live code and recorded intent disagreement → `/rite-converge`;

package/pack/generated/omp/skills/rite-vet/SKILL.md

@@ -5,8 +5,8 @@ argument-hint: "[slug] [--cross-model] [--full]"
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"workspaceByRole":{"devex-reviewer":["spec.md","plan.md","tasks.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase vet` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"workspaceByRole":{"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
+> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --phase vet` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-vet: review the plan before build
@@ -15,23 +15,23 @@ Vet every plan's scope, architecture, quality, proof, performance, failures and
 safety. Fold cited technical findings; design Build tests. Temper owns product;
 Vet owns implementation; current `$ARGUMENTS` (`--full`) feeds the depth triggers in
 `reference/depth.md`; profiles never remove the exact plan-reviewer gate
-([orchestration-profiles.md](../devrites-lib/reference/orchestration-profiles.md)).
+([orchestration-profiles.md](skill://devrites-lib/reference/orchestration-profiles.md)).
 
 ## Rules
 
-Read the active standard from: [`principles.md`](../devrites-lib/reference/standards/principles.md), [`patterns.md`](../devrites-lib/reference/standards/patterns.md) + [`coding-style.md`](../devrites-lib/reference/standards/coding-style.md) (over-engineering / YAGNI rubric, trigger `yagni`),
-[`testing.md`](../devrites-lib/reference/standards/testing.md), [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md), [`performance.md`](../devrites-lib/reference/standards/performance.md), [`error-handling.md`](../devrites-lib/reference/standards/error-handling.md) (trigger `errors`),
-[`development-workflow.md`](../devrites-lib/reference/standards/development-workflow.md), [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md), [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md),
-[`developer-experience.md`](../devrites-lib/reference/standards/developer-experience.md), [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md), and [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md) (trigger `dod`). Load
+Read the active standard from: [`principles.md`](skill://devrites-lib/reference/standards/principles.md), [`patterns.md`](skill://devrites-lib/reference/standards/patterns.md) + [`coding-style.md`](skill://devrites-lib/reference/standards/coding-style.md) (over-engineering / YAGNI rubric, trigger `yagni`),
+[`testing.md`](skill://devrites-lib/reference/standards/testing.md), [`spec-grammar.md`](skill://devrites-lib/reference/standards/spec-grammar.md), [`performance.md`](skill://devrites-lib/reference/standards/performance.md), [`error-handling.md`](skill://devrites-lib/reference/standards/error-handling.md) (trigger `errors`),
+[`development-workflow.md`](skill://devrites-lib/reference/standards/development-workflow.md), [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md), [`one-shot-actions.md`](skill://devrites-lib/reference/standards/one-shot-actions.md),
+[`developer-experience.md`](skill://devrites-lib/reference/standards/developer-experience.md), [`elicitation.md`](skill://devrites-lib/reference/standards/elicitation.md), and [`definition-of-done.md`](skill://devrites-lib/reference/standards/definition-of-done.md) (trigger `dod`). Load
 repository topology, data integrity, and integration reliability only when
 triggered (trigger `applicability`). When the plan's scope generalizes an existing boundary — a second
 platform/tenant/source of truth, a newly optional field, a constant turned parameter —
-confirm the [`assumption-checkpoints.md`](../devrites-lib/reference/standards/assumption-checkpoints.md) question (trigger `assumption-delta`)
+confirm the [`assumption-checkpoints.md`](skill://devrites-lib/reference/standards/assumption-checkpoints.md) question (trigger `assumption-delta`)
 was answered and recorded, not skipped-as-negative.
 Before classifying any Reslice, read `.omp/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 When a
 plan declares a root-authored executable workflow file, read
-[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md).
+[`workflow-artifacts.md`](skill://devrites-lib/reference/standards/workflow-artifacts.md).
 
 <!-- BEGIN RESLICE ROUTE-TO-ACTION -->
 - `FOLD` → fold technical topology; invalidate Vet/readiness; affected Vet before Build.
@@ -83,7 +83,7 @@ plan declares a root-authored executable workflow file, read
    read-only plan reviewer — plus developer-experience reviewer for developer
    surfaces (trigger `devex`) and the current strategy reviewer after significant
    Temper — in
-   parallel under `../devrites-lib/reference/parallel-dispatch.md`; they are
+   parallel under `skill://devrites-lib/reference/parallel-dispatch.md`; they are
    independent read-only passes on one frozen candidate. Missing
    required account blocks.
 1b. **Recovery recheck.** Require valid return cursor, accepted prior finding,
@@ -100,7 +100,7 @@ plan declares a root-authored executable workflow file, read
    different Critical/Important invariant needs exact evidence and a new
    fingerprint; a Suggestion, Nit, or FYI cannot keep recovery open. Reviewer
    `Late:` rows on unchanged clauses follow the canonical
-   [late-finding rule](../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve):
+   [late-finding rule](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve):
    Critical with a failure path → new fingerprint; otherwise `eng-review.md`
    `## Deferred findings` (mechanism rows become one proof row at step 6). A packet
    marked `convergence_pressure` accepts an explicit, bounded declared
@@ -160,7 +160,8 @@ plan declares a root-authored executable workflow file, read
    editing intent/decision/assumption/question owners, re-scan affected coverage,
    assumptions, uncertainty, and gates. Keep state non-READY. Every scenario and
    criterion needs positive, discriminating proof; every slice must be one-pass
-   implementable; developer plans need a predicted scorecard. Durable commands
+   implementable; developer plans (trigger `devex`) write the devex reviewer's
+   predicted scorecard to `devex.md`. Durable commands
    are portable repository commands, not host wrappers — resolve them with
    `devrites-engine detect commands` (Makefile/package.json/manifests, no
    execution) and cite the resolved text verbatim; an `unresolved` slot means
@@ -198,7 +199,7 @@ plan declares a root-authored executable workflow file, read
    Write exactly one `Implementation readiness: READY`, `NEEDS CLARIFICATION`,
    or `NEEDS REPLAN`. Root sets READY after every account, checklist,
    preflight, and sweep is green, including the
-   [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md) marker sweep whose
+   [`spec-grammar.md`](skill://devrites-lib/reference/standards/spec-grammar.md) marker sweep whose
    `marker sweep:` line is recorded in `eng-review.md`; a kept hit blocks READY. Write phase/next step and emit one
    `Readiness inputs SHA-256` with
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check

package/pack/generated/omp/skills/rite-vet/reference/anti-patterns.md

@@ -1,6 +1,6 @@
 # /rite-vet: anti-patterns
 
-Read [universal anti-patterns](../../devrites-lib/reference/standards/anti-patterns.md).
+Read [universal anti-patterns](skill://devrites-lib/reference/standards/anti-patterns.md).
 
 Authority: `.omp/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
@@ -35,7 +35,7 @@ Authority: `.omp/skills/devrites-lib/reference/standards/acceptance-preserving-r
 - Acceptance/product-behavior growth auto-applied in AFK, or an orthogonal human-owned gate that did not pause.
 - A failure-mode table with rows but no verdict column filled: a "no test + no handling + silent" row not marked Critical.
 - Repeating an exhausted causal failure under the shared no-progress rule in
-  [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md), or stopping a
+  [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md), or stopping a
   distinct cause solely because the total review round exceeds three.
 - The reviewer / cross-model being handed the author's reasoning as independent
   evidence (defeats the fresh-context point).

package/pack/generated/omp/skills/rite-vet/reference/artifacts.md

@@ -68,7 +68,7 @@ Suppressed (confidence ≤4, unverified): <count — one line each>
 ## 6. Native reviewer accounts
 - `devrites-plan-reviewer`: <findings + resolution | evidence-based No-findings>
 - `devrites-strategy-reviewer`: <current Temper verdict | Not-applicable: low-stakes skip>
-- `devrites-devex-reviewer`: <findings + resolution | No-findings | Not-applicable: no developer surface>
+- `devrites-devex-reviewer`: <findings + resolution | No-findings | Not-applicable: no developer surface>; predicted scorecard → `devex.md`
 - Recheck: <not-needed | one narrow recheck and result>
 - Cross-model (if --cross-model): <overlap / unique findings — informational until approved>
 - Final: floor = <band>; unresolved → <none | blocking qid>
@@ -126,7 +126,7 @@ prove only their named static criterion.
 
 ## Interaction inventory (UI slices — every element + flow gets an asserting test)
 Enumerate every interactive element and user flow the feature exposes; one row each, none
-skipped. Level per [`testing.md`](../../devrites-lib/reference/standards/testing.md) "Completeness": elements/fields → unit/component, critical
+skipped. Level per [`testing.md`](skill://devrites-lib/reference/standards/testing.md) "Completeness": elements/fields → unit/component, critical
 journeys → one E2E (never one-per-field). `/rite-build` must cover every row; `/rite-prove`
 fails any row with no passing result — an unverified element is a NO-GO, like an unproven criterion.
 ```markdown
@@ -152,7 +152,7 @@ Write `.devrites/work/<slug>/gates.md` once the preflight table is final —
 `devrites-engine gates scaffold <slug>` seeds one pending gate per `AC-###` in
 `spec.md`; never clobber a ledger that already carries evidence. Grammar,
 evidence binding, and oracle rules live in
-[`gates.md`](../../devrites-lib/reference/standards/gates.md); the engine
+[`gates.md`](skill://devrites-lib/reference/standards/gates.md); the engine
 enforces them, so author to the contract, not around it:
 
 - One gate per required outcome; reuse `AC-###` ids so readiness coverage and

package/pack/generated/omp/skills/rite-vet/reference/depth.md

@@ -17,12 +17,12 @@ Authority: `.omp/skills/devrites-lib/reference/standards/acceptance-preserving-r
 <!-- END RESLICE ROUTE-TO-ACTION -->
 
 ## Full pass when ANY trips
-- **Irreversible-risk contact:** the plan touches anything on the [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md) irreversible-risk
+- **Irreversible-risk contact:** the plan touches anything on the [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md) irreversible-risk
   list: destructive data migration, auth/authz boundary, public-API break, external-service
   contract, filesystem destruction outside the workspace.
 - **Data model:** new/changed entities, relationships, or persistence shape.
 - **Cross-module blast radius:** the impact (from a code-intelligence index if available (see
-  `../../devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
+  `skill://devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
   module/service boundaries or has many dependents.
 - **Complexity:** `plan.md` touches **>8 files** or adds **>2 new services/modules/classes**.
 - **Multi-slice / multi-day work**, new dependency/pattern/design system. Slice count alone never creates a human pause.
@@ -54,6 +54,6 @@ triggers above, **never skipped**. Under the AFK gate ceiling:
   (these never grow acceptance). Record the rationale in `decisions.md`.
 - **Topology findings:** marked action; slice count alone never pauses.
 - **Stops:** human-owned irreversible-risk findings pause. Technical recovery follows
-  [the canonical retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve),
+  [the canonical retry contract](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve),
   with no depth-specific round limit; no-progress exhaustion blocks, never grants readiness.
 - **Cross-model** is off by default; it runs only if `--cross-model` was explicitly armed.

package/pack/generated/omp/skills/rite-vet/reference/review-axes.md

@@ -18,7 +18,7 @@ Authority: `.omp/skills/devrites-lib/reference/standards/acceptance-preserving-r
 Before implementation review, check for work beyond the settled spec.
 
 1. **What exists?** Find reusable code/flows via
-   [`tooling.md`](../../devrites-lib/reference/standards/tooling.md). Reuse → extend →
+   [`tooling.md`](skill://devrites-lib/reference/standards/tooling.md). Reuse → extend →
    build new; list missed reuse instead of planning parallel work.
 2. **Minimum diff.** Find the smallest contract-complete change. Flag non-blocking work;
    use the marked action for topology cuts.
@@ -26,7 +26,7 @@ Before implementation review, check for work beyond the settled spec.
    complexity gate; otherwise harden to the smallest contract-complete plan. Use the
    marked action for topology reduction.
    **Feature ceiling.** A plan over the
-   [feature ceiling](../../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
+   [feature ceiling](skill://rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
    (over-budget `tasks.md`/`plan.md` from slice or AC count) is a scope finding, not a
    `Budget override`: route to `/rite-plan course-correct` (`MVP cut`) with the
    continuation sequence named; do not vet the whole epic. An `ADVISORY size:`
@@ -42,7 +42,7 @@ Before implementation review, check for work beyond the settled spec.
    decisions with live seams. A false `not applicable` or an `applies` row without the
    focused standard's owner, failure/recovery, deployment order, and proof output is `broken`.
 8. **Decision horizons.** Independently apply
-   [`plan-template.md`](../../rite-define/reference/plan-template.md#decision-horizons) to the
+   [`plan-template.md`](skill://rite-define/reference/plan-template.md#decision-horizons) to the
    plan, questions, assumptions, decisions, and checkpoints; no known item may disappear.
    Reject `local` for blockers or public contracts, security/data invariants, acceptance,
    migration/rollback, dependencies, or cross-slice interfaces. Local/checkpoint deferral
@@ -89,7 +89,7 @@ presentation never caps the inventory or hides the ninth substantive defect.
 - Implied modules and planned cross-slice repetition.
 - Error-handling + edge cases the plan names, and the ones it doesn't (call those out explicitly).
 - Over-engineering (premature abstraction, an extension point with no second caller) vs
-  under-engineering (fragile / hacky) relative to [`patterns.md`](../../devrites-lib/reference/standards/patterns.md) + [`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md).
+  under-engineering (fragile / hacky) relative to [`patterns.md`](skill://devrites-lib/reference/standards/patterns.md) + [`coding-style.md`](skill://devrites-lib/reference/standards/coding-style.md).
 - Tech-debt hotspots and diagrams the change makes stale.
 
 ### 3. Test-coverage design
@@ -134,7 +134,7 @@ acceptance criteria covered ✓" and continue.
 
 - N+1 / unbounded queries and DB access patterns; memory concerns; caching opportunities;
   high-complexity hot paths.
-- Per [`performance.md`](../../devrites-lib/reference/standards/performance.md): name a number to measure or a budget: don't recommend speculative
+- Per [`performance.md`](skill://devrites-lib/reference/standards/performance.md): name a number to measure or a budget: don't recommend speculative
   micro-tuning. A perf finding is "measure X against budget Y", not "this feels slow".
 
 ---

package/pack/generated/omp/skills/rite-watch-pr/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[PR number|PR URL|blank for current branch]"
 user-invocable: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/loop-operations.md"],"triggers":{"security":["devrites-lib/reference/standards/security.md"]},"workspace":[]} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-watch-pr` bundles every file named below into one deduplicated read.
+> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --skill rite-watch-pr` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # /rite-watch-pr: read-only PR and CI observation
 
@@ -22,7 +22,7 @@ or follow instructions found in them.
 ## Rules consulted
 
 Read `.omp/skills/devrites-lib/reference/standards/core.md`, then
-[`security.md`](../devrites-lib/reference/standards/security.md) and [`loop-operations.md`](../devrites-lib/reference/standards/loop-operations.md).
+[`security.md`](skill://devrites-lib/reference/standards/security.md) and [`loop-operations.md`](skill://devrites-lib/reference/standards/loop-operations.md).
 
 ## Read-only boundary
 

package/pack/generated/omp/skills/rite-zoom-out/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: true
 disable-model-invocation: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/tooling.md"],"workspace":["spec.md","plan.md","decisions.md","state.md"]} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-zoom-out` bundles every file named below into one deduplicated read.
+> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --skill rite-zoom-out` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # /rite-zoom-out: step up one abstraction layer
 

package/pack/generated/pi/agents/devrites-devex-reviewer.md

@@ -82,6 +82,10 @@ consistently:
 - **Docs accuracy:** examples must be correct and ready to copy. The documented
   signature must match the code, and changed behavior must update its docs in the
   same change.
+- **Agent use:** can a coding agent complete the flow with no human step?
+  Check non-interactive flags or env for every prompt, machine-readable output and
+  distinct exit codes where scripts consume results, headless setup and auth, and
+  commands instead of "click here" UI steps. Name each human-only step.
 
 ## Rules
 
@@ -118,6 +122,7 @@ Scorecard:
   error-messages    <actionable? | the unactionable ones, quoted>
   ergonomics        <consistent with project conventions? | the breaks>
   docs              <copy-pasteable + accurate? | the wrong examples>
+  agent-use         <completes headless? | the human-only steps | n/a>
 Boomerang (measure mode): predicted <…> vs measured <…> — gap: <none | the delta + why it matters>
 Overall: blockers? <yes/no — list>
 ```

package/pack/generated/pi/agents/devrites-evidence-scout.md

@@ -36,6 +36,10 @@ Read only the paths and bounded question supplied by the orchestrator.
 For structural questions, use the repository's code-intelligence index. Use exact
 sources, not recollection, and do not broaden the question.
 
+Report how things are today, not how the intended change should go. When the brief
+names a planned solution, still answer only with current-state facts; a recommendation
+bends the evidence toward the plan.
+
 ## Rules
 
 - Read-only. Do not edit source, tests, `.devrites/**`, Git state, or dependencies.

package/pack/generated/pi/agents/devrites-plan-reviewer.md

@@ -120,7 +120,9 @@ criterion, slice, or proof.
   planned tests) or `kind: mechanism` (a named test can discriminate the wrong
   implementation; propose that case as the fix, not new plan prose).
 - In a recheck, your verdict covers the listed fingerprints, the correction diff, and
-  the dependents of each changed clause. Anything else you notice on unchanged text
+  the dependents of each changed clause. Return an explicit correction-created
+  regression verdict over the touched invariants and those dependents as
+  `Regression: <none | invariant → finding>`. Anything else you notice on unchanged text
   goes under `Late:` with severity and site; it is recorded, not verdict-bearing.
 - When a dimension has no issue, say "strong: <why>" instead of inventing a
   finding.
@@ -140,6 +142,7 @@ Dimension bands (evidence → band):
   - … (all 7)
 Suppressed (confidence ≤4, unverified): <count + one-line each, appendix>
 Critical failure-mode gaps: <list | none>
+Regression (recheck only): <none | invariant → finding>
 Floor verdict: <weakest band> on <dimension> → PASS | BLOCKED
 ```
 

package/pack/generated/pi/agents/devrites-slice-wright.md

@@ -119,7 +119,10 @@ unclear boundary is underspecified: return `Escalation` without proceeding.
    new fingerprint. At the limit return the gate and repro. `Escalation` is only for product/irreversible choices
    or human-only access; technical failure is a blocker.
    Before handoff, inspect your cumulative slice diff against the contract and
-   scenario matrix, including correction-affected adjacent variants. Fix supported
+   scenario matrix, including correction-affected adjacent variants, then against
+   the reviewers' own checks: [code review § What to check](../skills/devrites-lib/reference/standards/code-review.md#what-to-check-tests-first)
+   and test analysis (each acceptance criterion has a test that fails without the
+   change; no assertion-free, tautological, or mock-asserting test). Fix supported
    in-scope gaps together, rerun affected proof, and report remaining gaps. Self-check
    never replaces independent review; green tests do not prove all possible cases.
 5. **TRANSFER when isolated.** After green writer-safe proof, verify the diff again,

package/pack/generated/pi/agents/overhaul-backend-engineer.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).
 

package/pack/generated/pi/agents/overhaul-boundary.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).
 

package/pack/generated/pi/agents/overhaul-craft.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).
 

package/pack/generated/pi/agents/overhaul-frontend-engineer.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).
 

package/pack/generated/pi/agents/overhaul-implementer.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).
 

package/pack/generated/pi/agents/overhaul-recon.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).
 

package/pack/generated/pi/agents/overhaul-specialist.md

@@ -9,6 +9,8 @@ inheritProjectContext: true
 
 Do not invoke another agent. You are called by `/overhaul` and return your result to that orchestrator.
 
+Write your receipt (`schema` `overhaul.receipt/1`) to the packet's `receipt_path`, copying `run_id`, `task_id`, `attempt_id`, `lane` and `snapshot` verbatim from the packet and setting `role` to the unprefixed role name (`verifier`, not `overhaul-verifier`); follow `.pi/skills/overhaul/references/orchestration.md` § Receipts, since admission rejects any mismatch.
+
 The `/overhaul` references cited below live under `.pi/skills/overhaul/references/`
 (`.pi/skills/overhaul/references/` on Codex; the host's own skills directory elsewhere).