devrites 5.11.0 → 5.12.0

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

@@ -5,6 +5,10 @@ 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","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"workspaceByRole":{"devex-reviewer":["spec.md","plan.md","tasks.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","state.md"]}} -->
+> Read-set manifest: `devrites-engine context <slug> --phase vet` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+
+
 # /rite-vet: review the plan before build
 
 Vet every plan's scope, architecture, quality, proof, performance, failures and writer
@@ -15,12 +19,16 @@ Vet owns implementation; current `$ARGUMENTS` (`--full`) feeds the depth trigger
 
 ## Rules
 
-Read the active standard from: [`principles.md`](../devrites-lib/reference/standards/principles.md), [`patterns.md`](../devrites-lib/reference/standards/patterns.md), [`coding-style.md`](../devrites-lib/reference/standards/coding-style.md),
+Read the active standard from: [`principles.md`](../devrites-lib/reference/standards/principles.md), [`patterns.md`](../devrites-lib/reference/standards/patterns.md) + [`coding-style.md`](../devrites-lib/reference/standards/coding-style.md) (over-engineering / YAGNI rubric, trigger `yagni`),
 [`testing.md`](../devrites-lib/reference/standards/testing.md), [`spec-grammar.md`](../devrites-lib/reference/standards/spec-grammar.md), [`performance.md`](../devrites-lib/reference/standards/performance.md), [`error-handling.md`](../devrites-lib/reference/standards/error-handling.md),
 [`development-workflow.md`](../devrites-lib/reference/standards/development-workflow.md), [`afk-hitl.md`](../devrites-lib/reference/standards/afk-hitl.md), [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md),
 [`developer-experience.md`](../devrites-lib/reference/standards/developer-experience.md), [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md), and [`definition-of-done.md`](../devrites-lib/reference/standards/definition-of-done.md). Load
 repository topology, data integrity, and integration reliability only when
