devrites 5.7.0 → 5.7.2

package/pack/generated/codex/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/codex/skills/rite-polish/SKILL.md

@@ -53,7 +53,7 @@ Incomplete comparison is **not** agreement. Record axis deltas in `polish-report
 ## Orchestration
 
 0. **Read** `.agents/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
    `.agents/skills/devrites-lib/reference/standards/browser-proof-checklist.md`.
    Then read the explicit or active workspace's `state.md` directly.

package/pack/generated/codex/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/codex/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/codex/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/codex/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 `.agents/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/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 `.agents/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/codex/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/codex/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/codex/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/codex/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

package/pack/generated/codex/skills/rite-seal/reference/final-evidence.md

@@ -9,7 +9,7 @@ results and exact `devrites-spec-reviewer` checks implementation and proof
 against its meaning. Bug fixes require original-symptom proof; self-report,
 inspection alone, and generic "tests pass" do not count.
 
-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.
 Unproven behavior: NO-GO.
 
@@ -37,5 +37,5 @@ devrites-engine check seal "<slug>"
 ```
 
 This checks structure and exact candidate bindings, never acceptance, test
-quality, doubt, or review. Apply [`testing.md`'s safe perturbation](../../devrites-lib/reference/standards/testing.md#safe-perturbation)
+quality, doubt, or review. Apply [[`testing.md`](../../devrites-lib/reference/standards/testing.md)'s safe perturbation](../../devrites-lib/reference/standards/testing.md#safe-perturbation)
 for its mandatory critical/regression cases and any additional project/test-plan requirement.

package/pack/generated/codex/skills/rite-seal/reference/phase-contract.md

@@ -6,7 +6,7 @@
 2. **Recheck identity and real proof.** Run
    `devrites-engine check candidate <slug>` and require its exact digest to match
    the single evidence/review bindings and the browser binding when present.
-   Apply `spec-grammar.md`'s Native grammar re-read checklist and
+   Apply [`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md)'s Native grammar re-read checklist and
    [evidence validity](../../devrites-lib/reference/candidate-integrity.md#evidence-validity).
    Run required `test-plan.md` commands unless valid observed proof already satisfies
    them under that contract. Rerun the

package/pack/generated/codex/skills/rite-ship/SKILL.md

@@ -11,10 +11,10 @@ user-invocable: true
 if absent, route to `$rite-spec <feature>`. Ship only with current **GO** in `seal.md`.
 
 ## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
-**Step 0:** Read `core.md`, then pull as needed:
-- `git-workflow.md`: Conventional Commits, atomicity, never-commit list.
-- `afk-hitl.md`: AFK pause rules for irreversible actions (the type-GO gate itself: [`git-ship.md`](reference/git-ship.md), [`rollout.md`](reference/rollout.md)).
-- `definition-of-done.md`: acceptance, evidence, drift, rollback, docs.
+**Step 0:** Read [`core.md`](../devrites-lib/reference/standards/core.md), then pull as needed:
+- [`git-workflow.md`](../devrites-lib/reference/standards/git-workflow.md): Conventional Commits, atomicity, never-commit list.
+- [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md): AFK pause rules for irreversible actions (the type-GO gate itself: [`git-ship.md`](reference/git-ship.md), [`rollout.md`](reference/rollout.md)).
+- [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md): acceptance, evidence, drift, rollback, docs.
 - [`release/ship-checklist.md`](../devrites-lib/reference/standards/release/ship-checklist.md): final pass/fail sweep.
 
 ## Operating rules

package/pack/generated/codex/skills/rite-ship/reference/git-ship.md

@@ -33,7 +33,7 @@ Rules:
 
 ## The candidate-safe Git ladder
 
-Follow `standards/git-workflow.md` and project convention; invent no release flow.
+Follow [`git-workflow.md`](../../devrites-lib/reference/standards/git-workflow.md) and project convention; invent no release flow.
 Candidate identity always comes from `devrites-engine check candidate`; do not
 implement a Git-side hash.
 

package/pack/generated/codex/skills/rite-spec/SKILL.md

@@ -14,9 +14,9 @@ Investigate and resolve material gaps into a placed, covered `spec.md`.
 > here for auth, data, migration, public API, or multi-slice work.
 
 ## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
-Pull `documentation.md` for significant decisions and `principles.md` for
+Pull [`documentation.md`](../devrites-lib/reference/standards/documentation.md) for significant decisions and [`principles.md`](../devrites-lib/reference/standards/principles.md) for
 declared invariants; an unavoidable principle violation is blocking.
-For behavioral/high-risk acceptance, use `spec-grammar.md` plus workspace schema;
+For behavioral/high-risk acceptance, use [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md) plus workspace schema;
 simple criteria stay flat `AC-###`. Apply
 [`acceptance-criteria.md`](reference/acceptance-criteria.md) so each is binary and observable.
 Use [`edge-case-trace.md`](../devrites-lib/reference/standards/edge-case-trace.md)
@@ -68,7 +68,7 @@ load a routed standard to discover required behavior, not to prescribe implement
    relevant `.devrites/**/decisions.md` files directly before asking the human to revisit a
    settled architecture, API, or auth choice. Compare exact requirement headers and meanings
    with the current ledger to choose ADDED/MODIFIED/REMOVED; never classify from memory. Use
-   `spec-grammar.md`'s singular `Capability impact:` declaration to name the affected
+   [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md)'s singular `Capability impact:` declaration to name the affected
    capabilities and change, or give its specific `none` justification.
    Inventory affected observable behavior from current test/contract/runtime/source
    evidence; map each outcome to preserving REQ/AC. Greenfield `none` needs the
@@ -98,7 +98,7 @@ load a routed standard to discover required behavior, not to prescribe implement
    backend/data/CLI features skip this.
 4. **Resolve human-owned gaps.** Recommend an option and let the human decide. Apply
    [question-protocol](reference/question-protocol.md), the shared
-   [`afk-hitl.md` option-set and decision-ownership rules](../devrites-lib/reference/standards/afk-hitl.md#decision-ownership-search-before-asking),
+   [[`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) option-set and decision-ownership rules](../devrites-lib/reference/standards/afk-hitl.md#decision-ownership-search-before-asking),
    and [`interview-patterns.md`](reference/interview-patterns.md) for a vague ask. Every
    material dimension is resolved by a human pick or explicitly deferred as non-blocking;
    only genuinely reversible, low-impact details go to `assumptions.md`. A paper-only
@@ -124,7 +124,7 @@ load a routed standard to discover required behavior, not to prescribe implement
    never by softening the question.
 6. **Run the complete readiness gate** at the bottom of
    [spec-template](reference/spec-template.md), then apply the
-   **Native grammar re-read checklist** in `spec-grammar.md` to the complete
+   **Native grammar re-read checklist** in [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md) to the complete
    saved `spec.md`. Re-open the file after corrections and verify every
    applicable item; there is no parser or replacement script. Natively compare
    deltas with the current ledger using exact header semantics and the ledger's

package/pack/generated/codex/skills/rite-spec/reference/spec-template.md

@@ -4,7 +4,7 @@ Contract WHAT users get, WHY, success, and scope. HOW belongs in `plan.md`,
 topology in `architecture.md`/`flows.md`, coverage in `traceability.md`.
 
 Use `[NEEDS CLARIFICATION: <question>]` (blocking stops `$rite-clarify`); before readiness
-every surviving marker converts to a gated `Q-###` open question (`spec-grammar.md` §
+every surviving marker converts to a gated `Q-###` open question ([`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md) §
 Unresolved-question markers — fail closed). Stable `REQ-001`/`AC-001` IDs; link, never
 duplicate, source artifacts; over-budget requires `Budget override: <reason>`.
 
@@ -128,7 +128,7 @@ status routes Define/Vet/Build/Prove to the named standard without copying it he
 - `brief.md`: request/outcome/scope; `architecture.md`: placement/integration;
   `flows.md`: Mermaid-first diagrams (optional `visual/<flow>.html`+`.outline.md` companion
   + link when richer presentation earns it — load playbooks via
-  `devrites-lib/reference/visual-playbooks/index.md`); `decisions.md`: decisions;
+  [`index.md`](../../devrites-lib/reference/visual-playbooks/index.md)); `decisions.md`: decisions;
   `decision-coverage.md`: Clarify topology/verdict; `traceability.md`: Define coverage;
   `design-brief.md`: UI direction.
 

package/pack/generated/codex/skills/rite-spec/reference/state-workspace.md

@@ -223,5 +223,5 @@ command.
 ## Compactness
 
 High-traffic files should stay within the budgets in
-`workspace-artifact-schema.md`. If a file truly must exceed its budget, add
+[`workspace-artifact-schema.md`](../../devrites-lib/reference/workspace-artifact-schema.md). If a file truly must exceed its budget, add
 `Budget override: <reason>` near the top.

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

@@ -15,12 +15,12 @@ is no readied `spec.md`, tell the user to run `$rite-spec`. Review depth follows
 the required exact strategy reviewer never changes with profile.
 
 ## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
-Pull on demand: `patterns.md` +
-`coding-style.md` (the over-engineering / YAGNI rubric (reuse the pack's standard, don't
-invent one), `documentation.md` (ADR-style `decisions.md` entries), `afk-hitl.md`
-(irreversible-risk list + gate ceiling), `elicitation.md` (the move-set to deepen a section
+Pull on demand: [`patterns.md`](../devrites-lib/reference/standards/patterns.md) +
+[`coding-style.md`](../devrites-lib/reference/standards/coding-style.md) (the over-engineering / YAGNI rubric (reuse the pack's standard, don't
+invent one), [`documentation.md`](../devrites-lib/reference/standards/documentation.md) (ADR-style `decisions.md` entries), [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md)
+(irreversible-risk list + gate ceiling), [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md) (the move-set to deepen a section
 that needs more than the default pre-mortem) selected by the section's risk). Load
-`repository-topology.md`, `data-integrity.md`, or `integration-reliability.md` only when
+[`repository-topology.md`](../devrites-lib/reference/standards/repository-topology.md), [`data-integrity.md`](../devrites-lib/reference/standards/data-integrity.md), or [`integration-reliability.md`](../devrites-lib/reference/standards/integration-reliability.md) only when
 the spec applicability map triggers that risk family.
 
 ## Operating rules
@@ -32,12 +32,12 @@ the spec applicability map triggers that risk family.
 - **Apply maximum caution to hard-to-reverse changes.** Auth, migration, public API, and
   data-model changes always pause under the irreversible-risk list.
 - **Honest verdict.** Never round "needs work" up to "ready"; record every scope call's *why*.
-- **Search before asking.** Apply `afk-hitl.md` decision ownership; only human-owned calls
+- **Search before asking.** Apply [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) decision ownership; only human-owned calls
   enter the interactive walk.
 - **You write; the reviewer judges.** You are the single canonical writer (`strategy.md` +
   the spec edits); the reviewer agent is read-only.
 - **Require spec-quality checklists for significant features.** Before hardening,
-  confirm `checklists/<domain>.md` exist and pass (`rite-spec/reference/spec-checklists.md`); a
+  confirm `checklists/<domain>.md` exist and pass ([`spec-checklists.md`](../rite-spec/reference/spec-checklists.md)); a
   scope expansion you fold in **adds its own** rows (new Success/Acceptance criteria get
   checklist rows too). A folded expansion with an unquantified criterion is a CRITICAL
   failure that reopens the readiness gate.

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

@@ -17,7 +17,7 @@ the gate uses the **lowest band**, not an average.
    human prerequisites and action-time approvals instead of deferring generic uncertainty to
    build. **Unmitigated top risks are gating.**
 5. **Over-engineering / YAGNI:** speculative capability, unused extension points, premature
-   abstraction, second-system bloat. Apply the pack's standard (`patterns.md`) and the YAGNI
+   abstraction, second-system bloat. Apply the pack's standard ([`patterns.md`](../../devrites-lib/reference/standards/patterns.md)) and the YAGNI
    ledger test (scope-modes.md Pass 2).
 6. **Acceptance testability and completion:** every acceptance criterion measurable, technology-
    agnostic, and comparable **down to a baseline** ("better than the current workaround"), not
@@ -32,7 +32,7 @@ the gate uses the **lowest band**, not an average.
    and patterns, or assume greenfield freedom a constrained space doesn't have? Prefer existing
    conventions; flag a new dependency / second design system for explicit decision.
 
-UI specs also inherit `rite-polish/reference/anti-ai-slop.md` at the cross-cutting
+UI specs also inherit [`anti-ai-slop.md`](../../rite-polish/reference/anti-ai-slop.md) at the cross-cutting
 dimension (design-system fit, anti-AI-slop), but `$rite-temper` reviews the *spec/design-brief*,
 not pixels; the built UI is judged later by `devrites-frontend-reviewer`.
 

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

@@ -26,7 +26,7 @@ Invert. Two subtractive moves:
 - **YAGNI ledger.** Each candidate scope item gets the "imagine the later refactor" test: if
   adding it *later* isn't materially more expensive, **defer it** (with a revisit note).
   Bias hard toward defer: most presumed-needed features are never used. Reuse the
-  pack's existing `patterns.md` standard ('no speculative abstraction or pattern
+  pack's existing [`patterns.md`](../../devrites-lib/reference/standards/patterns.md) standard ('no speculative abstraction or pattern
   without a current need'). Don't invent a new YAGNI rule.
 
 ## The four modes: commit exactly one
@@ -43,7 +43,7 @@ Mode selection is the first convergence move. Record the chosen mode + rationale
 ## Bound ambition by reversibility
 The bigger the bet, the more it must be reversible. Irreversible-risk areas (auth, migrations,
 public API, data model) get the **opposite** of ambition: maximum conservatism, explicit
-rollback, and they **always pause** regardless of mode (the `afk-hitl.md` irreversible-risk
+rollback, and they **always pause** regardless of mode (the [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md) irreversible-risk
 list is honored verbatim). Size big bets so that if the whole thing vanished tomorrow, you'd be
 fine.
 

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

@@ -6,7 +6,7 @@ optional `$rite-temper` path and the always-run (significance-gated) `$rite-auto
 so they agree on when it fires.
 
 ## Fire the FULL review when ANY trips
-- **Irreversible-risk contact:** the slice/spec touches anything on the `afk-hitl.md`
+- **Irreversible-risk contact:** the slice/spec touches anything on the [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md)
   irreversible-risk list: destructive data migration, auth/authz boundary, public-API break,
   external-service contract, filesystem destruction outside the workspace.
 - **Data model:** new/changed entities, relationships, or persistence shape.

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

@@ -14,7 +14,7 @@ structural migration, or generic cleanup.
 
 ## Rules consulted
 
-Read `devrites-lib/reference/standards/core.md`, its agent and workspace-schema
+Read [`core.md`](../devrites-lib/reference/standards/core.md), its agent and workspace-schema
 references, and only current phase contracts needed for the observed gap.
 
 ## Invariants