devrites 5.10.2 → 5.12.0

package/pack/generated/codex/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md

@@ -1,4 +1,6 @@
 # Acceptance-preserving Reslice
+> Applies when: before classifying or executing any reslice/split/reorder of an approved plan.
+
 ## Packet
 Exactly six groups;one slug/attempt;exact unordered keys
 <!-- BEGIN RESLICE PACKET -->

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

@@ -1,5 +1,7 @@
 # AFK & HITL: the pause/resume contract
 
+> Applies when: any rite/devrites skill that can pause for a human or run unattended; irreversible-risk list, budgets, recovery accounting.
+
 Defines two modes for `rite-*`/`devrites-*` skills that may pause; main
 callers are `$rite-build`, `$rite-status`, `$rite-resolve`, and
 `devrites-doubt`.

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

@@ -1,5 +1,7 @@
 # Agent orchestration
 
+> Applies when: dispatching or admitting any devrites-* role; the source-writing boundary.
+
 Follow DevRites policy and [`depth profiles`](../orchestration-profiles.md).
 
 ## Authority
@@ -38,6 +40,12 @@ Files own briefs; [`parallel-dispatch.md`](../parallel-dispatch.md) owns rosters
 Skills name exact fresh roles, omit native fields;
 hosts spawn/wait/deliver. Root MUST NOT advance/claim completion before admitting required results;
 running/orphaned/unavailable = `gap` — no root/generic substitute.
+Where a feature workspace exists, every fresh dispatch to a named `devrites-*`
+role — wave or solo — builds its read-set with `devrites-engine context <slug>
+--phase <p> --role <role>` and tracks the launch through `devrites-engine
+dispatch <slug> open|start|seal|return` (a solo dispatch is a wave of one;
+start/return auto-record metrics). Without a workspace the plain host dispatch
+contract above applies and no engine tracking is required.
 Workflow-named skills (e.g. devrites-source-driven) are invoked inline in the root context, never dispatched as agents.
 
 ## Source-writing boundary