-triggered. Before classifying any Reslice, read `.claude/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+triggered. When the plan's scope generalizes an existing boundary — a second
+platform/tenant/source of truth, a newly optional field, a constant turned parameter —
+confirm the [`assumption-checkpoints.md`](../devrites-lib/reference/standards/assumption-checkpoints.md) question (trigger `assumption-delta`)
+was answered and recorded, not skipped-as-negative.
+Before classifying any Reslice, read `.claude/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 When a
 plan declares a root-authored executable workflow file, read
 [`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md).
@@ -72,7 +80,8 @@ plan declares a root-authored executable workflow file, read
    recheck retains prior depth and enters 1b.
 1a. **Independent initial pass.** Freeze candidate and dispatch the exact fresh
    read-only plan reviewer — plus developer-experience reviewer for developer
-   surfaces and the current strategy reviewer after significant Temper — in
+   surfaces (trigger `devex`) and the current strategy reviewer after significant
+   Temper — in
    parallel under `../devrites-lib/reference/parallel-dispatch.md`; they are
    independent read-only passes on one frozen candidate. Missing
    required account blocks.
@@ -151,7 +160,18 @@ plan declares a root-authored executable workflow file, read
    assumptions, uncertainty, and gates. Keep state non-READY. Every scenario and
    criterion needs positive, discriminating proof; every slice must be one-pass
    implementable; developer plans need a predicted scorecard. Durable commands
-   are portable repository commands, not host wrappers.
+   are portable repository commands, not host wrappers — resolve them with
+   `devrites-engine detect commands` (Makefile/package.json/manifests, no
+   execution) and cite the resolved text verbatim; an `unresolved` slot means
+   name the concrete command in the plan, never guess one.
+   Once the `## Build-entry preflight` table is final, run
+   `devrites-engine gates scaffold <slug>` to seed `gates.md` (one pending gate
+   per `AC-###`; never clobber an existing ledger), then author each gate's
+   `CHECK`/`EXPECT`/`CWD` per artifacts.md §`gates.md` so every runnable oracle
+   is an approved preflight row. Run
+   `devrites-engine gates lint <slug> --strict` and resolve every finding before
+   READY; the readiness check refuses a missing or malformed ledger but does not
+   replace this oracle-quality gate.
 7. **Narrow recheck after edits.** Dispatch the exact plan reviewer once per
    fold — one dispatch covering every open fingerprint, preserving
    per correction/fingerprint accounting (each checked individually with its
@@ -171,8 +191,10 @@ plan declares a root-authored executable workflow file, read
    preflight, and sweep is green. Write phase/next step and emit one
    `Readiness inputs SHA-256` with
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
-   must pass. Technical failure records reproduction, not qid. Human gap awaits
-   Clarify. Optional cross-model follows `reference/cross-model.md`.
+   must pass. 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". Technical failure records reproduction, not qid. Human gap awaits
+   Clarify. Optional cross-model follows `reference/cross-model.md` (trigger `cross-model`).
 
    With READY, no pending remediation, and a valid technical return cursor,
    restore and consume the return cursor instead of defaulting to Build. Preserve

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

@@ -146,6 +146,25 @@ For every row in `plan.md`'s `Shared contract proof`, the per-gap requirements n
 provider- and consumer-side asserting tests and state how each consumes the same canonical
 artifact. Reference the plan row; do not reproduce its contract table here.
 
+## `gates.md`: the acceptance ledger
+
+Write `.devrites/work/<slug>/gates.md` once the preflight table is final —
+`devrites-engine gates scaffold <slug>` seeds one pending gate per `AC-###` in
+`spec.md`; never clobber a ledger that already carries evidence. Grammar,
+evidence binding, and oracle rules live in
+[`gates.md`](../../devrites-lib/reference/standards/gates.md); the engine
+enforces them, so author to the contract, not around it:
+
+- One gate per required outcome; reuse `AC-###` ids so readiness coverage and
+  the ledger name the same set.
+- A runnable gate's `CHECK` must be a `## Build-entry preflight` `Command`
+  verbatim with a matching `Cwd` — a gate whose command is absent from the
+  preflight table can never execute, so add the row first.
+- `EXPECT` names a line only success can print; `gates lint <slug>` flags
+  tautological commands and weak expectations before build.
+- Manual gates (`EVIDENCE` only) are for judgment-bound outcomes; Prove
+  attests them, Seal still requires them checked.
+
 ## Parallelization table (in `eng-review.md` §5 when there's an opportunity)
 
 ```markdown

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

@@ -75,6 +75,11 @@ presentation never caps the inventory or hides the ninth substantive defect.
 - Security architecture at the seams (auth, data access, API boundaries): does the plan name
   the trust boundary for each untrusted input?
 - One realistic production failure per new codepath/integration (feeds failure-mode table).
+- **Assumption delta:** when the plan or fresh evidence changes the *kind* of a spec
+  assumption (singular→plural, required→optional, chosen→derived, or back) that is an
+  identity-model change, not a detail. It needs an explicit promote-vs-add-alongside
+  decision routed through the Guard; silently widening the model in the plan is a
+  `broken` finding.
 - Does any key flow deserve an ASCII diagram in the plan or an inline comment in the code the
   build will write? Name the files that should carry one.
 

package/pack/generated/claude/skills/rite-watch-pr/SKILL.md

@@ -4,6 +4,8 @@ description: Observe one GitHub PR and CI state without mutating code, Git, thre
 argument-hint: "[PR number|PR URL|blank for current branch]"
 user-invocable: true
 ---
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/loop-operations.md"],"triggers":{"security":["devrites-lib/reference/standards/security.md"]},"workspace":[]} -->
+> Read-set manifest: `devrites-engine context [slug] --skill rite-watch-pr` bundles every file named below into one deduplicated read.
 
 # /rite-watch-pr: read-only PR and CI observation
 

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

@@ -5,6 +5,8 @@ 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"]} -->
+> Read-set manifest: `devrites-engine context [slug] --skill rite-zoom-out` bundles every file named below into one deduplicated read.
 
 # /rite-zoom-out: step up one abstraction layer
 

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

@@ -33,6 +33,10 @@ mirrors under `.agents/skills/devrites-lib/reference/standards/`. Apply the curr
 files, not a summary you remember.
 From `spec.md`'s applicability map, load only triggered [`repository-topology.md`](../skills/devrites-lib/reference/standards/repository-topology.md),
 [`data-integrity.md`](../skills/devrites-lib/reference/standards/data-integrity.md), or [`integration-reliability.md`](../skills/devrites-lib/reference/standards/integration-reliability.md); their cases remain feature-scoped.
+For per-file defect probes, load [`review/README.md`](../skills/devrites-lib/reference/standards/review/README.md):
+[`review/default.md`](../skills/devrites-lib/reference/standards/review/default.md) applies to every file, plus the language checklist matching
+each file's extension. A do-not-flag item raised as Critical/Important is a
+review defect — check that list before reporting.
 
 ## Inputs
 
@@ -72,10 +76,21 @@ for the feature scope and read the touched files.
     cast, or silent fallback that hides an unclear invariant?
   - Are repository/deployable roots, canonical contract and mutable-state ownership,
     shared resources, and sync/async consistency boundaries preserved without a cycle?
+  - Run `devrites-engine check dup <slug>` for near-duplicate leads, using the
+    mode that matches the packet's diff: `--base <ref>` when the feature's work
+    is committed, `--staged`/`--worktree` for uncommitted diffs. Triage each
+    reported cluster per
+    [`duplicate-code.md`](../skills/devrites-lib/reference/standards/duplicate-code.md)
+    — merge, keep-with-reason, or watch. A `*`-marked unit the diff added needs a
+    verdict, not suppression.
 - **Maintainability:** dead code, leftover TODOs or logs, and convention drift. Check
   **file size as well as diff size**. If a small diff pushes an already-large file
   past a healthy boundary, flag decompose-then-add and recommend extracting helpers
   or splitting modules first.
+- **Anchored notes:** when the workspace carries `notes.md`, run
+  `devrites-engine note list <slug>` and grade each anchor; a
+  `moved`/`stale`/`ambiguous`/`lost` note is a finding — the rationale it carries
+  no longer matches the code it names.
 - **Standards:** conformance to the project's conventions and the DevRites rules
   (naming, error handling, security, git/commit hygiene where the diff touches them).
 - **Hand-offs:** when input/auth/data/integration or a hot path/budget is in scope, flag
@@ -127,6 +142,7 @@ Return the report in this shape:
 Code review (<slug>) — independent
 Outcome: <findings | no-findings | gap>
 Account: <admitted findings | No-findings | Gap per Result admission>
+Coverage: <files read fully | hunk-level | skipped: name — reason>
 Finding: <severity> | <file:line> | <observed> | <impact> | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 Tests: <adequate? gaps>

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

@@ -78,6 +78,28 @@ Explicitly trace authn versus per-resource authz, tenant scope across storage/ca
 jobs/model context, privilege-changing actions, resolved filesystem/archive paths, request
 forgery control, unsafe deserialization, and fail-closed environment defaults when relevant.
 
+## Verification discipline
+
+- Enumerate the diff's security-relevant units before judging: endpoints, handlers,
+  trust boundaries, auth paths, deserialization sinks, and touched files. Audit each
+  and report audited-vs-total; unchecked units are a declared gap, never coverage by
+  omission.
+- Try to disprove every candidate before reporting it: re-check the cited site for
+  validation, authorization, escaping, or an existing guard that already neutralizes
+  it. A candidate that survives disproof is a finding; an unresolved fact names the
+  exact unknown (no severity claim); a disproved candidate stays visible as rejected
+  with the disproof, per [`agents.md`](../skills/devrites-lib/reference/standards/agents.md) § Result admission.
+- **Severity is capped at demonstrated impact in this codebase.** A candidate that
+  names principal, input, boundary, and observed crossing earns Critical; one that
+  weakens but does not defeat an explicit control caps at Important; a pattern
+  match with no shown crossing is Suggestion/FYI at most. "Best practice says so"
+  without a demonstrated boundary crossing is not a finding.
+- When scope is a surface larger than this diff — a subsystem, protocol surface, or
+  repo sweep — apply `.agents/skills/devrites-lib/reference/standards/audit-coverage.md`
+  (`.agents/skills/` mirror on Codex): coverage ledger, finder≠verifier, three-verdict
+  records, honest `deferred`/`blocked`. A unit never audited is a declared gap, not
+  coverage.
+
 ## Rules
 
 - Don't edit. Findings only, labeled Critical / Important / Suggestion / Nit / FYI with

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

@@ -39,7 +39,11 @@ files.
   points without removing them. Skip code that is already simple.
 - **Behavior-preserving only.** Observable behavior must stay identical and tests
   must remain green. Report any behavior-changing proposal separately because it is
-  not simplification.
+  not simplification. Green tests alone do not prove equivalence: inspect
+  observable representation, prototypes and key behavior, order, aliasing and
+  mutation, synchronous throws versus promise rejections and timing, and resource
+  lifetime where the proposed transformation touches them. Name the preserving
+  evidence or the unresolved edge case.
 - **Chesterton's Fence.** Explain *why* something exists before recommending its
   removal. If you cannot, flag "needs author intent" instead. A line that looks
   "useless" may protect a real edge case.
@@ -66,7 +70,13 @@ files.
 - **Simplify conditionals:** replace a long `if` and `else` chain with a switch,
   lookup table, or map, or split a complex boolean into well-named parts.
 - **Dedupe:** remove duplication, inline single-use indirection, or replace a
-  hand-rolled utility with the standard library or an existing helper.
+  hand-rolled utility with the standard library or an existing helper. Run
+  `devrites-engine check dup <slug>` for near-duplicate leads that survive
+  renaming — `--base <ref>`/`--worktree` matching the packet's diff, or `--all`
+  when the packet asks for a repo-wide pass. Read both units before proposing a
+  merge — convergent code is a keep, not a dedupe. Report each actionable
+  cluster with its hash per
+  [`duplicate-code.md`](../skills/devrites-lib/reference/standards/duplicate-code.md).
 - **Delete dead code:** remove only unreachable code added by this feature.
 
 ## Output

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

@@ -3,6 +3,8 @@ 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"]} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-api-interface` 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,6 +4,8 @@ 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"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-audit` bundles every file named below into one deduplicated read.
 
 # devrites-audit: read-only audit dispatch
 
@@ -21,6 +23,13 @@ decides how to use the report; this skill never edits.
 If no axis is supplied, infer only when intent is unambiguous; otherwise the root asks
 the human before dispatch.
 
+When scope is a surface larger than the feature diff — subsystem, protocol surface,
+repo sweep — apply [`audit-coverage.md`](../devrites-lib/reference/standards/audit-coverage.md)
+(trigger `audit-coverage`). When the audit calls for a whole-codebase structural
+score and a code index is present, apply
+[`architecture-health.md`](../devrites-lib/reference/standards/architecture-health.md)
+(trigger `architecture-health`).
+
 ## Gather and dispatch
 
 1. Resolve `.devrites/ACTIVE`; require `spec.md` and `touched-files.md`.

package/pack/generated/codex/skills/devrites-browser-proof/SKILL.md

@@ -3,6 +3,8 @@ name: devrites-browser-proof
 description: Observe and prove working UI behavior in a real browser with screenshots, interactions, network evidence, and Core Web Vitals. Use for browser proof or performance after the page works.
 user-invocable: false
 ---
+<!-- loads: {"always":["devrites-browser-proof/reference/browser-performance.md","devrites-browser-proof/reference/visual-verdict.md","devrites-frontend-craft/reference/quality-standards.md"],"triggers":{"security":["devrites-lib/reference/standards/security.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-browser-proof` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # devrites-browser-proof: runtime evidence for UI
 

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

@@ -4,6 +4,8 @@ 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"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-debug-recovery` 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,6 +3,8 @@ 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"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-doubt` bundles every file named below into one deduplicated read.
 
 # devrites-doubt: CLAIM → EXTRACT → DOUBT → RECONCILE → STOP
 

package/pack/generated/codex/skills/devrites-frontend-craft/SKILL.md

@@ -3,6 +3,8 @@ name: devrites-frontend-craft
 description: Build accessible production UI and all states during $rite-build. Use for frontend or design-system implementation; not for polish or design exploration.
 user-invocable: false
 ---
+<!-- loads: {"always":["devrites-frontend-craft/reference/craft.md","devrites-frontend-craft/reference/design-references.md","devrites-frontend-craft/reference/quality-standards.md","devrites-frontend-craft/reference/reuse-first.md","devrites-frontend-craft/reference/shape.md","rite-polish/reference/anti-ai-slop.md"],"triggers":{"fullstack":["devrites-frontend-craft/reference/fullstack.md"],"testing":["devrites-lib/reference/standards/testing.md"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-frontend-craft` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # devrites-frontend-craft: UI like a senior designer-engineer
 

package/pack/generated/codex/skills/devrites-frontend-craft/reference/design-references.md

@@ -86,6 +86,10 @@ the probe *chose* a lane; here you *match* the chosen target.
   focus, loading, empty, error: design those from the brief, the reference won't have them).
 
 Then implement to match, in the project's system:
+- **Match to measurable tolerance, not vibes.** Spacing and sizes land within ~10% of
+  the reference or on the nearest 4 pt step; radius within ±2 px; shadow blur/spread
+  within ~20%; color binds to the nearest existing token. Deviations are recorded in
+  the brief, not absorbed silently.
 - **Match the target, fill the gaps from the brief.** A static reference shows one state;
   ship the full state set (see `quality-standards.md`, "Focus & states").
 - **A reference that conflicts with the design system is a question for the user**, not a

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

@@ -13,6 +13,11 @@ these and write the brief per `../../devrites-ux-shape/reference/brief-template.
 return through `$rite-vet` before code.
 
 ## Answer these before writing markup
+0. **Surface intent:** is this a communication surface (a *site*: persuasion,
+   information, one message per section) or a task surface (an *app*: flows,
+   state, density)? Never ship one dressed as the other — a task tool built like
+   a landing page fails its user, and a marketing page built like a dashboard
+   fails its message.
 1. **User goal:** what is the user here to accomplish? One sentence.
 2. **Primary action:** the single most important thing on this surface. It must be
    visually obvious. Everything else is secondary.

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

@@ -3,6 +3,8 @@ 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"]} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-interview` bundles every file named below into one deduplicated read.
 
 # devrites-interview: extract intent
 
@@ -17,6 +19,9 @@ spec, plan, or code.
   > "I recommend CSV only because it covers the use case. Choose CSV, CSV + XLSX,
   > or something else?"
   This is a concrete candidate for the user's decision, not an assumption or confirmation.
+- **Ask in a full sentence that names the decision and why it changes the
+  build** — "Which export formats must v1 ship? Each adds a writer and a proof."
+  — never a bare label ("Formats?") or a context-free "any preference?"
 - **Highest-value question first:** order by how much the answer changes the build. A
   question that moves the data model or acceptance criteria beats a cosmetic one.
 - **Prioritize impact and bound each pass.** Order unknowns **scope > security/privacy > UX >

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

@@ -44,11 +44,46 @@ lifecycle state from chat or optional `README.md`.
 
 The engine is limited to:
 
-- `check readiness` for structure, `check candidate` for content-bound identity,
-  and `check seal` for structure plus exact artifact bindings; `secret-scan` and
-  `version` remain read-only helpers.
-- Atomic state: `state resolve` for answer/drop/batch and transactional
-  `state close`.
+- Checks: `check candidate` (content-bound identity), `check readiness`
+  (structure; `--emit-binding` emits the Build-input binding), `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).
+- 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
+  skill's `loads:` manifest into `.devrites/work/<slug>/ctx/` — dispatch targets
+  read it instead of selecting files. It prints `unselected=[...]` for declared
+  triggers not passed; an omitted applicable trigger is a gap, not a shortcut. A
+  `--role` call is a dispatch, so the `agents` trigger auto-fires when declared
+  (`auto=[agents]` in output); a role with no agent contract file fails instead
+  of emitting a contract-less packet.
+  Manifest grammar: `always` loads every call; `triggers` maps names to files that
+  load only when passed or suggested; `workspace` lists the feature artifacts every
+  reader may need; `workspaceByRole` maps a dispatch role to its own artifact list —
+  present role wins, absent role falls back to `workspace`, an empty list means the
+  role reads no workspace files. The engine prints `suggested=[...]` triggers
+  inferred from workspace facts (AFK/parallel flags, frontend/security wording,
+  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;
+  `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
+  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 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
   acquire the candidate bundle, source, and binary before invoking the engine.
 

package/pack/generated/codex/skills/devrites-lib/reference/candidate-integrity.md

@@ -28,12 +28,29 @@ current authority. Required feature proof cannot substitute slice results.
 Same-candidate accounts may be cited when permitted. Corrections require
 new candidate checks, affected real proof and fresh affected exact reviewers for
 all open findings and dependency/regression closure, including newly triggered roles.
+After an all-met acceptance ledger has been executed, any candidate digest change
+requires `devrites-engine gates reverify <slug>` against the corrected frozen
+candidate before refreshed evidence or review bindings are written; ordinary
+`gates run` skips already-met rows and cannot refresh them.
 Changed contracts or uncertain closure require a full applicable pass.
 Unchanged sub-scope needs explicit unchanged-input/dependency justification and a
 link to original evidence. Never relabel an old candidate-bound account.
 Keep one current aggregate binding; never copy a historical binding line, even quoted. Root reconciles complete coverage and binds
 it anew. Missing coverage blocks; required roles, criteria, proof and authority remain.
 
+## Resume validation
+
+On resume — compaction, new session, reopened workspace — recorded evidence is
+a claim, not a fact. Before reusing any of it, compare the ledger's candidate
+digest, contract version, environment, gate/fingerprint counters, and coverage
+inventory against the live workspace. Rows whose dependencies changed or cannot
+be bounded invalidate; rows that provably still apply are cited as reuse with
+their original observation. Counters survive session restarts and version
+bumps — a renamed file or a fresh context never resets a spent attempt. See
+[`standards/verification-methods.md`](standards/verification-methods.md) for the
+status (`fresh`/`reused`/`failed`/`missing`/`blocked`) and result
+(`pass`/`fail`/`unverified`) vocabulary coverage rows carry.
+
 ## Existing workspaces
 
 Upgrade routes a released-workspace candidate defect to Prove with a cited

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

@@ -17,6 +17,26 @@ ownership, relaxes a gate, or authorizes an irreversible action. Missing or
 incompatible exact roles stop for HITL; the root never substitutes a generic
 agent or performs the specialist's work inline.
 
+## Recorded route
+
+The decision is durable, not re-derived each phase: `brief.md` carries a
+`## Route` block (`Size`, `Profile`, `Why`) written by whichever rite first
+classified the change — `$rite-quick`'s significance gate or `$rite-spec` step
+5. Later phases read the recorded profile instead of re-judging size.
+
+| Recorded | Mapping |
+|---|---|
+| `small` + reversible + unambiguous | **Quick** — `$rite-quick` lane; the significance gate still escalates to Standard on auth, migration, public API, destructive, multi-slice, or ambiguous signals. |
+| `standard` (default) | **Standard** — the full required lifecycle. |
+| `large` or any high-stakes signal (security, migration, public contracts, high blast radius, explicit `--full`) | **Full**. |
+
+Route changes are one-directional without a recorded reason: any phase may
+escalate a profile when a significance signal appears; a downgrade needs an
+explicit recorded `Why` revision through the Spec Drift Guard. A recorded
+profile compresses artifact depth and reviewer breadth per the profile table —
+it never removes a named specialist, a required artifact, a gate, or an
+evidence binding.
+
 A child result is a claim. Admit it only against observations (`git diff
 --name-only`, recorded commands, artifact existence) — never against the
 child's prose. **Failing case:** a wright reports "done" and the parent

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

@@ -33,21 +33,42 @@ If the candidate diff has no matching surfaces, record
    inherited history/memory/sibling summaries. Use supported clean-context settings;
    unverified independence is a gap. Do not launch a probe agent per task;
    still validate each result's context and candidate.
-2. Ask for each exact named agent in fresh context; omit native syntax and
+2. Build each reviewer's read-set once with
+   `devrites-engine context <slug> --phase <p> --role <role> --trigger <set>` and
+   hand the bundle path as the packet's source list instead of a file roster.
+   Evaluate the skill's trigger conditions and pass each that fires — a role's
+   Trigger column maps to manifest names: `security-auditor` → `security`,
+   `frontend-reviewer` → `ui`/`frontend`, `performance-reviewer` → `performance`.
+   The `agents` dispatch contract needs no flag: `--role` auto-fires it
+   (`auto=[agents]` in the output). The command prints `unselected=[...]`; an
+   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>...`),
+   launch every native agent nonblocking, 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
+   serial launch-then-wait pattern impossible to record. Record each completion
+   with `dispatch ... return`; `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
+   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.
-3. Every dispatch reaches a terminal classification before reconciliation:
+5. Every dispatch reaches a terminal classification before reconciliation:
    `Outcome: findings`, `Outcome: no-findings`, `Outcome: gap`, or
    `unavailable: <reason>` when the step could not run at all. Reconciling over a
    partial roster is forbidden; an unavailable conditional step is recorded with its
    marker in `review.md`/`seal.md` — an omitted sub-step reads as a clean run.
    Findings later withdrawn at reconciliation stay visible: the account records
    `withdrawn: <n> (<reason>)` rather than silently dropping them.
-4. Apply [[`agents.md`](standards/agents.md) § Result admission](standards/agents.md#result-admission)
+6. Apply [[`agents.md`](standards/agents.md) § Result admission](standards/agents.md#result-admission)
    and dedupe by evidence/root cause. Account for all seven in
    `review.md`/`seal.md`: `Outcome:` plus admitted account, or
    `Not-applicable: <inspected-scope reason>`. Spec/Code may cite valid unchanged
    `review.md` under [evidence validity](candidate-integrity.md#evidence-validity); persist no dispatch telemetry.
-5. Missing profile, null/failure, or malformed output is a `gap`; never
+7. Missing profile, null/failure, or malformed output is a `gap`; never
    infer approval or substitute inline review.
 
 On exhaustion/contention: stop spawning; collect running results; batch/serialize.
@@ -55,6 +76,17 @@ Never restart/orphan the cohort or infer approval. Reviewers are read-only;
 accounts store evidence, never telemetry. Same-file writers stay serial.
 Capacity rejection is backpressure: retry batches; never shrink a roster.
 
+## Cancellation and terminal reconciliation
+
+Cancellation acknowledgement means the host accepted a request, not that the
+child stopped. A transport timeout likewise leaves execution unknown. Keep the
+child's handle, path/resource ownership and capacity reservation until the
+native host confirms a terminal state and returned work has been reconciled.
+Query or wait on that handle; do not replace the child, release its slot, or
+reuse its resources while it may still run. If terminal state cannot be
+established, record a gap and retain ownership. A result classification alone
+does not prove host termination.
+
 ## Scale limits
 
 The role table bounds rosters. Use roughly four concurrent read-only reviewers;

package/pack/generated/codex/skills/devrites-lib/reference/reply-contract.md

@@ -21,6 +21,27 @@ Next: <one recommended action>
 Record: <primary durable artifact path>
 ```
 
+`Changed:` is the complete write set, not a highlight reel: every file written
+or edited this turn — workspace artifact and project source alike — appears
+there or inside one named grouped entry, so a reviewer can `git diff` exactly
+those paths. `Record:` then names the single durable artifact a later session
+reads first.
+
+Mid-flight replies — the turns between completion states — obey the same economy:
+
+- **Restate position.** The reader cannot hold "step 3 of 5" between turns; name it
+  (`step N of M` / `state: <where things stand>`) rather than asking them to remember.
+- **One next action, doable now.** `Next:` names one concrete action completable in
+  under two minutes — a command, a file to open, a yes/no decision. "Want me to
+  continue?" is a stall, not an action.
+- **Numbered steps for multi-step work**, one bounded action each; fold trivial steps
+  into the one before. A short path finished beats a complete path abandoned.
+- **Name the win before the remainder.** A landed slice, a green gate, a merged
+  piece is stated first — visible progress beats an undifferentiated list.
+- **Cap enumerations.** Long lists collapse to a few grouped items with counts;
+  the full enumeration lives in the durable artifact, not the reply.
+- **Errors are matter-of-fact** — cause and fix, never alarm noise.
+
 Pre-send check: delete an opening sentence that only announces ("I'll now…") and a
 closing sentence that only recaps; then apply the two-line test — a reader seeing only
 the first and last lines must know what happened and what to do next.
@@ -66,7 +87,9 @@ Record: .devrites/archive/<slug>/ship.md
 ```
 
 Claims such as proved, reviewed, sealed, shipped, or complete must point to real
-output or an artifact. Use exactly one recommended next action except for
+output or an artifact. An expected verification that was skipped, unavailable, or
+could not start is named in `Evidence:` or `Open:` — omitting it reads as
+ran-and-green. Use exactly one recommended next action except for
 terminal agent-owned technical exhaustion, which has no runnable action.
 
 Use that terminal case only per [`one-shot-actions.md`](standards/one-shot-actions.md):

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

@@ -16,8 +16,12 @@ topic's owner.
 | `prose-style.md` | Writing prose artifacts or user replies. |
 | `error-handling.md` | Adding or reviewing failure paths. |
 | `testing.md` | Designing tests or judging proof quality. |
+| `gates.md` | Authoring, executing, or judging the `gates.md` acceptance ledger — runnable oracles, evidence binding, ABANDON handoffs. |
+| `verification-methods.md` | Choosing checks and counting coverage — method distinctness, the unit×check×environment denominator, status vs result, capability fallbacks, recipient-path execution. |
 | `spec-grammar.md` | Structuring high-risk behavioral requirements or capability deltas. |
 | `code-review.md` | Reviewing a change or sealing review findings. |
+| `review/README.md` | A diff touches source files — per-language defect-probe checklists (always with `code-review.md`). |
+| `duplicate-code.md` | Triage of near-duplicate clusters, the `check dup` scan, or the dup ignore ledger. |
 | `edge-case-trace.md` | Resolving relevant edge/prohibition classes and their evidence disposition. |
 | `security.md` | Handling input, auth, data, secrets, dependencies, or integrations. |
 | `repository-topology.md` | Work spans a monorepo member, nested root, multiple languages/services, or repositories. |
@@ -27,6 +31,7 @@ topic's owner.
 | `observability.md` | A changed runtime path must be diagnosed in production. |
 | `developer-experience.md` | A public API, CLI, SDK, webhook, config, error, or getting-started surface changes. |
 | `patterns.md` | Choosing or simplifying architecture. |
+| `architecture-health.md` | An audit needs a structural read on the whole codebase — coupling/cohesion/cycle score from a dependency index. |
 | `git-workflow.md` | Preparing commits, branches, tags, or changelog entries. |
 | `hooks.md` | Creating or changing repository hooks. |
 | `ci-cd.md` | Creating or changing a build/deploy pipeline. |
@@ -51,7 +56,12 @@ topic's owner.
 | `browser-proof-checklist.md` | UI behavior needs browser proof. |
 | `security-checklist.md` | Auth, input, data, or integration work needs a compact security sweep. |
 | `acceptance-preserving-reslice.md` | Classifying or reviewing a Reslice in Plan, Vet, or Autocomplete. |
+| `audit-coverage.md` | An audit covers a surface larger than one feature diff — ledger, hunter/critic waves, three-verdict findings. |
+| `architecture-health.md` | An audit needs a whole-codebase structural score from a code index — coupling, cohesion, cycles, god files, orphans, depth. |
+| `assumption-checkpoints.md` | Scope generalizes an existing boundary: a second case, a newly optional field, or a constant turned parameter. |
 | `debug-recovery.md` | Waiting on async readiness (server start, job completion, browser signal) needs a bounded condition-based poll. |
+| `windows.md` | A deferral marker (TODO/FIXME/skipped test/stub) is introduced or waived — the `check windows` ledger and grammar. |
+| `glossary.md` | A DevRites term is unclear; resolve it once here instead of inferring. |
 
 The table is a load trigger, not an exemption. [`core.md` § Rule summary](core.md#rule-summary-load-the-full-file-when-in-scope)
 makes every *applicable* owner mandatory. **Failing case:** a security or data-integrity