devrites 5.7.0 → 5.7.2

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

@@ -54,7 +54,6 @@ max_slices: 10                       # whole-workspace writer budget; seeds stat
 max_agents: 32                       # native agent dispatches in one host activation
 max_minutes: 120                     # wall-clock minutes in one host activation
 max_review_queue: 8                  # unresolved review/gate items admitted before fan-out stops
-expires_at: "<ISO-8601 UTC timestamp>" # absolute unattended-authority expiry
 # max_tokens: 200000                 # optional stricter host-observed token cap
 # max_cost_usd: 10                   # optional stricter host-observed cost cap
 notify: "ntfy.sh/my-topic"           # shell command; examples: rite-build/reference/afk-discipline.md
@@ -108,7 +107,7 @@ candidate manifest to cover the whole recorded chain — run
 
 - Only continuations recorded in the parent's `decisions.md` sequence
   ([slicing.md § Continuation workspaces](../../../rite-plan/reference/slicing.md#continuation-workspaces))
-  qualify; no recorded next entry, or the cap/expiry/review-queue bound reached, stops
+  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. Per-slice `WIP(<slug>)` checkpoints still
@@ -128,27 +127,26 @@ an explicit `$rite-build --parallel N` cap wins for that invocation.
 ## Unattended resource envelope
 
 AFK writer admission needs a bounded input queue, effective slice cap, and valid
-`max_agents`, `max_minutes`, `max_review_queue`, and `expires_at`. Existing sentinels
+`max_agents`, `max_minutes`, and `max_review_queue`. Existing sentinels
 that declare writer admission but miss/malform these fail closed; cold resume keeps the
-state-owned slice counter.
+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).
 
 `max_agents` counts every leaf in the native activation, including failures and
 parallel branches; do not add dispatch telemetry to `.devrites/`. `max_review_queue`
 counts open validating questions plus unresolved admitted Critical/Important findings.
-Above it stop; at it run only reconciliation that reduces the queue. `expires_at` is
-absolute ISO-8601 authority. Optional `max_tokens`/`max_cost_usd` lower enforceable
-native caps; if declared but unobservable, stop.
+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.
 
 Numeric limits are nonnegative decimals. Before costly checks, fan-out, or writing,
 run cheap readiness, reject overlap, count queue, and confirm agent/time/token/cost
 headroom; re-check after every result. Never start one call that can exceed remaining
 headroom. Agent/time/token/cost counters are per native activation and start fresh only
-for a genuinely new activation. Slices, recovery attempts, absolute expiry, and current
+for a genuinely new activation. Slices, recovery attempts, and current
 review queue remain durable/recomputed across wakes. Persist each activation stop and
 checkpoint before notification.
 
-New sentinels default `expires_at` to arming + 4h with no notification/token/cost cap.
+New sentinels write no `expires_at` and no notification/token/cost cap.
 Post-Vet pending count may lower slices. Existing files
 never receive missing defaults implicitly.
 
@@ -390,7 +388,7 @@ AFK changes which decisions are automatic. It changes nothing else.
 - Workflow integration: `$rite-build` (`.agents/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
-  (`reference/one-slice-cycle.md`).
+  ([`one-slice-cycle.md`](../../../rite-build/reference/one-slice-cycle.md)).
 - Render contract: `.agents/skills/rite-build/reference/checkpoint-protocol.md`.
 - Loop discipline: `.agents/skills/rite-build/reference/afk-discipline.md`.
 - Gate taxonomy: `.agents/skills/rite-define/reference/gates.md`.

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

@@ -12,7 +12,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** (`rite-plan/reference/slicing.md`). Whole-file deletions and
+  **thinner vertical slice** ([`slicing.md`](../../../rite-plan/reference/slicing.md)). Whole-file deletions and
   mechanical refactors may run large: review intent, not every line.
 
 ## What to check (tests first)

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

@@ -38,13 +38,13 @@ Every unattended loop must name:
 4. **Evaluator:** the skill's existing readiness, proof, review, or watcher verdict.
 5. **Budget:** every applicable `.devrites/AFK` resource cap.
 6. **Checkpoint:** durable workspace/evidence update before the turn ends.
-7. **Stop:** success, human/safety/access gate, expiry, budget exhaustion, unchanged
+7. **Stop:** success, human/safety/access gate, budget exhaustion, unchanged
    no-progress fingerprint, host failure, or terminal external state.
 8. **Notification:** optional native-host notification after state is durable; never a
    substitute for recording the stop.
 
 A read-only scheduled/event loop that has no active AFK workspace must still configure
-native maximum activations/iterations, wall time, and absolute expiry. Add token/cost
+native maximum activations/iterations and wall time. Add token/cost
 caps when the host exposes them. One observation cycle per wake is the work unit; the
 skill never starts its own timer or background poller.
 
@@ -76,7 +76,7 @@ armed AFK workspace whose exact scope, gates, and budgets permit it.
   is `gap`/`cannot_verify`, never success.
 - Do not retry unchanged work merely because a timer fired. Apply the exact
   causal-fingerprint recovery cap ([`afk-hitl.md`](afk-hitl.md)).
-- A cold resume continues durable slice/recovery state and absolute expiry. Fresh
+- A cold resume continues durable slice/recovery state. Fresh
   native activation counters follow `afk-hitl.md`; no durable bound is reinitialized.
 - Native notifications fire only after evidence and stop state are written.
 

package/pack/generated/codex/skills/devrites-lib/reference/standards/prose-style.md

@@ -49,12 +49,12 @@ the same decisions from it.
 | False binary contrast. "It's not X, it's Y", "The question isn't X. It's Y", "not just X but Y" | State Y directly. Drop the negation. |
 | Fake profundity. "Let that sink in", "This is the deepest problem", "make no mistake" | Show the thing; trust the reader to weigh it. |
 | Vague declaratives. "The implications are significant", "the reasons are structural" | Name the specific implication or reason. |
-| Marketing adjectives *selling* the work: "a robust, scalable, seamless, production-ready solution" | Say what it does and what proves it. (Calibrated: "robust"/"scalable"/"comprehensive" are legitimate in a precise technical claim ("robust to a dropped connection, see `evidence.md`"); slop only when they sell. Canonical tiering: `devrites-prose-craft/reference/banned-phrases.md` § AI vocabulary.) |
+| Marketing adjectives *selling* the work: "a robust, scalable, seamless, production-ready solution" | Say what it does and what proves it. (Calibrated: "robust"/"scalable"/"comprehensive" are legitimate in a precise technical claim ("robust to a dropped connection, see `evidence.md`"); slop only when they sell. Canonical tiering: [`banned-phrases.md`](../../../devrites-prose-craft/reference/banned-phrases.md) § AI vocabulary.) |
 | Hedging stacks. "It's important to note that, generally, in most cases" | Make the claim, or cut it. |
 | False agency: "the data tells us", "the complaint becomes a fix", "the decision emerges" | Name who did it. "The grader reads X and returns Y." |
 | Meta-narration, "In this section we'll…", "Let me walk you through…", "as we'll see" | Let the text move; delete the announcement. |
 | Reasoning-chain scaffolding. "Let me think step by step", "Breaking this down", "First, let's consider" | State the conclusion, then the evidence. |
-| Assistant leaks. Cutoff disclaimers, unfilled placeholders, chatbot citation markup, `utm_source=chatgpt.com` | Delete the leak; keep the fact. See `devrites-prose-craft/reference/banned-phrases.md`. |
+| Assistant leaks. Cutoff disclaimers, unfilled placeholders, chatbot citation markup, `utm_source=chatgpt.com` | Delete the leak; keep the fact. See [`banned-phrases.md`](../../../devrites-prose-craft/reference/banned-phrases.md). |
 
 ## Voice (prose register)
 

package/pack/generated/codex/skills/devrites-lib/reference/standards/release/ship-checklist.md

@@ -5,4 +5,4 @@
 - All strategy/decisions/review/seal residuals: one `ship.md` tracked path/ID or prior/explicit human-approved no-action; gaps block archive.
 - Success: archive; clear `ACTIVE`.
 
-`git-workflow.md`, `ci-cd.md`, `rite-ship/reference/git-ship.md`.
+[`git-workflow.md`](../git-workflow.md), [`ci-cd.md`](../ci-cd.md), [`git-ship.md`](../../../../rite-ship/reference/git-ship.md).

package/pack/generated/codex/skills/devrites-lib/reference/standards/skill-authoring.md

@@ -80,7 +80,7 @@ Optional flags obey `core.md` rule 10.
 - A reference file over ~300 lines opens with a table of contents so a partial
   read still sees the file's full scope.
 - A SKILL.md must link every supporting `.md` it may need in one hop.
-  `core.md`, `agents.md`, `README.md`, and `index.md` are indexes and may
+  `core.md`, `agents.md`, `README.md`, and [`index.md`](../visual-playbooks/index.md) are indexes and may
   point onward. Shared `standards/` and `visual-playbooks/` catalogs use
   those indexes. A skill-local reference must not be the only path to
   another non-catalog file in that skill.

package/pack/generated/codex/skills/devrites-lib/reference/standards/spec-grammar.md

@@ -51,7 +51,7 @@ The normative rules the root checks:
 ## Behavior first: WHAT, not HOW
 
 A spec requirement describes observable behavior, not the implementation that delivers it
-(the spec stays technology-agnostic: see `rite-spec/reference/spec-template.md`). "**THEN**
+(the spec stays technology-agnostic: see [`spec-template.md`](../../../rite-spec/reference/spec-template.md)). "**THEN**
 respond 401" is behavior; "**THEN** call `AuthGuard.reject()`" leaks the design and locks the
 plan before `$rite-define` has chosen it. Name the input, the observable output, and the state
 change, not the function, class, or library. Implementation belongs in `plan.md`, not the
@@ -166,7 +166,7 @@ above: names are unique and a rename is a remove + add), so the section MUST use
 header text for MODIFIED / REMOVED.
 
 For **MODIFIED**, compare the complete current requirement block with the proposed full
-replacement under the lossless rule in `rite-polish/reference/ledger.md`. An unexplained
+replacement under the lossless rule in [`ledger.md`](../../../rite-polish/reference/ledger.md). An unexplained
 omission blocks readiness; it is not cleanup.
 
 - **The `— capability: <name>` suffix is the fold target.** Omit it and the fold defaults to the

package/pack/generated/codex/skills/devrites-lib/reference/workspace-artifact-schema.md

@@ -154,7 +154,7 @@ and history in `state.md` (checkpoint narrative moves verbatim to
 pointer left behind). A legacy workspace may carry a temporary `Budget override:` line
 as a bridge; `$rite-upgrade` routes it to relocation or the split, and new writers never
 create one for those two reasons.
-Apply [`context-hygiene.md` dispatch packets](standards/context-hygiene.md#dispatch-packets)
+Apply [[`context-hygiene.md`](standards/context-hygiene.md) dispatch packets](standards/context-hygiene.md#dispatch-packets)
 for byte-size checks and lossless retrieval; budget overrides neither rewrite protected
 history nor require loading it all.
 

package/pack/generated/codex/skills/devrites-prose-craft/reference/examples.md

@@ -77,7 +77,7 @@ Dropped the pleasantries and the "not just X" inflation. Led with what's done an
 > Buffering the whole CSV OOM-ed on >100k rows. Stream rows to the response so memory stays
 > flat. Rules out an upfront total-count header; tracked in #123.
 
-Followed `git-workflow.md`: the *why*, wrapped, in plain language.
+Followed [`git-workflow.md`](../../devrites-lib/reference/standards/git-workflow.md): the *why*, wrapped, in plain language.
 
 ## 7. Fidelity when evidence is incomplete
 

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

@@ -15,11 +15,11 @@ profile by default and Full for high-risk scope or explicit `--full`; see
 
 ## Required rules
 
-Read `devrites-lib/reference/standards/core.md` and `afk-hitl.md` first. Read
-`one-shot-actions.md` before any stop/continue or execution decision involving a
+Read [`core.md`](../devrites-lib/reference/standards/core.md) and [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md) first. Read
+[`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md) before any stop/continue or execution decision involving a
 consumptive action. Before honoring a terminal cursor that names missing
 executable controller/harness/bundle bytes or a missing writer, read
-`workflow-artifacts.md`. Before classifying any Reslice, read `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md). Before classifying any Reslice, read `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
 <!-- BEGIN RESLICE ROUTE-TO-ACTION -->
 - `FOLD` → keep Plan repair/affected Vet internal; no stop solely for topology/count.
@@ -48,7 +48,7 @@ executable controller/harness/bundle bytes or a missing writer, read
 - Every exact causal fingerprint gets at most three no-progress corrections.
   Closing one is progress; a distinct Critical/Important invariant has its own
   budget. Lower severity cannot prolong recovery.
-- Enforce `--max-slices`, the AFK sentinel, expiry, review queue, and native
+- Enforce `--max-slices`, the AFK sentinel, review queue, and native
   agent/token/cost/time limits before every phase or dispatch. Count failed,
   malformed, and unavailable leaf calls. At the review cap, permit only work
   that reduces the queue.

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

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

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

@@ -18,7 +18,6 @@ max_slices: 10
 max_agents: 32
 max_minutes: 120
 max_review_queue: 8
-expires_at: "<now + 4 hours>"
 # continue_sequence: true          # opt-in: chain recorded continuations after Seal GO
 # max_workspaces: 5                # sequence budget when chaining
 # max_parallel: 10                 # Build batch cap; 1 = serial (default: eligible, cap 10)
@@ -28,11 +27,11 @@ expires_at: "<now + 4 hours>"
 ```
 
 Read an existing sentinel first. Preserve it byte-for-byte when valid; stop if
-its gate ceiling exceeds advisory, required envelope is malformed/expired, or
+its gate ceiling exceeds advisory, required envelope is malformed, or
 `max_slices` conflicts with the invocation. If absent, write it once after
-clarity, replacing the safe slice default only for explicit `--max-slices N`
-and resolving one absolute UTC expiry. It is read-only: never rewrite it after
-Vet or reset it on resume.
+clarity, replacing the safe slice default only for explicit `--max-slices N`.
+It is read-only: never rewrite it after Vet or reset it on resume. Leftover
+`expires_at` is ignored and never rewritten.
 
 ### Derive the mutable post-vet budget
 
@@ -44,13 +43,13 @@ or reinitialize it. AFK configuration itself stays unchanged.
 ### Admit each unattended cycle
 
 Before every phase, review fan-out, recovery, or writer dispatch, apply
-`afk-hitl.md#unattended-resource-envelope`: cheapest current-state/readiness
-check first; reject overlap; count unresolved review; check expiry and native
+[`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md#unattended-resource-envelope): cheapest current-state/readiness
+check first; reject overlap; count unresolved review; check native
 agent/token/cost/time headroom. Count every leaf result. At the review cap, only
 reconciliation that reduces the queue may run. Any reached or unobservable
 bound stops before more work and persists the winning reason. A new activation
-gets fresh activation-local counters but retains durable slice/recovery state,
-expiry, and recomputed queue.
+gets fresh activation-local counters but retains durable slice/recovery state
+and recomputed queue.
 
 `allow_gates: [advisory]` means validating gates pause now rather than becoming
 Seal NO-GO. Only explicit human configuration outside Autocomplete may widen it.
@@ -100,7 +99,7 @@ fields are missing is re-seeded from its `brief.md` parent/position and the
 parent's counter (same values, never a second charge); a child with no recorded
 parent/position is not a sequence member and the chain stops.
 
-Stop instead when: no recorded next entry; the cap, expiry, or review-queue bound is
+Stop instead when: no recorded next entry; the cap or review-queue bound is
 reached; a human-owned, safety, access, or exhaustion condition fires; or Seal returns
 `NO-GO`. On stop, report the sequence position, the sealed-but-unshipped workspaces, and
 the single release command (`$rite-autocomplete <release milestone> --ship`, or

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

@@ -71,11 +71,10 @@ exhausted.
   when slices remain; malformed state also stops. Report whether the winning
   bound was the pre-existing remaining value, explicit flag, sentinel cap, or post-vet pending count.
   Zero with no pending slices is normal completion and proceeds to Prove.
-- **Resource envelope:** missing/malformed/expired AFK, overlapping run,
+- **Resource envelope:** missing/malformed AFK, overlapping run,
   exhausted/unobservable declared agent/token/cost/time headroom, or review queue
   above cap. At cap, only queue-reducing reconciliation may run. Persist winning
-  bound and observed usage; a new activation does not reset durable budgets or
-  expiry.
+  bound and observed usage; a new activation does not reset durable budgets.
 - **Confidence:** intent still cannot become testable acceptance after interview.
 - **Repeated failure:** the exact fingerprint's bounded recovery is exhausted.
 

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

@@ -14,7 +14,7 @@ observer.
 
 ### User-facing render: the option set
 
-Present as `AskUserQuestion` ranked **option set** (`afk-hitl.md`): 2–4 options,
+Present as `AskUserQuestion` ranked **option set** ([`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md)): 2–4 options,
 recommended first + `(Recommended)`, dimension-tagged trade-offs, plus escape hatch.
 Header names slice + gate:
 

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

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

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

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

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

