devrites 6.10.0 → 7.0.1

package/pack/generated/codex/agents/devrites-frontend-reviewer.toml

@@ -38,7 +38,9 @@ catalog.
 In workspace `.devrites/work/<slug>/`, read `design-brief.md`,
 `polish-report.md`. Run `git diff` limited to `touched-files.md` paths, inspect the
 touched UI files, and check the
-project's tokens, shared components, and neighboring screens.
+project's tokens, shared components, and neighboring screens. Find consumers of a
+changed shared component with `trace_path` (`direction: "inbound"`) per
+`.agents/skills/devrites-lib/reference/standards/code-navigation.md`.
 
 ## Review
 Before the gate sweep, stamp a **pre-emit critique** over six axes — philosophy
@@ -109,9 +111,8 @@ draws a revision finding for variety 2.
 
 Return the report in this shape:
 ```
-Frontend review (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Critique: <philosophy n · hierarchy n · execution n · specificity n · restraint n · variety n | n/a>
 System alignment: <drift by root cause>

package/pack/generated/codex/agents/devrites-performance-reviewer.toml

@@ -31,6 +31,8 @@ Vitals. Use the current file rather than memory.
 ## Inputs
 In workspace `.devrites/work/<slug>/`, read `spec.md` for any performance budget,
 then `evidence.md`, `touched-files.md`, and the immutable diff supplied by the root.
+Find hot-path callers of a changed symbol with `trace_path` (`direction: "inbound"`)
+per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`.
 Look for Core Web Vitals evidence in `evidence.md`, a saved Lighthouse,
 PageSpeed Insights, or CrUX JSON artifact, and `browser-evidence.md`.
 
@@ -104,9 +106,8 @@ Return the report in this shape:
 
 **Measured mode**: lead with a compact scorecard, then the line findings:
 ```
-Performance review (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Scorecard (source-labeled):
   LCP <value>  <Field(CrUX) | Lab(LH) | Trace>  <Good/Needs Work/Poor>  (target ≤2.5s)
@@ -120,9 +121,8 @@ Verdict: <blockers? none/list>
 
 **Source mode**: no artifacts; one scorecard line, findings tagged `potential`:
 ```
