devrites 6.0.4 → 6.1.0

package/pack/generated/omp/skills/overhaul/references/records.md

@@ -123,14 +123,19 @@ verifier attempt, repository-relative locations (external ones are labels, never
 host paths); `revisions.plan.file` equal to `revisions/plan-r<rev>.json`, required
 once approvals or writers exist; plan digest pins; known, acyclic dependencies;
 allowed paths that are exact files inside the repository (no `*` or `?`, no
-directories, no `.git`, no symlink or traversal escape); a separate verifier role;
+directories, no `.git` component or run-area path in any letter case or through a
+symlink, no symlink or traversal escape); a separate verifier role;
 approval and `accept-degradation` events with quote and trusted channel, approvals
 matching the plan digest, closure and current revision, none active after a later
 stop; a scorecard only with `revisions.rubric` and the same verdict as `run.json`;
+`READY_FOR_USER_REVIEW` only with a scorecard whose verdict is `MEETS_TARGETS`, and
+`COMPLETED_WITH_APPROVED_DEGRADATION` only with `MEETS_TARGETS_WITH_APPROVED_DEGRADATION`,
+each listing every audit gate (plus every repair gate outside assessment-only runs) as
+`PASS` or `NOT_APPLICABLE` (`G-CONCURRENCY` may be `WAIVED_OPERATIONAL` for the degraded outcome);
 no approval or writer in an assessment-only run; unchanged `run_id`, `repo_root`,
 `mode` and `assessment_only`; writers authorized for their task; one live writer
-per path (case-folded, symlink-resolved); no `dispatched`, `running` or `returned`
-attempt once the outcome leaves `RUNNING`; one outcome per approved task at the end;
+per path (case-folded, symlink-resolved); every attempt `admitted`, `rejected` or
+`cancelled` once the outcome leaves `RUNNING` (`timed-out` and `unknown` are not settled); one outcome per approved task at the end;
 a coverage denominator that never shrinks; append-only cycles, findings history and
 approval events; immutable revisions; view stamps; manifest integrity; stale stages
 and interrupted publishes. Across records: every finding's `domain` is a score key;

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

@@ -6,7 +6,7 @@ user-invocable: true
 disable-model-invocation: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md"],"triggers":{"intent":["devrites-lib/reference/intent-map.md"],"menu":["rite/reference/menu.md"],"dispatch":["devrites-lib/reference/parallel-dispatch.md"],"reply":["devrites-lib/reference/reply-contract.md"]}} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite` 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` (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: DevRites menu + router
 
@@ -16,7 +16,7 @@ Two modes:
   workspace status; `/rite-status` owns that.
 - **Verb arg** → pass-through invocation of the matching `rite-<verb>` skill (`/rite spec foo` ≡ `/rite-spec foo`); the called skill owns the output.
 
-When the user asks which rite fits, load [`devrites-lib/reference/intent-map.md`](../devrites-lib/reference/intent-map.md).
+When the user asks which rite fits, load [`devrites-lib/reference/intent-map.md`](skill://devrites-lib/reference/intent-map.md).
 When they ask how phases connect, load [`reference/menu.md`](reference/menu.md).
 
 ## Dispatch
@@ -74,9 +74,10 @@ What each verb does lives once, in the Menu below; this table is the invocation
 Both forms call the same skill. The menu supports discovery; `/rite-<verb>` is the direct form.
 
 `use <slug>` is handled **inline**. There is no `rite-use` skill. Confirm
-`.devrites/work/<slug>/` exists, then re-point `.devrites/ACTIVE` to `<slug>` and report
+`<slug>` is a safe slug and `.devrites/work/<slug>/state.md` is a contained regular file, then re-point `.devrites/ACTIVE` to `<slug>` and report
 the now-active feature. It is cheap context-switching only: no re-spec, no phase run. If
-the workspace is missing, list the slugs under `.devrites/work/` and stop.
+the workspace or its `state.md` is missing, list the slugs under `.devrites/work/` that have
+`state.md` and stop.
 
 `guide` is an inline walkthrough for the first feature. Agree on one **real, small**
 change, then run spec → clarify → temper → define → vet → build → prove → polish → review → seal →
@@ -89,13 +90,13 @@ Specialist triggers (model-invoked inside the above):
 decision) · `devrites-api-interface` (cross-boundary) ·
 `devrites-audit <security|perf|simplify>` (single-axis review/polish pass) ·
 `devrites-debug-recovery` (failures). Parallel reviewer fan-out at seal is a shared
