devrites 6.0.4 → 6.1.1

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/candidate-integrity.md","devrites-lib/reference/standards/testing.md","devrites-lib/reference/standards/spec-grammar.md","devrites-lib/reference/standards/test-proof-checklist.md","devrites-lib/reference/standards/agents.md","devrites-lib/reference/standards/gates.md","devrites-lib/reference/standards/verification-methods.md","rite-prove/reference/acceptance-proof.md","rite-prove/reference/proof-ladder.md","rite-prove/reference/failure-triage.md","rite-prove/reference/test-command-discovery.md","rite-prove/reference/anti-patterns.md","rite-build/reference/checkpoint.md"],"triggers":{"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"browser":["devrites-lib/reference/standards/browser-proof-checklist.md","rite-prove/reference/browser-proof.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"observability":["devrites-lib/reference/standards/observability.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.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","evidence.md","touched-files.md","browser-evidence.md"],"workspaceByRole":{"proof-runner":["spec.md","test-plan.md","tasks.md","gates.md","evidence.md","touched-files.md","browser-evidence.md","state.md"],"spec-reviewer":["brief.md","spec.md","decision-coverage.md","questions.md","decisions.md","assumptions.md","state.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase prove` 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 prove` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-prove: prove the completed feature
@@ -15,30 +15,32 @@ Prove the assembled feature once. No workspace: use `/verify` or `/run`;
 pending tasks: stop for `/rite-build`.
 Never assert unobserved passes. After Polish/Review edits, repeat affected
 criteria/dependencies and bind under
-[evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
+[evidence validity](skill://devrites-lib/reference/candidate-integrity.md#evidence-validity).
 Initial full feature proof and required mutable observations still run.
 
 ## Rules
 
-Read the applicable standards: [`testing.md`](../devrites-lib/reference/standards/testing.md), [`test-proof-checklist.md`](../devrites-lib/reference/standards/test-proof-checklist.md),
-[`browser-proof-checklist.md`](../devrites-lib/reference/standards/browser-proof-checklist.md) for UI, [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md), [`performance.md`](../devrites-lib/reference/standards/performance.md),
-[`observability.md`](../devrites-lib/reference/standards/observability.md), topology/data/integration rules named by the plan,
-[`developer-experience.md`](../devrites-lib/reference/standards/developer-experience.md), [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md), [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md), and
-[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md). Developer surfaces require an observed flow, measured
+Read the applicable standards: [`testing.md`](skill://devrites-lib/reference/standards/testing.md), [`test-proof-checklist.md`](skill://devrites-lib/reference/standards/test-proof-checklist.md),
+[`browser-proof-checklist.md`](skill://devrites-lib/reference/standards/browser-proof-checklist.md) for UI, [`spec-grammar.md`](skill://devrites-lib/reference/standards/spec-grammar.md), [`performance.md`](skill://devrites-lib/reference/standards/performance.md),
+[`observability.md`](skill://devrites-lib/reference/standards/observability.md), topology/data/integration rules named by the plan,
+[`developer-experience.md`](skill://devrites-lib/reference/standards/developer-experience.md), [`definition-of-done.md`](skill://devrites-lib/reference/standards/definition-of-done.md), [`one-shot-actions.md`](skill://devrites-lib/reference/standards/one-shot-actions.md), and
+[`workflow-artifacts.md`](skill://devrites-lib/reference/standards/workflow-artifacts.md). Developer surfaces require an observed flow, measured
 TTHW, and exact signal-bearing errors; never assert DX (trigger `devex`).
 
 - Each claim needs an executed positive, discriminating assertion and decisive
   signal; green commands alone are unproven. Methods must be genuinely distinct
   and coverage counted against an explicit denominator — apply
-  [`verification-methods.md`](../devrites-lib/reference/standards/verification-methods.md).
-- Follow [`candidate-integrity.md`](../devrites-lib/reference/candidate-integrity.md). Prove owns proof binding, not candidate
+  [`verification-methods.md`](skill://devrites-lib/reference/standards/verification-methods.md).
+- Follow [`candidate-integrity.md`](skill://devrites-lib/reference/candidate-integrity.md). Prove owns proof binding, not candidate
   grammar/hashing. Spec Drift Guard owns revealed contract drift.
 - Root runs vetted gates/browser and records immutable evidence; proof runner
   validates it. Only the bounded wright fixes product source/tests.
 - **Prove remains the controlling caller** during technical backtracking. Save
   its cursor; run Plan repair, Recovery Vet, remediation, and re-proof inline;
-  consume nested boundaries; resume the failed rung. Recovery exhausts after
-  three no-progress attempts on the exact same fingerprint. Closing one or exposing a distinct
+  consume nested boundaries; resume the failed rung. A strategy is spent after
+  three no-progress attempts on the exact same fingerprint; escalate it per the
+  [retry contract](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve)
+  instead of stopping. Closing one or exposing a distinct
   Critical/Important invariant is progress, not a reason to hand work off.
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"Prove consumes installed Workflow Artifact or CLEANED rerun","action":"VERIFY_EXISTING or admitted proof path ending PROVE_AND_RETURN","return":"saved Prove cursor; stop before real action"} -->
 ## Released-workspace refresh
@@ -78,7 +80,7 @@ test changes.
    candidate and require identical digest/no source mutation. Reject substituted
    commands, malformed manifests, zero-test/skipped/filtered behavioral claims,
    exit-status-only claims, status-masking forms, and source drift. A retry-only
-   pass is `flaky` per [`testing.md`](../devrites-lib/reference/standards/testing.md#determinism-no-flaky-tests),
+   pass is `flaky` per [`testing.md`](skill://devrites-lib/reference/standards/testing.md#determinism-no-flaky-tests),
    never green. Static gates prove only their named
    static criterion.
    Run the acceptance ledger: `devrites-engine gates run <slug>` executes every
@@ -89,11 +91,11 @@ test changes.
    human's own words or source; placeholder notes are unmet and an AFK run never
    self-attests. Only gates manual at Vet are attested; runnable-to-manual
    conversion, EXPECT loosening, or CHECK/CWD/row change here is Plan repair plus
-   re-Vet ([`gates.md`](../devrites-lib/reference/standards/gates.md)). An impossible outcome
+   re-Vet ([`gates.md`](skill://devrites-lib/reference/standards/gates.md)). An impossible outcome
    is `gates abandon` plus a handoff, never a deleted row or a false pass.
    `gates status <slug>` must reduce to `all-met` before Prove records green.
 5. **Gate consumptive actions.** Immediately before execution, apply
-   [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md): current retained identity, bounds/sanitization,
+   [`one-shot-actions.md`](skill://devrites-lib/reference/standards/one-shot-actions.md): current retained identity, bounds/sanitization,
    injective boundary map, per-seam fault fixtures, collision mutant, terminal
    fixtures, and cleanup-survival proof must be green. Missing/stale/disposable-
    only evidence returns to Vet without spending an attempt. Record the admitted artifact identity before execution.
@@ -128,7 +130,7 @@ test changes.
 10. **Record.** Root updates `evidence.md`, optional `browser-evidence.md`,
     traceability, and state, with exactly one observed candidate binding.
     After independent validators are green, checkpoint remaining candidate
-    diffs per [`checkpoint.md`](../rite-build/reference/checkpoint.md). A wright
+    diffs per [`checkpoint.md`](skill://rite-build/reference/checkpoint.md). A wright
     correction during Recover red does not commit on control until this step.
 
 > Do not claim an unobserved pass, skip browser proof, or proceed with pending

package/pack/generated/omp/skills/rite-prove/reference/acceptance-proof.md

@@ -1,14 +1,14 @@
 # Acceptance proof
 
 Map each `spec.md` criterion to `test | command | browser | judgment` evidence
-and one-line reason. Run [`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md)'s Native grammar re-read on the saved
+and one-line reason. Run [`spec-grammar.md`](skill://devrites-lib/reference/standards/spec-grammar.md)'s Native grammar re-read on the saved
 spec before mapping; reopen after corrections. No parser/script may replace it.
 
 Every structured WHEN/THEN scenario needs a passing asserting test. When
 `test-plan.md` exists, every acceptance/gap requirement, interactive element, and
 user flow needs a passing result. Missing coverage blocks.
 
-Apply [[`testing.md`](../../devrites-lib/reference/standards/testing.md)'s positive, discriminating proof](../../devrites-lib/reference/standards/testing.md#positive-discriminating-proof),
+Apply [[`testing.md`](skill://devrites-lib/reference/standards/testing.md)'s positive, discriminating proof](skill://devrites-lib/reference/standards/testing.md#positive-discriminating-proof),
 including invalid-result exclusions and static/textual criterion boundaries.
 Unsupported behavioral claims are `cannot_verify` and block proof.
 
@@ -37,12 +37,12 @@ judgment or pass.
 
 Reconcile `spec.md`'s applicability map with the final diff. For each triggered owner:
 
-- [`repository-topology.md`](../../devrites-lib/reference/standards/repository-topology.md): prove commands ran at every affected root and both provider
+- [`repository-topology.md`](skill://devrites-lib/reference/standards/repository-topology.md): prove commands ran at every affected root and both provider
   and consumer used the same canonical contract; identify generated/vendor sources.
-- [`data-integrity.md`](../../devrites-lib/reference/standards/data-integrity.md): prove declared invariants plus relevant duplicate/retry,
+- [`data-integrity.md`](skill://devrites-lib/reference/standards/data-integrity.md): prove declared invariants plus relevant duplicate/retry,
   concurrency, interruption/resume, old/new coexistence, tenant isolation, and
   rollback/forward-recovery cases with recorded scale/counts.
-- [`integration-reliability.md`](../../devrites-lib/reference/standards/integration-reliability.md): prove relevant invalid/partial response, auth failure,
+- [`integration-reliability.md`](skill://devrites-lib/reference/standards/integration-reliability.md): prove relevant invalid/partial response, auth failure,
   timeout/unknown outcome, rate limit/outage, duplicate/order, poison/backlog, cache/partition,
   degradation, and recovery behavior.
 
@@ -53,7 +53,7 @@ or a mock that cannot produce the risk.
 ## Critical-path assertion strength
 
 For regression-Critical, irreversible, and data-loss paths, require
-[[`testing.md`](../../devrites-lib/reference/standards/testing.md)'s safe perturbation](../../devrites-lib/reference/standards/testing.md#safe-perturbation).
+[[`testing.md`](skill://devrites-lib/reference/standards/testing.md)'s safe perturbation](skill://devrites-lib/reference/standards/testing.md#safe-perturbation).
 Missing evidence is `cannot_verify`; a green test on broken code is unproven.
 Pure transforms also get a round-trip or
 metamorphic property check when applicable.
@@ -61,7 +61,7 @@ metamorphic property check when applicable.
 ## Runtime observability branch
 
 For endpoints, jobs, consumers, integrations, user flows, or new error paths,
-trigger failure and observe the required log/metric/trace per [`observability.md`](../../devrites-lib/reference/standards/observability.md);
+trigger failure and observe the required log/metric/trace per [`observability.md`](skill://devrites-lib/reference/standards/observability.md);
 record it. Skip pure internal, docs, config, and type-only changes.
 
 ## Developer-facing branch

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

@@ -5,7 +5,7 @@ report a pass you didn't observe, skip a rung of the browser-proof ladder,
 or proceed without all slices built.
 
 Pack-wide rationalizations + red flags (incl. observed-but-not-recorded):
-see [standards/anti-patterns.md](../../devrites-lib/reference/standards/anti-patterns.md).
+see [standards/anti-patterns.md](skill://devrites-lib/reference/standards/anti-patterns.md).
 
 ## Phase-specific rationalizations
 

package/pack/generated/omp/skills/rite-prove/reference/browser-proof.md

@@ -31,14 +31,14 @@ What `browser-evidence.md` must capture for a UI slice. Delegates to
 ```
 
 ## Rules
-- The `## Visual Verdict` table follows [visual-verdict.md](../../devrites-browser-proof/reference/visual-verdict.md),
+- The `## Visual Verdict` table follows [visual-verdict.md](skill://devrites-browser-proof/reference/visual-verdict.md),
   which owns its rows, verdict values and severity mapping.
 - Open every screenshot path and describe it: never assert from the filename.
 - Read `design-brief.md` + `references.md` first. Compare fidelity only with references
   classified **target**; check constraints as rules and never pixel-match inspiration.
 - Render every proof target named by the brief/slice using the canonical viewport
-  set and state coverage in [quality-standards.md](../../devrites-frontend-craft/reference/quality-standards.md).
-  Apply [capture admissibility](../../devrites-lib/reference/standards/browser-proof-checklist.md)
+  set and state coverage in [quality-standards.md](skill://devrites-frontend-craft/reference/quality-standards.md).
+  Apply [capture admissibility](skill://devrites-lib/reference/standards/browser-proof-checklist.md)
   before assigning a visual verdict; invalid captures leave proof `cannot_verify`.
 - Compare structure before decoration: hierarchy/layout → responsive/state behavior →
   type/spacing/color → polish. Record each material delta, fix it, and re-render. A visual

package/pack/generated/omp/skills/rite-prove/reference/failure-triage.md

@@ -6,7 +6,7 @@ loop to `devrites-debug-recovery`.
 ## Triage ladder
 1. **Reproduce:** for a repeatable command, run it again and capture the exact
    error (quote it). For a consumptive action under
-   [`one-shot-actions.md`](../../devrites-lib/reference/standards/one-shot-actions.md),
+   [`one-shot-actions.md`](skill://devrites-lib/reference/standards/one-shot-actions.md),
    never rerun it: use the retained bounded artifact as the reproduction input.
 2. **Classify** the failure:
    - test is right, code is wrong → fix the code (in scope).
@@ -20,7 +20,7 @@ loop to `devrites-debug-recovery`.
      blocker citing that baseline, never green; without the baseline it is unresolved.
    - flaky (at least one fail and one pass on the unchanged candidate digest;
      timing/order) → record every attempt and apply
-     [the Determinism standard](../../devrites-lib/reference/standards/testing.md#determinism-no-flaky-tests):
+     [the Determinism standard](skill://devrites-lib/reference/standards/testing.md#determinism-no-flaky-tests):
      the green attempt proves nothing; fix it or record a blocker. Don't paper over with retries.
    - external dependency down → record blocker; don't fake the result.
 3. **Isolate:** minimize to the smallest failing case; bisect the diff if needed.
@@ -47,6 +47,7 @@ loop to `devrites-debug-recovery`.
 - Three no-progress attempts on the exact same causal fingerprint consume the
   shared recovery cap. A recheck that closes the reproduction is progress; a
   different evidenced Critical/Important invariant gets its own fingerprint.
-  Preserve the reproduction and dead ends, then stop once as a technical blocker.
+  Preserve the reproduction and dead ends, then escalate or park per the
+  [retry contract](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
   Ask only when the remaining decision is human-owned.
 - A failure you can't fix in scope is a recorded **blocker**, not a silent skip.

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/definition-of-done.md","devrites-lib/reference/orchestration-profiles.md"],"triggers":{"coding":["devrites-lib/reference/standards/coding-style.md"],"testing":["devrites-lib/reference/standards/testing.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"security":["devrites-lib/reference/standards/security.md"],"principles":["devrites-lib/reference/standards/principles.md"],"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["state.md"]} -->
-> Read-set manifest: `devrites-engine context <slug> --phase quick` 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 quick` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-quick: express lane for small changes
@@ -16,14 +16,14 @@ copy tweak, a one-function fix, or a small config change. `/rite-quick` keeps th
 discipline that matters (idiom, TDD, evidence, escape-to-full-lifecycle) and drops the
 artifacts that don't, in a **single pass**. Senior-engineer "right step, right time" made
 executable, not advisory. This lane uses the **Quick** depth profile from
-[`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 significance gate (the whole safety story)
 
 **Run this first. If ANY of these holds, STOP and route to `/rite-spec`. Do NOT use the
 express lane:**
 - Touches **auth / authz**, a **data migration**, a **public API contract**, or any
-  **destructive / data-loss** path in the irreversible-risk list. See `../devrites-lib/reference/standards/afk-hitl.md`.
+  **destructive / data-loss** path in the irreversible-risk list. See `skill://devrites-lib/reference/standards/afk-hitl.md`.
 - Spans **more than one vertical slice**, or more than a couple of files of real logic.
 - **Ambiguous scope:** you'd have to guess what "done" means, or the ask hides a design
   decision (data model, new dependency, second design system).
@@ -38,16 +38,16 @@ express lane on a risky one is the failure mode the lifecycle exists to prevent.
 
 ## Rules consulted (read on demand from `.omp/skills/devrites-lib/reference/standards/`)
 Load this lane's conditional standards when needed:
-- [`coding-style.md`](../devrites-lib/reference/standards/coding-style.md): naming, guard clauses, reuse-first.
-- [`testing.md`](../devrites-lib/reference/standards/testing.md): TDD, **completeness** (every touched behavior/element asserted) +
+- [`coding-style.md`](skill://devrites-lib/reference/standards/coding-style.md): naming, guard clauses, reuse-first.
+- [`testing.md`](skill://devrites-lib/reference/standards/testing.md): TDD, **completeness** (every touched behavior/element asserted) +
   **assertion strength** (no tautological tests; see it fail first), scaled to the change.
-- [`error-handling.md`](../devrites-lib/reference/standards/error-handling.md) / [`security.md`](../devrites-lib/reference/standards/security.md): only if the change touches input/errors.
-- [`principles.md`](../devrites-lib/reference/standards/principles.md): when `.devrites/principles.md` exists; a change that breaks an invariant is a gate, not a quick fix.
-- [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md): standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.
+- [`error-handling.md`](skill://devrites-lib/reference/standards/error-handling.md) / [`security.md`](skill://devrites-lib/reference/standards/security.md): only if the change touches input/errors.
+- [`principles.md`](skill://devrites-lib/reference/standards/principles.md): when `.devrites/principles.md` exists; a change that breaks an invariant is a gate, not a quick fix.
+- [`definition-of-done.md`](skill://devrites-lib/reference/standards/definition-of-done.md): standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.
 
 
 ## Workflow
-0. **Orient.** Read [`core.md`](../devrites-lib/reference/standards/core.md). If a `.devrites/` workspace is active, read its
+0. **Orient.** Read [`core.md`](skill://devrites-lib/reference/standards/core.md). If a `.devrites/` workspace is active, read its
    `state.md` directly; `/rite-quick` does **not** require
    a workspace and does **not** create the full tree.
 1. **Significance gate** (above). Fail → STOP, tell the user to run `/rite-spec <feature>`.
@@ -64,7 +64,11 @@ Load this lane's conditional standards when needed:
 3. **Build with TDD.** Failing test first when behavior changes (see it fail for the right
    reason) → smallest complete change in the **project's idiom** (reuse before you write,
    anti-AI-slop) → cover every touched behavior / interactive element with a **real**
-   assertion. UI → check the states + a browser glance.
+   assertion. UI → check the states + a browser glance. The root never edits source/tests:
+   dispatch exact `devrites-slice-wright` with an exact-path contract per
+   [wright-dispatch.md § Standalone correction](skill://rite-build/reference/wright-dispatch.md#standalone-correction) and the
+   [source-writing boundary](skill://devrites-lib/reference/standards/agents.md#source-writing-boundary);
+   reject any returned path outside it.
 4. **Prove (scoped).** Run the **targeted** tests + typecheck / lint for what changed (not
    the whole suite) → green. Record the command + output — resolve the project's real
    typecheck/lint commands with `devrites-engine detect commands` rather than guessing.
@@ -74,10 +78,11 @@ Load this lane's conditional standards when needed:
    fail is not proof.
 5. **Review-lite + ship.** Self-review the diff for correctness, scope, and idiom. If
    `.devrites/principles.md` exists, confirm that no declared invariant is broken. This is
-   `/rite-frame`'s AUDIT pass: one pass, no subagent fan-out. Show the diff, then on the user's confirm commit it
-   (Conventional Commits, atomic), or hand to `/rite-ship` only when the change belongs to the active
-   feature's candidate; otherwise commit standalone. **Never push
-   without the user asking.**
+   `/rite-frame`'s AUDIT pass: one pass, no subagent fan-out. Show the diff. A change that belongs to the
+   active feature's candidate is not committed here: append its exact paths to
+   `touched-files.md`, then route to `/rite-prove` →
+   `/rite-review` → `/rite-seal` (`/rite-ship` needs Seal GO). Otherwise, on the
+   user's confirm, commit it standalone (Conventional Commits, atomic). **Never push without the user asking.**
 
 ## Escalation (mid-flight): the Spec Drift Guard still applies
 If the "small" change turns out to be not small: a second slice appears, a real design

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

@@ -1,12 +1,12 @@
 ---
 name: rite-resolve
 description: User-invoked resume verb for answering, dropping, or batch-resolving open `questions.md` gates.
-argument-hint: "<qid> \"<answer>\"  |  --drop <qid> [\"<reason>\"]  |  --batch <path-to-file>"
+argument-hint: "<qid> \"<answer>\"  |  --drop <qid> [\"<reason>\"]  |  --batch <plain-text-file>"
 user-invocable: true
 disable-model-invocation: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","rite-resolve/reference/answer-protocol.md"],"triggers":{"standards":["devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/documentation.md"]}} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-resolve` 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> --skill rite-resolve` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # /rite-resolve: answer the human gate
 
@@ -20,14 +20,14 @@ skill takes the human's answer (or `--drop` / `--batch`), writes it to `question
 
 It has one verb, one source of truth (`questions.md`), and one cursor (`state.md`). The
 full AFK / HITL contract lives in
-[`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md).
+[`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md).
 
 ## Rules consulted (read on demand from `.omp/skills/devrites-lib/reference/standards/`)
 
 Pull these via `Read` when shaping the resolve:
 
-- [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md): gate taxonomy, `questions.md` schema, AFK exception rules.
-- [`documentation.md`](../devrites-lib/reference/standards/documentation.md): record decisions and rationale where the answer changes scope.
+- [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md): gate taxonomy, `questions.md` schema, AFK exception rules.
+- [`documentation.md`](skill://devrites-lib/reference/standards/documentation.md): record decisions and rationale where the answer changes scope.
 
 ## Operating rules
 
@@ -63,7 +63,7 @@ Pull these via `Read` when shaping the resolve:
    - `<qid> "<answer>"`: answer the single open question.
    - `--drop <qid>` (optional `"<reason>"`): mark the question `dropped`; record
      the reason inline.
-   - `--batch <path-to-file>`: bulk resolve, one entry per qid (see
+   - `--batch <plain-text-file>`: bulk resolve, one entry per qid (see
      [`reference/answer-protocol.md`](reference/answer-protocol.md) for the batch
      format).
 2. **Load context.** Read `state.md`, `questions.md`, and the relevant slice from

package/pack/generated/omp/skills/rite-resolve/reference/answer-protocol.md

@@ -48,11 +48,10 @@ q-2026-05-28-002: clinician sign-off required at runtime, not at plan time
 ```
 
 - One qid per line. The first colon is the separator; the rest of the line is the value.
-- Order matters only for `state.md` clearance: the script processes top-to-bottom and
-  flushes `Awaiting human` after each match.
-- Errors abort the batch at the first failing line so partial state is small and
-  diagnosable. Report the failing line, exit code, and the qids already applied. (Re-run after fixing the offending line; already-applied lines refuse to
-  re-apply because their `status` is no longer `open`.)
+- The batch is all-or-nothing: every line is validated before one atomic write, then
+  `Awaiting human` is cleared for the resolved qids.
+- An error applies nothing. Report the failing line and exit code, fix that line, and
+  re-run the whole file.
 
 ## Never overwrite
 

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/candidate-integrity.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/agents.md","devrites-lib/reference/standards/tooling.md","rite-review/reference/feature-scoped-review.md","rite-review/reference/five-axis-review.md","rite-review/reference/anti-patterns.md"],"triggers":{"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"code-review":["devrites-lib/reference/standards/code-review.md","devrites-lib/reference/standards/review-checklist.md","devrites-lib/reference/standards/review/README.md","devrites-lib/reference/standards/duplicate-code.md"],"performance":["devrites-lib/reference/standards/performance.md","rite-review/reference/performance-review.md","rite-review/reference/performance-checklist.md"],"principles":["devrites-lib/reference/standards/principles.md"],"security":["devrites-lib/reference/standards/security.md","devrites-lib/reference/standards/security-checklist.md","rite-review/reference/security-review.md"],"testing":["devrites-lib/reference/standards/testing.md"],"ui":["rite-review/reference/nielsen-heuristics.md","rite-review/reference/cognitive-load.md","rite-review/reference/performance-checklist.md"],"workflow-artifacts":["devrites-lib/reference/workspace-artifact-schema.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","evidence.md","touched-files.md","design-brief.md","browser-evidence.md"],"workspaceByRole":{"code-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","architecture.md","decisions.md","state.md","evidence.md","touched-files.md"],"devex-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"doubt-reviewer":["spec.md","plan.md","tasks.md","state.md","decisions.md"],"frontend-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md","design-brief.md"],"performance-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","state.md"],"security-auditor":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"simplifier-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md"],"spec-reviewer":["brief.md","spec.md","decision-coverage.md","questions.md","decisions.md","assumptions.md","state.md"],"test-analyst":["spec.md","tasks.md","test-plan.md","state.md","evidence.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase review` 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 review` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-review: feature-scoped review
@@ -17,26 +17,26 @@ tell the user to run `/rite-spec <feature>`.
 > **Scope:** `/code-review` is a generic diff review with no workspace context.
 > `/rite-review` reads
 > `.devrites/work/<slug>/spec.md` first, runs Spec ↔ Code-review axes as
-> parallel fresh-context reviewers (see [`parallel-dispatch.md`](../devrites-lib/reference/parallel-dispatch.md)), and gates feeding
+> parallel fresh-context reviewers (see [`parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md)), and gates feeding
 > into `/rite-seal`. Use `/code-review` for a one-off diff; use
 > `/rite-review` for a DevRites feature where the spec is the contract. Use the shared depth rules in
-[`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);
 all workflow-named roles remain mandatory at every depth.
 
 ## Rules consulted (read on demand from `.omp/skills/devrites-lib/reference/standards/`)
 
 Pull these via `Read` when the diff demands them:
 
-- [`code-review.md`](../devrites-lib/reference/standards/code-review.md): small PRs, severity labels, tests-first review focus.
-- [`review-checklist.md`](../devrites-lib/reference/standards/review-checklist.md): compact pass/fail sweep before reporting the verdict.
-- [`principles.md`](../devrites-lib/reference/standards/principles.md): declared project invariants (`.devrites/principles.md`); a diff that violates one with no recorded exception is a Critical, blocking finding.
-- [`testing.md`](../devrites-lib/reference/standards/testing.md): confirm that passing tests actually prove the spec.
-- [`agents.md`](../devrites-lib/reference/standards/agents.md): when to fan out to which review subagent.
-- [`security.md`](../devrites-lib/reference/standards/security.md): when input / auth / data / integrations / secrets are in scope.
-- [`security-checklist.md`](../devrites-lib/reference/standards/security-checklist.md): for the same security-sensitive scope, the compact trust-boundary sweep.
-- [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md): only
+- [`code-review.md`](skill://devrites-lib/reference/standards/code-review.md): small PRs, severity labels, tests-first review focus.
+- [`review-checklist.md`](skill://devrites-lib/reference/standards/review-checklist.md): compact pass/fail sweep before reporting the verdict.
+- [`principles.md`](skill://devrites-lib/reference/standards/principles.md): declared project invariants (`.devrites/principles.md`); a diff that violates one with no recorded exception is a Critical, blocking finding.
+- [`testing.md`](skill://devrites-lib/reference/standards/testing.md): confirm that passing tests actually prove the spec.
+- [`agents.md`](skill://devrites-lib/reference/standards/agents.md): when to fan out to which review subagent.
+- [`security.md`](skill://devrites-lib/reference/standards/security.md): when input / auth / data / integrations / secrets are in scope.
+- [`security-checklist.md`](skill://devrites-lib/reference/standards/security-checklist.md): for the same security-sensitive scope, the compact trust-boundary sweep.
+- [`repository-topology.md`](skill://devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](skill://devrites-lib/reference/standards/data-integrity.md), [`integration-reliability.md`](skill://devrites-lib/reference/standards/integration-reliability.md): only
   when the spec applicability map or final diff triggers their ownership/failure/proof checks.
-- [`performance.md`](../devrites-lib/reference/standards/performance.md): only when perf is relevant or a regression risk is visible.
+- [`performance.md`](skill://devrites-lib/reference/standards/performance.md): only when perf is relevant or a regression risk is visible.
 
 ## Operating rules
 
@@ -49,11 +49,11 @@ Pull these via `Read` when the diff demands them:
   normalized or polished UI. If review finds a remaining complexity issue, record it as
   a finding rather than rerunning a simplification pass.
 - Follow the shared
-  [`candidate-integrity.md`](../devrites-lib/reference/candidate-integrity.md).
+  [`candidate-integrity.md`](skill://devrites-lib/reference/candidate-integrity.md).
   Review starts only from the digest Polish closed.
 - Findings are labeled (below). Re-prove after any accepted correction.
 - **Reviewers judge; root reconciles; wright fixes.** Per
-  [`agents.md`](../devrites-lib/reference/standards/agents.md), root directly
+  [`agents.md`](skill://devrites-lib/reference/standards/agents.md), root directly
   reconciles verdicts/writes artifacts; engines do not. Accepted corrections
   route to `devrites-slice-wright`.
 
@@ -71,13 +71,14 @@ Pull these via `Read` when the diff demands them:
    `devrites-engine check candidate <slug>` and require its digest to match the
    single `evidence.md` binding and the `browser-evidence.md` binding when that
    file exists. Read those ledgers via the bounded advisory read
-   ([`workspace-artifact-schema.md`](../devrites-lib/reference/workspace-artifact-schema.md) § Read next by phase; trigger `workflow-artifacts`): binding line, `EVID-###`
+   ([`workspace-artifact-schema.md`](skill://devrites-lib/reference/workspace-artifact-schema.md) § Read next by phase; trigger `workflow-artifacts`): binding line, `EVID-###`
    index, then bodies for this candidate's AC/slice IDs only. A missing,
    malformed, or open candidate returns to Polish/Prove.
    Read `touched-files.md` `## Review trail` and `eng-review.md` `## Deferred findings`:
    every deferred row is an input finding for the step-3 cohort (quoted in the owning
    reviewer's brief without severity) and ends in `review.md` with its own label and
-   action tag — never silently dropped.
+   action tag — never silently dropped. Hand each lane reviewer the
+   `devrites-engine recall --paths <its touched paths>` pointers as prior context, not findings.
 2. **Review tests first:** do they prove the acceptance criteria? Missing,
    weak, or wrong tests are the first findings.
    **Completion:** every acceptance criterion maps to a proven test or a labeled finding.
@@ -88,7 +89,7 @@ Pull these via `Read` when the diff demands them:
    Separate contexts prevent one axis from masking the other. This is the initial
    full pass; a correction uses step 7's bounded recheck:
    - Freeze that closed digest and give the same digest to the **two** axis reviewers (three when
-     [engineering lanes](../devrites-lib/reference/parallel-dispatch.md) split the code axis) in
+     [engineering lanes](skill://devrites-lib/reference/parallel-dispatch.md) split the code axis) in
      parallel, each with its own narrow brief and no
      cross-pollination — and evaluate the frontend (step 4), security (step 5),
      and performance (step 6) dispatch conditions from this same diff now,
@@ -105,14 +106,14 @@ Pull these via `Read` when the diff demands them:
        checks. Apply canonical anti-slop and silent-failure lenses; inspect each hunk
        for unrequested deletion. Unexcepted `.devrites/principles.md` violations are
        Critical. Distinguish binding standards from judgment-only baseline smells."
-       Route it through [parallel-dispatch.md § Engineering lanes](../devrites-lib/reference/parallel-dispatch.md#engineering-lanes):
+       Route it through [parallel-dispatch.md § Engineering lanes](skill://devrites-lib/reference/parallel-dispatch.md#engineering-lanes):
        a frontend+backend diff gets two lane reviewers in this cohort.
    - **Do NOT merge or re-rank** their findings. Present them under separate
      `## Spec` and `## Code review` sub-sections in `review.md`. Surface contradictions
      between the axes explicitly (e.g. "Spec axis says complete, Code-review axis says
      untestable"): `/rite-seal` decides what blocks. Preserve each reviewer's
      `Outcome:` and admit its account through
-     [[`agents.md`](../devrites-lib/reference/standards/agents.md) § Result admission](../devrites-lib/reference/standards/agents.md#result-admission).
+     [[`agents.md`](skill://devrites-lib/reference/standards/agents.md) § Result admission](skill://devrites-lib/reference/standards/agents.md#result-admission).
      Either `Outcome: gap` stops Review; silence, failure, or malformed output never
      becomes an empty findings list.
 4. **Reconcile, don't re-review.** With the two parallel reports in hand, the inline
@@ -141,7 +142,7 @@ Pull these via `Read` when the diff demands them:
    updates the candidate manifest, returns through affected Prove, and then starts
    a fresh Review binding on the new digest. Dispatch affected exact reviewers on
    all their open findings and the dependency/regression closure under
-   [evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
+   [evidence validity](skill://devrites-lib/reference/candidate-integrity.md#evidence-validity).
    Cite unchanged sub-scope coverage only with its original identity and explicit
    justification; never relabel old accounts. Changed contracts or uncertain impact
    require the full applicable pass.
@@ -150,7 +151,7 @@ Pull these via `Read` when the diff demands them:
    cited unchanged sub-scope evidence and reconciling complete coverage.
    **Completion:** the records name the reviewed candidate identity and every accepted
    correction has affected proof plus a fresh Review. Then checkpoint remaining
-   candidate diffs per [`checkpoint.md`](../rite-build/reference/checkpoint.md);
+   candidate diffs per [`checkpoint.md`](skill://rite-build/reference/checkpoint.md);
    a wright correction does not commit on control until that Review is green.
 
 ## Finding labels
@@ -168,7 +169,7 @@ seal; `non-blocking` / `if-minor` findings are recorded, not a stop.
 
 ## Confidence and severity
 
-Apply [[`agents.md`](../devrites-lib/reference/standards/agents.md) § Result admission](../devrites-lib/reference/standards/agents.md#result-admission).
+Apply [[`agents.md`](skill://devrites-lib/reference/standards/agents.md) § Result admission](skill://devrites-lib/reference/standards/agents.md#result-admission).
 Roll trivia into one line. `/rite-seal` gates on `Critical == 0`,
 `Important == 0` (y/N override), acceptance, and drift. No composite score.
 

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

@@ -4,7 +4,7 @@ Load this when standing a non-trivial review decision, when tempted to
 demote severity to hide a finding, or when crossing out of feature scope.
 
 Pack-wide rationalizations + red flags: see
-[standards/anti-patterns.md](../../devrites-lib/reference/standards/anti-patterns.md).
+[standards/anti-patterns.md](skill://devrites-lib/reference/standards/anti-patterns.md).
 
 ## Phase-specific rationalizations
 

package/pack/generated/omp/skills/rite-review/reference/cognitive-load.md

@@ -75,14 +75,14 @@ Treat each as a finding when present; classify by load type so the fix is obviou
 ## The cheap-fix test
 
 If a finding would take more than 30 minutes to fix, classify it (token gap /
-component miss / flow misalignment per [`ui.md`](../../rite-polish/reference/ui.md)) and
+component miss / flow misalignment per [`ui.md`](skill://rite-polish/reference/ui.md)) and
 route to the appropriate bucket. Cognitive-load review surfaces problems; it
 doesn't decide the rewrite strategy.
 
 ## What this lens **doesn't** cover
 
 - **Accessibility:** separate axis (WCAG 2.2; see
-  [`devrites-frontend-craft/reference/quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md)).
+  [`devrites-frontend-craft/reference/quality-standards.md`](skill://devrites-frontend-craft/reference/quality-standards.md)).
 - **Performance:** separate axis (Core Web Vitals; see
   [`performance-checklist.md`](performance-checklist.md)).
 - **Code quality:** covered by the simplification audit

package/pack/generated/omp/skills/rite-review/reference/nielsen-heuristics.md

@@ -119,7 +119,7 @@ Users can find what they need without leaving the surface.
 
 In `/rite-review` output, surface heuristics scoring **≤2**, plus any 3 with a specific
 noted gap, as findings; every score feeds the UX axis. Each surfaced finding gets a
-severity label per [`SKILL.md`](../SKILL.md).
+severity label per [`SKILL.md`](skill://rite-review/SKILL.md).
 
 The rubric is descriptive, not gating. A score of 2 on aesthetic-minimalist isn't
 an automatic NO-GO; the `rite-seal` gate is `Critical == 0`, not "every heuristic

package/pack/generated/omp/skills/rite-review/reference/performance-checklist.md

@@ -3,7 +3,7 @@
 The minimum baseline `devrites-performance-reviewer` checks against, in feature scope. It
 is a checklist, not a mandate: flag what the diff touches or what a measurement
 flags, never a project-wide sweep. The philosophy lives in
-[`standards/performance.md`](../../devrites-lib/reference/standards/performance.md) (measure first). This file is the
+[`standards/performance.md`](skill://devrites-lib/reference/standards/performance.md) (measure first). This file is the
 concrete what-to-look-for.
 
 ## Core Web Vitals targets

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

@@ -2,7 +2,7 @@
 
 Apply only when a stated budget or visible regression risk makes performance relevant.
 The canonical measurement, pitfall, optimization, and scope rules live in
-[`performance.md`](../../devrites-lib/reference/standards/performance.md); apply every
+[`performance.md`](skill://devrites-lib/reference/standards/performance.md); apply every
 one before filing a performance finding.
 
 The agent runs **Source mode** (static scan, findings tagged `potential` + the verify

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

@@ -7,7 +7,7 @@ integrations, secrets, or permissions. Delegates to `devrites-audit security`.
 
 This is the **single-sourced OWASP-web checklist** both `/rite-review` and the
 `devrites-security-auditor` agent apply (trust-boundary + the OWASP **LLM** Top 10 live in
-[`standards/security.md`](../../devrites-lib/reference/standards/security.md)). Keep the enumeration here; don't restate it.
+[`standards/security.md`](skill://devrites-lib/reference/standards/security.md)). Keep the enumeration here; don't restate it.
 
 - **Injection:** parameterized queries; no string-built SQL/shell/HTML; validate &
   encode at boundaries.
@@ -31,7 +31,7 @@ This is the **single-sourced OWASP-web checklist** both `/rite-review` and the
 
 ## Trust boundary
 Apply the three-tier discipline (untrusted → boundary → trusted) per the canonical rule
-in [`standards/security.md`](../../devrites-lib/reference/standards/security.md#trust-boundary-three-tiers). A value
+in [`standards/security.md`](skill://devrites-lib/reference/standards/security.md#trust-boundary-three-tiers). A value
 that skips the boundary tier is a finding.
 
 ## Rules