@@ -48,9 +56,21 @@ Isolated-worktree pilot only under [`wright-dispatch.md`](../../../rite-build/re
 
 Each job gets objective/exclusions, exact paths/immutable candidate, rubric/result shape, a **stop condition** (when to return), and the exact result shape; a dispatch missing them is malformed and re-issued. Briefs MUST NOT seed verdict/severity cap/conclusion/suppression. Results state status/scope, outcome, commands/escalation; wright adds paths, changed files, gates, stood decisions; results never widen scope.
 
+**Same-tree concurrent sessions claim first.** Worktree dispatch isolates
+parallel batch siblings, but two agent *sessions* (two hosts, two features, or
+a human plus an agent) can share one working tree. Before a same-tree writer
+starts, it records an advisory claim — `devrites-engine claim add --session
+<id> <paths>` — retains the returned `<claim-id>`, then checks the same paths
+with `devrites-engine claim check --session <id> <paths>`; a held claim from a
+live foreign session is a stop-and-report, not a merge-later problem. On every
+terminal path after `add` — success, gap, stop, or launch failure — run
+`devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
+by TTL only as crash recovery; `claim list` shows who holds what. Claims are
+advisory coordination, never a substitute for the one-writer-per-worktree rule.
+
 ## Independence
 
-- A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, or edited context; seeding voids the packet.
+- A fresh result sees scope/paths-diff/rubric only — never another result's or the root's conclusions, severities, expected verdicts, chosen verification methods, or edited context; seeding voids the packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is $rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

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

@@ -1,5 +1,7 @@
 # DevRites: universal anti-patterns
 
+> Applies when: universal rationalizations; load when tempted to shortcut any standard.
+
 The pack-wide rationalizations the agent reaches for when discipline gets in
 the way. Apply at every phase. Each `rite-*/reference/anti-patterns.md`
 extends this with phase-specific items.

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

@@ -0,0 +1,64 @@
+# Architecture health
+
+> Applies when: an audit, vet, or seal needs a structural read on the whole
+> codebase — not the diff — and a dependency index is available.
+
+A health score compresses six structural signals into one 0–100 number with a
+letter grade. It is an *audit instrument*, not a gate: it ranks surfaces for
+attention and tracks drift between milestones. It never proves a change safe
+and never substitutes for review.
+
+## When to measure
+
+Compute a score only when a code index covers the repo (see
+[`code-navigation.md`](code-navigation.md) § Index freshness). With no index,
+report `unmeasured` — a placeholder number presented as a measurement is a
+false pass. **Failing case:** an audit reports "health: 100/100" on a repo the
+instrument could not parse.
+
+## Dimensions
+
+Weight the dimensions exactly once; do not invent extra dimensions ad hoc —
+record repo-specific signals as findings instead.
+
+| Dimension | Weight | What it measures | Healthy | Warning |
+| --- | --- | --- | --- | --- |
+| Coupling | 25% | Cross-file edges per file; penalize god-file outliers (max ≫ 3× mean) and >70% cross-directory share | avg ≤3 connections | avg >10 |
+| Cohesion | 20% | Share of a directory's edges that stay inside it | ≥70% internal | <30% |
+| Circular deps | 20% | File-level dependency cycles per 100 files | 0 cycles | >5 per 100 |
+| God files | 15% | Files with >3× mean connections | none | >6% of files |
+| Orphans & dead exports | 10% | Unreferenced files; exported symbols with zero dependents (60/40 blend) | 0% orphans | >10% orphans or >5% dead exports |
+| Depth | 10% | Longest dependency chain, cycles collapsed to one hop each (SCC-condensed DAG) | ≤4 levels | >8 |
+
+Grade bands: ≥90 A · ≥80 B · ≥70 C · ≥60 D · below F.
+
+## Rules
+
+- **Measure before and after.** A score's value is the delta: record
+  before/after for structural work in `evidence.md`; a drop >3 points needs a
+  named cause, not a shrug.
+- **Count runtime edges, not type-only edges.** `import type`-style
+  relationships inform dead-code analysis but do not execute; including them
+  overstates coupling.
+- **Exclude fixtures and generated files** from orphan/dead counts — a
+  directory of test fixtures is not dead code.
+- **Depth is computed on the condensed graph.** Collapse each cycle (strongly
+  connected component) to one node first; an exact longest-path search on a
+  cyclic graph is unbounded and returns no honest number.
+- **Every recommendation names the dimension it moves.** "Improve the
+  architecture" is not an action; "extract `x/` → `y/` edge to cut cross-dir
+  coupling (Coupling, est. +8)" is.
+- **Trend over snapshots.** Keep the score per milestone in `evidence.md` or
+  the feature's audit artifact; a single reading without a baseline is a
+  weather report, not a climate signal.
+
+## Orphan and dead-export semantics
+
+An orphan file has zero cross-file runtime edges. A dead export is an exported
+top-level symbol (function/class/interface/type/enum/constant) with zero
+incoming edges — member-level symbols (methods, properties) are excluded:
+they are not meaningful architecture-level candidates and produce false
+positives. Both counts feed only this dimension; the *removal decision* for a
+dead export follows [`deprecation.md`](deprecation.md), including its
+confidence rubric — a low-confidence dead lead is a watch item, never an
+automatic deletion.

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

@@ -0,0 +1,42 @@
+# Assumption-delta checkpoints
+
+> Applies when: planning or vetting a slice whose scope generalizes an existing
+> boundary — the seam where a quiet assumption loses its monopoly.
+
+Most quietly imported architectural debt comes from the seam: a later change adds a
+*second case* — platform, auth method, tenant, region, source of truth — and nobody
+re-asks whether the original abstraction still names the right thing. The change that
+adds the second case is the cheap moment to ask.
+
+## The detector
+
+Scan the phase scope, spec delta, or task list for transition signals:
+
+| Signal | Shape | The question it raises |
+|---|---|---|
+| `pluralization` | A second X where exactly one existed (platform, provider, tenant, region, source of truth) | Does the identity model still name the right noun? |
+| `optionality` | A required or `only`-assumed field becomes optional | Is that field still the right anchor, or did the anchor move? |
+| `choice` | A derived value becomes chosen; a constant becomes a parameter | Has a config decision silently become a modeling decision? |
+
+Code blocks, comments, and prose that merely *mention* a trigger word do not count.
+
+## Firing the checkpoint
+
+A firing signal surfaces **one** question before the plan is finalized — not a
+redesign, one question: *does the name/model chosen when N=1 still hold at N=2?*
+
+- `detected:false` — skip the checkpoint; do not raise it.
+- `skipped` — the scope was never examined. A skipped check asserts *nothing*: never
+  record "no assumption changed" from a skipped result; skipped ≠ negative.
+- `detected:true` — ask the one question and record the answer in `decisions.md` or
+  `assumptions.md`; an answered checkpoint that leaves no trace re-fires next round.
+
+## Promote, don't add alongside
+
+When a generalization is real, the default-correct move is to **promote** the general
+representation to primary and demote the old specific one to a detail of one variant —
+not to add the new shape alongside the still-required old one, which silently
+contradicts the generalized intent.
+
+**Failing case:** `region` added as an optional column beside `primaryRegion`; every
+write now guesses which is authoritative.

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

@@ -0,0 +1,103 @@
+# Coverage-led auditing
+
+> Applies when: auditing a surface larger than one feature diff — a repo, subsystem,
+> or trust boundary — where "I looked at it" must become countable coverage.
+
+A surface audit must answer *what the run covered and what it never examined* — with
+a coverage ledger, not a summary paragraph.
+
+## Coverage ledger
+
+The coordinator alone maintains the ledger; a unit is one auditable cell — surface
+(path/endpoint/command) × trust boundary × check class.
+
+States: `planned` → `assigned` → `candidate` (produced a finding candidate) →
+`covered` (evidence recorded); plus `deferred` (postponed, reason recorded),
+`blocked` (exact blocker recorded), and `out_of_scope` (declared-scope exclusion —
+never written as `covered`). `deferred` and `blocked` are honest states; a unit
+silently dropped is a lie.
+
+Instruments obey the same honesty rule: a scanner or metric that could not read
+its target reports `unmeasured`/`no_data`, never a placeholder presented as a
+measurement. A health score computed over zero parseable files is not a 100.
+When the audit covers whole-repo structure, score it per
+[`architecture-health.md`](architecture-health.md) and record before/after
+deltas as ledger evidence.
+
+## Findings carry three verdicts, not two
+
+- **`confirmed`** — complete source trace plus a bounded observed or owner-observable
+  result; names the lower-trust principal, crossed boundary, affected
+  principal/resource, and concrete effect.
+- **`needs_validation`** — a real lead blocked on one exact unresolved fact, which is
+  named. Carries **no severity**: severity without established impact is theater.
+- **`rejected`** — a disproved candidate kept with its disproof; it suppresses
+  re-raising the same unchanged claim, never coverage of its unit.
+
+Hardening notes are not findings: if one layer already prevents the attack, the
+absent second layer is a depth observation, not a vulnerability.
+
+## Finder never verifies its own find
+
+Every surviving candidate goes to a fresh verifier that did not produce it and tries
+to **disprove** it, per [`agents.md`](agents.md) § Independence — a seeded packet
+voids the verification. Promotions to `confirmed` and material changes to root
+cause, trace, reproduction, impact, or severity require fresh independent
+verification. Without that independent evidence, keep the candidate unresolved;
+a rewritten explanation is not verification.
+
+## Critics between waves
+
+After each hunting wave, a **coverage critic** — a fresh agent comparing the ledger
+with targeted source and entry-point evidence — looks for holes: unseeded surfaces,
+boundaries with no check class,
+units stuck `assigned`, `rejected` patterns suggesting a hunter fires blanks.
+Accepted discoveries become `planned` units. Reserve critic and verifier capacity
+**before** spending on hunters; a wave launched with no verification reserve hunts
+for findings nobody may claim.
+
+## Re-runs are additive, never assumed
+
+A prior ledger must be re-checked against current source — a prior commit ref is not
+evidence a path is unchanged. Prior `confirmed` carries forward only when its source
+is unchanged **and** it re-passes current verification; prior `needs_validation` /
+`blocked` / `deferred` become current work and never suppress a unit. A partial prior
+run contributes recorded evidence and gaps, never an implied "the rest is fine"; no
+prior ledger → the report says so.
+
+## Profiles scale breadth, never the bar
+
+`quick` (one hunter wave + one critic pass, coarser units), `standard` (waves to
+critic-clean, per-candidate fresh verifier), `deep` (units split per
+subsystem/lifecycle; carried records re-verified). Profiles change granularity and
+redundancy, never the evidence bar: boundary-plus-result, independent verification,
+three verdicts, and honest `deferred`/`blocked` survive every profile. A scoped run
+presents itself as partial coverage.
+
+## Budget discipline
+
+A budget counts agent invocations, not effort. Reserve critic and verifier capacity
+before spending on hunters; a budget that cannot fund reconnaissance plus required
+reserves funds nothing — narrow scope or profile instead of silently thinning
+evidence. A run exhausted mid-verification ends `incomplete` with unvalidated
+candidates still linked to `candidate` units — never relabeled, never reported
+complete.
+
+## Target execution is sandboxed
+
+When a unit requires *running* the target — a build, a test, a probe — execute
+it under containment, never in the operator's ambient environment:
+
+- No external network and no live-service probing from the audit run.
+- No credentials, tokens, or secrets visible to target-controlled processes.
+- Only commands the repository or CI itself sanctions run verbatim; invented
+  commands are findings to propose, not actions to take.
+- Output captured through the harness, not through target-written files the
+  run then trusts.
+
+An audit that executed unaudited code with ambient privileges has crossed the
+boundary it was measuring; that run's `confirmed` rows name the execution
+context so reviewers can judge contamination.
+
+**Failing case:** "no critical findings" reported while 40% of units sit `planned` —
+the honest sentence was "60% of the surface was examined."

package/pack/generated/codex/skills/devrites-lib/reference/standards/browser-proof-checklist.md

@@ -1,5 +1,7 @@
 # Browser proof checklist
 
+> Applies when: UI proof: compact sweep before claiming a rendered/browser pass.
+
 Compact sweep only. Numbers and failing cases live in
 [`quality-standards.md`](../../../devrites-frontend-craft/reference/quality-standards.md)
 § Focus & states, § Responsive, and § Browser chrome — do not restate a shorter

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

@@ -1,5 +1,7 @@
 # CI/CD & automation
 
+> Applies when: creating or changing a build/deploy pipeline or CI config.
+
 Read this only when creating or changing a build/deploy pipeline. [`hooks.md`](hooks.md) owns local checks, [`development-workflow.md`](development-workflow.md) owns trunk health, and [`deprecation.md`](deprecation.md) owns migrations.
 
 ## Pipeline gates
@@ -14,6 +16,15 @@ Read the specific failure, fix its root cause, verify locally, then push again.
 
 A designated Build Cop (a human/team role, not a pack agent) owns restoring a broken trunk by fixing or reverting, whichever is faster. Restoring trunk outranks feature work.
 
+## Verification economy
+
+Paid or remote validation runs once per prepared state, not per attempt: batch repairs,
+verify locally first, and never blind-retry an infra operation that already reported
+failure (deploy, migrate, seed) — read the failure output, fix the cause, then re-run.
+A green check the diff cannot affect is not re-run; an expected run that is deliberately
+skipped is named in the report, not omitted. Capture failure output as an artifact so the
+next attempt starts from evidence, not memory.
+
 ## Deploy versus release
 
 Keep incomplete or risky behavior disabled behind a flag so deploy and release remain separate and rollback does not require a redeploy. Every flag has an owner and a removal trigger; remove it through the [`deprecation.md`](deprecation.md) expand/contract path.

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

@@ -1,5 +1,7 @@
 # Code navigation
 
+> Applies when: choosing structural search tools (code index vs grep) before exploring.
+
 Decision tree for structural questions. Load with [`tooling.md`](tooling.md);
 this file is the pack-canonical routing table agents cite in Build, Vet, and
 Review.
@@ -15,16 +17,61 @@ Review.
 | Rename, references, diagnostics | LSP (`lsp` rename/references) when available | graph trace + grep |
 | Known file, one-line fix | `Read` at offset/limit | — |
 | Literal string / config value | `Grep` | — |
+| Does a similar implementation already exist? | embedding/similarity tool when present | `search_graph` on purpose-words and name variants, then targeted `Read` |
 
 ## Before cross-file edits
 
 1. Run **one** primary route from the table (record tool + query in the artifact).
-2. Read symbol bodies you will change (`read_symbol` counts as read).
-3. After edits: LSP diagnostics + project tests.
+   **Compute the affected set before writing code, not after** — the blast-radius
+   list is the edit plan: every file on it is a touch or a conscious skip.
+2. Read symbol bodies you will change (`read_symbol` counts as read), comments
+   included — a why-comment is often the only record of a decision.
+3. After edits: LSP diagnostics + project tests. Compiler errors are the oracle
+   for callers the graph listed — fix them in dependency order, direct
+   dependents first. Errors absent from the list mean the list was incomplete
+   (see blind spots below); record the gap.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.
 
+## Query budget
+
+Spend the minimum that settles the question:
+
+- Minimal output first — pass the smallest detail/scope option a tool offers;
+  escalate to a fuller answer only when the minimal one cannot decide.
+- One structural question ≈ five index calls. The sixth means the question needs
+  re-scoping or a file read, not another query.
+- Stop at sufficiency: an index answer that names the symbols and their source
+  ends the search; re-verifying it with grep is waste, not diligence.
+
+## What the static graph cannot see
+
+Import/call edges are only the statically visible share of the dependency
+surface. A blast-radius answer that ignores the rest is a false negative
+factory:
+
+- **Cross-language edges:** HTTP/RPC call sites (`fetch("/api/…")` → the route
+  handler file), subprocess/CLI invocations, and queue topic names couple files
+  no import statement links. Grep the literal route/command/topic when a
+  producer or consumer file changes.
+- **Dynamic binding:** `import()`/dynamic `require`, reflection, string-keyed
+  DI/registries, plugin/extension loading, ORM model registration,
+  `require.context`-style glob imports. A symbol with zero static dependents
+  may be load-bearing at runtime.
+- **Co-change coupling:** files that change together in `git log` but share no
+  import edge are coupled by convention (paired configs, parallel
+  implementations, duplicated schemas). Before a structural edit, run
+  `git log --name-only` on the target file's recent history and treat repeat
+  companions as soft dependents.
+- **Type-only edges** (`import type`, generics-only references) inform impact
+  and dead-code reads but do not execute — do not count them as runtime
+  coupling (see [`architecture-health.md`](architecture-health.md)).
+
+The compiler and the test suite are the oracle for everything in this list:
+zero static dependents + zero compiler errors + green tests is evidence;
+zero static dependents alone is a hypothesis.
+
 ## Index freshness
 
 | Index path | Provider |
@@ -32,8 +79,28 @@ Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 | `.codegraph/` | CodeGraph |
 | `.code-review-graph/` | code-review-graph MCP |
 | `.codebase-memory/` | codebase-memory MCP |
-Run `devrites-engine check indexes` for a quick presence check. Stale or missing index:
-build/refresh per provider docs, or fall back to LSP + grep and note the gap.
+| `graph.json` | Graphify (`graphify query` / `graphify path A B`) |
+Run `devrites-engine check indexes` for a quick presence check. It detects
+**in-repo artifacts only** — codebase-memory may be indexed in the server's
+central store with no `.codebase-memory/` dir; when the MCP server answers
+(`list_projects`/`index_status`), trust it over the file probe. Stale or missing
+index: build/refresh per provider docs, or fall back to LSP + grep and note the gap.
+
+## Tool availability
+
+- On Claude hosts, provider tools arrive as `mcp__<server>__<tool>` — e.g.
+  `mcp__codegraph__codegraph_explore`, `mcp__code-review-graph__query_graph_tool`,
+  `mcp__codebase-memory-mcp__search_graph`. DevRites agent profiles and
+  `.claude/settings.json` already allowlist these servers; a server that is not
+  installed simply offers no tools — fall back per the table, no error path needed.
+- Server names are install-configured (`codebase-memory-mcp` and `codebase-memory`
+  are both allowlisted). If your server uses another name, add it to
+  `settings.json` allow and the agent `tools:` lines.
+- CodeGraph and Graphify also run as CLIs (`codegraph explore`,
+  `graphify query` / `graphify path A B`) — allowlisted via `Bash(...)` rules.
+- On non-Claude hosts the `mcp__*` entries are ignored by generation; use each
+  host's own nav extensions or the CLI forms. All listed tools are read-only
+  navigation — do not call index rebuild, refactor-apply, or mutation tools.
 
 ## Anti-patterns
 

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

@@ -1,5 +1,7 @@
 # Code review
 
+> Applies when: reviewing any diff for design clarity, logic, tests, risk.
+
 Ask whether the change improves or preserves design clarity, logic, tests, and risk.
 If it does not, do not merge it.
 
@@ -18,18 +20,47 @@ If it does not, do not merge it.
 ## What to check (tests first)
 1. **Tests:** do they exist and prove the behavior + failure modes (empty, error,
    boundary, concurrency)? Would they fail if the code were wrong? A `skip`/`only`/
-   `TODO` placeholder or assertion-free test is a finding, not coverage.
-2. **Correctness:** logic, edge cases, error paths, race conditions, wrong assumptions. For branching or boundary changes, run the [`edge-case trace`](edge-case-trace.md): relevant probe classes, fixed-set siblings, real wiring, negative intent, and deletion contracts with an evidence disposition.
-3. **Readability:** names, function size, control flow, intent obvious without the author.
-4. **Architecture:** right seam, coupling/cohesion, fits existing patterns, no premature
+   `TODO` placeholder or assertion-free test is a finding, not coverage. Account
+   for coverage per changed function, not per file: name the test that drives each
+   changed function, or list the function under `Missing tests:` — a file-level
+   "tests exist" over a diff whose riskiest function is unexercised is a gap.
+2. **Bar integrity:** sweep the diff for a lowered bar masquerading as a change:
+   new suppression comments (`@ts-ignore`, `eslint-disable`, `noqa`, `nolint`),
+   loosened thresholds (coverage floors, budgets, lint levels, timeout bumps with
+   no justification), stripped assertions, deleted or skipped tests, and new
+   unimplemented stubs or `throw`-only placeholders. Each names what it lowers and
+   needs a recorded reason in the diff or `decisions.md`; unexplained is a finding.
+3. **Correctness:** logic, edge cases, error paths, race conditions, wrong assumptions. For branching or boundary changes, run the [`edge-case trace`](edge-case-trace.md): relevant probe classes, fixed-set siblings, real wiring, negative intent, and deletion contracts with an evidence disposition.
+4. **Readability:** names, function size, control flow, intent obvious without the author.
+5. **Architecture:** right seam, coupling/cohesion, fits existing patterns, no premature
    abstraction. Check how it fits the larger system as well as its local behavior.
-5. **Security:** trust boundaries, input validation, authz, secrets.
-6. **Risk:** migrations, destructive changes, rollback.
-7. **Read depth matches risk:** the review's `Basis` names **full reads of the largest
+   Search for a **reimplemented-elsewhere** twin: a new function/module that
+   semantically duplicates an existing one (renamed, reshaped, or vendored) is an
+   architecture finding; reuse the canonical implementation or justify the fork.
+   Run `devrites-engine check dup` in the mode matching the diff (`--base <ref>`
+   for committed work, `--staged`/`--worktree` for uncommitted) for leads and
+   triage each cluster per [`duplicate-code.md`](duplicate-code.md).
+6. **Security:** trust boundaries, input validation, authz, secrets.
+7. **Risk:** migrations, destructive changes, rollback.
+8. **Read depth matches risk:** the review's `Basis` names **full reads of the largest
    diff files** (top three by changed lines), and any config/dependency/SQL/auth/migration
    file is read in full — never skimmed. A review that cannot name what it fully read is
    unproven. **Failing case:** a 600-line diff gets hunk-by-hunk commentary on the first
    screen and silence on the migration file at the bottom.
+9. **Every file in the review set gets its own pass.** Reviewing an implementation
+   file does not cover its header, interface, test, or config counterpart — being the
+   smaller member of a group is no reason to skip it. Findings attach to files inside
+   the review set, never outside it. Report the accounting: a `Coverage:` line names
+   the files reviewed in full, reviewed at hunk level, and explicitly skipped with
+   reason (generated, vendored, lockfile). Files named nowhere count as not reviewed.
+10. **Per-language probes.** For each file, apply [`review/README.md`](review/README.md):
+    `review/default.md` always, plus the checklist for the file's language. These are
+    defect probes with explicit do-not-flag lists — a do-not-flag item raised as
+    Critical/Important is a review defect, not a finding.
+11. **Large diffs get a risk pass.** When the diff exceeds the soft ceiling (~400
+    lines) or touches a migration, auth, dependency, or config file, run a second
+    focused pass over just those surfaces after the general pass — first-pass
+    attention decays with diff size and the risk-bearing file is usually last.
 
 ## Give actionable feedback
 - Read surrounding source before severity: call sites, existing guards, and the nearest consumer decide impact; a diff hunk alone is not enough.
@@ -54,6 +85,15 @@ If it does not, do not merge it.
   was inspected; the consolidated account names what was not covered or marks `gap`.
   **Failing case:** a findings list silent on, say, migration safety is not a clean
   migration review — name the inspection or the gap.
+- **Separate the verdict from its context.** A verdict flips only on evidence
+  scoped to the change under review — its diffs, its acceptance criteria, its
+  blast radius. Whole-repo signals gathered along the way (a global health
+  score, an unrelated security note, a pre-existing smell) are recorded under
+  an informational/deferred heading with that label, never folded silently into
+  the verdict — and never used to soften or harden it either direction.
+  **Failing case:** a clean change is failed because a repo-wide scan surfaced
+  a decade-old finding the diff did not introduce — or a broken change is
+  approved because "overall health" still looked fine.
 - Let automation (linters, formatters, CI) catch the trivial stuff so review focuses on
   design and correctness.
 
@@ -73,6 +113,26 @@ An author who is factually right wins over a reviewer's taste.
 
 Root re-verifies each claimed consequence at the cited site, keeps the surviving evidence, sets final severity itself (reviewer severity advisory), records what decided ([agents.md § Independence](agents.md#independence)); unresolved conflicts stay open blockers.
 
+Adjudication is asymmetric: dropping a true finding destroys it silently, while
+keeping a false one costs only a re-check. A finding is removed only on two
+grounds, each citing evidence:
+
+1. **Refuted at the site** — the quoted code or a direct read shows the claim is
+   factually wrong (the guard exists, the value cannot be nil, the test asserts
+   it). "Looks unlikely" is not refutation.
+2. **Out of scope** — the file is not in the review set or the finding describes
+   pre-existing code the diff did not touch. Route it as a follow-up, never
+   delete the record.
+
+"Cannot verify", "suspicious", "would not have raised it", and "inconvenient to
+fix now" are not grounds for removal — the finding stays open.
+
+**Protected subjects** veto dismissal regardless of convenience: a claim of a
+correctness bug, a security exposure, a data-loss/migration risk, a silently
+dropped error, or a violated project principle survives unless ground 1 produces
+a direct counter-read at the cited site. Never drop a protected-subject finding
+because the fix is large or the release is close — escalate the decision instead.
+
 ## Heuristic checks: FLAG vs NOTE
 
 A heuristic check that gates emits **FLAG** only when it can state the observed

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

@@ -1,5 +1,7 @@
 # Coding style
 
+> Applies when: writing or editing code; naming, reuse, guard clauses, readability.
+
 Write code the next engineer can read without you in the room. Match the project's
 existing idiom first; these rules fill the gaps.
 
@@ -30,10 +32,13 @@ Handle unwanted cases first and return early; keep the success path flat.
 
 ## Reuse before you write
 Before adding a new util, helper, hook, type, component, or formatter, **search** for an
-existing one. **Reuse → extend → build new**, in that order. Don't re-implement what the
-project (or stdlib) already provides. If forcing reuse would distort the existing thing's
-shape, build a sibling and consolidate later: duplication is cheaper than the wrong
-abstraction (AHA).
+existing one. Search by *problem shape*, not just name — the same problem solved under
+different names is still an existing implementation, and the hardest duplicates to spot
+are the renamed and reshaped ones. **Reuse → extend → build new**, in that order. Don't
+re-implement what the project (or stdlib) already provides. If forcing reuse would
+distort the existing thing's shape, build a sibling and consolidate later: duplication
+is cheaper than the wrong abstraction (AHA). When a plan or slice adds a new
+implementation, name the nearest existing analog it considered — or record `none found`.
 
 ## Edit reliably, change only what's asked
 - **No elision.** Never write `// ... rest unchanged` / `# ... existing code` in place of an

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

@@ -1,5 +1,7 @@
 # Context hygiene
 
+> Applies when: persisting phase results, resuming after compaction, before /clear.
+
 Persist phase results before starting fresh. The feature workspace, not chat memory,
 stores continuity.
 
@@ -44,9 +46,16 @@ changed contracts, implementation, proof, or dependencies, not every prior gener
 Required review rosters and final proof remain. Preserve protected history unchanged;
 a compact current view references originals without omitting active requirements.
 
-**Compaction fallback:** when hooks do not restore context, read `.devrites/ACTIVE`,
-then the `state.md` cursor, open `questions.md` gates, `decisions.md`, and
-`test-plan.md`/`evidence.md` proof pointers.
+**Compaction fallback:** after compaction, reload `.devrites/ACTIVE`, `state.md`,
+`questions.md`, `decisions.md`, `test-plan.md`, and `evidence.md`. When hooks do
+not restore context, run
+`devrites-engine handoff [slug]` first — one deterministic resume record reduced
+from durable artifacts (cursor, `awaiting_human`, open `questions.md` gates,
+the `gates.md` reduction with unmet/stale ids, `decisions.md` dead ends, and the
+canonical read-next order). Open the artifacts `read_next` names; resume from
+the record, not from transcript memory. Then `devrites-engine check
+regression <slug>`: `BLOCKED` names a durable fact lost since the last
+checkpoint; `unproven` does not block.
 
 ## Authority and trust
 
@@ -107,3 +116,11 @@ handoff.
 
 For a break longer than a few hours, point the footer at `$rite-handoff`: persist
 chat-only context to canonical files before clearing or closing the session.
+
+## Resume reconciliation
+
+Before trusting recorded state on resume, reconcile it against the tree:
+`git status --short` and `git diff --stat` versus the `state.md` cursor,
+`touched-files.md`, and the last recorded phase. Tree changes with no recorded
+provenance are drift — surface them (`drift.md` or a question) before doing new
+work on top, never silently absorb them into the current change.

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

@@ -1,7 +1,13 @@
 # DevRites core rules
 
+> Applies when: always; every workspace rite reads it first.
+
 Each workspace rite reads core first; load phase files from `README.md` on demand.
 
+Rules are cited as `core.md #N` (CORE-N). Numbering is stable: text may be
+reworded, an ID never changes meaning. Other files name the ID instead of
+repeating the rule.
+
 Repository conventions follow [Precedence](#precedence).
 
 ## Operating rules (every phase)
@@ -25,7 +31,10 @@ Repository conventions follow [Precedence](#precedence).
    stop. HITL never auto-continues; AFK runs to its slice budget
    ([`afk-hitl.md`](afk-hitl.md)).
 6. **Evidence over confidence:** tests, builds, runtime, screenshots beat
-   assertions; record commands and output.
+   assertions; record commands and output. Tag how each claim was known:
+   `observed` (you ran or read the evidence), `inferred` (deduced — name the
+   step), `asserted` (unverified). An `inferred`/`asserted` claim never reads
+   as `observed`.
 7. **Feature scope only:** keep review/simplify/polish/security within the active
    feature and touched files; no drive-by refactor. Route account creation,
    production provisioning/testing, and credential/secret work to the human.