-reference (see [`devrites-lib/reference/parallel-dispatch.md`](../devrites-lib/reference/parallel-dispatch.md)).
+reference (see [`devrites-lib/reference/parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md)).
 
 ## What to output
 
 Reply-contract exception: `/rite` is the menu/router, not a workspace completion step.
 Called phase skills own the shared completion reply contract
-([`reply-contract.md`](../devrites-lib/reference/reply-contract.md)).
+([`reply-contract.md`](skill://devrites-lib/reference/reply-contract.md)).
 
 1. **Verb in `$ARGUMENTS`** → invoke the matching skill per the table above.
 2. **No args** → menu mode, as above.
@@ -150,4 +151,4 @@ UTILITY       /rite frame | prototype | handoff | zoom-out | pressure-test  (or
 
 The operating rules live in `.omp/skills/devrites-lib/reference/standards/core.md`; DevRites skills Read it as
 their first step, and the other rule files load on demand. See
-[`.omp/skills/devrites-lib/reference/standards/README.md`](../devrites-lib/reference/standards/README.md) for the full index.
+[`.omp/skills/devrites-lib/reference/standards/README.md`](skill://devrites-lib/reference/standards/README.md) for the full index.

package/pack/generated/omp/skills/rite/reference/menu.md

@@ -32,14 +32,15 @@ Phase-ordered `/rite` reference. Load only for command detail or phase connectio
   `/rite-define` (plan) → `/rite-vet` (engineering review; light or full) →
   `/rite-build` ×N (all slices) → `/rite-prove` (once all built) →
   `/rite-polish` (always: code + UI if UI) → `/rite-review` → `/rite-seal` → `/rite-ship`.
-- **Existing codebase**: `/rite-adopt` → `/rite-clarify` → `/rite-define` → `/rite-vet` → build.
+- **Existing codebase**: `/rite-adopt` → `/rite-spec` → `/rite-clarify` → `/rite-define` → `/rite-vet` → build.
 - **Drift mid-build**: classify → bounded recovery for objective defects, `/rite-plan`
   repair for a wrong durable plan, or one user decision for real product/risk drift.
 - **Older workspace cannot resume**: `/rite-upgrade` audits first → only proven gaps use
-  Clarify/Plan repair/Converge/Vet or Prove/Polish/Review/Seal → resume. It never
-  migrates cursor format or invents a prior pass.
-- **Resumed / adopted / stalled**: `/rite-converge` (assess live code vs intent → append the
-  remaining slices) → `/rite-vet` → `/rite-build` ×N → continue at `/rite-prove`.
+  Clarify/Plan repair/Converge/Vet or Prove/Polish/Review/Seal → resume. A cursor with
+  no `schema` row needs `devrites-engine migrate <slug>` first; upgrade never migrates
+  cursor format itself or invents a prior pass.
+- **Resumed / stalled, or adopted after Define** (has `plan.md` + `tasks.md`): `/rite-converge`
+  (assess live code vs intent → append the remaining slices) → `/rite-vet` → `/rite-build` ×N → continue at `/rite-prove`.
 
 ## Rules this menu obeys
 

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

@@ -5,7 +5,7 @@ argument-hint: "[path or area to adopt] [+ what you want to build next]"
 user-invocable: true
 ---
 <!-- loads: {"always":["rite-adopt/reference/adoption.md","rite-adopt/reference/anti-patterns.md","rite-polish/reference/ledger.md"],"triggers":{"security":["devrites-lib/reference/standards/security.md"]}} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-adopt` 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-adopt` (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-adopt: onboard existing code
 
@@ -35,7 +35,7 @@ parallel convention system.
    the measurable next objective. Record each `contested` convention from
    [`adoption.md`](reference/adoption.md) in `questions.md`; propose no guidance for it.
 4. For a structured baseline, follow the ledger's read workflow in
-   [`ledger.md`](../rite-polish/reference/ledger.md) § Reading in Spec and Adopt:
+   [`ledger.md`](skill://rite-polish/reference/ledger.md) § Reading in Spec and Adopt:
    list ledger specs with the host filesystem and read only the touched capabilities;
    classify against current file content, never memory. The native preview/write
    workflow runs during Polish, not Adopt.
@@ -44,11 +44,12 @@ parallel convention system.
    Propose only. When the nearest scope is `AGENTS.md`, `CLAUDE.md`, or another host identity
    or memory file, `/rite-customize` applies the edit after `devrites-engine check skill-trust
    <path>` and explicit human approval, never here (trigger `security`). Owner:
-   [`security.md`](../devrites-lib/reference/standards/security.md) § Prompt-injection
+   [`security.md`](skill://devrites-lib/reference/standards/security.md) § Prompt-injection
    resistance. Never create convention bands, scores, or a command cache.
 6. A genuine non-negotiable invariant may be proposed for
    `.devrites/principles.md`; the human must ratify it.
-7. Set the next step to `/rite-clarify` and stop. Do not plan or build.
+7. Set the next step to `/rite-spec <slug>` and stop; Spec extends this workspace and owns
+   `brief.md`, `checklists/`, and `spec_gate`. Do not plan or build.
 
 > Refuse the rationalizations in [`anti-patterns`](reference/anti-patterns.md).
 
@@ -59,5 +60,5 @@ Done: adopted <scope> into <slug>.
 Changed: <workspace artifacts>; project guidance <proposed | unchanged>
 Evidence: <source/CI paths inspected>
 Open: <questions | none>
-Next: /rite-clarify
+Next: /rite-spec <slug>
 ```

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

@@ -1,6 +1,6 @@
 # /rite-adopt: anti-patterns
 
-Start with the universal table in [`../../devrites-lib/reference/standards/anti-patterns.md`](../../devrites-lib/reference/standards/anti-patterns.md).
+Start with the universal table in [`skill://devrites-lib/reference/standards/anti-patterns.md`](skill://devrites-lib/reference/standards/anti-patterns.md).
 Below are the rationalizations specific to onboarding an existing codebase.
 
 ## Adoption-specific rationalizations

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/one-shot-actions.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/standards/acceptance-preserving-reslice.md","rite-autocomplete/reference/decision-policy.md","rite-autocomplete/reference/loop.md","rite-autocomplete/reference/stop-conditions.md"],"triggers":{"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"]},"workspace":["state.md","spec.md","plan.md","tasks.md","questions.md","decisions.md","drift.md","evidence.md","test-plan.md"]} -->
-> Read-set manifest: `devrites-engine context <slug> --phase autocomplete` 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 autocomplete` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-autocomplete: full lifecycle, unattended
@@ -19,15 +19,15 @@ option auto-resolve; they are not a user handoff, except a question whose answer
 would add acceptance or product scope, which a recommended option never resolves.
 Use the Standard native
 profile by default and Full for high-risk scope or explicit `--full`; see
-[`orchestration-profiles.md`](../devrites-lib/reference/orchestration-profiles.md).
+[`orchestration-profiles.md`](skill://devrites-lib/reference/orchestration-profiles.md).
 
 ## Required rules
 
-Read [`core.md`](../devrites-lib/reference/standards/core.md) and [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) first. Read
-[`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md) before any stop/continue or execution decision involving a
+Read [`core.md`](skill://devrites-lib/reference/standards/core.md) and [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md) first. Read
+[`one-shot-actions.md`](skill://devrites-lib/reference/standards/one-shot-actions.md) before any stop/continue or execution decision involving a
 consumptive action. Before honoring a terminal cursor that names missing
 executable controller/harness/bundle bytes or a missing writer, read
-[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
+[`workflow-artifacts.md`](skill://devrites-lib/reference/standards/workflow-artifacts.md)
 (trigger `workflow-artifacts` — only when a workspace declares them). Before classifying any Reslice, read `.omp/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
 <!-- BEGIN RESLICE ROUTE-TO-ACTION -->
@@ -127,11 +127,12 @@ executable controller/harness/bundle bytes or a missing writer, read
    product scope is never auto-resolved by a recommended option; it stops for a human.
    Technical exhaustion records terminal
    `Next step: none`, never a routine phase command. **Completion:** no stop is active, or its cursor and reason are durable.
-6. **Seal boundary.** Without a ship flag, stop at Seal GO with `/rite-ship` —
-   unless `continue_sequence: false` or sequence budget is spent; otherwise
-   leave the sealed workspace unshipped and open the next recorded continuation
-   ([loop.md § Sequence continuation](reference/loop.md#sequence-continuation));
-   report the sequence position on every stop.
+6. **Seal boundary.** Without a ship flag, leave the sealed workspace unshipped and
+   open the next recorded continuation
+   ([loop.md § Sequence continuation](reference/loop.md#sequence-continuation))
+   unless `continue_sequence: false`, the sequence budget is spent, or no entry
+   remains; then stop at Seal GO with `/rite-ship`. Report the sequence position on
+   every stop.
    With a ship flag, perform Ship preflight, disclose the exact Git plan, and stop for
    fresh literal `GO` plus native approval. **Completion:** performed no Git action before fresh literal `GO` plus native approval.
 

package/pack/generated/omp/skills/rite-autocomplete/reference/decision-policy.md

@@ -30,7 +30,7 @@ not pick the option that's merely easiest to implement.
 
 - Follow the project's existing conventions, components, and test commands: always.
 - Prefer the smallest vertical slice that proves the acceptance criterion.
-- Reuse → extend → build new, in that order ([`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md)).
+- Reuse → extend → build new, in that order ([`coding-style.md`](skill://devrites-lib/reference/standards/coding-style.md)).
 - When two options are equivalent on the evidence, choose the lower-risk / more
   reversible one.
 

package/pack/generated/omp/skills/rite-autocomplete/reference/loop.md

@@ -53,7 +53,8 @@ and parallel AFK headroom as stop conditions. Pass this invocation's
 that already name a ranked recommended option (recommended pick via
 `devrites-engine state resolve`) instead of queuing them or handing
 `/rite-resolve` to the user. Escalating, irreversible-risk, access, and
-blocking with no recommended option still pause.
+blocking with no recommended option still pause, as does Seal's judgment-only
+validating question (`slice: seal`).
 
 ## Phase arc
 
@@ -86,7 +87,7 @@ floor; `--update` never excuses an unreconciled regression.
 ## Sequence continuation
 
 Unless `continue_sequence: false`, while sequence budget remains
-([sentinel](../../devrites-lib/reference/standards/afk-hitl.md#sequence-continuation-continue_sequence-max_workspaces)),
+([sentinel](skill://devrites-lib/reference/standards/afk-hitl.md#sequence-continuation-continue_sequence-max_workspaces)),
 step 10 does not end the run: leave the sealed workspace unshipped with its
 `Next step: /rite-ship`, then invoke the next recorded continuation
 (`/rite-spec <parent>-<n> "<objective>"` from the parent's `decisions.md` sequence)
@@ -96,7 +97,7 @@ Spend accounting is durable in `state.md` cursors, not chat. Before invoking the
 continuation, ensure the current workspace's `sequence_workspaces_remaining` is
 set — absent, write `max_workspaces - 1` and `sequence_position: 1` first — and
 `> 0`. `/rite-spec` seeds the child's sequence cursor at creation per the
-[continuation contract](../../rite-plan/reference/slicing.md#continuation-workspaces);
+[continuation contract](skill://rite-plan/reference/slicing.md#continuation-workspaces);
 after the child's `state.md` exists, verify it — `sequence_parent` = the current
 slug, `sequence_position` = parent position + 1,
 `sequence_workspaces_remaining` = parent remaining − 1, and — when the recorded

package/pack/generated/omp/skills/rite-autocomplete/reference/stop-conditions.md

@@ -66,7 +66,8 @@ exhausted.
   would add acceptance or product scope is never auto-picked, even with a
   recommended option; it stops for a human. Blocking with no
   recommended option still stops. Validating: auto-pick the recommended option,
-  close the question, continue.
+  close the question, continue — except Seal's judgment-only acceptance question
+  (`slice: seal`), which only a human answers; it stops.
 - **Temper:** `expand` and extra acceptance stop: ask through `ask`, hold the
   fold, and continue only after a human resolves the qid (an ADR is not that answer).
   Irreversible-risk still pauses. `hold-rigor`, `reduce-to-MVP`, and a skip do not pause.

package/pack/generated/omp/skills/rite-build/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/standards/agents.md","rite-build/reference/phase-contract.md","rite-build/reference/one-slice-cycle.md","rite-build/reference/wright-dispatch.md","rite-build/reference/checkpoint.md","rite-build/reference/spec-drift-guard.md","rite-build/reference/output.md","rite-build/reference/anti-patterns.md"],"rootOnly":["rite-build/reference/phase-contract.md","rite-build/reference/wright-dispatch.md","rite-build/reference/checkpoint.md","rite-build/reference/output.md","rite-build/reference/afk-discipline.md","rite-build/reference/checkpoint-protocol.md","rite-build/reference/parallel-batch.md","devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/workflow-artifacts.md"],"triggers":{"afk":["rite-build/reference/afk-discipline.md","devrites-lib/reference/standards/afk-hitl.md","rite-build/reference/checkpoint-protocol.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"coding":["devrites-lib/reference/standards/coding-style.md"],"debug-recovery":["devrites-lib/reference/standards/debug-recovery.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"frontend":["rite-build/reference/frontend-trigger.md"],"parallel":["rite-build/reference/parallel-batch.md"],"patterns":["devrites-lib/reference/standards/patterns.md"],"principles":["devrites-lib/reference/standards/principles.md"],"security":["devrites-lib/reference/standards/security.md"],"tdd":["rite-build/reference/tdd.md","devrites-lib/reference/standards/testing.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","strategy.md"],"workspaceByRole":{"code-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","architecture.md","decisions.md","state.md"],"doubt-reviewer":["spec.md","plan.md","tasks.md","state.md","decisions.md"],"slice-wright":["brief.md","spec.md","architecture.md","plan.md","tasks.md","test-plan.md","state.md","decisions.md","assumptions.md","questions.md"],"test-analyst":["spec.md","tasks.md","test-plan.md","state.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase build` 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 build` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-build: one verified slice
@@ -21,7 +21,7 @@ caps and pause rules. Every wright returns after one slice.
 Root owns gates/bookkeeping; fresh
 [`devrites-slice-wright`](.omp/agents/devrites-slice-wright.md) writes source/tests.
 Workflow Artifacts use
-[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
+[`workflow-artifacts.md`](skill://devrites-lib/reference/standards/workflow-artifacts.md)
 (trigger `workflow-artifacts` — only when the plan declares them).
 Execute [`reference/phase-contract.md`](reference/phase-contract.md)
 ([`one-slice-cycle.md`](reference/one-slice-cycle.md),
@@ -48,15 +48,15 @@ Wright applies anti-slop; root verifies returns and never patches source. Refuse
   adjacent issues. An adjacent issue or non-obvious rationale bound to specific
   code anchors as a note — `devrites-engine note add <slug> <file> "<verbatim
   quote>" <title>` — so refactors regrade it instead of losing it
-  ([`notes.md`](../devrites-lib/reference/workspace-artifact-schema.md#anchored-notes)).
+  ([`notes.md`](skill://devrites-lib/reference/workspace-artifact-schema.md#anchored-notes)).
 - Re-prove affected behavior after edits (core.md #6); reuse observations only
-  under [evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
+  under [evidence validity](skill://devrites-lib/reference/candidate-integrity.md#evidence-validity).
 - Unplanned dependency/design-system/gap/repair → Vet/Spec Drift Guard batch
   sweep: every contract-assumption violation recorded before one folded
   repair+vet. Ask only for licensing/cost/security/product or explicit
   architecture-policy decisions (core.md #8).
 - Root never edits product source/tests (`.devrites/` + Workflow Artifact only;
-  [agents.md](../devrites-lib/reference/standards/agents.md) source-writing
+  [agents.md](skill://devrites-lib/reference/standards/agents.md) source-writing
   boundary). Wright is sole product writer; extras in returned paths/`git diff
   --name-only` hard-stop via `check diff-scope`.
 - Principles bind; irreversible conflict needs human exception or stop.
@@ -65,7 +65,7 @@ Wright applies anti-slop; root verifies returns and never patches source. Refuse
   [`spec-drift-guard.md`](reference/spec-drift-guard.md); checkpoint →
   [`checkpoint.md`](reference/checkpoint.md).
 - Async readiness waits during slice work follow
-  [`debug-recovery.md`](../devrites-lib/reference/standards/debug-recovery.md)
+  [`debug-recovery.md`](skill://devrites-lib/reference/standards/debug-recovery.md)
   (bounded poll + last-signal artifact; no blind sleep as primary strategy).
 
 ## Workflow Artifact branch
@@ -103,7 +103,7 @@ Run every step in `reference/phase-contract.md`: readiness, one target, dispatch
 or canonical transaction, return inspection, independent code/doubt/test analysis,
 approved fail-on-red proof, record, AFK accounting, and stop. Use
 [`reference/output.md`](reference/output.md) plus the shared
-[`reply contract`](../devrites-lib/reference/reply-contract.md). HITL never starts
+[`reply contract`](skill://devrites-lib/reference/reply-contract.md). HITL never starts
 the next slice automatically; AFK obeys remaining budget; Prove requires all slices built.
 
 ## Phase exit

package/pack/generated/omp/skills/rite-build/reference/afk-discipline.md

@@ -4,7 +4,7 @@ AFK mode is active when `.devrites/AFK` exists. It lets `/rite-build` chain slic
 without per-slice user input. The rules below limit that unattended work.
 
 Load the shared
-[`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md#the-sentinel-devritesafk)
+[`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md#the-sentinel-devritesafk)
 contract for the sentinel schema, defaults, gate ceiling, and mutable-counter
 ownership. This file owns only Build's dispatch, charging, and red-path behavior.
 

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

@@ -4,7 +4,7 @@ Load when a non-trivial decision stands or stopping, TDD, or doubt discipline
 feels inconvenient.
 
 Pack-wide rationalizations and red flags live in
-[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-build/reference/checkpoint-protocol.md

@@ -14,7 +14,7 @@ observer.
 
 ### User-facing render: the option set
 
-Present as `ask` ranked **option set** ([`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md)): 2–4 options,
+Present as `ask` ranked **option set** ([`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md)): 2–4 options,
 recommended first + `(Recommended)`, dimension-tagged trade-offs, plus escape hatch.
 Header names slice + gate:
 
@@ -56,7 +56,7 @@ rewrite; do not claim cross-file atomicity):
    `<N — name>`, `slice_mode` = `HITL`, `next_action` = `/rite-resolve <qid> "<answer>"`;
    then the `Awaiting human` table (`question_id`, `gate`, `blocking_slices` from
    `Blocked by` lookups) per its owner,
-   [`state-workspace.md`](../../rite-spec/reference/state-workspace.md#statemd-template) § state.md template.
+   [`state-workspace.md`](skill://rite-spec/reference/state-workspace.md#statemd-template) § state.md template.
    Question text, `proposed`, and `raised_at` stay in the step 1 entry. Legacy
    `- Status:`/`- Next step:`/`- qid:` bullets are engine-accepted aliases, not the
    authoring format.

package/pack/generated/omp/skills/rite-build/reference/checkpoint.md

@@ -57,11 +57,11 @@ facts were lost this cycle; restore or route them before landing the commit.
 After a crash, a fresh session may read the last `WIP(<slug>)` body as crash context.
 Authoritative state remains in `.devrites/`: validate the body against that workspace;
 never reconstruct or advance state from the commit body. Reload per
-[`context-hygiene.md`](../../devrites-lib/reference/standards/context-hygiene.md)
+[`context-hygiene.md`](skill://devrites-lib/reference/standards/context-hygiene.md)
 (`.devrites/ACTIVE`, `state.md`, `questions.md`, `decisions.md`, `test-plan.md`/`evidence.md`).
 
 ## Collapse at ship
 WIP commits are scratch and never reach shared history. `/rite-ship` folds them into the
 one atomic feature commit before the Conventional-Commit ladder: see the collapse step in
-[git-ship.md](../../rite-ship/reference/git-ship.md). Result: one clean commit, bisect
+[git-ship.md](skill://rite-ship/reference/git-ship.md). Result: one clean commit, bisect
 stays green.

package/pack/generated/omp/skills/rite-build/reference/frontend-trigger.md

@@ -28,7 +28,7 @@ If the slice spans both layers, it's both a frontend **and** a backend slice. De
 (DB → service → API → UI), apply the engineering rules to the backend and
 `devrites-frontend-craft` to the UI, map each contract error to a real UI state, and
 **prove both layers** (contract tests + browser proof). See
-[`fullstack.md`](../../devrites-frontend-craft/reference/fullstack.md).
+[`fullstack.md`](skill://devrites-frontend-craft/reference/fullstack.md).
 
 ## When NOT triggered
 Pure backend/data/CLI/infra slices skip craft and browser proof, but still get tests

package/pack/generated/omp/skills/rite-build/reference/parallel-batch.md

@@ -63,7 +63,7 @@ case:** two parallel wrights share a path and fan-out proceeds without that
 check.
 
 Before `parallel select`, add each slice's hidden write surfaces (list owner:
-[repository-topology.md § Ownership rules](../../devrites-lib/reference/standards/repository-topology.md#ownership-rules))
+[repository-topology.md § Ownership rules](skill://devrites-lib/reference/standards/repository-topology.md#ownership-rules))
 — lockfile/manifest, the generated target of an edited source, migration chain,
 snapshot directory, formatter sweep — and compare paths case-folded
 (`src/Api.ts` = `src/api.ts`). Slices colliding on either run serially; the rest
@@ -104,7 +104,7 @@ Lease: `batch_id`, `created_at`, `base_sha`, `n`,
    proof in the same window as that review. Gap or Critical/Important → `gap`;
    else proof → `green|red|gap`.
    Reviewer fan-out for a batch is itself batched under
-   [`parallel-dispatch.md`](../../devrites-lib/reference/parallel-dispatch.md#scale-limits)
+   [`parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md#scale-limits)
    (≈4 concurrent read-only reviewers, 8 only with disjoint paths), and `max_agents`
    headroom bounds the batch size — one batch never assumes unbounded reviewers.
 5. Non-green siblings → **repair round** (below) in the same worktrees; lease
@@ -160,7 +160,7 @@ Repair rejected work in place; never discard/rebuild while budget remains.
   approach unsound and no corrected decomposition exists, that is exhaustion
   → blocked, preserve, STOP. **Reviewer stall/cancel or missing
   verdict** → reconcile the old host handle under
-  [terminal reconciliation](../../devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation)
+  [terminal reconciliation](skill://devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation)
   before re-dispatching the reviewer, not the wright. **Product/policy/
   irreversible** → stops for the human.
 - Dispatch one fresh repair-all `devrites-slice-wright` (cwd=worktree; step 3
@@ -174,7 +174,7 @@ Repair rejected work in place; never discard/rebuild while budget remains.
   to `B` — that destroys the work under repair. The commit must still descend
   from `B` and diff path-exact vs `B`.
 - Budget and exhaustion follow only
-  [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).
   Record one failed invariant, mechanism, reproduction, correction, and decisive
   recheck per fingerprint; never use an umbrella like "covering" or "review is red again".
 - A distinct post-repair Critical/Important gets a new fingerprint: refresh the

package/pack/generated/omp/skills/rite-build/reference/phase-contract.md

@@ -1,14 +1,14 @@
 # rite-build phase contract
 
 Apply [`one-slice-cycle.md`](one-slice-cycle.md) and
-[`candidate-integrity.md`](../../devrites-lib/reference/candidate-integrity.md).
+[`candidate-integrity.md`](skill://devrites-lib/reference/candidate-integrity.md).
 Opt-in `--parallel N` replaces steps 2–8 with [`parallel-batch.md`](parallel-batch.md);
 Spec Drift Guard still applies.
 
 1. **Gate.** Read core, `.devrites/ACTIVE`, then `devrites-engine orient <slug>`
    (`devrites-engine next <slug>` prints the minimal remaining path) and the
    Build read-next in
-   [`workspace-artifact-schema.md`](../../devrites-lib/reference/workspace-artifact-schema.md#read-next-by-phase):
+   [`workspace-artifact-schema.md`](skill://devrites-lib/reference/workspace-artifact-schema.md#read-next-by-phase):
    the selected slice via `devrites-engine observe slice <slug> <SLICE-ID>`, not whole
    `tasks.md`; over-budget or `bulk_files` artifacts are read by anchor only. Require
    `Implementation readiness: READY`, current `Readiness inputs SHA-256`, exact
@@ -23,7 +23,7 @@ Spec Drift Guard still applies.
    Verify relevant assumptions live; falsified acceptance/architecture/scope/proof
    routes through Spec Drift Guard. Resolve human-owned/irreversible gates before
    source work; AFK follows its ceiling. Vet-ready Workflow Artifacts use
-   [`workflow-artifacts.md`](../../devrites-lib/reference/standards/workflow-artifacts.md).
+   [`workflow-artifacts.md`](skill://devrites-lib/reference/standards/workflow-artifacts.md).
 3. **Dispatch.** Apply [`wright-dispatch.md`](wright-dispatch.md). Put the smallest
    exact project-relative source/test path list directly in the task;
    dispatch the exact `devrites-slice-wright` fresh. Root never writes product
@@ -48,7 +48,7 @@ Spec Drift Guard still applies.
    same-environment baseline; otherwise unresolved.
 
    Technical failure uses `devrites-debug-recovery` and
-   [canonical recovery](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
+   [canonical recovery](skill://devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
    Reapply host admission before correction; affected proof/evidence follows candidate
    integrity. Human gates remain product/irreversible/access decisions.
 7. **Record green.** Upsert actual scoped `present`/`deleted` rows in `touched-files.md`;
@@ -75,7 +75,7 @@ and one exact `devrites-doubt-reviewer` per stood decision that meets
 `devrites-doubt` § When to use (boundary, data model, auth, public API, migration,
 user flow, assumption tests cannot prove); other stood decisions are recorded in
 `decisions.md` without dispatch. Bundles take `--slice <SLICE-ID>`. Dispatch fresh,
-read-only under [`parallel-dispatch.md`](../../devrites-lib/reference/parallel-dispatch.md).
+read-only under [`parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md).
 Wait for every required account to become terminal; missing/gap needs a valid result.
 Fold supported in-scope Critical/Important findings by cause into one inventory.
 Dispatch one repair-all wright instructed to fix every finding, then attack its own
@@ -90,7 +90,7 @@ and unchanged-coverage evidence under candidate integrity; include newly trigger
 roles. A changed contract or uncertain impact requires the full inventory.
 Collect all required rechecks before another folded correction. Canonical recovery
 owns fingerprints/budget and the
-[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):
 a recheck's `Late:` rows on hunks unchanged since that role's previous pass go to
 `touched-files.md` `## Review trail` for `/rite-review`, not into another slice
 repair, unless Critical with a failure path. Evidenced scope coverage never

package/pack/generated/omp/skills/rite-build/reference/tdd.md

@@ -19,7 +19,7 @@ produce evidence:
 
 ## Rules
 - Use the project's existing test framework and commands (per the discovery contract
-  [`test-command-discovery.md`](../../rite-prove/reference/test-command-discovery.md)). Don't introduce a new test runner
+  [`test-command-discovery.md`](skill://rite-prove/reference/test-command-discovery.md)). Don't introduce a new test runner
   to prove a slice.
 - One behavior per test; name it for the behavior, not the function.
 - A green test you never saw fail proves nothing: always see red first.

package/pack/generated/omp/skills/rite-build/reference/wright-dispatch.md

@@ -6,11 +6,20 @@ Wright alone writes; no agents.
 
 ## Host gate
 
-Apply [source-writing boundary](../../devrites-lib/reference/standards/agents.md#source-writing-boundary):
+Apply [source-writing boundary](skill://devrites-lib/reference/standards/agents.md#source-writing-boundary):
 omp has no permission modes: only the wright's `tools` allowlist has `edit`/`write`, and the root stays source-read-only by instruction. Claude grants only the exact wright `acceptEdits`; Codex uses its workspace root,
 the exact `:workspace` wright, and read-only specialists. Never bypass/substitute
 the wright or recreate an engine bridge.
 
+## Standalone correction
+
+`/rite-quick`, `/rite-dogfood`, and `/rite-pr-feedback` fixes have no `tasks.md`
+slice, so skip Prepare's `check slice`, `context --slice`, and the build `dispatch`
+wave. Give the wright an inline contract: goal, acceptance check, exact
+project-relative paths, and proof command. With an active workspace, `claim add`
+those paths first. On return, compare its file list and `git diff --name-only`
+with the paths; reject any extra path.
+
 ## Isolated writer-worktree pilot
 
 Use native isolation only when the current host exposes an explicit named-writer
@@ -50,12 +59,12 @@ worktrees stay forbidden.
    directories/globs, traversal, symlink escapes, duplicates, and `.devrites/**`.
    A target composed only of vetted executable workflow artifacts routes to the
    controlling root under
-   [`workflow-artifacts.md`](../../devrites-lib/reference/standards/workflow-artifacts.md);
+   [`workflow-artifacts.md`](skill://devrites-lib/reference/standards/workflow-artifacts.md);
    its rejection here is not a blocker.
 2. Include goal, verbatim acceptance, exclusions, context,
    `test-plan.md` proof commands, applicable standards, and the exact
    `WIP(<slug>):` subject (no slice id). Build the wright's read-set with
-   `devrites-engine context <slug> --phase build --role slice-wright --slice <SLICE-ID> --trigger <set>`
+   `devrites-engine context --skills-root .omp/skills <slug> --phase build --role slice-wright --slice <SLICE-ID> --trigger <set>`
    and hand it the bundle path (over-budget artifacts arrive as anchor indexes;
    read owning sections live). Evaluate each trigger condition and pass those
    that fire (TDD slice → `tdd`, AFK run → `afk`, UI work → `frontend`, …).
@@ -64,6 +73,8 @@ worktrees stay forbidden.
    topology/data/integration standard, include only the feature-specific owner/invariant,
    failure or partial-state case, recovery rule, and required proof from the vetted plan.
    Do not paste the whole standard or silently omit an applicable risk.
+   Quote every active `decisions.md` carry-forward constraint whose `Files:`
+   overlap the task paths (or that names no files).
    A new path requires a new bounded contract; the wright cannot widen the task.
 3. Record `git diff --name-only` before dispatch so unrelated work remains
    distinguishable. For an isolated pilot, also record committed base SHA and exact
@@ -76,8 +87,8 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
-is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+[`agents.md`](skill://devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](skill://devrites-lib/reference/standards/workflow-artifacts.md).
 Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
@@ -85,7 +96,7 @@ launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
 rounds on one slice, `open` blocks for a reslice review: propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
-[acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
+[acceptance-preserving-reslice](skill://devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record
 `## <DRIFT-ID> — <SLICE-ID> reslice review` with why no smaller split exists and
 reopen with `--reslice-review <DRIFT-ID>`. Use
@@ -97,7 +108,7 @@ substitute a generic agent. Opt-in `/rite-build --parallel N` fans out only unde
 After `claim add`, every terminal path releases the claim with
 `devrites-engine claim release --session <id> --id <claim-id>`: successful
 return, rejected result, stop, or a launch the host refused with no handle. A
-timeout or unknown outcome keeps the claim ([`parallel-dispatch.md`](../../devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation)).
+timeout or unknown outcome keeps the claim ([`parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation)).
 TTL is crash recovery, not normal cleanup.
 
 ## Inspect and prove
@@ -125,7 +136,7 @@ TTL is crash recovery, not normal cleanup.
    and, in the same window, run only repository proof already approved by
    `test-plan.md` against the same frozen candidate; neither waits for the
    other. Human choices return; technical failures follow
-   [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).
    Derive accounting from recorded reproductions, corrections, and decisive rechecks.
 4. After proof, inspect `git diff --name-only` again in case a proof tool changed
    source; a change rejects that candidate and voids the concurrent review. A
@@ -141,3 +152,11 @@ TTL is crash recovery, not normal cleanup.
    escalation without the checked-assumption list (verified|falsified) is
    malformed; root sweeps the unchecked remainder per
    [`spec-drift-guard.md`](spec-drift-guard.md) before repair.
+6. **Learning edge.** A correction accepted with a confirmed cause (a review,
+   gate, or proof rejection plus its fix) becomes a carry-forward constraint so
+   later slices start where this one ended: append one line under
+   `decisions.md` `## Carry-forward constraints` —
+   `- <rule> — from <SLICE-ID> (<evidence ref>); Files: <paths>`. Record the
+   derived rule, not the output, at the scope its evidence supports: "this
+   button is blue" never becomes "buttons are blue". Never edit `tasks.md` mid-build (it is a
+   readiness input). **Failing case:** slice 3 repeats a defect slice 2 fixed.

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/afk-hitl.md","rite-clarify/reference/decision-coverage.md","rite-clarify/reference/anti-patterns.md"],"triggers":{"agents":["devrites-lib/reference/standards/agents.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md"],"workspaceByRole":{"evidence-scout":["brief.md","spec.md","state.md","questions.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase clarify` 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 clarify` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-clarify: resolve product decisions
@@ -16,15 +16,15 @@ decision, ask no questions. Otherwise stay until each material decision has an
 owner. This phase settles behavior and constraints; `/rite-define` settles
 implementation.
 
-Reuse [`devrites-interview`](../devrites-interview/SKILL.md) in `/clarify mode`. Write
+Reuse [`devrites-interview`](skill://devrites-interview/SKILL.md) in `/clarify mode`. Write
 `decision-coverage.md` as scan evidence, not an interview transcript.
 
 ## Rules consulted
 
-Read [`core.md`](../devrites-lib/reference/standards/core.md), its [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md), and
+Read [`core.md`](skill://devrites-lib/reference/standards/core.md), its [`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md), and
 [`reference/decision-coverage.md`](reference/decision-coverage.md). Fresh evidence
 dispatch uses
-[`agents.md`](../devrites-lib/reference/standards/agents.md).
+[`agents.md`](skill://devrites-lib/reference/standards/agents.md).
 
 ## Rules