devrites 5.7.0 → 5.7.2

package/pack/generated/pi/skills/rite-define/SKILL.md

@@ -14,10 +14,10 @@ what/why; Define owns how. **Do not write code.**
 
 Pull these via `Read` when shaping the plan:
 
-- `development-workflow.md`: small batches, trunk-always-green, definition of done.
-- `principles.md`: the project invariants (`.devrites/principles.md`) the chosen approach must conform to.
-- `documentation.md`: record plan-time decisions and rationale.
-- `repository-topology.md`, `data-integrity.md`, and `integration-reliability.md`:
+- [`development-workflow.md`](../devrites-lib/reference/standards/development-workflow.md): small batches, trunk-always-green, definition of done.
+- [`principles.md`](../devrites-lib/reference/standards/principles.md): the project invariants (`.devrites/principles.md`) the chosen approach must conform to.
+- [`documentation.md`](../devrites-lib/reference/standards/documentation.md): record plan-time decisions and rationale.
+- [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), and [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md):
   load only for matching `spec.md` applicability rows; each applicable owner is mandatory.
 - `../devrites-lib/reference/workspace-artifact-schema.md`: artifact purposes, budgets, IDs, and read triggers.
 
@@ -25,13 +25,13 @@ Pull these via `Read` when shaping the plan:
 
 - **Requires a readied spec.** Gate conditions and STOP routing are step 0;
   never plan it.
-- Apply `afk-hitl.md` ownership. Prefer conventions; source-check new dependencies/design
+- Apply [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) ownership. Prefer conventions; source-check new dependencies/design
   systems, asking only about licensing, cost, security, or policy.
 - Author one `architecture.md`/`plan.md` section at a time. Before slicing, use
   [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md) Tournament for open
   designs and Delphi for uncertain estimates.
 - **Derive the slice count from the work.**
-  One per independently-shippable increment, sized by `slicing.md`; map every acceptance
+  One per independently-shippable increment, sized by [`slicing.md`](../rite-plan/reference/slicing.md); map every acceptance
   criterion. User counts are hints: explain honest differences, never pad/compress.
   `.devrites/AFK` `max_slices` is an iteration budget, not decomposition. A derivation
   over the [feature ceiling](../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
@@ -49,7 +49,7 @@ Pull these via `Read` when shaping the plan:
 
 0. **Read `.pi/skills/devrites-lib/reference/standards/core.md`:** the always-on operating rules and anti-rationalizations.
    Resolve the active slug from `.devrites/ACTIVE`, require its `state.md`, and
-   re-open `spec.md` and apply `spec-grammar.md`'s Native grammar re-read
+   re-open `spec.md` and apply [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md)'s Native grammar re-read
    checklist. If there is no active workspace, no `spec.md`, the checklist
    fails, or its readiness gate hasn't passed →
    **STOP** and tell the user to run `/rite-spec <feature>` first.
@@ -80,9 +80,9 @@ Pull these via `Read` when shaping the plan:
    dependencies by drivers, trade-offs, and consequences. Specify cross-boundary interfaces for independent work:
    invariants, I/O, ordering/idempotency, errors, versioning, config, and relevant budgets.
    Establish repository/deployable roots, state and contract ownership, shared mutable
-   resources, and deployment order under `repository-topology.md`. For applicable durable
-   data or integration rows, include the exact required plan table from `data-integrity.md`
-   or `integration-reliability.md`; do not replace it with "handle retries/migration" prose.
+   resources, and deployment order under [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md). For applicable durable
+   data or integration rows, include the exact required plan table from [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md)
+   or [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md); do not replace it with "handle retries/migration" prose.
    For any changed provider/consumer boundary, complete `plan.md`'s canonical
    `Shared contract proof` table with one reused contract artifact and provider- and
    consumer-side asserting tests that both consume it. Otherwise record the exact justified
@@ -98,10 +98,10 @@ Pull these via `Read` when shaping the plan:
 3. **Create vertical tasks:** each delivers one independently verifiable, observable
    capability end to end; first is the thinnest useful path, ordered by dependency then
    risk. Apply the slice-count and broad-refactor rules above plus
-   `rite-plan/reference/slicing.md` and `rite-plan/reference/task-breakdown.md`.
+   [`slicing.md`](../rite-plan/reference/slicing.md) and [`task-breakdown.md`](../rite-plan/reference/task-breakdown.md).
    Mark per slice: **Frontend craft required**
    and **Browser proof required** (UI), and whether it's **fullstack** (FE+BE → contract
-   first, see `devrites-frontend-craft/reference/fullstack.md`). **For UI slices, name which
+   first, see [`fullstack.md`](../devrites-frontend-craft/reference/fullstack.md)). **For UI slices, name which
    of `design-brief.md`'s key states + interaction the slice delivers, and give it a binary
    **Visual acceptance** target (state × viewport × input + target R-id/brief rule)**, so
    the design contract maps to slices as well as acceptance criteria.