-Performance review (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Scorecard: not measured (Source mode)
 Budget: <breached | unverified — missing <measurement> | none stated>

package/pack/generated/codex/agents/devrites-plan-drafter.toml

@@ -18,7 +18,9 @@ seams supplied by the orchestrator.
 - `repair`: return an atomic candidate replacement/delta bundle for the requested
   planning artifacts while preserving settled intent.
 
-Reuse existing seams and dependencies before proposing new ones. Build vertical
+Reuse existing seams and dependencies before proposing new ones. Per
+`.agents/skills/devrites-lib/reference/standards/code-navigation.md`, map seams with `get_architecture`, find reuse
+with `search_graph`, and size blast radius with `trace_path` (`direction: "inbound"`). Build vertical
 slices in dependency order; put a hub file's shared edit in one seam slice
 ([slicing.md](.agents/skills/rite-plan/reference/slicing.md#slice-independence)). Map every REQ and AC to a slice and executable proof,
 name rollback and failure paths; keep acceptance-changing proposals separate. Each proof

package/pack/generated/codex/agents/devrites-plan-reviewer.toml

@@ -32,8 +32,9 @@ scope; `tasks.md` for vertical slices and gates; and `spec.md` for the objective
 acceptance criteria. Read `strategy.md`, `decisions.md`, or `assumptions.md` only
 when needed to check a claim. Do not read the author's chat reasoning.
 
-Use the index order in `.agents/skills/devrites-lib/reference/standards/tooling.md` to
-check blast radius, placement, and reuse; fall back to Read/Grep/Glob.
+Per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`, check
+placement with `get_architecture`, reuse with `search_graph`, and blast radius with
+`trace_path` (`direction: "inbound"`); fall back to Read/Grep/Glob.
 
 ## Score the seven dimensions
 For each dimension, **cite the evidence first**, including an absent plan or spec
@@ -136,9 +137,8 @@ criterion, slice, or proof.
 
 Return the report in this shape:
 ```
-Plan review (<slug>) — independent, pre-build
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n> contract=<n> mechanism=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Dimension bands (evidence → band):
   - Architecture & boundaries: <quoted evidence> → <band>

package/pack/generated/codex/agents/devrites-security-auditor.toml

@@ -33,7 +33,8 @@ supply-chain risk. Use the current file rather than memory.
 
 In workspace `.devrites/work/<slug>/`, read `spec.md` for the data model, API, and
 affected areas, then `decisions.md` and `touched-files.md`. Run `git diff` and
-inspect the touched files.
+inspect the touched files. For source-to-sink candidates use `trace_path`
+(`mode: "data_flow"`) per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`, then confirm each hop by reading it.
 
 ## Audit (feature scope, OWASP-oriented)
 
@@ -115,9 +116,8 @@ forgery control, unsafe deserialization, and fail-closed environment defaults wh
 Return the report in this shape:
 
 ```
-Security audit (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Coverage: <audited>/<total> units; unchecked: <unit — reason | none>
 Rejected: <candidate — disproof file:line | none>

package/pack/generated/codex/agents/devrites-simplifier-reviewer.toml

@@ -35,7 +35,9 @@ comprehension test, deletion test, and "reduce not relocate" rule as written.
 
 In workspace `.devrites/work/<slug>/`, read `spec.md` for acceptance criteria,
 then `tasks.md` and `touched-files.md`. Run `git diff` and inspect the touched
-files. No diff, or an unreadable input → `Outcome: gap` naming it; a diff with no
+files. Per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`, find near-duplicates of new code with `search_graph`
+(`semantic_query`); a new symbol with no `trace_path` inbound callers is a dead-code
+candidate, subject to the static-graph blind spots. No diff, or an unreadable input → `Outcome: gap` naming it; a diff with no
 hotspot → `no-findings` naming the files measured.
 
 ## Discipline
@@ -89,9 +91,8 @@ hotspot → `no-findings` naming the files measured.
 Return the report in this shape:
 
 ```
-Simplification review (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n> Suggestion · <n> Nit · <n> FYI
+Counts: suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Fences (do not remove — reason unclear): file:line — what it seems to guard
 Hotspots (most complex; addressed or left + why): file:line — note

package/pack/generated/codex/agents/devrites-slice-wright.toml

@@ -64,12 +64,14 @@ unclear boundary is underspecified: return `Escalation` without proceeding.
 
 ## Procedure: the one-slice cycle
 1. **ORIENT.** Before editing, read the target files and their neighbors. Learn the
-   local naming, casing, layers, error model, test style, and existing helpers. Use
-   a code-intelligence index when available. Start with `codebase-memory-mcp`;
-   use at most one cross-check only if it is incomplete, stale, unpinned, or
-   conflicting, then fall back to Read/Grep/Glob. Follow
-   `.agents/skills/devrites-lib/reference/standards/tooling.md` for placement,
-   callers, and impact. **Reuse → extend → build new**: look for an existing
+   local naming, casing, layers, error model, test style, and existing helpers. With
+   codebase-memory-mcp available (preflight, coverage, host access, and fallback in
+   `.agents/skills/devrites-lib/reference/standards/code-index.md`): get exact
+   names from `search_graph`, the affected set from `trace_path` (`direction:
+   "inbound"`) before editing, and bodies from `get_code_snippet`; after edits,
+   compare `detect_changes` (explicit `base_branch`) with the contract's path list.
+   If the packet carries index evidence instead, use it; never index. Otherwise use
+   Read/Grep/Glob. **Reuse → extend → build new**: look for an existing
    utility, type, component, or helper before adding one.
    Read named `.devrites/principles.md`; live-code evidence cannot override its
    invariants. Rule 6 governs conflicts.
@@ -102,7 +104,10 @@ unclear boundary is underspecified: return `Escalation` without proceeding.
    - **No process residue.** Do not put `SLICE-###`, slice numbers, or "this slice"
      in product source, tests, comments, or filenames.
 4. **VERIFY (fail-on-red).** Run writer-safe tests/types/lint: `Tests/proof` plus
-   tests of changed code; `## Feature gates` rows are root-owned. Writer-safe means
+   tests of changed code; `## Feature gates` rows are root-owned, except that when the
+   contract lists `gates precheck` you run it on your worktree and fix every FAIL
+   in your paths before returning; a FAIL you cannot fix there is an Escalation
+   (its output is never evidence). Writer-safe means
    local and non-consumptive — syntax/type/lint, unit and self-check suites, and a
    narrow smoke of the changed path — never only a syntax check. spawn_agent text that
    says to skip tests, run nothing, or leave all proof to the root does not waive
@@ -121,6 +126,7 @@ unclear boundary is underspecified: return `Escalation` without proceeding.
    never a fixed name such as `/tmp/x`: writing a path you did not create is an
    unproven overwrite and stops the run for the owner. Edit allowlisted files with
    the edit tool; a blocked edit is a gap to report, never routed around.
+   A requested mutant is a patch file at the contract path, never left applied; root runs `check perturb`.
    For non-trivial failure, invoke `devrites-debug-recovery` with the exact error,
    hypotheses, and dead ends. Caller and recovery share three no-progress attempts per
    exact causal fingerprint. Count only corrections whose recheck preserves the same
@@ -213,7 +219,10 @@ Every key is required; use an empty array when there is nothing to report.
 **Before returning, check every requirement:** one minimal complete in-scope slice;
 project idiom/reuse; no slop; principles honored; real green output; every applicable
 topology/data/integration behavior proved (or exact vetted root proof `not-run`);
-bookkeeping returned only. Fix defects, report technical blockers, and escalate
+bookkeeping returned only. Then attack your claim as the reviewers will: code meets
+each claimed criterion's quoted acceptance text, not a later decision's looser reading
+(a conflict escalates); a repair opens no new race, stale read, or ordering gap; each
+claimed criterion has a test that fails without the change. Fix defects, report technical blockers, and escalate
 human-owned choices. Never silently ship a known gap.
 
 ## Tools / read-write mode

package/pack/generated/codex/agents/devrites-spec-reviewer.toml

@@ -37,7 +37,8 @@ Read `.agents/skills/devrites-lib/reference/standards/spec-grammar.md` first
 
 From `.devrites/work/<slug>/`, read `spec.md`, `tasks.md`, `decisions.md`,
 `assumptions.md`, and `drift.md`; inspect the active feature's `git diff` limited to
-the `touched-files.md` manifest paths.
+the `touched-files.md` manifest paths. For Placement, compare `detect_changes`
+(explicit `base_branch`, `scope: "files"`) with the spec, per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`.
 
 ## Assess
 
@@ -70,9 +71,8 @@ the `touched-files.md` manifest paths.
 ## Output
 
 ```text
-Spec review (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 
 Coverage:

package/pack/generated/codex/agents/devrites-strategy-reviewer.toml

@@ -38,9 +38,9 @@ to check a claim; never band the plan, which `devrites-plan-reviewer` owns. With
 `strategy.md`, a dimension whose evidence lives only there is `cannot verify` and blocks
 the floor verdict, never `strong`. Do not read the author's chat reasoning.
 
-Follow `.agents/skills/devrites-lib/reference/standards/tooling.md`: use the primary
-available code index for blast radius and placement, add at most one cross-check for a
-named incomplete/stale/conflicting predicate, then fall back to LSP or file search.
+Per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`: placement from
+`get_architecture`, blast radius from `trace_path` (`direction: "inbound"`), and
+`check_index_coverage` on cited paths; then fall back to LSP or file search.
 
 ## Score the nine dimensions
 For each dimension, **cite the spec line or its absence first**, then assign the
@@ -88,9 +88,8 @@ pre-mortem risk remains.
 
 Return the report in this shape:
 ```
-Strategy review (<slug>) — independent, pre-plan
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Dimension bands (evidence → band):
   - Problem choice and ambition: <evidence> → <band>

package/pack/generated/codex/agents/devrites-test-analyst.toml

@@ -38,7 +38,11 @@ In workspace `.devrites/work/<slug>/`, read `spec.md` for the acceptance criteri
 `evidence.md`, `tasks.md`, and `touched-files.md` by the schema's bounded rule: when
 `devrites-engine orient <slug>` reports one over budget, index it (`grep -n`) and load only
 entries naming this candidate's AC/slice IDs. Run `git diff` limited to `touched-files.md`
-paths to inspect the code and tests, then read the test files.
+paths to inspect the code and tests, then read the test files. To find the tests that
+reach each changed symbol, use `trace_path` (`direction: "inbound"`, `include_tests:
+true`) and `TESTS` edges via `query_graph`, per
+`.agents/skills/devrites-lib/reference/standards/code-navigation.md`; a changed
+symbol no test reaches is a finding.
 
 ## Assess
 - **Coverage of acceptance criteria:** map each criterion to the tests that prove it.
@@ -86,9 +90,8 @@ paths to inspect the code and tests, then read the test files.
 
 Return the report in this shape:
 ```
-Test analysis (<slug>) — independent
 Outcome: <findings | no-findings | gap>
-Counts: <n per severity or kind used in the rows below>
+Counts: critical=<n> important=<n> suggestion=<n> nit=<n> fyi=<n> gap=<n>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Claim map: <claim> | <exact_test> | <consumer_path> | <testing.md category> | <evidence gap> | <discriminating proof>
 Verdict: verified | behavior_unverified

package/pack/generated/codex/agents/fast-builder.toml

@@ -31,7 +31,9 @@ unclear boundary is an escalation, not a guess.
 ## Procedure
 
 1. **Orient.** Read the target files and their neighbors. Learn naming, layers, error
-   model, test style, and existing helpers. Reuse, then extend, then build new.
+   model, test style, and existing helpers. Reuse, then extend, then build new. Find
+   helpers with `search_graph` and callers with `trace_path` per
+   `.agents/skills/devrites-lib/reference/standards/code-navigation.md`.
 2. **Tests with the code.** For every AC in the contract, write a test that would
    fail without the change: real assertions on the new behavior, including the error
    and edge cases the AC names. Use the project's existing runner and style.

package/pack/generated/codex/agents/fast-checker.toml

@@ -31,7 +31,8 @@ baseline paths in `plan.md`.
 3. **Scope.** Every changed path belongs to a slice. Every new behavior belongs to an
    AC. Anything else is `out-of-scope`.
 4. **Contracts.** For each changed function, type, or interface, check its callers
-   still match.
+   still match: list them with `trace_path` (`direction: "inbound"`) per
+   `.agents/skills/devrites-lib/reference/standards/code-navigation.md`, then read each call site.
 5. **Leftovers.** `TODO`, `TBD`, stubs, `not implemented`, commented-out code, or
    debug output in changed lines.
 6. **Check run.** Each red command becomes one `failing-command` gap with its first

package/pack/generated/codex/agents/fast-critic.toml

@@ -22,7 +22,8 @@ input, auth, data, or integrations.
 
 `spec.md` and `plan.md` from `.devrites/work/<slug>/`, and the feature diff: `git diff`
 plus untracked files, minus the baseline paths in `plan.md`. Read the touched files
-and their callers, not only the hunks.
+and their callers, not only the hunks; list callers with `trace_path`
+(`direction: "inbound"`) per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`.
 
 ## Review
 

package/pack/generated/codex/agents/fast-planner.toml

@@ -28,8 +28,8 @@ Formats live in `.agents/skills/rite-fast/reference/artifacts.md`
 
 1. **Facts from the repository, not from the user.** Find where the change lives,
    the existing helpers, types, and patterns to reuse, the test runner and test
-   style, and the callers the change affects. Use a code-intelligence index when
-   available, then Read/Grep/Glob. A question whose answer sits in a file is a
+   style, and the callers the change affects. Use `search_graph` and `trace_path`
+   (`direction: "inbound"`) per `.agents/skills/devrites-lib/reference/standards/code-navigation.md`, then Read/Grep/Glob. A question whose answer sits in a file is a
    defect in your output.
 2. **Acceptance criteria.** Observable behavior at a named surface, one test able
    to show each. Include error and edge behavior the task implies. No criteria for

package/pack/generated/codex/agents/overhaul-recon.toml

@@ -39,10 +39,11 @@ and proposals.
    denominator. Note submodules (boundary only), binaries and assets, candidate
    vendored or generated paths with the evidence for each (generator, header, config),
    and security-sensitive ignored inputs by path only.
-3. Use a code graph when the host offers one, to map faster, never to decide scope:
-   `codebase-memory-mcp` (architecture, call paths) or `codegraph` for a full project,
-   `code-review-graph` (changed nodes, impact radius) for a PR or branch. Record which
-   graph you used, its index time and the commit it was built from. A graph is a hint:
+3. Use codebase-memory-mcp when the host offers it, to map faster, never to decide
+   scope: `get_architecture` and `trace_path` for a full project, `detect_changes`
+   (explicit `base_branch`) for a PR or branch, per
+   `.agents/skills/devrites-lib/reference/standards/code-navigation.md`. Record the project, its `indexed_at`
+   and the commit it was built from. A graph is a hint:
    it may be stale or miss dynamic calls, so it can add entry points, contract seeds
    and cross-file edges but never remove a file, range or lane from the step 2
    inventory. Verify every graph-derived fact you report against the source. Without a

package/pack/generated/codex/skills/devrites-api-interface/SKILL.md

@@ -3,7 +3,7 @@ name: devrites-api-interface
 description: Shape stable API, type, module, or frontend/backend contracts before implementation. Use when a slice crosses a boundary; not for internal helpers.
 user-invocable: false
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"deprecation":["devrites-lib/reference/standards/deprecation.md"],"security":["devrites-lib/reference/standards/security.md","rite-review/reference/security-review.md"]},"workspace":["spec.md","plan.md","tasks.md","state.md","decisions.md"]} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"deprecation":["devrites-lib/reference/standards/deprecation.md"],"security":["devrites-lib/reference/standards/security.md","rite-review/reference/security-review.md"]},"workspace":["spec.md","plan.md","tasks.md","state.md","decisions.md"],"rootOnly":["devrites-lib/reference/standards/afk-hitl.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --skill devrites-api-interface` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # devrites-api-interface: contract before implementation

package/pack/generated/codex/skills/devrites-audit/SKILL.md

@@ -4,7 +4,7 @@ description: Audit one feature read-only for security, performance, or simplific
 argument-hint: "<security | perf | simplify>"
 user-invocable: false
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/agents.md"],"triggers":{"audit-coverage":["devrites-lib/reference/standards/audit-coverage.md"],"architecture-health":["devrites-lib/reference/standards/architecture-health.md"]},"workspace":["spec.md","plan.md","tasks.md","touched-files.md","evidence.md","state.md","decisions.md"],"workspaceByRole":{"performance-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"security-auditor":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"simplifier-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md"]}} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/standards/code-index.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/agents.md"],"triggers":{"audit-coverage":["devrites-lib/reference/standards/audit-coverage.md"],"architecture-health":["devrites-lib/reference/standards/architecture-health.md"]},"workspace":["spec.md","plan.md","tasks.md","touched-files.md","evidence.md","state.md","decisions.md"],"workspaceByRole":{"performance-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"security-auditor":["spec.md","plan.md","tasks.md","state.md","touched-files.md","evidence.md"],"simplifier-reviewer":["spec.md","plan.md","tasks.md","state.md","touched-files.md"]},"rootOnly":["devrites-lib/reference/standards/code-index.md","devrites-lib/reference/parallel-dispatch.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --skill devrites-audit` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # devrites-audit: read-only audit dispatch

package/pack/generated/codex/skills/devrites-debug-recovery/SKILL.md

@@ -4,7 +4,7 @@ description: Fix application test, build, CI, runtime, browser, or 500 failures
 argument-hint: "[<slug>]"
 user-invocable: false
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/code-navigation.md","devrites-debug-recovery/reference/build-the-loop.md","devrites-debug-recovery/reference/cleanup-and-classify.md","devrites-debug-recovery/reference/hypotheses.md","devrites-debug-recovery/reference/instrumentation.md","devrites-debug-recovery/reference/regression-test.md","devrites-debug-recovery/reference/trace.md","devrites-lib/reference/standards/debug-recovery.md"],"triggers":{"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"security":["devrites-lib/reference/standards/security.md"],"workspace":["devrites-lib/reference/standards/workflow-artifacts.md"]}} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/standards/code-index.md","devrites-debug-recovery/reference/build-the-loop.md","devrites-debug-recovery/reference/cleanup-and-classify.md","devrites-debug-recovery/reference/hypotheses.md","devrites-debug-recovery/reference/instrumentation.md","devrites-debug-recovery/reference/regression-test.md","devrites-debug-recovery/reference/trace.md","devrites-lib/reference/standards/debug-recovery.md"],"triggers":{"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"security":["devrites-lib/reference/standards/security.md"],"workspace":["devrites-lib/reference/standards/workflow-artifacts.md"]},"rootOnly":["devrites-lib/reference/standards/code-index.md","devrites-lib/reference/standards/workflow-artifacts.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --skill devrites-debug-recovery` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # devrites-debug-recovery: fix the root cause, not the symptom

package/pack/generated/codex/skills/devrites-doubt/SKILL.md

@@ -3,7 +3,7 @@ name: devrites-doubt
 description: Stress-test one consequential decision independently. Use for uncertainty around boundaries, data, auth, APIs, or migrations; not trivial choices.
 user-invocable: false
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/agents.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"security":["devrites-lib/reference/standards/security.md"],"tooling":["devrites-lib/reference/standards/tooling.md"]},"workspace":["spec.md","plan.md","tasks.md","state.md","decisions.md"],"workspaceByRole":{"doubt-reviewer":["spec.md","plan.md","tasks.md","state.md","decisions.md"]}} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/agents.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"security":["devrites-lib/reference/standards/security.md"],"tooling":["devrites-lib/reference/standards/tooling.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/standards/code-index.md"]},"workspace":["spec.md","plan.md","tasks.md","state.md","decisions.md"],"workspaceByRole":{"doubt-reviewer":["spec.md","plan.md","tasks.md","state.md","decisions.md"]},"rootOnly":["devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/code-index.md","devrites-lib/reference/standards/tooling.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --skill devrites-doubt` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # devrites-doubt: CLAIM → EXTRACT → DOUBT → RECONCILE → STOP
@@ -42,10 +42,10 @@ complexity reappears across N callers, the abstraction concentrates real complex
 Wait for a second real caller before keeping a pass-through that fails this test.
 
 ## Rules
-- For "where does this claim reach / what would change with it" questions, prefer a
-  code-intelligence index under [`tooling.md`](../devrites-lib/reference/standards/tooling.md): use the primary available index,
-  add at most one cross-check for a named incomplete/stale/conflicting predicate, then fall
-  back to LSP or file search. Do not query several indexes for reassurance.
+- For "where does this claim reach / what would change with it" questions (trigger
+  `tooling`), use codebase-memory `trace_path` (`direction: "inbound"`) per
+  [`code-navigation.md`](../devrites-lib/reference/standards/code-navigation.md),
+  then fall back to LSP or file search. Do not repeat a query for reassurance.
 - The reviewer prompt must be adversarial: its job is to break the claim, not to agree.
 - Strip your own justification before review; reasoning anchors the reviewer toward
   agreement.

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

@@ -9,9 +9,9 @@ This applies to UI **and** non-UI code: utilities, helpers, types, validators, s
 formatters, hooks, query helpers: anything that might already exist.
 
 ## The decision (in order)
-1. **Search first.** Apply `../../devrites-lib/reference/standards/tooling.md`: use the
-   primary available code index to find similar definitions, cross-check only a named
-   unresolved predicate, then fall back to grep/glob over `components/`, design tokens, hooks/,
+1. **Search first.** Apply `../../devrites-lib/reference/standards/code-navigation.md`: find
+   similar definitions with codebase-memory `search_graph` (`semantic_query` plus
+   `name_pattern` variants), then fall back to grep/glob over `components/`, design tokens, hooks/,
    utils/, lib/. Look for things doing the *same job*, not just the same name.
 2. **Exact fit → REUSE.** Compose / import the existing thing. No copy, no fork.
 3. **Close fit → EXTEND.** Add a variant/prop/option that the existing component or util

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

@@ -3,7 +3,7 @@ name: devrites-interview
 description: Interview the user one question at a time to extract intent. Use when the user says "interview me", "I am not sure what I want", or the ask is underspecified. Not for casual clarification.
 user-invocable: false
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","rite-spec/reference/interview-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["spec.md","questions.md","decisions.md","assumptions.md","decision-coverage.md","state.md"]} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","rite-spec/reference/interview-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["spec.md","questions.md","decisions.md","assumptions.md","decision-coverage.md","state.md"],"rootOnly":["devrites-lib/reference/standards/afk-hitl.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --skill devrites-interview` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # devrites-interview: extract intent

package/pack/generated/codex/skills/devrites-lib/SKILL.md

@@ -45,14 +45,16 @@ lifecycle state from chat or optional `README.md`.
 The engine is limited to:
 
 - Checks: `check candidate` (content-bound identity), `check readiness`
-  (structure; `--emit-binding` emits the Build-input binding), `check seal` (structure
+  (structure; `--emit-binding` emits the Build-input binding), `check
+  preconditions` (Vet preflight rows), `check seal` (structure
   plus exact artifact bindings and evidence freshness), `check slice` (slice
   contract preflight before wright dispatch), `check task-graph`, `check
   diff-scope` (mechanical changed-paths ⊆ allowlist before reviewer dispatch),
   `check path-disjoint`, `check skill-trust`, `check indexes`, `check
   regression` (progress high-water mark), `check drift` (readiness-input
   attribution), `check windows` (deferral-marker waivers), `check dup`
-  (advisory near-duplicates), `detect commands` (repository test/lint wiring).
+  (advisory near-duplicates), `check anchors` (Critical/Important quote
+  anchoring), `check perturb` (safe-perturbation probe), `detect commands` (repository test/lint wiring).
 - Observation: `observe summary` (`orient` alias), `observe slice`, `next`
   (minimal remaining lifecycle path), `handoff` (deterministic resume record).
 - Coordination: `context` emits one deduplicated read-set bundle from each
@@ -71,17 +73,20 @@ The engine is limited to:
   principles presence); confirm them rather than re-deriving conditions. Repeat
   calls with unchanged inputs print `unchanged` and reuse the existing bundle.
   `dispatch` owns the launch-wave barrier — seal needs a distinct handle per
-  role, return needs seal, and start/return auto-record into the `metrics`
-  ledger. `claim` owns the advisory session-scoped `claims.jsonl` ledger;
+  role (the last start seals), return needs seal, open --claim-session/--claim
+  takes the wave's file claim (released by the completing return or abandon
+  --release), and start/return auto-record into the `metrics` ledger;
+  `candidate freeze` and `packet` write a wave's frozen diff and packets. `claim` owns the advisory session-scoped `claims.jsonl` ledger;
   `note` owns anchored `notes.md` entries (`check seal` refuses non-exact
   anchors); `parallel` owns deterministic worktree lease/create/integrate/
   cleanup for parallel slices.
 - `gates` owns the machine-checked acceptance ledger (`gates.md`): `scaffold`,
