devrites 6.0.3 → 6.1.0

package/pack/generated/omp/skills/devrites-frontend-craft/reference/quality-standards.md

@@ -33,8 +33,8 @@ these are the floor, not the ceiling.
 ## Responsive
 - Fluid layouts; no fixed widths that break. Verify at **320 / 768 / 1024 / 1440** px;
   preserve content and controls at **200% text zoom** and **400% browser zoom from
-  1280 px** (320 CSS px). This is the canonical viewport set for UI evidence: [`ui.md`](../../rite-polish/reference/ui.md), [`browser-proof-checklist.md`](../../devrites-lib/reference/standards/browser-proof-checklist.md), and
-  [`browser-polish-evidence.md`](../../rite-polish/reference/browser-polish-evidence.md) cite it rather than restating it.
+  1280 px** (320 CSS px). This is the canonical viewport set for UI evidence: [`ui.md`](skill://rite-polish/reference/ui.md), [`browser-proof-checklist.md`](skill://devrites-lib/reference/standards/browser-proof-checklist.md), and
+  [`browser-polish-evidence.md`](skill://rite-polish/reference/browser-polish-evidence.md) cite it rather than restating it.
 - **No page-level horizontal scroll anywhere in 320–1920.** Sweep between checkpoints:
   a `1fr` track given a 1024 px image can overflow at 900 px. Fix intrinsic sizing
   (for example `minmax(0, 1fr)`), wrapping and media constraints; root clipping is
@@ -58,7 +58,7 @@ website by section 7") is a tell: **one declared color strategy and role budget*
 
 ## Numerical bar (enforceable specifics)
 
-These are the hard numbers that move "good UI" from opinion to checkable. Project tokens win when stricter. Contrast, target size, focus and reflow numbers are A11Y floors; the rest are DS build defaults. A review finding against a DS default needs the mismatch evidence of the [admission rule](../../rite-polish/reference/anti-ai-slop.md).
+These are the hard numbers that move "good UI" from opinion to checkable. Project tokens win when stricter. Contrast, target size, focus and reflow numbers are A11Y floors; the rest are DS build defaults. A review finding against a DS default needs the mismatch evidence of the [admission rule](skill://rite-polish/reference/anti-ai-slop.md).
 
 ### Color
 - **OKLCH-only** for new tokens: perceptually uniform, predictable lightness
@@ -241,10 +241,10 @@ rung that carries the structure.
   token.
 - **No decorative glass.** `backdrop-filter: blur(...)` is for a fixed/sticky surface over
   moving content (a sticky header, a sheet over scroll), never a default panel look
-  ([`anti-ai-slop.md`](../../rite-polish/reference/anti-ai-slop.md)).
+  ([`anti-ai-slop.md`](skill://rite-polish/reference/anti-ai-slop.md)).
 
 ### NEVER (UI numerical bar)
-- Never reintroduce anything [`rite-polish` anti-ai-slop](../../rite-polish/reference/anti-ai-slop.md) bans (review findings follow its admission rule).
+- Never reintroduce anything [`rite-polish` anti-ai-slop](skill://rite-polish/reference/anti-ai-slop.md) bans (review findings follow its admission rule).
 - Never hard-code a spacing value the 4 pt scale or project tokens cover.
 - Never animate an exit at 100 % of enter duration (feels uncontrolled).
 - Never use raw `z-index` numbers outside the semantic scale.
@@ -263,19 +263,19 @@ rung that carries the structure.
 - [ ] **Responsive** at the canonical viewport set (§ Responsive); no lost content or
       controls, no page overflow; bounded exceptions tested; zoom-safe
 - [ ] **No accessibility violations** (axe or equivalent, WCAG 2.2 tags enabled for a 2.2 AA claim); every `incomplete` result resolved as a manual row, `inapplicable` read as not exercised: zero violations alone never ticks this
-- [ ] Meets the **CWV budget** above (measure, don't assume; lab vs field status per [`performance.md`](../../devrites-lib/reference/standards/performance.md) § Frontend)
+- [ ] Meets the **CWV budget** above (measure, don't assume; lab vs field status per [`performance.md`](skill://devrites-lib/reference/standards/performance.md) § Frontend)
 - [ ] Aligned to the **design system** (tokens, components, type, spacing)
 - [ ] **Focus indicator** passes SC 2.4.7/1.4.11 (DS focus token where declared); no custom scrollbar the DS lacks (§ Browser chrome)
 - [ ] Clickables show `cursor: pointer` + a hover state; icons are SVG from the one set
       (no emoji); nothing trapped under fixed/sticky bars
 - [ ] **Consistency locks hold** (declared color strategy/roles / one radius scale / one theme) and the
-      mechanical pre-flight's ENG/DS rows pass ([`anti-ai-slop.md`](../../rite-polish/reference/anti-ai-slop.md))
+      mechanical pre-flight's ENG/DS rows pass ([`anti-ai-slop.md`](skill://rite-polish/reference/anti-ai-slop.md))
 
 ## Craft convergence bar
 
 Craft work terminates; it does not loop. Findings classify as **Critical /
 Important / Suggestion** on the pack's severity scale, owned by
-[`code-review.md`](../../devrites-lib/reference/standards/code-review.md): done
+[`code-review.md`](skill://devrites-lib/reference/standards/code-review.md): done
 means zero Critical, zero Important, and every remaining Suggestion accepted **in
 writing** (owner + reason) in `polish-report.md` — an unwritten suggestion is an
 ignored finding, not an accepted one. AES proposals are capped at Suggestion and

package/pack/generated/omp/skills/devrites-frontend-craft/reference/reuse-first.md

@@ -1,7 +1,7 @@
 # Reuse first: frontend application
 
 Frontend application of the canonical rule in
-[`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md#reuse-before-you-write):
+[`coding-style.md`](skill://devrites-lib/reference/standards/coding-style.md#reuse-before-you-write):
 reuse → extend → build new, AHA caveat below. Before creating any new component, style,
 token, icon, hook, util, or helper, search the project first.
 
@@ -9,7 +9,7 @@ This applies to UI **and** non-UI code: utilities, helpers, types, validators, s
 formatters, hooks, query helpers: anything that might already exist.
 
 ## The decision (in order)
-1. **Search first.** Apply `../../devrites-lib/reference/standards/tooling.md`: use the
+1. **Search first.** Apply `skill://devrites-lib/reference/standards/tooling.md`: use the
    primary available code index to find similar definitions, cross-check only a named
    unresolved predicate, then fall back to grep/glob over `components/`, design tokens, hooks/,
    utils/, lib/. Look for things doing the *same job*, not just the same name.

package/pack/generated/omp/skills/devrites-frontend-craft/reference/shape.md

@@ -9,7 +9,7 @@ is a **per-slice refinement of that brief for the surface you're about to code**
 the answers below against the brief and fill any slice-specific gaps; don't re-derive the
 design. **Only shape from scratch here** when a UI slice has no `design-brief.md` (a spec
 written before shaping), then run `devrites-ux-shape` first; only if it cannot run, answer
-these and write the brief per `../../devrites-ux-shape/reference/brief-template.md`, and
+these and write the brief per `skill://devrites-ux-shape/reference/brief-template.md`, and
 return through `/rite-vet` before code.
 
 ## Answer these before writing markup
@@ -41,7 +41,7 @@ return through `/rite-vet` before code.
 The answers live in the feature's `design-brief.md` (shaped at spec by `devrites-ux-shape`).
 In build, append any slice-specific refinement to its **Build-time refinements** section;
 if you shaped from scratch (no brief existed), write the brief now per
-`../../devrites-ux-shape/reference/brief-template.md`. This drives the build and the polish
+`skill://devrites-ux-shape/reference/brief-template.md`. This drives the build and the polish
 checklist.
 
 ## NEVER (shape)

package/pack/generated/omp/skills/devrites-interview/SKILL.md

@@ -4,7 +4,7 @@ description: Interview the user one question at a time to extract intent. Use wh
 user-invocable: false
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","rite-spec/reference/interview-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["spec.md","questions.md","decisions.md","assumptions.md","decision-coverage.md","state.md"]} -->
-> Read-set manifest: `devrites-engine context [slug] --skill devrites-interview` bundles every file named below into one deduplicated read.
+> Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --skill devrites-interview` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # devrites-interview: extract intent
 
@@ -30,7 +30,7 @@ spec, plan, or code.
   is explicitly selected or explicitly deferred by the user. A cap MUST NOT move a blocker to
   `assumptions.md`. Own and log reversible, low-impact technical details instead of asking.
 - **Structured options** when the space is enumerable: present them as the standard ranked
-  **option set** ([[`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) → "Option set"](../devrites-lib/reference/standards/afk-hitl.md#option-set-how-every-gap-is-presented)): recommended **first**, labelled
+  **option set** ([[`afk-hitl.md`](skill://devrites-lib/reference/standards/afk-hitl.md) → "Option set"](skill://devrites-lib/reference/standards/afk-hitl.md#option-set-how-every-gap-is-presented)): recommended **first**, labelled
   `(Recommended)`, each with a dimension-tagged rationale (`logic · infra · business ·
   architecture`, + `security`/`UX`/`risk` when in scope), plus the escape hatch. Render via
   `ask` when the harness has it:
@@ -73,7 +73,7 @@ Approval requires an **explicit** yes. Treat these replies differently:
 For a short or vague request (`"design a contact page"`), do not ask isolated questions.
 Sketch the **decision tree** first, then resolve each branch **depth-first** with the
 protocol above. Domain branches per area:
-[`../rite-spec/reference/interview-patterns.md`](../rite-spec/reference/interview-patterns.md).
+[`skill://rite-spec/reference/interview-patterns.md`](skill://rite-spec/reference/interview-patterns.md).
 
 ## Reframe (once, when stuck)
 If the interview is not converging, use **one** turn to challenge the premise:

package/pack/generated/omp/skills/devrites-lib/reference/intent-map.md

@@ -24,7 +24,7 @@ Every model-invoked `rite-*` appears in the table or a tie-breaker; one absent i
 same index bug. Rites omitted from both are explicit-only (`disable-model-invocation:
 true`) and run only by exact invocation or the `/rite` menu. Internal `devrites-*`
 specialists route by their description plus the specialist-trigger line in
-[`rite/SKILL.md`](../../rite/SKILL.md#dispatch) § Dispatch; their tie pairs are below.
+[`rite/SKILL.md`](skill://rite/SKILL.md#dispatch) § Dispatch; their tie pairs are below.
 **Failing case:** the table still lists a deleted skill after rename, or a model-invoked
 rite has no row while this section claims completeness.
 
@@ -69,15 +69,15 @@ Wrong-skill fire: stop, admit it, switch rites.
 | Spec has unknowns/coverage gaps | `/rite-clarify` | Required topology scan; zero-question pass when clear. |
 | Derive intent from existing code without an active feature contract | `/rite-adopt` | Establish the brownfield contract. |
 | Reconcile implementation with an active feature contract | `/rite-converge` | Identify gaps and add missing slices. |
-| Older workspace cannot resume | `/rite-upgrade` | Audit cited current-contract defects; age alone is no defect. Route semantic repairs to normal owners; preserve history without synthetic proof. |
+| Older workspace cannot resume (explicit only) | `/rite-upgrade` | Audit cited current-contract defects; age alone is no defect. Route semantic repairs to normal owners; preserve history without synthetic proof. |
 | Turn an approved spec into its first plan | `/rite-define` | No `tasks.md` slices yet; writes architecture, slices, traceability. |
 | Reslice, reorder, or repair an existing plan | `/rite-plan` | Slices exist and evidence invalidates them. |
 | Review plan before code | `/rite-vet` | Every plan; depth scales to risk. |
 | Small safe fix | `/rite-quick` | Escalates auth, migration, public API, destructive, ambiguous, or multi-slice work. |
 | Mid-size work, fast lane (explicit only) | `/rite-fast` | Spec + plan + questions once, ≤10 slices, one completeness check, review, polish, proof; risk deepens questions. |
 | Prove UI/runtime | `/rite-prove` + `devrites-browser-proof` | Capture real evidence. |
-| Stuck/unfamiliar | `/rite-zoom-out` | Map before editing. |
-| Teach me | `/rite-explain` | Human learning loop. |
+| Stuck/unfamiliar (explicit only) | `/rite-zoom-out` | Map before editing. |
+| Teach me (explicit only) | `/rite-explain` | Human learning loop. |
 | Decide ship readiness | `/rite-seal` | Decides; never mutates Git. |
 | Execute ship after GO | `/rite-ship` | Requires GO/type-GO. |
 | Unattended lifecycle | `/rite-autocomplete` | Clean baseline/checkpoints; hard gates stop. |

package/pack/generated/omp/skills/devrites-lib/reference/parallel-dispatch.md

@@ -4,7 +4,7 @@ Host dispatch; DevRites governs.
 
 ## Roster
 
-Review: Spec/Code; Seal: all applicable roles.
+Review: Spec/Code plus triggered frontend/security/performance; Seal: all applicable roles.
 
 | Reviewer | Fires | Trigger |
 |---|---|---|
@@ -34,12 +34,13 @@ If the candidate diff has no matching surfaces, record
    unverified independence is a gap. Do not launch a probe agent per task;
    still validate each result's context and candidate.
 2. Build each reviewer's read-set once with
-   `devrites-engine context <slug> --phase <p> --role <role> --trigger <set>` and
+   `devrites-engine context --skills-root .omp/skills <slug> --phase <p> --role <role> --trigger <set>` and
    hand the bundle path as the packet's source list instead of a file roster.
    Build roles add `--slice <SLICE-ID>` (slice-scoped, slice-named bundle).
    Evaluate the skill's trigger conditions and pass each that fires — a role's
-   Trigger column maps to manifest names: `security-auditor` → `security`,
-   `frontend-reviewer` → `ui`/`frontend`, `performance-reviewer` → `performance`.
+   Trigger column maps to the phase manifest's names: `security-auditor` →
+   `security`; at Review, `frontend-reviewer` → `ui` and `performance-reviewer` →
+   `performance`. Seal declares neither; those roles load their own standards.
    The `agents` dispatch contract needs no flag: `--role` auto-fires it
    (`auto=[agents]` in the output). The command prints `unselected=[...]`; an
    omitted applicable trigger is a gap, not a shortcut.
@@ -97,7 +98,7 @@ in `review.md`/`seal.md`.
   the same wave (`dispatch open ... --role code-reviewer.frontend --role
   code-reviewer.backend`; distinct handles — the sealed wave's handles and start
   stamps are the concurrency receipt). Build each bundle with `devrites-engine
-  context <slug> --phase <p> --role code-reviewer --trigger <set> --out
+  context --skills-root .omp/skills <slug> --phase <p> --role code-reviewer --trigger <set> --out
   ctx/<p>-code-reviewer.<lane>.bundle.md`; the default name collides. Each packet
   names its lane, the lane's path set (the whole diff stays readable for context),
   the triggered profile ([`review/README.md`](standards/review/README.md)), and the
@@ -138,7 +139,7 @@ claim is released or its holder is proven terminal. A wright that never returned
 admitted result leaves unadmitted bytes: task-path changes since its pre-dispatch
 `git diff --name-only` baseline are never cited as built nor discarded, and are
 named in the re-dispatch contract; changes outside task paths stop for the human
-(Converge side: [`rite-converge`](../../rite-converge/SKILL.md)).
+(Converge side: [`rite-converge`](skill://rite-converge/SKILL.md)).
 
 ## Scale limits
 
@@ -155,4 +156,4 @@ or with the implementer. A mesh without a parent is not a DevRites profile.
 **Failing case:** two reviewers agree a compromise in a shared channel and the
 parent records that compromise as independent review.
 
-Arbitration/independence → [agents.md § Independence](standards/agents.md#independence); writer batches → [`parallel-batch.md`](../../rite-build/reference/parallel-batch.md).
+Arbitration/independence → [agents.md § Independence](standards/agents.md#independence); writer batches → [`parallel-batch.md`](skill://rite-build/reference/parallel-batch.md).

package/pack/generated/omp/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -108,12 +108,12 @@ candidate manifest to cover the whole recorded chain — run
 `devrites-engine state merge-manifest <slug>` before Prove.
 
 - Only continuations recorded in the parent's `decisions.md` sequence
-  ([slicing.md § Continuation workspaces](../../../rite-plan/reference/slicing.md#continuation-workspaces))
+  ([slicing.md § Continuation workspaces](skill://rite-plan/reference/slicing.md#continuation-workspaces))
   qualify; no recorded next entry, or the cap/review-queue bound reached, stops
   with the winning reason.
 - Milestones are **not** shipped: they stay sealed and unarchived in `.devrites/work/`
   with `Next step: /rite-ship` preserved. Local `WIP(<slug>):` checkpoints still
-  land ([checkpoint.md](../../../rite-build/reference/checkpoint.md)), so the tree
+  land ([checkpoint.md](skill://rite-build/reference/checkpoint.md)), so the tree
   stays clean and crash-safe.
 - Git stays human-gated. The release ship is one disclosed plan, one literal `GO`, and
   one native approval; it collapses the sequence's `WIP` commits into the single
@@ -132,13 +132,14 @@ from `--max-slices`. **Failing case:** `/rite-autocomplete --parallel 5` honors
 leftover `max_parallel: 1` and stays serial.
 Unattended runs take the largest eligible set ≤ that cap and recompute after
 every completed round (serial slice or parallel integrate)
-([parallel-batch.md § Dynamic selection and re-batching](../../../rite-build/reference/parallel-batch.md#dynamic-selection-and-re-batching)).
+([parallel-batch.md § Dynamic selection and re-batching](skill://rite-build/reference/parallel-batch.md#dynamic-selection-and-re-batching)).
 
 ## Unattended resource envelope
 
-AFK writer admission needs a bounded input queue, effective slice cap, and valid
-`max_agents`, `max_minutes`, and `max_review_queue`. Existing sentinels
-that declare writer admission but miss/malform these fail closed; cold resume keeps the
+Outside `/rite-autocomplete`, AFK writer admission needs a bounded input queue,
+effective slice cap, and valid `max_agents`, `max_minutes`, and `max_review_queue`.
+Existing sentinels that declare writer admission but miss/malform these fail closed
+(Autocomplete's sentinel omits them as unlimited; see below); cold resume keeps the
 state-owned slice counter. A leftover `expires_at` is ignored and never rewritten.
 Read-only watchers use equivalent native caps from [`loop-operations.md`](loop-operations.md).
 
@@ -148,7 +149,7 @@ counts open validating questions plus unresolved admitted Critical/Important fin
 Above it stop; at it run only reconciliation that reduces the queue. Optional
 `max_tokens`/`max_cost_usd` lower enforceable native caps; if declared but unobservable, stop.
 `/rite-autocomplete` deliberately ignores `max_slices`, `max_agents`, `max_minutes` and
-`max_review_queue` ([stop-conditions.md](../../../rite-autocomplete/reference/stop-conditions.md));
+`max_review_queue` ([stop-conditions.md](skill://rite-autocomplete/reference/stop-conditions.md));
 there they are not a ceiling.
 
 Numeric limits are nonnegative decimals. Before costly checks, fan-out, or writing,
@@ -168,7 +169,7 @@ To leave AFK, delete the file. The next skill invocation reverts to HITL.
 ## The four gates
 
 Every `Mode: HITL` slice declares a `Gate:` and an `SLA:`. See
-[`.omp/skills/rite-define/reference/gates.md`](../../../rite-define/reference/gates.md)
+[`.omp/skills/rite-define/reference/gates.md`](skill://rite-define/reference/gates.md)
 for the full taxonomy. Summary:
 
 | Gate | Stakes | Pause? | SLA | AFK auto-handle when in `allow_gates`? |
@@ -290,7 +291,7 @@ boundary owns any such request and requires explicit user approval.
 When a HITL gate fires, `/rite-build` sets cursor `status` to `awaiting_human` and
 `next_action` to `/rite-resolve <qid> "<answer>"`, then writes the `Awaiting human` table
 (`question_id`, `gate`, `blocking_slices`) owned by
-[`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.
 The question text, `proposed` answer, and `raised_at` live in the `questions.md` entry.
 Legacy `- Status:`/`- Next step:`/`- qid:` bullet keys are engine-accepted aliases, not
 the authoring format.
@@ -304,7 +305,7 @@ Three shapes:
 ```
 /rite-resolve <qid> "<answer>"
 /rite-resolve --drop <qid> ["<reason>"]
-/rite-resolve --batch <path-to-yaml>
+/rite-resolve --batch <plain-text-file>
 ```
 
 `/rite-resolve` is the canonical writer for **async** resume: a gate that already paused and
@@ -358,7 +359,7 @@ access, safety and irreversible-action boundaries independently stop work.
   recovery. Initial discovery and expected test-first RED are not corrections;
   total rounds, re-batches and distinct-finding counts never exhaust recovery.
   Every 5 Build wright rounds on one slice, the next first needs a reslice review
-  ([`wright-dispatch.md`](../../../rite-build/reference/wright-dispatch.md#run)).
+  ([`wright-dispatch.md`](skill://rite-build/reference/wright-dispatch.md#run)).
 - **Rechecks are scoped; late findings never reopen the round.** *Late* applies only
   from a phase's **second** review pass (Vet 1b, Build's recheck after the first repair,
   Review step 7); an initial pass has no late findings and every supported finding is
@@ -412,7 +413,7 @@ AFK changes which decisions are automatic. It changes nothing else.
 - Workflow integration: `/rite-build` (`.omp/skills/rite-build/SKILL.md`),
   the readiness / HITL pre-flight stages before dispatch, and the DOUBT → PROVE
   (fail-on-red) → RECORD stages on the wright's return
-  ([`one-slice-cycle.md`](../../../rite-build/reference/one-slice-cycle.md)).
+  ([`one-slice-cycle.md`](skill://rite-build/reference/one-slice-cycle.md)).
 - Render contract: `.omp/skills/rite-build/reference/checkpoint-protocol.md`.
 - Loop discipline: `.omp/skills/rite-build/reference/afk-discipline.md`.
 - Gate taxonomy: `.omp/skills/rite-define/reference/gates.md`.

package/pack/generated/omp/skills/devrites-lib/reference/standards/agents.md

@@ -2,7 +2,7 @@
 
 > Applies when: dispatching or admitting any devrites-* role; the source-writing boundary.
 
-Follow DevRites policy and [`depth profiles`](../orchestration-profiles.md).
+Follow DevRites policy and [`depth profiles`](skill://devrites-lib/reference/orchestration-profiles.md).
 
 ## Authority
 
@@ -33,7 +33,7 @@ Follow DevRites policy and [`depth profiles`](../orchestration-profiles.md).
 | `devrites-retrospector` |
 | `devrites-slice-wright` |
 
-Files own briefs; [`parallel-dispatch.md`](../parallel-dispatch.md) owns rosters.
+Files own briefs; [`parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md) owns rosters.
 
 ## Native invocation
 
@@ -41,7 +41,7 @@ Skills name exact fresh roles, omit native fields;
 hosts spawn/wait/deliver. Root MUST NOT advance/claim completion before admitting required results;
 running/orphaned/unavailable = `gap` — no root/generic substitute.
 Where a feature workspace exists, every fresh dispatch to a named `devrites-*`
-role — wave or solo — builds its read-set with `devrites-engine context <slug>
+role — wave or solo — builds its read-set with `devrites-engine context --skills-root .omp/skills <slug>
 --phase <p> --role <role>` and tracks the launch through `devrites-engine
 dispatch <slug> open|start|seal|return` (a solo dispatch is a wave of one;
 start/return auto-record metrics). Without a workspace the plain host dispatch
@@ -52,7 +52,7 @@ Workflow-named skills (e.g. devrites-source-driven) are invoked inline in the ro
 
 omp: only the wright's `tools` allowlist has `edit`/`write`; the root stays source-read-only by instruction. Claude grants only wright `acceptEdits`; Codex root is workspace-capable (children cannot elevate). Wright alone `:workspace`; others `:read-only`. Wright gets the smallest exact project-relative source/test list — no directories/globs, traversal, or `.devrites/**`; no scope widening; root rejects `git diff --name-only` extras. Never patch product source/tests in root, bypass/substitute wright, accept drift, or recreate a dispatch bridge.
 
-Isolated-worktree pilot only under [`wright-dispatch.md`](../../../rite-build/reference/wright-dispatch.md#isolated-writer-worktree-pilot): one writer, committed/clean baseline, non-submodule parent, exact transfer commit, candidate reconciliation — never parallel writers nor weaker exact-path admission. Root may materialize only exact Vet-ready workflow-artifact paths per [`workflow-artifacts.md`](workflow-artifacts.md) — not a writer dispatch or candidate mutation.
+Isolated-worktree pilot only under [`wright-dispatch.md`](skill://rite-build/reference/wright-dispatch.md#isolated-writer-worktree-pilot): one writer, committed/clean baseline, non-submodule parent, exact transfer commit, candidate reconciliation — never parallel writers nor weaker exact-path admission. Root may materialize only exact Vet-ready workflow-artifact paths per [`workflow-artifacts.md`](workflow-artifacts.md) — not a writer dispatch or candidate mutation.
 
 Each job gets objective/exclusions, exact paths/immutable candidate, rubric/result shape, a **stop condition** (when to return), and the exact result shape; a dispatch missing them is malformed and re-issued. Briefs MUST NOT seed verdict/severity cap/conclusion/suppression. Results state status/scope, outcome, commands/escalation; wright adds paths, changed files, gates, stood decisions; results never widen scope.
 
@@ -63,7 +63,7 @@ starts, it records an advisory claim — `devrites-engine claim add --session
 <id> <paths>` — retains the returned `<claim-id>`, then checks the same paths
 with `devrites-engine claim check --session <id> <paths>`; a held claim from a
 live foreign session is a stop-and-report, not a merge-later problem. On every
-host-confirmed terminal path after `add` ([unknown outcomes keep it](../parallel-dispatch.md#cancellation-and-terminal-reconciliation)) — return,
+host-confirmed terminal path after `add` ([unknown outcomes keep it](skill://devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation)) — return,
 rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
@@ -151,7 +151,7 @@ return is the bundle the root writes) and the wright's change evidence.
 Root rejects stale/out-of-scope work, dedupes by root cause, records
 accepted conclusions, and reruns only affected proof/review. Reconciliation runs
 only after every dispatch reaches a terminal classification
-([parallel-dispatch.md](../parallel-dispatch.md)); findings that do not survive stay
+([parallel-dispatch.md](skill://devrites-lib/reference/parallel-dispatch.md)); findings that do not survive stay
 visible as `withdrawn: <n> (<reason>)` in the account rather than being silently
 dropped, so a later reader can audit what was discarded and why.
 Route defects before correction: product/acceptance → Spec Drift Guard/Clarify;

package/pack/generated/omp/skills/devrites-lib/reference/standards/browser-proof-checklist.md

@@ -3,7 +3,7 @@
 > Applies when: UI proof: compact sweep before claiming a rendered/browser pass.
 
 Compact sweep only. Numbers and failing cases live in
-[`quality-standards.md`](../../../devrites-frontend-craft/reference/quality-standards.md)
+[`quality-standards.md`](skill://devrites-frontend-craft/reference/quality-standards.md)
 § Focus & states, § Responsive, and § Browser chrome — do not restate a shorter
 viewport set here.
 
@@ -14,7 +14,7 @@ viewport set here.
   stale candidate is missing evidence. Recapture; until resolved, record
   `cannot_verify` and block visual approval. A convincing narrative cannot repair it.
 - **Evidence matrix.** Layout-bearing states (default, long content, and every
-  role-applicable surface state from [`quality-standards.md`](../../../devrites-frontend-craft/reference/quality-standards.md) § Focus & states) × every
+  role-applicable surface state from [`quality-standards.md`](skill://devrites-frontend-craft/reference/quality-standards.md) § Focus & states) × every
   canonical viewport; interaction states at ≥1 small and ≥1 large viewport (hover
   only with a hover-capable pointer); one keyboard traversal; a `reduce` capture when
   motion changed; every shipped theme. Each cell holds a capture, `cannot_verify`, or

package/pack/generated/omp/skills/devrites-lib/reference/standards/ci-cd.md

@@ -46,7 +46,8 @@ Keep incomplete or risky behavior disabled behind a flag so deploy and release r
   gates precede exposure.
 - Feature flags separate exposure only when both states are tested, the off path preserves
   current behavior, and disabling the flag stops the risky effect. A flag cannot undo an
-  already destructive schema or data change.
+  already destructive schema or data change. Each flag names its removal trigger (full
+  rollout or kill); a flag past its trigger is dead code ([`deprecation.md`](deprecation.md)).
 
 ## Secrets
 

package/pack/generated/omp/skills/devrites-lib/reference/standards/code-review.md

@@ -14,7 +14,7 @@ If it does not, do not merge it.
   (~1000+ total lines) is an inspection signal: extract the helper or module *first*,
   then add.
 - To self-split: **stack** (land the smallest standalone piece, build on top) or cut a
-  **thinner vertical slice** ([`slicing.md`](../../../rite-plan/reference/slicing.md)). Whole-file deletions and
+  **thinner vertical slice** ([`slicing.md`](skill://rite-plan/reference/slicing.md)). Whole-file deletions and
   mechanical refactors may run large: review intent, not every line.
 
 ## What to check (tests first)
@@ -33,7 +33,7 @@ If it does not, do not merge it.
    `devrites-engine check windows` flags the mechanical subset (suppressions,
    skip/focus, stubs, empty catch, deleted tests, stripped assertions) against
    `windows.md` waivers; loosened thresholds remain this sweep's judgment.
-3. **Correctness:** logic, edge cases, error paths, race conditions, wrong assumptions. For branching or boundary changes, run the [`edge-case trace`](edge-case-trace.md): relevant probe classes, fixed-set siblings, real wiring, negative intent, and deletion contracts with an evidence disposition.
+3. **Correctness:** logic, edge cases, error paths, race conditions, wrong assumptions. A join, match, upsert, or dedupe keyed on a mutable or non-unique attribute (email, name, title) instead of a stable ID is a finding ([`data-integrity.md`](data-integrity.md)). For branching or boundary changes, run the [`edge-case trace`](edge-case-trace.md): relevant probe classes, fixed-set siblings, real wiring, negative intent, and deletion contracts with an evidence disposition.
 4. **Readability:** names, function size, control flow, intent obvious without the author.
 5. **Architecture:** right seam, coupling/cohesion, fits existing patterns, no premature
    abstraction. Check how it fits the larger system as well as its local behavior.
@@ -168,7 +168,7 @@ at `/rite-review` / `/rite-seal`:
    human-approved exception** is a **Critical** finding and a **NO-GO** at seal, the same standing
    as an unproven acceptance criterion. Check the diff against each principle's scope; an absent
    or empty file means none are declared (gate passes).
-2. **The anti-slop charter** ([`anti-ai-slop.md`](../../../rite-polish/reference/anti-ai-slop.md)
+2. **The anti-slop charter** ([`anti-ai-slop.md`](skill://rite-polish/reference/anti-ai-slop.md)
    UI + code lists; [`prose-style.md`](prose-style.md) for prose). [`coding-style.md`](coding-style.md)
    points at the code list — it is not a second catalog. **Failing case:** a backend-only
    diff is charged UI anti-slop (Inter / lavender / gradient); those fire only when a

package/pack/generated/omp/skills/devrites-lib/reference/standards/coding-style.md

@@ -22,7 +22,7 @@ Handle unwanted cases first and return early; keep the success path flat.
 ## Comments explain *why*, not *what*
 - Self-explanatory code beats a comment restating it; delete commented-out code. The
   full comment do-not list (what-comments, tutorial noise, ownerless TODOs, edit-narration,
-  hedging) is owned by [`anti-ai-slop.md`](../../../rite-polish/reference/anti-ai-slop.md)
+  hedging) is owned by [`anti-ai-slop.md`](skill://rite-polish/reference/anti-ai-slop.md)
   § Code anti-slop — one canonical list, consumed by build, polish, and review.
 
 ## Simplicity

package/pack/generated/omp/skills/devrites-lib/reference/standards/context-hygiene.md

@@ -58,7 +58,7 @@ regression <slug>`: `BLOCKED` names a durable fact lost since the last
 checkpoint; `unproven` does not block. Before any re-dispatch, run
 `devrites-engine dispatch <slug> status`, `devrites-engine parallel status --root <repo>
 --slug <slug>`, and `devrites-engine claim list --all`, and reconcile open waves, leases, and
-claims per [`parallel-dispatch.md`](../parallel-dispatch.md#cancellation-and-terminal-reconciliation) § Cancellation.
+claims per [`parallel-dispatch.md`](skill://devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation) § Cancellation.
 **Failing case:** after compaction the root re-dispatches a review cohort whose original
 children still run, and duplicate accounts arrive.
 
@@ -89,7 +89,7 @@ to their owners (`/rite-handoff`); `/compact` preserves unrecorded continuity.
 ## The hygiene footer
 
 Every `rite-*` reply names the **single command** that resumes work on its action line
-(`Next:`, or `Resume:`/`Fix:` in a stop shape; [`reply-contract.md`](../reply-contract.md))
+(`Next:`, or `Resume:`/`Fix:` in a stop shape; [`reply-contract.md`](skill://devrites-lib/reference/reply-contract.md))
 and ends with one advisory line after `Record:`:
 
 ```

package/pack/generated/omp/skills/devrites-lib/reference/standards/core.md

@@ -3,7 +3,7 @@
 > Applies when: always; every workspace rite reads it first.
 
 Each workspace rite reads core first. Its `loads:` manifest `always` set is its required
-read-set (`devrites-engine context <slug> --skill <name>` where a workspace exists, else
+read-set (`devrites-engine context --skills-root .omp/skills <slug> --skill <name>` where a workspace exists, else
 read the listed files); a trigger's files load when its named condition holds. Load any
 other rule file from `README.md` on demand.
 
@@ -97,7 +97,7 @@ the final response; standalone phase invocations still stop normally.
 ## Final response
 
 Immediately before its final response, each rite loads
-[`reply-contract.md`](../reply-contract.md) then uses the compact form: evidenced
+[`reply-contract.md`](skill://devrites-lib/reference/reply-contract.md) then uses the compact form: evidenced
 claims plus one next action.
 
 ## Rationalization guard
@@ -153,7 +153,7 @@ Before any `rite-*` skill stops:
 - Next-action ambiguous? → resolve to one command in `state.md`.
 - HITL pause? → before stopping, set cursor `status` to `awaiting_human` and write the
   `Awaiting human` table in `state.md` 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;
   resume via `/rite-resolve <qid> "<answer>"`. See [`afk-hitl.md`](afk-hitl.md) for the
   full AFK / HITL contract.
 

package/pack/generated/omp/skills/devrites-lib/reference/standards/data-integrity.md

@@ -13,6 +13,10 @@ declared invariants.
 Name before planning implementation:
 
 - the authoritative owner of each fact and every writer;
+- the stable identity key of each record: joins, matches, upserts, and dedupes key on
+  an immutable unique ID, never on a mutable or non-unique attribute (email, name,
+  title, path); **failing case:** two accounts share an email, or a user changes it,
+  and the match merges or orphans their records;
 - uniqueness, referential, ordering, range, and lifecycle invariants;
 - tenant/subject partition keys and authorization boundary;
 - transaction boundary and externally visible commit point;

package/pack/generated/omp/skills/devrites-lib/reference/standards/debug-recovery.md

@@ -3,7 +3,7 @@
 > Applies when: polling async readiness, timeouts, retries, stuck-wait triage.
 
 Triggered standard for polling async readiness without blind sleep. Skill owner:
-[`devrites-debug-recovery`](../../../devrites-debug-recovery/SKILL.md).
+[`devrites-debug-recovery`](skill://devrites-debug-recovery/SKILL.md).
 
 ## Condition-based wait (bounded)
 

package/pack/generated/omp/skills/devrites-lib/reference/standards/definition-of-done.md

@@ -19,7 +19,7 @@ re-judge from this table alone.
 | Open hard gates closed | [`afk-hitl.md`](afk-hitl.md), `rite-seal` | HITL, red tests, drift, or NO-GO still open |
 | Rollback named for risky work | [`data-integrity.md`](data-integrity.md) | "revert if needed" with no trigger/procedure/proof |
 | Docs/ADR for public behavior | [`documentation.md`](documentation.md) | Command or contract changed; docs did not |
-| Written artifacts re-read from disk before handoff | [`workspace-artifact-schema.md`](../workspace-artifact-schema.md), phase owner | Report describes a spec/plan/evidence state the file on disk does not contain |
+| Written artifacts re-read from disk before handoff | [`workspace-artifact-schema.md`](skill://devrites-lib/reference/workspace-artifact-schema.md), phase owner | Report describes a spec/plan/evidence state the file on disk does not contain |
 | Recipient-path execution | [`verification-methods.md`](verification-methods.md), `rite-prove` | Tests run against the working tree; the packaged artifact was never installed, opened, or navigated as its recipient would |
 
 Use from `rite-vet`, `rite-build`, `rite-prove`, `rite-seal`, and `rite-quick`.

package/pack/generated/omp/skills/devrites-lib/reference/standards/developer-experience.md

@@ -11,7 +11,7 @@ have to read the source to learn. Un-tested DX is a claim, the same way un-run c
 
 This rule is the developer-facing counterpart to [`performance.md`](performance.md): perf says
 *measure the speed before you assert it*; this says *measure the experience before you assert
-it*. It pairs with the [`devrites-api-interface`](../../../devrites-api-interface/SKILL.md)
+it*. It pairs with the [`devrites-api-interface`](skill://devrites-api-interface/SKILL.md)
 skill (which shapes the contract). This rule **proves** the shape is usable.
 
 ## Scope: when this applies
@@ -28,7 +28,7 @@ It applies when the diff changes a **developer-facing surface**:
 - the **getting-started path**. README, install steps, quickstart, the first-run docs.
 
 Skip it for pure-internal refactors, private helpers, app-only UI (that's
-[`devrites-frontend-craft`](../../../devrites-frontend-craft/SKILL.md) /
+[`devrites-frontend-craft`](skill://devrites-frontend-craft/SKILL.md) /
 `devrites-frontend-reviewer`), docs-only typo fixes, and config that no external consumer
 touches. Don't DX-review a change with no developer-facing surface: the same scope discipline
 as the rest of the conditional rules. End-user UX is a different axis; this rule is about the
@@ -77,6 +77,11 @@ touches:
   carries meaning by colour alone; a status only colour conveys is a finding.
 - **Docs accuracy:** examples are copy-pasteable and correct, the signature in the docs matches
   the code, and changed behavior updated its docs in the same change ([`documentation.md`](documentation.md)).
+- **Agent use:** a coding agent is now a common consumer. Can it complete the flow with no
+  human step: non-interactive flags or env for every prompt, machine-readable output and
+  distinct exit codes where scripts consume results, setup and auth that run headless, and
+  docs that give commands rather than "click here" UI steps? A step only a human can do is
+  friction; name it.
 
 ## Measure, don't assert
 
@@ -87,7 +92,7 @@ The same discipline as `performance.md` "measure first" and `testing.md` "see it
   a clean state, the real CLI `--help`, the real error path) and recording what happened.
 - **Quote the artifact.** Record exact signal-bearing error text with typed security redactions
   (not paraphrase), secret-free command shape, and measured TTHW. For docs, use the
-  [browser-proof ladder](../../../devrites-browser-proof/SKILL.md) and describe the screenshot;
+  [browser-proof ladder](skill://devrites-browser-proof/SKILL.md) and describe the screenshot;
   a path alone is not proof.
 - **No measurement → no DX claim**, and usually no finding above Suggestion. "Feels confusing" is
   a hypothesis to test, not a verdict.

package/pack/generated/omp/skills/devrites-lib/reference/standards/glossary.md

@@ -11,7 +11,7 @@
 | Applicability map | `spec.md` table routing risk families (topology, data, integration, security, delivery) to their owning standard. A routed standard is mandatory, not optional. |
 | Binding | A recorded hash tying evidence or review to one exact candidate; stale binding = unproven. |
 | Bundle (context) | One deduplicated read-set file emitted by `devrites-engine context` into `ctx/`; a dispatch target reads it instead of selecting files. |
-| Candidate | The content-bound project state (digest + file set) reviews and proof run against. [`candidate-integrity.md`](../candidate-integrity.md). |
+| Candidate | The content-bound project state (digest + file set) reviews and proof run against. [`candidate-integrity.md`](skill://devrites-lib/reference/candidate-integrity.md). |
 | Consumptive action | An action whose failed attempt is not safely retryable (spends quota, mutates external state, or deletes its own failure evidence). [`one-shot-actions.md`](one-shot-actions.md). |
 | Controlling caller | The rite that invoked an earlier rite inline for repair; it keeps authority and resumes after the nested stop. |
 | Cursor | The `state.md` key/value table (phase, status, next_action, …) that is the authoritative lifecycle position. |
@@ -20,14 +20,14 @@
 | Diff-scope gate | `devrites-engine check diff-scope`: changed paths ⊆ allowlist, run before reviewer dispatch. |
 | Drift baseline | `readiness-inputs.json`: per-input SHA-256 snapshot recorded by `check drift --record` after Vet's binding; `check drift` attributes later input changes to the exact artifact. Advisory, never a gate. |
 | Dup ignore ledger | `.devrites/dup-ignore`: one `check dup` cluster hash per line with a `#` reason; content-derived hashes resurface on structural edits. [`duplicate-code.md`](duplicate-code.md). |
-| Evidence freshness | The rule that proof must postdate the candidate it claims to cover; [`candidate-integrity.md`](../candidate-integrity.md) § evidence validity. |
+| Evidence freshness | The rule that proof must postdate the candidate it claims to cover; [`candidate-integrity.md`](skill://devrites-lib/reference/candidate-integrity.md) § evidence validity. |
 | Finding shape (C2) | Canonical `Outcome / Finding / Basis` result rows every reviewer must return; [`agents.md`](agents.md) § Result admission. |
 | Gap | Result state naming missing/stale/unreadable input or a skipped required check; a required gap blocks, it is never `no-findings`. |
 | Gates ledger | `gates.md`: machine-checked acceptance rows (scaffold/status/run/reverify/lint/attest/abandon). [`gates.md`](gates.md). |
 | Loads manifest | The `<!-- loads: {...} -->` block in a SKILL.md declaring its exact read-set (`always`, `triggers`, `workspace`) for `devrites-engine context`. |
 | Metrics ledger | Append-only `metrics.jsonl` in a feature workspace recording dispatches, returns, bundle bytes, repair rounds. |
 | Nested phase boundary | A `STOP` inside a caller-invoked repair rite; it returns control to the caller, not the human. |
-| Read next | The per-phase bounded read order for workspace artifacts; [`workspace-artifact-schema.md`](../workspace-artifact-schema.md) § Read next by phase. |
+| Read next | The per-phase bounded read order for workspace artifacts; [`workspace-artifact-schema.md`](skill://devrites-lib/reference/workspace-artifact-schema.md) § Read next by phase. |
 | Regression baseline | `regression-baseline.json`: the durable high-water mark of workspace progress facts; `check regression` compares against it, `--update` ratchets it at a checkpoint. |
 | Seal | Final GO/NO-GO decision phase; a GO never authorizes irreversible mutation by itself. |
 | Slice | One vertical, independently provable unit of the plan (`SLICE-###` in `tasks.md`). |

package/pack/generated/omp/skills/devrites-lib/reference/standards/loop-operations.md

@@ -38,6 +38,9 @@ Every unattended loop must name:
 2. **Objective:** one active workspace or one read-only external observation.
 3. **Cycle:** one documented skill invocation; no hidden command chain.
 4. **Evaluator:** the skill's existing readiness, proof, review, or watcher verdict.
+   A cycle may add proof but never loosens or retargets what judges it (a test, gate,
+   threshold, benchmark, or fixture) to pass; an unattended optimizer overfits whatever
+   it can touch. An objective with no verifiable evaluator is not loopable; it stays HITL.
 5. **Budget:** every applicable `.devrites/AFK` resource cap.
 6. **Checkpoint:** durable workspace/evidence update before the turn ends; a
    `devrites-engine check regression <slug> --update` ratchet after each durable

package/pack/generated/omp/skills/devrites-lib/reference/standards/performance.md

@@ -15,6 +15,8 @@ Measure first. An optimization without a measurement is a guess that adds comple
 ## Optimize responsibly
 - Fix the **measured** bottleneck, then **re-measure** to prove the win (before/after).
   An optimization that doesn't move the number is just added complexity: revert it.
+  A win counts only while behavior proof stays green on an unchanged workload; tuning
+  the benchmark, fixture, or workload to the candidate games the number and is a finding.
   Keep compact failed and neutral experiment notes in the existing evidence:
   hypothesis, change, comparable measurements, and keep/revert decision. Do not
   create a separate experiment framework or ledger.
@@ -41,7 +43,7 @@ source-labeled scorecard); with no artifact it runs in Source mode and names the
   TBT may appear only as a labeled proxy.
 
 Baseline checks + measurement commands:
-[`rite-review/reference/performance-checklist.md`](../../../rite-review/reference/performance-checklist.md).
+[`rite-review/reference/performance-checklist.md`](skill://rite-review/reference/performance-checklist.md).
 
 ## Scope
 Optimize what the change touches or what a measurement flags. Project-wide performance