@@ -114,7 +114,7 @@ Pull these via `Read` when shaping the plan:
    unchanged baseline green, perturb realistic behavior red, restore green, then modify. Never
    expand this into repository-wide coverage.
 4. **Map coverage and wiring:** every `AC-###` spec acceptance criterion maps to ≥1 `SLICE-###`
-   (`rite-spec/reference/acceptance-criteria.md`); no orphaned criteria, no slice without a
+   ([`acceptance-criteria.md`](../rite-spec/reference/acceptance-criteria.md)); no orphaned criteria, no slice without a
    criterion. Lift covered/backstop `Edge Coverage` rows and resolved `Prohibitions (must-NOT)`
    rows into `traceability.md` and `test-plan.md`; unresolved rows get a gate/owner. Each
    cross-slice boundary names producer, consumer, invariant, integration step, and proof.

package/pack/generated/pi/skills/rite-define/reference/gates.md

@@ -78,7 +78,7 @@ it's `blocking`.
 
 ## Picking the gate
 
-First apply `afk-hitl.md` decision ownership: an objective implementation/tooling failure
+First apply [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md) decision ownership: an objective implementation/tooling failure
 or reversible technical choice is agent work and gets no human gate. Then apply this
 decision tree per HITL slice:
 

package/pack/generated/pi/skills/rite-dogfood/SKILL.md

@@ -11,7 +11,7 @@ disable-model-invocation: true
 Dogfood what changed as a user journey. This complements `/rite-prove`: prove checks acceptance; dogfood finds journey breaks and paper cuts.
 
 ## Rules consulted
-Step 0: Read `.pi/skills/devrites-lib/reference/standards/core.md`, then `tooling.md`, `testing.md`, and `afk-hitl.md` when relevant.
+Step 0: Read `.pi/skills/devrites-lib/reference/standards/core.md`, then [`tooling.md`](../devrites-lib/reference/standards/tooling.md), [`testing.md`](../devrites-lib/reference/standards/testing.md), and [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) when relevant.
 
 ## Operating rules
 - Diff-scoped, not whole-app exploration.

package/pack/generated/pi/skills/rite-explain/SKILL.md

@@ -60,7 +60,7 @@ free: prefer it over re-deriving:
 - A **diff** or **recap** → the workspace and archive: `seal.md`, `evidence.md`, `decisions.md`,
   `traceability.md`, the shipped `.devrites/archive/<slug>/`, and `git log` / `git diff`.
 - A **concept** with footprint in this repo → live code through the primary index selected by
-  `standards/tooling.md` (one named-predicate cross-check only when needed), plus any
+  [`tooling.md`](../devrites-lib/reference/standards/tooling.md) (one named-predicate cross-check only when needed), plus any
   `.devrites/principles.md` or ADRs that already take a position on it.
 - An **idea** or a concept with no repo footprint → the user's framing plus, only if it sharpens
   the teaching, current external sources (weight by date; the year is 2026).
@@ -136,7 +136,7 @@ not force it; offer once.
   Wikipedia paragraph. If it has footprint in this repo, quote the repo.
 - **Not a review.** `/rite-explain` never judges the code or files findings, that is `/rite-review`.
   It explains what *is*, adversarially neutral.
-- **Not `/rite-learn`.** It writes to `.devrites/explainers/`, never to `principles.md`
+- **Not `/rite-learn`.** It writes to `.devrites/explainers/`, never to [`principles.md`](../devrites-lib/reference/standards/principles.md)
   or any rule file. Teaching the human is not promoting a repo rule.
 
 ## Output

package/pack/generated/pi/skills/rite-frame/SKILL.md