-  `status`, `run`, `reverify`, `lint`, `attest`, `abandon` — grammar and
+  `status`, `run`, `reverify`, `lint`, `precheck`, `attest`, `abandon` — grammar and
   authoring rules in
   [`reference/standards/gates.md`](reference/standards/gates.md).
 - Atomic state: `state resolve` for answer/drop/batch, `state merge-manifest`
-  for the predecessor-chain union, transactional `state close`, and `migrate`
+  for the predecessor-chain union, `state set`/`state append` for cursor fields and
+  ledger sections, transactional `state close`, and `migrate`
   for fail-closed workspace-schema normalization.
 - `secret-scan`, `open-visual`, and `version` remain read-only helpers.
 - Offline, local `install`, `update`, and `uninstall`; their shell/npm callers

package/pack/generated/codex/skills/devrites-lib/reference/orchestration-profiles.md

@@ -1,5 +1,7 @@
 # Native execution profiles
 
+> Root-only: not inlined in --role bundles.
+
 Profiles scale **change depth**, not orchestration machinery. The host discovers
 the exact project specialist named by a workflow, dispatches it in fresh context,
 waits for the result, validates the result shape, and reconciles the evidence.

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

@@ -1,5 +1,7 @@
 # Native review dispatch
 
+> Root-only: not inlined in --role bundles.
+
 Host dispatch; DevRites governs.
 
 ## Roster
