devrites 6.10.0 → 7.0.1

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

@@ -5,7 +5,7 @@ argument-hint: "[feature-slug]"
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/candidate-integrity.md","devrites-lib/reference/standards/git-workflow.md","devrites-lib/reference/standards/definition-of-done.md","devrites-lib/reference/standards/release/ship-checklist.md","rite-ship/reference/git-ship.md","rite-ship/reference/rollout.md","rite-ship/reference/close-out.md","rite-ship/reference/ship-template.md","rite-ship/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md","evidence.md","touched-files.md","review.md","seal.md"]} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/candidate-integrity.md","devrites-lib/reference/standards/git-workflow.md","devrites-lib/reference/standards/definition-of-done.md","devrites-lib/reference/standards/release/ship-checklist.md","rite-ship/reference/git-ship.md","rite-ship/reference/rollout.md","rite-ship/reference/close-out.md","rite-ship/reference/ship-template.md","rite-ship/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md","evidence.md","touched-files.md","review.md","seal.md"],"rootOnly":["devrites-lib/reference/standards/afk-hitl.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --phase ship` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 

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

@@ -5,7 +5,7 @@ argument-hint: "<feature or idea>"
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/elicitation.md","devrites-lib/reference/standards/agents.md","rite-spec/reference/investigation.md","rite-spec/reference/question-protocol.md","rite-spec/reference/spec-template.md","rite-spec/reference/spec-checklists.md","rite-spec/reference/state-workspace.md","rite-spec/reference/acceptance-criteria.md","rite-spec/reference/interview-patterns.md","rite-spec/reference/ai-spec-template.md","rite-spec/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"documentation":["devrites-lib/reference/standards/documentation.md"],"edge-cases":["devrites-lib/reference/standards/edge-case-trace.md"],"frontend":["rite-build/reference/frontend-trigger.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"principles":["devrites-lib/reference/standards/principles.md"],"references":["rite-spec/reference/references-intake.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md"],"workspaceByRole":{"evidence-scout":["brief.md","spec.md","state.md","questions.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/standards/elicitation.md","devrites-lib/reference/standards/agents.md","rite-spec/reference/investigation.md","rite-spec/reference/question-protocol.md","rite-spec/reference/spec-template.md","rite-spec/reference/spec-checklists.md","rite-spec/reference/state-workspace.md","rite-spec/reference/acceptance-criteria.md","rite-spec/reference/interview-patterns.md","rite-spec/reference/ai-spec-template.md","rite-spec/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"documentation":["devrites-lib/reference/standards/documentation.md"],"edge-cases":["devrites-lib/reference/standards/edge-case-trace.md"],"frontend":["rite-build/reference/frontend-trigger.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"principles":["devrites-lib/reference/standards/principles.md"],"references":["rite-spec/reference/references-intake.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md"],"workspaceByRole":{"evidence-scout":["brief.md","spec.md","state.md","questions.md"]},"rootOnly":["devrites-lib/reference/standards/code-index.md","devrites-lib/reference/standards/afk-hitl.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --phase spec` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
@@ -124,7 +124,8 @@ load a routed standard to discover required behavior, not to prescribe implement
    owned prerequisites. Keep a build checkpoint only for unavailable pre-code evidence or a
    mandatory action-time approval. **Completion:** no foreseeable human choice is deferred.
 5. **Create or update the workspace** + set `.devrites/ACTIVE` from
-   [state-workspace](reference/state-workspace.md). If the slug already exists,
+   [state-workspace](reference/state-workspace.md); a `--lookahead` run
+   leaves `.devrites/ACTIVE` unchanged. If the slug already exists,
    update the existing workspace rather than overwrite it; preserve history and
    unrelated settled content. Write every required artifact and conditional
    annex exactly from [spec-template](reference/spec-template.md)

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

@@ -4,10 +4,10 @@ Understand the requirement, decide where it belongs, define the outcome, and ide
 every issue and gap. Resolve material gaps with the user before the spec is ready. A
 gap first found during `$rite-build` is a drift event.
 
-Use a code-intelligence index if available (see
-`../../devrites-lib/reference/standards/tooling.md`) for structural questions such as
-where code lives, what calls it, and what it could break. With none present, use
-Read/Grep/Glob. When a gap depends on an external fact, such as a standard, UX pattern,
+Use codebase-memory-mcp if available (routes, preflight, and coverage in
+`../../devrites-lib/reference/standards/code-navigation.md`) for structural questions:
+`get_architecture` for where code lives, `search_graph` for reuse, `trace_path` for
+what calls it and what it could break. With none present, use Read/Grep/Glob. When a gap depends on an external fact, such as a standard, UX pattern,
 or comparable product, **search the web if available** (brave MCP preferred;
 `../../devrites-lib/reference/standards/tooling.md`). Cite the finding in the option
 presented to the human.
@@ -41,7 +41,7 @@ Use native file search over `.devrites/archive/*/{spec,decisions}.md`.
    anything that makes the obvious approach wrong. Each issue gets a disposition.
 6. **Gaps:** unknowns, ambiguities, undecided behavior, missing inputs. **Every gap
    becomes a question** (next section).
-7. **Blast radius:** what this change could break (use the code graph's impact/callers).
+7. **Blast radius:** what this change could break (`trace_path` with `direction: "inbound"` on the symbols to change).
    Informs risks, test strategy, and rollback.
 8. **Human prerequisites:** credentials, accounts, approval windows, or irreversible
    action-time decisions the acceptance path requires. Separate these from agent-owned

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

@@ -6,7 +6,7 @@ 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-YYYY-MM-DD-NNN` open question (released `Q-###` kept) ([`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>`. `spec.md`
+duplicate, source artifacts; over-budget requires `Budget override: <=N lines; <reason>` (N at most 2x the budget). `spec.md`
 is the product contract only: the phase verdict goes in the `state.md` `spec_gate` row,
 never in this file (every reviewer read-set includes `spec.md`).
 

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

@@ -154,7 +154,8 @@ Before an active caller moves backward, it copies its current phase and
 non-empty action into the two return rows. Nested Plan, Vet, Build, and proof
 work preserves that valid cursor. Once the prerequisite chain is green, the
 controlling caller restores the saved phase/action and removes both rows in one
-rewrite. A real HITL or parked-recovery stop retains the cursor for cold
+rewrite (`devrites-engine state set <slug> phase=<p> next_action=<a> --unset
+return_phase --unset return_next_action`). A real HITL or parked-recovery stop retains the cursor for cold
 resume. Never overwrite an existing valid return cursor, and preserve every
 unrelated Markdown byte. `$rite-clarify` applies its stricter native cursor protocol in `$rite-clarify`.
 
@@ -192,8 +193,9 @@ question: <one crisp sentence>
 options:
   1. <recommended> (Recommended) - <trade-off>
   2. <alternative> - <trade-off>
-proposed: <best current answer>
-raised_at: <iso>
+  3. Something else - describe it
+proposed: <option 1 restated; omit with no (Recommended)>
+raised_at: <RFC 3339, e.g. 2026-10-19T08:17:08Z>
 answered_at:
 answer:
 answered_by:        # human, only when resolved with `state resolve --human`
@@ -235,4 +237,4 @@ Why: <one line — the significance signals that picked the profile>
 
 High-traffic files should stay within the budgets in
 [`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.
+`Budget override: <=N lines; <reason>` (N at most 2x the budget) near the top.

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

@@ -48,7 +48,7 @@ status, and evidence for its claims. If chat contains missing durable context,
 recommend `$rite-handoff` before the lifecycle command.
 `devrites-engine handoff [slug]` emits the deterministic resume record (cursor,
 `awaiting_human`, blocking question gates, ledger reduction, dead ends,
-read-next order) — cite it for items 3–6 and the handoff-readiness verdict
+in-flight waves, read-next order) — cite it for items 3–6 and the handoff-readiness verdict
 rather than re-deriving them. If that command is not found or exits nonzero,
 report items 3–6 and `Handoff:` as `unavailable: <command> <not found | exit N>` —
 never re-derive them from other files, never leave them blank — and set `Next:`

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

@@ -5,7 +5,7 @@ argument-hint: "[feature-slug] [--mode expand|selective|hold-rigor|reduce-to-MVP
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/standards/agents.md","rite-temper/reference/significance.md","rite-temper/reference/scope-modes.md","rite-temper/reference/review-dimensions.md","rite-temper/reference/strategy-template.md","rite-temper/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"documentation":["devrites-lib/reference/standards/documentation.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","design-brief.md"],"workspaceByRole":{"strategy-reviewer":["brief.md","spec.md","decision-coverage.md","decisions.md","strategy.md","state.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/orchestration-profiles.md","devrites-lib/reference/standards/agents.md","rite-temper/reference/significance.md","rite-temper/reference/scope-modes.md","rite-temper/reference/review-dimensions.md","rite-temper/reference/strategy-template.md","rite-temper/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"documentation":["devrites-lib/reference/standards/documentation.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","design-brief.md"],"workspaceByRole":{"strategy-reviewer":["brief.md","spec.md","decision-coverage.md","decisions.md","strategy.md","state.md"]},"rootOnly":["devrites-lib/reference/standards/code-index.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/standards/afk-hitl.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --phase temper` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 

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

@@ -24,8 +24,8 @@ the gate uses the **lowest band**, not an average.
    up to an unbounded ideal. Vague adjectives ("fast/robust/intuitive") and "handles X
    gracefully" are flagged.
 7. **Irreversibility & blast radius:** are auth / migration / public-API / data-model touches
-   treated with conservatism + rollback, and is the blast radius understood (from a
-   code-intelligence index if available)?
+   treated with conservatism + rollback, and is the blast radius understood (from
+   codebase-memory `trace_path` if available)?
 8. **Cross-cutting coverage:** security/trust-boundary, data & migration, observability, and
    modifiability each explicitly addressed **or explicitly N/A**: no silent omission.
 9. **Convention fit & placement realism:** does the ambition fit the codebase's existing seams

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

@@ -14,8 +14,8 @@ Diverge on the *real problem*, not the obvious path. Ask:
 
 Ambition aims at the **outcome** (problem definition, success bar, user value) and at
 complexity-**neutral** future-proofing. It never aims at the **solution surface** (that's Pass 2's
-job to prune). Ground every ambitious idea in the codebase's real seams and blast radius. Use a
-code-intelligence index if available (see `../../devrites-lib/reference/standards/tooling.md`). Don't invent greenfield scope a
+job to prune). Ground every ambitious idea in the codebase's real seams and blast radius. Use
+codebase-memory `get_architecture` and `trace_path` if available (see `../../devrites-lib/reference/standards/code-navigation.md`). Don't invent greenfield scope a
 constrained codebase can't absorb.
 
 ## Pass 2: INVERSION (quench: pre-mortem + prune)

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

@@ -10,8 +10,8 @@ so they agree on when it fires.
   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.
-- **Cross-module blast radius:** the impact (from a code-intelligence index if available (see
-  `../../devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
+- **Cross-module blast radius:** the impact (from codebase-memory `trace_path` per
+  `../../devrites-lib/reference/standards/code-navigation.md`, or an honest estimate) crosses
   module/service boundaries or has many dependents.
 - **Greenfield / ambiguous scope:** a new surface with no existing seam to follow, or a spec
   whose "right size" is genuinely open (multiple defensible scopes).

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

@@ -5,7 +5,7 @@ argument-hint: "[slug] [--cross-model] [--full]"
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"rootOnly":["devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/elicitation.md"],"workspaceByRole":{"doubt-reviewer":["spec.md","architecture.md","plan.md","tasks.md","test-plan.md","decisions.md","state.md"],"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.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/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"rootOnly":["devrites-lib/reference/standards/code-index.md","devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/elicitation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/workflow-artifacts.md"],"workspaceByRole":{"doubt-reviewer":["spec.md","architecture.md","plan.md","tasks.md","test-plan.md","decisions.md","state.md"],"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --phase vet` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
@@ -74,8 +74,8 @@ plan declares a root-authored executable workflow file, read
 0. **Orient.** Read core. Resolve active slug, require state, and read plan,
    tasks, spec, decision coverage, optional strategy/design brief, decisions,
    assumptions, and state. Require approved Plan and `Decision coverage: CLEAR`;
-   otherwise stop for Define or Clarify. Use code intelligence for placement,
-   blast radius, and reuse.
+   otherwise stop for Define or Clarify. Check placement (`get_architecture`),
+   blast radius (`trace_path`), and reuse (`search_graph`) per [`code-navigation.md`](../devrites-lib/reference/standards/code-navigation.md).
 1. **Select depth.** Apply `reference/depth.md` exactly; never skip. Every initial
    pass records an engineering verdict and test-plan coverage. A valid Recovery
    recheck retains prior depth and enters 1b.
@@ -136,7 +136,11 @@ plan declares a root-authored executable workflow file, read
 
    For each consumptive action, bind every `reference/artifacts.md` Consumptive
    action gates column; every fingerprint identifies one actionable seam; aliasing multiple
-   emit sites is a gap. Preflight observes but need not make future behavior pass.
+   emit sites is a gap. Preflight observes but need not make future behavior pass,
+   except that a manifest/lockfile edit is dry-run now: before READY run
+   `devrites-engine check preconditions <slug>` (rows with `Run at` `vet`, including each
+   `dependency-dry-run` and preserve-baseline row). A failure folds into Plan repair; only an
+   owner-owned decision becomes a question, batched under the afk-hitl decision-chain rule.
 4. **Audit readiness.** Goal-backward map every requirement, criterion, NFR,
    interaction, edge/prohibition, and decision row to one slice and executable
    proof. Verify UX/spec/architecture alignment, contracts, dependency order,
@@ -207,7 +211,9 @@ plan declares a root-authored executable workflow file, read
    `marker sweep:` line is recorded in `eng-review.md`; a kept hit blocks READY. Write phase/next step and emit one
    `Readiness inputs SHA-256` with
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
-   must pass. Record the per-input drift baseline alongside it:
+   must pass. A `sequence_lookahead: yes` workspace also records one
+   `Predecessor readiness: <predecessor> <digest>` line from the predecessor's
+   `--emit-binding` hex; readiness re-checks it. Record the per-input drift baseline alongside it:
    `devrites-engine check drift <slug> --record` — a later stale binding then
    names the exact artifact that moved instead of "something changed". An `ADVISORY
    proportion:` line names a slice whose proof outgrew its ACs: move its rows without a

package/pack/generated/codex/skills/rite-vet/reference/artifacts.md

@@ -96,10 +96,15 @@ writes tests from it; `$rite-prove` walks it against `evidence.md`. Specify
 From $rite-vet on <iso>. Runner + conventions: <detected framework + command>.
 
 ## Build-entry preflight
-| Gate | Command | Cwd | Expected | Prerequisites | Provenance to recapture |
-|---|---|---|---|---|---|
-| <test/browser/package> | <exact command> | <path> | <exit/output> | <service/browser/credential owner> | <tool version + full SHA-256s> |
+| Gate | Command | Cwd | Expected | Prerequisites | Provenance to recapture | Run at |
+|---|---|---|---|---|---|---|
+| <test/browser/package> | <exact command> | <path> | <exit/output> | <service/browser/credential owner> | <tool version + full SHA-256s> | vet / pre-dispatch SLICE-### / action |
 
+`check preconditions` runs `vet` rows (`--slice` runs `pre-dispatch` rows; `action` rows
+never run there) and passes on exit 0. A slice editing a manifest or lockfile needs a
+`dependency-dry-run SLICE-###` row at `vet`: apply the planned pin in an isolated copy, run
+the tidy/lock step, then the project's admission checks. Resource rows only read
+eligibility (swap, cpuset, env var present); they never measure or change the host.
 Link any disposable parser fixture. Preflight values are planning evidence, not post-build proof;
 Prove recaptures the observed command, candidate identity, and result.
 
@@ -184,6 +189,8 @@ enforces them, so author to the contract, not around it:
   tautological commands and weak expectations before build.
 - Manual gates (`EVIDENCE` only) are for judgment-bound outcomes; Prove
   attests them, Seal still requires them checked.
+- Carry a `Tests/proof` row marked `RUN: writer` at define into its gate as
+  `RUN: writer`; never on a CHECK that needs an empty `git diff` or a driver.
 
 ## Parallelization table (in `eng-review.md` §5 when there's an opportunity)
 

package/pack/generated/codex/skills/rite-vet/reference/depth.md

@@ -21,8 +21,8 @@ Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preservin
   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.
-- **Cross-module blast radius:** the impact (from a code-intelligence index if available (see
-  `../../devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
+- **Cross-module blast radius:** the impact (from codebase-memory `trace_path` per
+  `../../devrites-lib/reference/standards/code-navigation.md`, or an honest estimate) crosses
   module/service boundaries or has many dependents.
 - **Complexity:** `plan.md` touches **>8 files** or adds **>2 new services/modules/classes**.
 - **Multi-slice / multi-day work**, new dependency/pattern/design system. Slice count alone never creates a human pause.

package/pack/generated/codex/skills/rite-vet/reference/review-axes.md

@@ -17,8 +17,8 @@ Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preservin
 
 Before implementation review, check for work beyond the settled spec.
 
-1. **What exists?** Find reusable code/flows via
-   [`tooling.md`](../../devrites-lib/reference/standards/tooling.md). Reuse → extend →
+1. **What exists?** Find reusable code/flows with `search_graph` (`semantic_query`) per
+   [`code-navigation.md`](../../devrites-lib/reference/standards/code-navigation.md). Reuse → extend →
    build new; list missed reuse instead of planning parallel work.
 2. **Minimum diff.** Find the smallest contract-complete change. Flag non-blocking work;
    use the marked action for topology cuts.

package/pack/generated/codex/skills/rite-zoom-out/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[symbol | file | area to map]"
 user-invocable: true
 disable-model-invocation: true
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/tooling.md"],"workspace":["spec.md","plan.md","decisions.md","state.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/standards/tooling.md"],"workspace":["spec.md","plan.md","decisions.md","state.md"],"rootOnly":["devrites-lib/reference/standards/code-index.md"]} -->
 > Read-set manifest: `devrites-engine context --skills-root .agents/skills <slug> --skill rite-zoom-out` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # $rite-zoom-out: step up one abstraction layer
@@ -34,12 +34,12 @@ A **structural map**: terse. One pass should answer:
 - **Smallest sensible change-scope:** where a fix would naturally land, so the next
   step doesn't drift into a project-wide refactor.
 
-## Prefer a code-intelligence index (if available)
+## Prefer codebase-memory-mcp (if available)
 
-Apply `.agents/skills/devrites-lib/reference/standards/tooling.md`: use the primary
-available architecture/code index, add at most one cross-check for a named incomplete,
-stale, or conflicting predicate, then fall back to LSP and file search. Do not query
-multiple indexes merely to confirm the same map.
+Apply `.agents/skills/devrites-lib/reference/standards/code-navigation.md`:
+`get_architecture` (`aspects: ["overview"]`, `path` = the area) for modules,
+`trace_path` (`direction: "inbound"` / `"outbound"`) for callers and calls, then fall
+back to LSP and file search. Do not repeat a query merely to confirm the same map.
 
 ## Vocabulary discipline
 

package/pack/generated/devin/agents/devrites-code-reviewer.md

@@ -56,7 +56,11 @@ diff scope. Read `spec.md` for the objective and acceptance criteria, then
 reports one over budget, index it (`grep -n`) and load only entries naming this
 candidate's AC/slice IDs. The principles are binding project invariants. Run `git diff`
 for the feature scope and read the touched files. No diff or an empty candidate →
-`Outcome: gap` naming it.
+`Outcome: gap` naming it. For blast radius, run `detect_changes` (explicit
+`base_branch` = feature base, `scope: "impact"`) and `trace_path` (`direction:
+"inbound"`) on impacted symbols that carry a finding, per
+`.devin/skills/devrites-lib/reference/standards/code-navigation.md`; check
+cited paths with `check_index_coverage`.
 
 A lane assignment (`code-reviewer.frontend` or `code-reviewer.backend`) names your
 lane, its path set, its profile, and the contracts crossing it: verdicts cover your
@@ -158,12 +162,12 @@ not as a blocker on this diff.
 Return the report in this shape:
 
 ```
-Code review (<slug>) — independent · lane: <frontend | backend | single: <domain>>
 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>
+Lane: <frontend | backend | single: <domain>>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Coverage: <files read fully | hunk-level | skipped: name — reason>
-Finding: <severity> conf <n> | <file:line> | <observed> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
+Finding: <severity> conf <n> | <file:line> | `<quoted cited line>` <observed result> | when <input/state/sequence> → <effect> | breaks <ID or standard §> "<quoted line>" | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 Contract: <applicable | not-applicable> — <basis: both sides read · crossing test>
 Tests: <adequate? gaps>

package/pack/generated/devin/agents/devrites-devex-reviewer.md

@@ -55,7 +55,8 @@ The available artifacts select one of two modes:
 You receive a feature slug or workspace path (`.devrites/work/<slug>/`) and the
 diff scope. Read `spec.md`, `plan.md`, `decisions.md`, `touched-files.md`, and
 `.devrites/principles.md` if present. Public API invariants in the principles file
-are binding. Read `devex.md` if present for predicted or measured scores, plus
+are binding. Find consumers of a changed public symbol with `trace_path`
+(`direction: "inbound"`) per `.devin/skills/devrites-lib/reference/standards/code-navigation.md`. Read `devex.md` if present for predicted or measured scores, plus
 `evidence.md`, `browser-evidence.md`, and the root-supplied immutable diff for the
 measured run. Inspect the developer-facing files it
 touches, including route handlers, CLI entry points, exported signatures, README
@@ -113,9 +114,9 @@ consistently:
 Return the report in this shape:
 
 ```
-DevEx review (<slug>) — independent · mode: predict | measure
 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>
+Mode: <predict | measure>
 Account: <admitted findings | No-findings | Gap per Result admission>
 Scorecard:
   discoverability   <band/score + one-line basis>

package/pack/generated/devin/agents/devrites-doubt-reviewer.md

@@ -39,7 +39,8 @@ attack, not support.
 A **claim** of one to three sentences and an **artifact + contract**, such as a
 function, decision, diff hunk, or interface. You may also receive a workspace path
 for `spec.md`, `decisions.md`, and the relevant `git diff`. Read only what you need
-to test the claim.
+to test the claim. Where a claim reaches: `trace_path` (`direction: "inbound"`) on its
+symbols, per `.devin/skills/devrites-lib/reference/standards/code-navigation.md`.
 
 When the claim concerns branching, boundary handling, or deletion, read
 `.devin/skills/devrites-lib/reference/standards/edge-case-trace.md` or its Codex
@@ -80,9 +81,8 @@ mirror.
 Return the report in this shape:
 
 ```
-Doubt review
 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: <restated>
 Attempts to break it: <what you tried>

package/pack/generated/devin/agents/devrites-evidence-scout.md

@@ -38,7 +38,8 @@ Read only the paths and bounded question supplied by the orchestrator.
   versioned docs/standards. Cite URL or `path:line`, version, and for external sources
   the retrieval date (ISO).
 
-For structural questions, use the repository's code-intelligence index. Use exact
+For structural questions, use codebase-memory-mcp per the route table and coverage
+rule in `.devin/skills/devrites-lib/reference/standards/code-index.md`. Use exact
 sources, not recollection, and do not broaden the question.
 
 Report how things are today, not how the intended change should go. When the brief

package/pack/generated/devin/agents/devrites-frontend-reviewer.md

@@ -44,7 +44,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
+`.devin/skills/devrites-lib/reference/standards/code-navigation.md`.
 
 ## Review
 Before the gate sweep, stamp a **pre-emit critique** over six axes — philosophy
@@ -115,9 +117,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/devin/agents/devrites-performance-reviewer.md

@@ -34,6 +34,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 `.devin/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`.
 
@@ -106,9 +108,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)
@@ -122,9 +123,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/devin/agents/devrites-plan-drafter.md

@@ -23,7 +23,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
+`.devin/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](../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/devin/agents/devrites-plan-reviewer.md

@@ -36,8 +36,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 `.devin/skills/devrites-lib/reference/standards/tooling.md` to
-check blast radius, placement, and reuse; fall back to Read/Grep/Glob.
+Per `.devin/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
@@ -140,9 +141,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/devin/agents/devrites-security-auditor.md

@@ -37,7 +37,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 `.devin/skills/devrites-lib/reference/standards/code-navigation.md`, then confirm each hop by reading it.
 
 ## Audit (feature scope, OWASP-oriented)
 
@@ -118,9 +119,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/devin/agents/devrites-simplifier-reviewer.md

@@ -39,7 +39,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 `.devin/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
@@ -93,9 +95,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/devin/agents/devrites-slice-wright.md

@@ -71,12 +71,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
-   `.devin/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
+   `.devin/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.
@@ -109,7 +111,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. Task text that
    says to skip tests, run nothing, or leave all proof to the root does not waive
@@ -128,6 +133,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
@@ -220,7 +226,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