@@ -67,19 +67,19 @@ map + worked examples: [`reference/failure-modes.md`](reference/failure-modes.md
 
 - [ ] **1 · Silent assumption**: did I pick one reading of an ambiguous ask and run with it?
       Any value, contract, or behavior I *guessed*? → surface it; route material ones through
-      the Spec Drift Guard (`core.md` #4; surface per #2/#3).
+      the Spec Drift Guard ([`core.md`](../devrites-lib/reference/standards/core.md) #4; surface per #2/#3).
 - [ ] **2 · Overcomplication**: an abstraction / flag / indirection nobody asked for? 200 lines
       where 50 would do? A defensive check inside trusted code? → apply the **deletion test**;
-      simplify (`coding-style.md`, `patterns.md`, `devrites-audit simplify`).
+      simplify ([`coding-style.md`](../devrites-lib/reference/standards/coding-style.md), [`patterns.md`](../devrites-lib/reference/standards/patterns.md), `devrites-audit simplify`).
 - [ ] **3 · Out-of-scope edit**: did I touch code, comments, or formatting outside the ask?
       "While I'm here" refactors? → revert to the boundary; record the rest as an FYI follow-up
-      (`core.md` #7, `touched-files.md`).
+      ([`core.md`](../devrites-lib/reference/standards/core.md) #7, `touched-files.md`).
 - [ ] **4 · Unverifiable goal**: is there a command that proves this, run, with output? Or am
       I asserting "it works"? Tautological test that can't fail? → run the FRAME verify command;
-      record command + output (`testing.md`, evidence-over-confidence).
+      record command + output ([`testing.md`](../devrites-lib/reference/standards/testing.md), evidence-over-confidence).
 - [ ] **Principle check**, if `.devrites/principles.md` exists, does the change break a declared
       invariant? A violation with no recorded, human-approved exception is a **Critical**: the
-      express lane is not a way around a project gate; escalate it, don't ship it (`principles.md`).
+      express lane is not a way around a project gate; escalate it, don't ship it ([`principles.md`](../devrites-lib/reference/standards/principles.md)).
 
 The test for each changed line: **it traces directly to the criterion, and the criterion can
 be proven false.** A line that fails either is a finding.

package/pack/generated/pi/skills/rite-frame/reference/failure-modes.md

@@ -8,10 +8,10 @@ reach the normal gates.
 
 | # | Failure mode | The tell in a diff / a reply | Cure already in the pack |
 |---|---|---|---|
-| 1 | **Silent assumption** | A value, contract, edge case, or interpretation was *guessed* and run with: no note, no question. The ask had two readings and one was picked silently. | `core.md` #2 (no silent assumptions) / #3 (no guessing through confusion); the Spec Drift Guard; `devrites-doubt` for a single high-stakes call; `devrites-interview` when the ask is underspecified. |
-| 2 | **Overcomplication** | An abstraction, flag, config knob, or indirection nobody asked for. 200 lines where 50 would do. A single-use factory. Defensive `try/catch` + null checks inside trusted code. A dependency added where an in-repo option exists. | `coding-style.md` (simplicity, reuse-first), `patterns.md` (avoid over-engineering), `devrites-audit simplify` (deletion test, Chesterton's Fence), the "over-defensive guarding is slop" anti-pattern. |
-| 3 | **Out-of-scope edit** | Touched code, comments, or formatting outside the ask. A "while I'm here" refactor. Renamed something orthogonal. Reflowed an import block. | `core.md` #7 (feature scope only), the exact paths stated in the writer task, `git diff --name-only` plus `touched-files.md`, and the "it's only a small refactor" anti-pattern. |
-| 4 | **Unverifiable goal** | "It works" with no command, no output, no test. A success criterion that can't be false ("make it better"). A tautological test that passes no matter what. | `rite-spec/reference/acceptance-criteria.md` (measurable acceptance), `core.md` #6 (evidence over confidence), `testing.md` (assertion strength, see it fail first), the TDD wright. |
+| 1 | **Silent assumption** | A value, contract, edge case, or interpretation was *guessed* and run with: no note, no question. The ask had two readings and one was picked silently. | [`core.md`](../../devrites-lib/reference/standards/core.md) #2 (no silent assumptions) / #3 (no guessing through confusion); the Spec Drift Guard; `devrites-doubt` for a single high-stakes call; `devrites-interview` when the ask is underspecified. |
+| 2 | **Overcomplication** | An abstraction, flag, config knob, or indirection nobody asked for. 200 lines where 50 would do. A single-use factory. Defensive `try/catch` + null checks inside trusted code. A dependency added where an in-repo option exists. | [`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md) (simplicity, reuse-first), [`patterns.md`](../../devrites-lib/reference/standards/patterns.md) (avoid over-engineering), `devrites-audit simplify` (deletion test, Chesterton's Fence), the "over-defensive guarding is slop" anti-pattern. |
+| 3 | **Out-of-scope edit** | Touched code, comments, or formatting outside the ask. A "while I'm here" refactor. Renamed something orthogonal. Reflowed an import block. | [`core.md`](../../devrites-lib/reference/standards/core.md) #7 (feature scope only), the exact paths stated in the writer task, `git diff --name-only` plus `touched-files.md`, and the "it's only a small refactor" anti-pattern. |
+| 4 | **Unverifiable goal** | "It works" with no command, no output, no test. A success criterion that can't be false ("make it better"). A tautological test that passes no matter what. | [`acceptance-criteria.md`](../../rite-spec/reference/acceptance-criteria.md) (measurable acceptance), [`core.md`](../../devrites-lib/reference/standards/core.md) #6 (evidence over confidence), [`testing.md`](../../devrites-lib/reference/standards/testing.md) (assertion strength, see it fail first), the TDD wright. |
 
 Karpathy named the first three. The fourth supplies the falsifiable criterion needed
 for an agent to work without repeated human confirmation. FRAME defines that criterion

package/pack/generated/pi/skills/rite-handoff/SKILL.md

@@ -91,7 +91,7 @@ Print the absolute path in `Record:` so the user or next agent can open it witho
 
 ## Session hygiene
 Close with the one-line hygiene advisory + the single resume command. This skill *is* the
-pre-`/clear` bridge, so it's where the advisory matters most (`context-hygiene.md`):
+pre-`/clear` bridge, so it's where the advisory matters most ([`context-hygiene.md`](../devrites-lib/reference/standards/context-hygiene.md)):
 ```
 ↻ Hygiene: /clear
 ```

package/pack/generated/pi/skills/rite-learn/SKILL.md

@@ -24,7 +24,7 @@ of one authority; it cannot promote a rule alone.
 3. Keep corrections repeated in two features, a judgement call made twice, or a defect class seen twice; drop one-off preferences, task-specific detail, generic advice.
 4. Verify claims against live authoritative sources; state currentness signal, applies/does-not-apply scope, `unknown` where unverifiable.
    **Research promotion requires:** each external claim carries a dated citation per
-   [`tooling.md` § Research provenance](../devrites-lib/reference/standards/tooling.md#research-provenance-staleness-and-cost).
+   [[`tooling.md`](../devrites-lib/reference/standards/tooling.md) § Research provenance](../devrites-lib/reference/standards/tooling.md#research-provenance-staleness-and-cost).
    **Failing case:** "best practice is X" with no source → reject promotion.
 5. Apply durable promotion's recoverability test; search same/contrary rules, choose one existing owner (nearest instruction/standard, ADR, or feature `decisions.md`), and name discovery.
 6. Show the exact edit + duplicate/conflict/supersession disposition; update/narrow/replace/retire contradictions; apply only after user approval of exact edits.

package/pack/generated/pi/skills/rite-plan/SKILL.md

@@ -14,9 +14,9 @@ artifact-only**: reconcile
 editing source code.
 
 ## Rules consulted (read on demand from `.pi/skills/devrites-lib/reference/standards/`)
-Pull `development-workflow.md` via `Read` when reshaping slice cadence or DoD
+Pull [`development-workflow.md`](../devrites-lib/reference/standards/development-workflow.md) via `Read` when reshaping slice cadence or DoD
 criteria.
-Load `repository-topology.md`, `data-integrity.md`, or `integration-reliability.md`
+Load [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), or [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md)
 when the spec applicability map or observed drift triggers them.
 Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
@@ -76,7 +76,7 @@ Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standard
    affected artifacts, settled contract, and failure/drift. Await one atomic, read-only
    the drafter's `candidate_files` bundle; human choices return separately.
    When the observed failure is missing or ambiguous consumptive-action evidence,
-   require the drafter to apply `one-shot-actions.md` and return the bounded
+   require the drafter to apply [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md) and return the bounded
    diagnostic-amplification design, injective boundary map, per-seam fixtures, and
    collision mutant. Past evidence loss is not terminal. The drafter supplies no bodies.
    A repair candidate carries a delta self-check scoped to what the patch

package/pack/generated/pi/skills/rite-plan/reference/replan-and-repair.md

@@ -89,7 +89,7 @@ or `traceability.md` — never source. Propose/confirm the file set first. Only
 
 Unchanged acceptance/behavior with non-equivalent `proposed_coverage` is a
 contradictory input: the canonical classifier blocks it — there is no fourth
-route (see `acceptance-preserving-reslice.md`).
+route (see [`acceptance-preserving-reslice.md`](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md)).
 
 **Budget relocation** (admitted by `/rite-upgrade`, or by the phase owner when
 `orient` reports `over: true`): move checkpoint narrative, historical fold text and

package/pack/generated/pi/skills/rite-polish/SKILL.md

@@ -53,7 +53,7 @@ Incomplete comparison is **not** agreement. Record axis deltas in `polish-report
 ## Orchestration
 
 0. **Read** `.pi/skills/devrites-lib/reference/standards/core.md` first (the always-on operating rules). The
-   per-phase rule files (`coding-style.md`, `error-handling.md`, …) load on demand
+   per-phase rule files ([`coding-style.md`](../devrites-lib/reference/standards/coding-style.md), [`error-handling.md`](../devrites-lib/reference/standards/error-handling.md), …) load on demand
    from `reference/code.md` / `reference/ui.md` when their phase runs; for UI scope also read
    `.pi/skills/devrites-lib/reference/standards/browser-proof-checklist.md`.
    Then read the explicit or active workspace's `state.md` directly.

package/pack/generated/pi/skills/rite-polish/reference/anti-ai-slop.md

@@ -40,7 +40,7 @@ match the neighbors.
 - **Modal-first thinking** — reaching for a modal as the answer to every interaction.
 - **Ghost-card** — a `1px` border *and* a soft (blur ≥16px) shadow on the same element.
   Borders separate; shadows lift — pick one
-  (`devrites-frontend-craft/reference/quality-standards.md` — Materiality).
+  ([`quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md) — Materiality).
 - **Balloon radius** — `border-radius` above ~16px on cards, inputs, panels. Cards top
   out around 12–16px; full pills are for tags and buttons only.
 - **Uppercase tracked eyebrow above every section** — one named kicker is voice; one per
@@ -87,9 +87,9 @@ second one catches what the first one misses.
   teal", "fintech → navy + gold", "AI tool → black with a violet accent",
   "crypto → neon on black" — the styling is on the first training-data
   reflex. Rework the scene sentence
-  (`devrites-frontend-craft/reference/design-references.md`) and the
+  ([`design-references.md`](../../devrites-frontend-craft/reference/design-references.md)) and the
   colour-commitment strategy
-  (`devrites-frontend-craft/reference/quality-standards.md`) until the
+  ([`quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md)) until the
   answer isn't obvious from the domain.
 - **Second-order:** if a stranger looked at the surface with *no copy
   visible* and confidently said "this is a CRM / fitness tracker / fintech
@@ -121,10 +121,10 @@ Each is pass/fail by counting or grep, not judgment:
   hop with no value. Inline or remove.
 - **Over-engineered abstractions** for trivial problems — a factory + interface + plugin
   registry for a 10-line function. **Don't add abstraction before two real callers**
-  (see `coding-style.md`, `patterns.md`).
+  (see [`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md), [`patterns.md`](../../devrites-lib/reference/standards/patterns.md)).
 - **Convention-blind** code — ignores the repo's naming, file layout, error patterns,
   validation style. "Generic good code" beats the project's idiom; reuse first (see
-  `coding-style.md`).
+  [`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md)).
 - **Going beyond the spec** — features/options/configs/flags the spec didn't ask for.
   Implement exactly what was specified; flag extras as follow-ups.
 - **Comment noise — the most common code tell.** Default to **zero** comments; the code and
@@ -174,14 +174,14 @@ Each is pass/fail by counting or grep, not judgment:
   account/provider/test ID inline with no name or source. Give it a name (a const) or a home
   (config/env). The mirror image of premature config, and just as much a tell.
 - **Copy-paste duplication** — a near-identical block pasted and tweaked instead of reused.
-  Reuse → extend → build new (`coding-style.md`, `patterns.md`); duplication beats the *wrong*
+  Reuse → extend → build new ([`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md), [`patterns.md`](../../devrites-lib/reference/standards/patterns.md)); duplication beats the *wrong*
   abstraction, but pasted clones are slop, not a deliberate AHA call.
 
 ## Why banned, what instead
 They signal model-generated rather than team-designed work: they ignore register and
 idiom, add noise, hide bugs (defensive catches), bloat diffs, and often fail a11y or
 correctness review. Instead: project tokens/components, validate at trust boundaries,
-catch narrow and rethrow, one clear name per concept, reuse first (`coding-style.md`),
+catch narrow and rethrow, one clear name per concept, reuse first ([`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md)),
 implement exactly the spec. If the project intentionally uses one of these, follow the
 project — consistency beats the rule. A check or abstraction you can't justify in one
 sentence is slop: delete it or ask.

package/pack/generated/pi/skills/rite-polish/reference/backend-polish.md

@@ -22,7 +22,7 @@ schemas. Polishes the **server side** to ship-quality before review, the way UI
       errors; not 200 with `{ error: ... }`).
 - [ ] **Custom error classes** (or equivalent) so callers can distinguish error kinds.
 - [ ] **Fail closed** on auth/permission/transaction errors: deny + roll back; never
-      default to allow or partial commit (`error-handling.md`, `security.md`).
+      default to allow or partial commit ([`error-handling.md`](../../devrites-lib/reference/standards/error-handling.md), [`security.md`](../../devrites-lib/reference/standards/security.md)).
 - [ ] **Narrow `catch`**: no blanket `catch (e) {}` swallows. If you catch, recover or
       rethrow with context.
 
@@ -52,7 +52,7 @@ schemas. Polishes the **server side** to ship-quality before review, the way UI
       keys).
 - [ ] **Pagination, sorting, filtering** consistent with neighboring endpoints.
 - [ ] **Validation at the boundary**: type/length/format/range on untrusted input;
-      reject what doesn't match (see `security.md` three-tier).
+      reject what doesn't match (see [`security.md`](../../devrites-lib/reference/standards/security.md) three-tier).
 
 ### Performance (measure first)
 - [ ] Hot-path work measured; obvious wins (cache, batch, hoist) applied; perf claims

package/pack/generated/pi/skills/rite-polish/reference/browser-polish-evidence.md

@@ -6,7 +6,7 @@ in `polish-report.md`).
 
 ## Required when a browser can run
 - Screenshots of the polished UI at the canonical viewport set
-  (`devrites-frontend-craft/reference/quality-standards.md` § Responsive — currently
+  ([`quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md) § Responsive — currently
   320 / 768 / 1024 / 1440).
   **Open each screenshot and describe what's visible**: a path is not proof.
 - All key interaction states captured or exercised: hover, focus, active, disabled,

package/pack/generated/pi/skills/rite-polish/reference/code.md

@@ -5,11 +5,11 @@ code polish (Phase 1) and, when backend is touched, backend polish (Phase 2).
 
 ## Rules consulted (read on demand from `.pi/skills/devrites-lib/reference/standards/`)
 
-- `coding-style.md`: Phase 1 (simplify, dead code, naming, comments).
-- `patterns.md`: Phase 1 simplification: avoid over-engineering.
-- `error-handling.md`: Phase 2 backend (no silent catches, consistent errors).
-- `performance.md`: Phase 2 backend (N+1s, query bounds).
-- `documentation.md`: keep touched docs current; record polish-time decisions.
+- [`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md): Phase 1 (simplify, dead code, naming, comments).
+- [`patterns.md`](../../devrites-lib/reference/standards/patterns.md): Phase 1 simplification: avoid over-engineering.
+- [`error-handling.md`](../../devrites-lib/reference/standards/error-handling.md): Phase 2 backend (no silent catches, consistent errors).
+- [`performance.md`](../../devrites-lib/reference/standards/performance.md): Phase 2 backend (N+1s, query bounds).
+- [`documentation.md`](../../devrites-lib/reference/standards/documentation.md): keep touched docs current; record polish-time decisions.
 
 ## Operating rules
 
@@ -65,7 +65,7 @@ feature only.
   beat a cryptic one.
 - **Done when:** every touched change passes the comprehension test, every anti-slop charter
   item in the touched code is cleared (the AI-tells do-not list: [anti-ai-slop.md](anti-ai-slop.md)
-  Code section, `coding-style.md`) **and** the feature's targeted tests + build re-run green.
+  Code section, [`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md)) **and** the feature's targeted tests + build re-run green.
   An open charter item or a red check means Phase 1 isn't done.
 
 ## Phase 2: Backend polish *(if BE touched)*

package/pack/generated/pi/skills/rite-polish/reference/design-memory.md

@@ -6,7 +6,7 @@ copy proven, reusable design rules into the project-level `DESIGN.md` for later
 features.
 
 `devrites-ux-shape` §1 and
-`devrites-frontend-craft/reference/design-references.md` read `DESIGN.md` when present.
+[`design-references.md`](../../devrites-frontend-craft/reference/design-references.md) read `DESIGN.md` when present.
 This step writes that file from real feature evidence before Review.
 
 ## When it runs
@@ -14,7 +14,7 @@ This step writes that file from real feature evidence before Review.
 - **During Polish, after initial proof and before candidate closure.** Any update
   enters the candidate manifest and is proved and reviewed with the feature.
 - **Opt in and confirm.** A project-wide artifact is outside feature scope
-  (`standards/core.md` rule 7), so never write it silently. Present a ranked option set
+  ([`core.md`](../../devrites-lib/reference/standards/core.md) rule 7), so never write it silently. Present a ranked option set
   (see [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md), "Option set");
   **default is skip**. The user opts to persist.
 - **AFK:** first-time `DESIGN.md` creation is a `validating` gate because it adds a

package/pack/generated/pi/skills/rite-polish/reference/ledger.md

@@ -39,7 +39,7 @@ Run during Polish before Review so ledger edits enter the proved candidate.
 2. **Preview, do not write.** Show exact target paths; every delta with before/after
    header; full requirement order; and changed files. Apply the table to current
    bytes and the preservation rule to MODIFIED and REMOVED. Conflicts stop.
-3. **Check feature grammar.** Apply `spec-grammar.md`'s Native grammar re-read
+3. **Check feature grammar.** Apply [`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md)'s Native grammar re-read
    checklist to the saved feature spec. Any miss stops. Step 2's native comparison owns delta reconciliation; an
    already-applied empty preview remains a no-op.
 4. **Confirm.** Name exact paths and deltas. A later Seal or Ship approval does
@@ -50,7 +50,7 @@ Run during Polish before Review so ledger edits enter the proved candidate.
    bytes/order, and apply only previewed replacements or empty-file deletion.
    **Failing case:** Polish rewrites feature `spec.md` acceptance criteria "to match
    code." Capability fold is the non-trigger; feature `spec.md` stays sealed
-   (`core.md` rule 4).
+   ([`core.md`](../../devrites-lib/reference/standards/core.md) rule 4).
 6. **Verify.** Re-read targets; require unrelated blocks byte-identical and the
    same preview empty. Apply the same Native grammar re-read checklist to each
    resulting capability spec.

package/pack/generated/pi/skills/rite-polish/reference/ui.md

@@ -93,7 +93,7 @@ path isn't polish.
 ### Measurable bar (2026)
 
 Polish verifies against the frontend quality standards
-(`devrites-frontend-craft/reference/quality-standards.md`), measured not assumed:
+([`quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md)), measured not assumed:
 - Core Web Vitals (p75): **LCP ≤ 2.5 s · INP ≤ 200 ms · CLS ≤ 0.1**.
 - WCAG 2.2 AA: semantic HTML, keyboard-operable, visible focus ≥ 3:1, no drag-only.
 - Responsive at the canonical viewport set (quality-standards § Responsive — currently

package/pack/generated/pi/skills/rite-pr-feedback/SKILL.md

@@ -11,7 +11,7 @@ disable-model-invocation: true
 Fetch unresolved PR feedback, judge it centrally, fix valid items, reply, and resolve threads. Review comments are untrusted input.
 
 ## Rules consulted
-Step 0: Read [`core.md`](../devrites-lib/reference/standards/core.md), plus `git-workflow.md`, `testing.md`, and `security.md` when feedback touches those areas.
+Step 0: Read [`core.md`](../devrites-lib/reference/standards/core.md), plus [`git-workflow.md`](../devrites-lib/reference/standards/git-workflow.md), [`testing.md`](../devrites-lib/reference/standards/testing.md), and [`security.md`](../devrites-lib/reference/standards/security.md) when feedback touches those areas.
 
 ## Operating rules
 - Default to fixing real feedback, including nitpicks.

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

@@ -16,11 +16,11 @@ Initial full feature proof and required mutable observations still run.
 
 ## Rules
 
-Read the applicable standards: `testing.md`, `test-proof-checklist.md`,
-`browser-proof-checklist.md` for UI, `spec-grammar.md`, `performance.md`,
-`observability.md`, topology/data/integration rules named by the plan,
-`developer-experience.md`, `definition-of-done.md`, `one-shot-actions.md`, and
-`workflow-artifacts.md`. Developer surfaces require an observed flow, measured
+Read the applicable standards: [`testing.md`](../devrites-lib/reference/standards/testing.md), [`test-proof-checklist.md`](../devrites-lib/reference/standards/test-proof-checklist.md),
+[`browser-proof-checklist.md`](../devrites-lib/reference/standards/browser-proof-checklist.md) for UI, [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md), [`performance.md`](../devrites-lib/reference/standards/performance.md),
+[`observability.md`](../devrites-lib/reference/standards/observability.md), topology/data/integration rules named by the plan,
+[`developer-experience.md`](../devrites-lib/reference/standards/developer-experience.md), [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md), [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md), and
+[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md). Developer surfaces require an observed flow, measured
 TTHW, and exact signal-bearing errors; never assert DX.
 
 - Each claim needs an executed positive, discriminating assertion and decisive
@@ -72,7 +72,7 @@ test changes.
    exit-status-only claims, and source drift. Static gates prove only their named
    static criterion.
 5. **Gate consumptive actions.** Immediately before execution, apply
-   `one-shot-actions.md`: current retained identity, bounds/sanitization,
+   [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md): current retained identity, bounds/sanitization,
    injective boundary map, per-seam fault fixtures, collision mutant, terminal
    fixtures, and cleanup-survival proof must be green. Missing/stale/disposable-
    only evidence returns to Vet without spending an attempt. Record the admitted artifact identity before execution.

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

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

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

@@ -34,16 +34,16 @@ express lane on a risky one is the failure mode the lifecycle exists to prevent.
 
 ## Rules consulted (read on demand from `.pi/skills/devrites-lib/reference/standards/`)
 Load this lane's conditional standards when needed:
-- `coding-style.md`: naming, guard clauses, reuse-first.
-- `testing.md`: TDD, **completeness** (every touched behavior/element asserted) +
+- [`coding-style.md`](../devrites-lib/reference/standards/coding-style.md): naming, guard clauses, reuse-first.
+- [`testing.md`](../devrites-lib/reference/standards/testing.md): TDD, **completeness** (every touched behavior/element asserted) +
   **assertion strength** (no tautological tests; see it fail first), scaled to the change.
-- `error-handling.md` / `security.md`: only if the change touches input/errors.
-- `principles.md`: when `.devrites/principles.md` exists; a change that breaks an invariant is a gate, not a quick fix.
-- `definition-of-done.md`: standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.
+- [`error-handling.md`](../devrites-lib/reference/standards/error-handling.md) / [`security.md`](../devrites-lib/reference/standards/security.md): only if the change touches input/errors.
+- [`principles.md`](../devrites-lib/reference/standards/principles.md): when `.devrites/principles.md` exists; a change that breaks an invariant is a gate, not a quick fix.
+- [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md): standing Done bar: acceptance mapped, fresh proof, no open hard gates, scoped edits, rollback/docs where needed.
 
 
 ## Workflow
-0. **Orient.** Read `core.md`. If a `.devrites/` workspace is active, read its
+0. **Orient.** Read [`core.md`](../devrites-lib/reference/standards/core.md). If a `.devrites/` workspace is active, read its
    `state.md` directly; `/rite-quick` does **not** require
    a workspace and does **not** create the full tree.
 1. **Significance gate** (above). Fail → STOP, tell the user to run `/rite-spec <feature>`.

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

@@ -24,8 +24,8 @@ full AFK / HITL contract lives in
 
 Pull these via `Read` when shaping the resolve:
 
-- `afk-hitl.md`: gate taxonomy, `questions.md` schema, AFK exception rules.
-- `documentation.md`: record decisions and rationale where the answer changes scope.
+- [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md): gate taxonomy, `questions.md` schema, AFK exception rules.
+- [`documentation.md`](../devrites-lib/reference/standards/documentation.md): record decisions and rationale where the answer changes scope.
 
 ## Operating rules
 

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

@@ -23,16 +23,16 @@ all workflow-named roles remain mandatory at every depth.
 
 Pull these via `Read` when the diff demands them:
 
-- `code-review.md`: small PRs, severity labels, tests-first review focus.
-- `review-checklist.md`: compact pass/fail sweep before reporting the verdict.
-- `principles.md`: declared project invariants (`.devrites/principles.md`); a diff that violates one with no recorded exception is a Critical, blocking finding.
-- `testing.md`: confirm that passing tests actually prove the spec.
-- `agents.md`: when to fan out to which review subagent.
-- `security.md`: when input / auth / data / integrations / secrets are in scope.
-- `security-checklist.md`: for the same security-sensitive scope, the compact trust-boundary sweep.
-- `repository-topology.md`, `data-integrity.md`, `integration-reliability.md`: only
+- [`code-review.md`](../devrites-lib/reference/standards/code-review.md): small PRs, severity labels, tests-first review focus.
+- [`review-checklist.md`](../devrites-lib/reference/standards/review-checklist.md): compact pass/fail sweep before reporting the verdict.
+- [`principles.md`](../devrites-lib/reference/standards/principles.md): declared project invariants (`.devrites/principles.md`); a diff that violates one with no recorded exception is a Critical, blocking finding.
+- [`testing.md`](../devrites-lib/reference/standards/testing.md): confirm that passing tests actually prove the spec.
+- [`agents.md`](../devrites-lib/reference/standards/agents.md): when to fan out to which review subagent.
+- [`security.md`](../devrites-lib/reference/standards/security.md): when input / auth / data / integrations / secrets are in scope.
+- [`security-checklist.md`](../devrites-lib/reference/standards/security-checklist.md): for the same security-sensitive scope, the compact trust-boundary sweep.
+- [`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md): only
   when the spec applicability map or final diff triggers their ownership/failure/proof checks.
-- `performance.md`: only when perf is relevant or a regression risk is visible.
+- [`performance.md`](../devrites-lib/reference/standards/performance.md): only when perf is relevant or a regression risk is visible.
 
 ## Operating rules
 
@@ -67,7 +67,7 @@ Pull these via `Read` when the diff demands them:
    `devrites-engine check candidate <slug>` and require its digest to match the
    single `evidence.md` binding and the `browser-evidence.md` binding when that
    file exists. Read those ledgers via the bounded advisory read
-   (`workspace-artifact-schema.md` § Read next by phase): binding line, `EVID-###`
+   ([`workspace-artifact-schema.md`](../devrites-lib/reference/workspace-artifact-schema.md) § Read next by phase): binding line, `EVID-###`
    index, then bodies for this candidate's AC/slice IDs only. A missing,
    malformed, or open candidate returns to Polish/Prove.
    Read `touched-files.md` `## Review trail` and `eng-review.md` `## Deferred findings`:
@@ -105,7 +105,7 @@ Pull these via `Read` when the diff demands them:
      between the axes explicitly (e.g. "Spec axis says complete, Code-review axis says
      untestable"): `/rite-seal` decides what blocks. Preserve each reviewer's
      `Outcome:` and admit its account through
-     [`agents.md` § Result admission](../devrites-lib/reference/standards/agents.md#result-admission).
+     [[`agents.md`](../devrites-lib/reference/standards/agents.md) § Result admission](../devrites-lib/reference/standards/agents.md#result-admission).
      Either `Outcome: gap` stops Review; silence, failure, or malformed output never
      becomes an empty findings list.
 4. **Reconcile, don't re-review.** With the two parallel reports in hand, the inline
@@ -159,7 +159,7 @@ seal; `non-blocking` / `if-minor` findings are recorded, not a stop.
 
 ## Confidence and severity
 
-Apply [`agents.md` § Result admission](../devrites-lib/reference/standards/agents.md#result-admission).
+Apply [[`agents.md`](../devrites-lib/reference/standards/agents.md) § Result admission](../devrites-lib/reference/standards/agents.md#result-admission).
 Roll trivia into one line. `/rite-seal` gates on `Critical == 0`,
 `Important == 0` (y/N override), acceptance, and drift. No composite score.
 

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

@@ -75,7 +75,7 @@ Treat each as a finding when present; classify by load type so the fix is obviou
 ## The cheap-fix test
 
 If a finding would take more than 30 minutes to fix, classify it (token gap /
-component miss / flow misalignment per `rite-polish/reference/ui.md`) and
+component miss / flow misalignment per [`ui.md`](../../rite-polish/reference/ui.md)) and
 route to the appropriate bucket. Cognitive-load review surfaces problems; it
 doesn't decide the rewrite strategy.
 

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

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