@@ -27,7 +29,9 @@ If the candidate diff has no matching surfaces, record
 
 ## Dispatch contract
 
-1. Freeze one candidate; give each reviewer the same spec, paths, and diff.
+1. Freeze one candidate with `devrites-engine candidate freeze <slug> --wave <w>
+   (--slice <SLICE-ID> | --paths <path>...) [--base <ref>]` (writes
+   `packets/<w>.diff` and `packets/<w>.sha256`); give each reviewer the same spec, paths, and diff.
    Parallelize only when writes/state/locks/tool sessions/scarce resources
    (ports/processes/quotas/FDs/browsers/MCP) are compatible. Frozen read-only
    usually is; pressure requires batches or serial work.
@@ -37,8 +41,10 @@ If the candidate diff has no matching surfaces, record
    still validate each result's context and candidate.
 2. Build each reviewer's read-set once with
    `devrites-engine context --skills-root .agents/skills <slug> --phase <p> --role <role> --trigger <set>` and
-   hand the bundle path as the packet's source list instead of a file roster.
-   Build roles add `--slice <SLICE-ID>` (slice-scoped, slice-named bundle).
+   render each reviewer, auditor, and test-analyst packet (other roles, such as
+   `proof-runner`, keep their own) with `devrites-engine packet <slug> --wave <w> --phase <p>
+   --role <role> [--slice <SLICE-ID>] [--focus <file>]`: it names the bundle and frozen
+   diff by reference, copies the digests, and runs the `open` lints. Build roles add `--slice <SLICE-ID>` (slice-scoped, slice-named bundle).
    Evaluate the skill's trigger conditions and pass each that fires — a role's
    Trigger column maps to the phase manifest's names: `security-auditor` →
    `security`; at Review, `frontend-reviewer` → `ui` and `performance-reviewer` →