@@ -17,7 +17,7 @@ Reuse [`devrites-interview`](../devrites-interview/SKILL.md) in `/clarify mode`.
 
 ## Rules consulted
 
-Read [`core.md`](../devrites-lib/reference/standards/core.md), its `afk-hitl.md`, and
+Read [`core.md`](../devrites-lib/reference/standards/core.md), its [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md), and
 [`reference/decision-coverage.md`](reference/decision-coverage.md). Fresh evidence
 dispatch uses
 [`agents.md`](../devrites-lib/reference/standards/agents.md).

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

@@ -24,15 +24,15 @@ prerequisite skill to run.
 
 Pull on demand:
 
-- `principles.md`: the project invariants (`.devrites/principles.md`); code that violates a
+- [`principles.md`](../devrites-lib/reference/standards/principles.md): the project invariants (`.devrites/principles.md`); code that violates a
   MUST principle is the highest-severity gap and produces a remediation slice.
-- `spec-grammar.md`: buildable acceptance criteria vs `## Success metrics` (outcome KPIs the
+- [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md): buildable acceptance criteria vs `## Success metrics` (outcome KPIs the
   code can't make true and this pass never enqueues); structured `### Requirement:` /
   `#### Scenario:` blocks, each scenario one behavior to check as built / partial / absent.
-- `tooling.md`: use the primary available code index; cross-check only a named unresolved
+- [`tooling.md`](../devrites-lib/reference/standards/tooling.md): use the primary available code index; cross-check only a named unresolved
   predicate, then fall back to LSP/file search. Read live code, not artifact claims.
-- `testing.md`: a criterion with code but no covering test is *partial*, not done.
-- `repository-topology.md`, `data-integrity.md`, `integration-reliability.md`: only for
+- [`testing.md`](../devrites-lib/reference/standards/testing.md): a criterion with code but no covering test is *partial*, not done.
+- [`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 for
   triggered applicability rows; missing failure/recovery behavior is partial or absent.
 
 ## Operating rules
@@ -48,7 +48,7 @@ Pull on demand:
 - **Use artifacts as intent.** The spec, plan, tasks, and principles are the
   contract. If assessing reveals the *spec* is wrong (the code is right and the requirement is
   stale), that's **Spec Drift**: stop and route it through the Spec Drift Guard
-  (`rite-build/reference/spec-drift-guard.md`) + a recorded decision; never paper over a spec
+  ([`spec-drift-guard.md`](../rite-build/reference/spec-drift-guard.md)) + a recorded decision; never paper over a spec
   bug by appending a task that changes correct code to match a wrong requirement.
 - **Partial is not done.** Code that exists but is untested, half-wired, or covers only the
   happy path is an unmet gap: enqueue the remainder, don't round it up.
@@ -83,7 +83,7 @@ Pull on demand:
    proof still agrees with its `test-plan.md` row, and the mapped prose preserves the
    requirement's meaning. Record orphaned, invented, duplicate, or contradictory
    mappings as gaps. Then read the live code
-   (code-intelligence index per `tooling.md`); artifact mappings never prove implementation.
+   (code-intelligence index per [`tooling.md`](../devrites-lib/reference/standards/tooling.md)); artifact mappings never prove implementation.
 4. **Assess each unit as built / partial / absent** against the live code (the rubric is in
    [`reference/convergence-assessment.md`](reference/convergence-assessment.md)): every
    acceptance criterion / scenario, every plan touch-point, and every existing slice's stated

package/pack/generated/codex/skills/rite-converge/reference/convergence-assessment.md

@@ -8,7 +8,7 @@ Assess three kinds of unit against the live code:
 
 1. **Acceptance criteria / scenarios:** each buildable `AC-###` and each `#### Scenario:`
    (WHEN/THEN) in `spec.md`. `## Success metrics` lines are **not** units. They carry no
-   `AC-###` id, no slice can satisfy them, and this pass never enqueues one (`spec-grammar.md`).
+   `AC-###` id, no slice can satisfy them, and this pass never enqueues one ([`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md)).
 2. **Plan touch-points:** the files/components/modules `plan.md` says get built or edited, and
    each existing slice's stated **Produces** (the interface it was meant to expose).
 3. **Principles:** each invariant in `.devrites/principles.md`, checked against the code as it
@@ -21,11 +21,11 @@ slice.
 
 | Verdict | Test | Action |
 |---|---|---|
-| **built** | The behavior exists in the code **and** a test covers it (a criterion with code but no covering test is not built: `testing.md`). | Nothing: do not append. |
+| **built** | The behavior exists in the code **and** a test covers it (a criterion with code but no covering test is not built: [`testing.md`](../../devrites-lib/reference/standards/testing.md)). | Nothing: do not append. |
 | **partial** | Some of it exists: happy path only, un-wired, untested, a TODO stub, or an edge case from the scenario's WHEN/THEN missing. | Append a slice for the **remainder**, its `Known-Gotchas` naming what's already there so `$rite-build` extends rather than rebuilds. |
 | **absent** | No code implements it. | Append a full slice. |
 
-Read the code to decide: do not infer from the plan. Apply `standards/tooling.md`: use the
+Read the code to decide: do not infer from the plan. Apply [`tooling.md`](../../devrites-lib/reference/standards/tooling.md): use the
 primary available code index, cross-check only a named unresolved predicate, then use LSP/file
 search so the verdict reflects live code. Read `traceability.md` to see what is mapped; only
 code and tests tell you what is built.
@@ -49,7 +49,7 @@ Before appending a slice, separate the two failure directions:
 - **Code gap:** the spec is right, the code falls short. → append a slice. (This skill's job.)
 - **Spec drift:** the code is right, the requirement is stale or wrong. → **do not** append a
   slice that bends correct code to a wrong spec. Stop, route through the Spec Drift Guard
-  (`rite-build/reference/spec-drift-guard.md`) + a recorded decision, and let `$rite-plan
+  ([`spec-drift-guard.md`](../../rite-build/reference/spec-drift-guard.md)) + a recorded decision, and let `$rite-plan
   repair` reshape intent. Convergence enqueues work; it never launders a spec bug into a code
   task.
 

package/pack/generated/codex/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 `.agents/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/codex/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/codex/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 `.agents/skills/devrites-lib/reference/standards/core.md`, then `tooling.md`, `testing.md`, and `afk-hitl.md` when relevant.
+Step 0: Read `.agents/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/codex/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/codex/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/codex/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/codex/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/codex/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/codex/skills/rite-plan/SKILL.md

@@ -14,9 +14,9 @@ artifact-only**: reconcile
 editing source code.
 
 ## Rules consulted (read on demand from `.agents/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 `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
@@ -76,7 +76,7 @@ Before classifying any Reslice, read `.agents/skills/devrites-lib/reference/stan
    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