@@ -48,21 +54,25 @@ If the candidate diff has no matching surfaces, record
    omitted applicable trigger is a gap, not a shortcut.
 3. Enforce the launch barrier through the engine, not prose. Open the wave
    (`devrites-engine dispatch <slug> open --phase <p> --wave <w> --role <r>...`;
-   a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
-   those agents receive, and `open` refuses one that seeds a gate result, outcome,
-   count, or "already passed" claim; at Review and Seal it also needs the packet to
-   name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
+   a reviewer, auditor, or test-analyst wave adds `--packet <file>`, any one of the
+   wave's rendered `packets/<w>.<role>.md` (hand each agent its own file unedited), and `open` refuses one that seeds a gate result, outcome,
+   count, or "already passed" claim; a Build reviewer wave adds `--slice <SLICE-ID>`
+   so its findings key on that slice; at Review and Seal it also needs the packet to
+   name the frozen candidate diff and the manifest to cover every checkpointed path;
+   a same-tree writer wave adds `--claim-session <id> --claim <path>...` per
+   [`wright-dispatch.md`](../../rite-build/reference/wright-dispatch.md#run)), launch every native agent nonblocking through the host's own agent
    tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
    dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
    record each returned host handle
-   (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
-   seal fails until every declared role has a distinct handle, which makes a
+   (`dispatch ... start --wave <w> --role <r> --handle <id>`) — the last start
+   seals the wave (an explicit `seal` is a no-op), which makes a
    serial launch-then-wait pattern impossible to record. Record each completion
-   with `dispatch ... return`; `return` refuses before seal. `dispatch status`
+   with `dispatch ... return`; a reviewer adds `--result <file>` holding its return verbatim (the engine stores it as `packets/<wave>-<role>.return.md`, derives the outcome from its head, and records its `Finding:` keys; a file already at that path is kept), or `--outcome <findings|no-findings|gap>` when the host cannot hand the return over as a file; `return` refuses before seal. `dispatch status`
    exits nonzero while the wave is open, sealed, or abandoned. `start`/`return`
    auto-record the dispatch/return metrics events — no separate ledger call. If
    an opened wave cannot obtain every handle or reach `seal`, run
-   `devrites-engine dispatch <slug> abandon --wave <w> --reason <reason>` before
+   `devrites-engine dispatch <slug> abandon --wave <w> --reason <reason>` (with
+   `--release` on a host-confirmed stop or refused launch) before
    recording the gap; never leave an open wave to block a retry.
 4. Ask for each exact named agent in fresh context; omit native syntax and
    `agent_type`/`task_name`/`fork_turns` from the instruction.
@@ -142,13 +152,14 @@ session, the claim proof below settles it. A result classification alone
 does not prove host termination.
 
 On resume (compaction or a new session), run `devrites-engine dispatch <slug>
-status`, `parallel status`, and `claim list --all` before any dispatch. A read-only
+status`, `parallel status`, and `claim list` before any dispatch. A read-only
 wave whose handles this session cannot query: `abandon` it, record each unreturned
 role `gap`, and re-dispatch fresh on the current digest; its late returns are
 `stale`. A writer keeps its claim and lease — no relaunch on those paths until the
 claim is released or its holder is proven terminal. For an unqueryable writer,
-`claim list --all` showing its claim `released` or `dead` (the engine proved the
-holding session exited on this host) is that proof: `abandon` the wave, record the
+`claim list` showing its claim `dead` (the engine proved the holding session
+exited on this host), or `claim list --all --session <id>` showing it `released`
+(bare `list` only counts released rows), is that proof: `abandon` the wave, record the
 role `gap`, claim the paths, and re-dispatch without waiting on the launching
 session. `live` or `expired` stays held. A wright that never returned an
 admitted result leaves unadmitted bytes: task-path changes since its pre-dispatch

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

@@ -47,7 +47,8 @@ topic's owner.
 | `afk-hitl.md` | A pause, question, resume, or AFK decision is possible. |
 | `one-shot-actions.md` | A failed proof/action would spend paid or rate-limited quota, mutate external state, or delete its own failure evidence. |
 | `tooling.md` | Structural lookup, current external facts, or architecture memory is needed. |
-| `code-navigation.md` | Choosing graph, LSP, grep, or read routes before cross-file edits. |
+| `code-navigation.md` | Editing across files or claiming a blast radius: affected set, enclosing-body reads, fresh diagnostics, static-graph blind spots. |
+| `code-index.md` | Choosing graph, LSP, grep, or read routes: index preflight, route table, coverage, query budget, host access. |
 | `skill-authoring.md` | Creating, editing, routing, evaluating, or pruning a DevRites skill. |
 | `definition-of-done.md` | Prove, Seal, Ship, or Quick must decide whether work is finished. |
 | `review-checklist.md` | A compact review pass/fail sweep is enough. |