devrites 5.13.1 → 5.14.0

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

@@ -57,15 +57,21 @@ If the candidate diff has no matching surfaces, record
 4. Ask for each exact named agent in fresh context; omit native syntax and
    `agent_type`/`task_name`/`fork_turns` from the instruction.
 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.
+   `Outcome: findings`, `Outcome: no-findings`, `Outcome: gap`, or — for a
+   conditional step that could not run at all — its NOT-RUN marker recorded in
+   `review.md`/`seal.md` per [core.md § Gate contract](standards/core.md#gate-contract);
+   an unavailable required role stops for HITL. Reconciling over a partial roster
+   is forbidden. Admit one account per role label per candidate: only the return
+   bound to the sealed wave's handle counts; a double delivery or a return from an
+   abandoned or re-issued wave is recorded `duplicate`/`stale`, never as a second
+   account or corroboration. **Failing case:** abandoned-wave and re-dispatched
+   code-reviewers both return, and "two reviewers agree" dismisses a spec finding.
    Findings later withdrawn at reconciliation stay visible: the account records
    `withdrawn: <n> (<reason>)` rather than silently dropping them.
 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
+   `review.md`/`seal.md`, each [engineering lane](#engineering-lanes) separately:
+   `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.
 7. Missing profile, null/failure, or malformed output is a `gap`; never
@@ -76,6 +82,41 @@ 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.
 
+## Engineering lanes
+
+Classify each changed path by the runtime it executes in — from entry points, build
+targets, and the import graph, never filename or language: `frontend`
+(client-rendered, browser, or native UI runtime), `backend` (server, worker, CLI, or
+data runtime), `boundary` (a serialized contract between them), or `other` (build
+tooling, libraries, game engines: own profile, no forced split; native app UI is
+`frontend`). Record the lane map
+in `review.md`/`seal.md`.
+
+- **Frontend and backend both changed:** dispatch `devrites-code-reviewer` twice in
+  the same wave (`dispatch open ... --role code-reviewer.frontend --role
+  code-reviewer.backend`; distinct handles — the sealed wave's handles and start
+  stamps are the concurrency receipt). Build each bundle with `devrites-engine
+  context <slug> --phase <p> --role code-reviewer --trigger <set> --out
+  ctx/<p>-code-reviewer.<lane>.bundle.md`; the default name collides. Each packet
+  names its lane, the lane's path set (the whole diff stays readable for context),
+  the triggered profile ([`review/README.md`](standards/review/README.md)), and the
+  contracts crossing the lane. Otherwise one code-reviewer, lane recorded.
+- **Reconcile per contract:** each lane returns `Contract:` rows; root pairs both
+  sides of each contract. A contract assessed from one side only is a `gap`; a
+  missing crossing test is Important.
+- **Accounting:** each lane is its own account; a combined verdict never hides a
+  failed or unassessed lane, and a blocked question on one lane does not stop the
+  other. A mixed file may be reviewed by both lanes; writes stay with one wright.
+  `devrites-frontend-reviewer` (craft/a11y) supplements, never substitutes, the
+  frontend lane.
+- **Capacity:** temporary backpressure keeps the batch rule above. If the host
+  cannot launch concurrent children at all, record `lane-concurrency: unavailable
+  <reason>` and ask the user once before dispatching lanes serially; record the
+  answer in `decisions.md`.
+
+**Failing case:** one code-reviewer covers a full-stack diff from the handler side;
+the client renames a field its mocked test still passes, and the verdict reads clean.
+
 ## Cancellation and terminal reconciliation
 
 Cancellation acknowledgement means the host accepted a request, not that the
@@ -87,11 +128,22 @@ 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.
 
+On resume (compaction or a new session), run `devrites-engine dispatch <slug>
+status`, `parallel status`, and `claim list --all` before any dispatch. A read-only
+wave whose handles this session cannot query: `abandon` it, record each unreturned
+role `gap`, and re-dispatch fresh on the current digest; its late returns are
+`stale`. A writer keeps its claim and lease — no relaunch on those paths until the
+claim is released or its holder is proven terminal. A wright that never returned an
+admitted result leaves unadmitted bytes: task-path changes since its pre-dispatch
+`git diff --name-only` baseline are never cited as built nor discarded, and are
+named in the re-dispatch contract; changes outside task paths stop for the human
+(Converge side: [`rite-converge`](../../rite-converge/SKILL.md)).
+
 ## Scale limits
 
-The role table bounds rosters. Use roughly four concurrent read-only reviewers;
-eight only with disjoint paths/resources. Refuse unbounded swarms and role
-substitution: sharpen scope or use a bounded second pass when coverage is missing.
+The role table bounds rosters. Use roughly four concurrent read-only reviewers,
+counting children any leaf spawned; eight only with disjoint paths/resources.
+Refuse unbounded swarms and role substitution: sharpen scope or use a bounded second pass when coverage is missing.
 Overlapping reviewers increase duplicate findings and reconciliation work.
 
 ## Children are tools, not peers

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

@@ -38,13 +38,28 @@ Mid-flight replies — the turns between completion states — obey the same eco
   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.
+- **Cap enumerations.** Long lists collapse to at most 5 items per group plus
+  `k of N; rest: <path>`, where N equals the count in that durable artifact; the full
+  enumeration lives there, not the reply. **Failing case:** the reply says "3 open
+  findings" while `review.md` lists 7 and no path is named.
 - **Errors are matter-of-fact** — cause and fix, never alarm noise.
+- **Paste-safe commands.** A command on a `Next:`/`Resume:`/`Fix:` line has no trailing
+  `#` comment, uses paths that resolve from the user's working directory (project-relative
+  or absolute, never a sandbox/temp path), and chains dependent steps with `&&`.
+  **Failing case:** `Next: devrites-engine handoff billing  # resume` errors on first paste
+  in zsh, which passes the comment as arguments.
 
 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.
+the first line (its state token: `Done`, `Awaiting human`, `Stopped`, `NO-GO`, `GO`,
+`Shipped`, or the lead label a utility rite's own output template defines, such as
+`Verdict:` or `Feature:`) and the action line (`Next:`, or `Resume:`/`Fix:` in a stop shape) must know
+what happened and what to do next. Prose before the state token fails the test.
+
+The reply has one next action. A `↻ Hygiene:` footer
+([`context-hygiene.md`](standards/context-hygiene.md#the-hygiene-footer)) names only
+`/clear`, `/compact`, or `/rite-handoff`, plus the action-line command unchanged if it
+repeats one. **Failing case:** `Next: /rite-prove` above a footer resuming with `/rite-review`.
 
 If a required decision, proof, or invariant is missing, use one of these states
 instead of `Done`:
@@ -87,9 +102,9 @@ Record: .devrites/archive/<slug>/ship.md
 ```
 
 Claims such as proved, reviewed, sealed, shipped, or complete must point to real
-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
+output or an artifact. A NOT-RUN verification keeps its marker in `Evidence:` or `Open:`
+per [`core.md`](standards/core.md#gate-contract) § Gate contract.
+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/omp/skills/devrites-lib/reference/standards/README.md

@@ -31,7 +31,6 @@ 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. |

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

@@ -28,7 +28,7 @@ The contract uses one sentinel, one queue, and one resume verb.
 ## Run modes
 
 - **HITL (default):** human is present. At a gap/checkpoint the skill **asks inline** via
-  the harness `AskUserQuestion` tool: a ranked **option set** (recommended first, each with
+  the harness `ask` tool: a ranked **option set** (recommended first, each with
   dimension-tagged rationale; see [Option set](#option-set-how-every-gap-is-presented)). The
   human picks; the skill records the pick to `questions.md` (`answered`) + `decisions.md` and
   **continues in place: no `/rite-resolve` round-trip**. `/rite-resolve` is only for answering
@@ -208,7 +208,7 @@ Wherever a gap, checkpoint, or non-trivial decision surfaces (`/rite-spec`, `/ri
   be silently dropped, merged, or preselected to fit the UI.
 - Recommend for project conventions, stack, scale, and domain, not a generic default.
 
-**HITL** renders the set via `AskUserQuestion`; the human's pick resolves the gate **in place**.
+**HITL** renders the set via `ask`; the human's pick resolves the gate **in place**.
 **AFK** auto-picks option 1 for gates it may auto-handle. Record the chosen option verbatim and
 keep the **rejected options in `questions.md`**.
 
@@ -279,22 +279,15 @@ boundary owns any such request and requires explicit user approval.
 
 ## `state.md` `Awaiting human` block
 
-When a HITL gate fires, `/rite-build` writes:
+When a HITL gate fires, `/rite-build` sets cursor `status` to `awaiting_human` and
+`next_action` to `/rite-resolve <qid> "<answer>"`, then writes the `Awaiting human` table
+(`question_id`, `gate`, `blocking_slices`) owned by
+[`state-workspace.md`](../../../rite-spec/reference/state-workspace.md#statemd-template) § state.md template.
+The question text, `proposed` answer, and `raised_at` live in the `questions.md` entry.
+Legacy `- Status:`/`- Next step:`/`- qid:` bullet keys are engine-accepted aliases, not
+the authoring format.
 
-```markdown
-- Status: awaiting_human
-- Next step: /rite-resolve <qid> "<answer>"
-
-## Awaiting human
-- qid: <q-...>
-- gate: <gate>
-- question: <crisp text>
-- proposed: <agent's tentative answer>
-- raised_at: <iso>
-- blocking_slices: [<slice ids that cannot advance>]
-```
-
-`/rite-resolve` removes the block on success and flips `Status: running`.
+`/rite-resolve` removes the block on success and sets cursor `status` to `running`.
 
 ## The resume verb: `/rite-resolve`
 
@@ -309,7 +302,7 @@ Three shapes:
 `/rite-resolve` is the canonical writer for **async** resume: a gate that already paused and
 stopped the session (an AFK blocking/escalating/irreversible queue, or a HITL pause the human
 walked away from), plus `--batch`. In an **interactive HITL** session the skill resolves the
-`AskUserQuestion` pick **in place** (the same `questions.md` `answered` write + `state.md`
+`ask` pick **in place** (the same `questions.md` `answered` write + `state.md`
 clear), so you don't type `/rite-resolve` for gaps you answer live. Both paths flip
 `status: open → answered` and clear `Awaiting human` through the **same `devrites-engine state resolve` writer**:
 one source of truth, two entry points (live pick vs typed verb). Use the writer;

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

@@ -50,7 +50,7 @@ Workflow-named skills (e.g. devrites-source-driven) are invoked inline in the ro
 
 ## Source-writing boundary
 
-Claude grants only wright `acceptEdits`; Codex root is workspace-capable (children cannot elevate). Wright alone `:workspace`; others `:read-only`. Wright gets the smallest exact project-relative source/test list — no directories/globs, traversal, or `.devrites/**`; no scope widening; root rejects `git diff --name-only` extras. Never patch product source/tests in root, bypass/substitute wright, accept drift, or recreate a dispatch bridge.
+omp: only the wright's `tools` allowlist has `edit`/`write`; the root stays source-read-only by instruction. Claude grants only wright `acceptEdits`; Codex root is workspace-capable (children cannot elevate). Wright alone `:workspace`; others `:read-only`. Wright gets the smallest exact project-relative source/test list — no directories/globs, traversal, or `.devrites/**`; no scope widening; root rejects `git diff --name-only` extras. Never patch product source/tests in root, bypass/substitute wright, accept drift, or recreate a dispatch bridge.
 
 Isolated-worktree pilot only under [`wright-dispatch.md`](../../../rite-build/reference/wright-dispatch.md#isolated-writer-worktree-pilot): one writer, committed/clean baseline, non-submodule parent, exact transfer commit, candidate reconciliation — never parallel writers nor weaker exact-path admission. Root may materialize only exact Vet-ready workflow-artifact paths per [`workflow-artifacts.md`](workflow-artifacts.md) — not a writer dispatch or candidate mutation.
 
@@ -67,6 +67,11 @@ 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.
+Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
+expected write (engine max 240) and re-add before it lapses; before writing, also
+read `claim list --all` — a foreign `expired` claim on overlapping paths whose
+session is not proven terminal counts as held (stop and report). **Failing case:**
+session B's `claim check` passes at minute 35 over session A's still-running wright.
 
 ## Independence
 
@@ -85,26 +90,53 @@ Each required reviewer/analyst/auditor starts with exactly one:
 
 ```text
 Outcome: <findings | no-findings | gap>
-Finding: <severity> | <file:line or artifact section> | <observed quote/result> | <impact> | <minimum fix>
+Counts: <n per severity or kind used in the rows below>
+Finding: <severity> conf <n> | <file:line or artifact section> | <observed quote/result> | when <input/state/sequence> → <effect> | <minimum fix>
 Basis: <files read · commands run to reach this finding>
 ```
 
 - **`findings`:** each row uses the shape above; confidence 1–10 on Critical/Important.
   Critical/Important requires 7+, exact evidence, concrete impact, and a non-empty
   `Basis` — a correct verdict reached by an unrecorded inspection path is unproven.
+  A Critical/Important row carries `conf <n>` in its severity cell and writes impact
+  as `when <input/state/sequence> → <effect>`; missing either, root admits it as
+  `Unverified: <claim> — missing trigger` (stays `gap`).
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;
   tool/reviewer failure; or another limit. Required gaps block.
 
 Root treats results as claims; verifies proposed Critical/Important blockers
-against candidate. Missing fields become
+against candidate, first anchoring each row's quote at its cited `file:line` on the
+frozen digest: exact → admit; found at exactly one other location → relocate,
+keeping both locations; not found or found at several → `Unverified: <claim> —
+anchor lost|ambiguous`, a gap that is never a finding or a dismissal. A leaf result
+produced by spawning a nested agent is `gap`, and each hidden child counts toward
+the concurrent pool and `max_agents`. Missing fields become
 `Unverified: <claim> — missing <proof>` and stay `gap` until verified/rejected
 with evidence—never silently dropped/demoted. Null/timeout/failure/malformed
 output is `gap`, never `no-findings`. Conditional `Not-applicable` must name the
 inspected scope and why its trigger did not fire. **Failing case:** parent admits a
 wright "done" with no `git diff --name-only` ⊆ path-contract (allowlist) observation.
 
+### Return budget
+
+Every read-only leaf returns rows, not prose, so the root keeps its context for
+decisions and nothing is lost in a retelling. Exempt: `devrites-plan-drafter` (its
+return is the bundle the root writes) and the wright's change evidence.
+
+- Lead with the result line (`Outcome:` for reviewers, the role's own status line
+  otherwise), then `Counts:` with the number of rows per severity or kind.
+- No restated task, preamble, approach narrative or closing summary. An optional
+  `Notes:` block carries at most five lines that no row can hold.
+- Point, don't paste: cite `file:line` with at most one quoted line (160
+  characters); for a command, give the exact command, its exit code and the one
+  decisive output line. Never paste whole files, diffs, logs or test output.
+- Each row stands alone: a reader of that row alone can re-check it from its pointer.
+- The root records admitted rows verbatim, adds its own verification beside them, and
+  never rewrites, merges or summarizes a row; deduplication references rows by
+  position or ID instead of rewording them.
+
 ## Reconciliation
 
 Root rejects stale/out-of-scope work, dedupes by root cause, records

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

@@ -52,7 +52,11 @@ After each hunting wave, a **coverage critic** — a fresh agent comparing the l
 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
+Accepted discoveries become `planned` units. Coverage is `complete` only after a
+critic returns no accepted missing or reassigned unit and no unit is `planned`;
+otherwise the run is partial, and a wave or agent cap is never evidence of
+completeness. A reassigned unit gets a fresh owner; the old attempt's evidence stays
+attributed to it and is never merged into the new attempt. Reserve critic and verifier capacity
 **before** spending on hunters; a wave launched with no verification reserve hunts
 for findings nobody may claim.
 

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

@@ -13,9 +13,20 @@ viewport set here.
   wrong route, blank render, unexpected login wall, inconsistent dimensions, or
   stale candidate is missing evidence. Recapture; until resolved, record
   `cannot_verify` and block visual approval. A convincing narrative cannot repair it.
-- Interactive slices capture each relevant canonical state and the canonical
-  viewport set. Omission needs a one-line `not-needed` reason; states must exist
-  in source — an unreachable state's capture proves nothing.
+- **Evidence matrix.** Layout-bearing states (default, long content, and every
+  role-applicable surface state from [`quality-standards.md`](../../../devrites-frontend-craft/reference/quality-standards.md) § Focus & states) × every
+  canonical viewport; interaction states at ≥1 small and ≥1 large viewport (hover
+  only with a hover-capable pointer); one keyboard traversal; a `reduce` capture when
+  motion changed; every shipped theme. Each cell holds a capture, `cannot_verify`, or
+  `not-needed (<reason>)`; an empty cell is `cannot_verify`. States must exist in source
+  — an unreachable state's capture proves nothing.
+- A capture counts only with fonts loaded, animations settled, the real route (a harness
+  or story capture is labelled and never fills a route cell) and matching candidate
+  identity. Hover, touch, iOS zoom or safe-area behaviour seen only in emulation is
+  `unverified (device)`, never a pass.
+- A finding closes only with a capture of the same route, state and viewport class on the
+  corrected candidate; a failed or incomplete capture run never counts as gone.
+  **Failing case:** a 320 px overflow closed by a clean 1440 px screenshot.
 - Browser-default chrome is judged by § Browser chrome; reflow, zoom and bounded
   two-dimensional exceptions by § Responsive. Compare to `design-brief.md` → Visual Verdict.
 - Tooling unavailable ⇒ record fallback + limitation. Backend-only changes record

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

@@ -11,7 +11,7 @@ Review.
 | Question | First tool | Fallback |
 | --- | --- | --- |
 | Explore unfamiliar area, architecture, blast radius | `codegraph_explore` or codebase-memory `search_graph` / `get_architecture` | code-review-graph `detect_changes_tool` / `get_impact_radius_tool` |
-| Callers, callees, data flow across files | codebase-memory `trace_path` | code-review-graph `query_graph_tool` |
+| Callers, callees, call paths across files (value/taint flow: [`tooling.md`](tooling.md) route table) | codebase-memory `trace_path` | code-review-graph `query_graph_tool` |
 | PR/review context for a diff | code-review-graph `get_review_context_tool` | `detect_changes_tool` |
 | Exact symbol body before edit | `read_symbol` / `module_report` (pi-lens) | `get_code_snippet` then targeted `Read` |
 | Rename, references, diagnostics | LSP (`lsp` rename/references) when available | graph trace + grep |
@@ -29,7 +29,13 @@ Review.
 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.
+   (see blind spots below); record the gap. Diagnostics count only when bound to the
+   current bytes: the server received the post-edit sync or save, the project is loaded
+   and ready, and the file is within its size limits. A `0` from a cold, not-ready, or
+   oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
+   <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
+   the language server returns 0 diagnostics before the project finishes compiling and
+   the slice records "diagnostics clean".
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

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

@@ -81,10 +81,9 @@ If it does not, do not merge it.
   never approval or silent demotion.
 - **Skipped checks are recorded.** A check you couldn't run gets a
   `Skipped: <check> — <why>` line.
-- **Unreviewed is not clean.** A report that never names an area does not prove that area
-  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.
+- **Unreviewed is not clean** ([core.md § Gate contract](core.md#gate-contract)): an area
+  the report never names counts as uninspected — name the inspection or mark `gap`
+  (silence on migration safety is not a clean migration review).
 - **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
@@ -124,6 +123,14 @@ grounds, each citing evidence:
    pre-existing code the diff did not touch. Route it as a follow-up, never
    delete the record.
 
+A dispute that turns on runtime, configuration, ordering, or environment (race,
+retry, config default, framework behavior) is decided only by a discriminating
+reproduction naming trigger and result: an approved command, or a wright-authored
+regression test. A green general suite, an assumed framework guarantee, or how many
+reviewers agree never decides it; without the reproduction the conflict stays an
+open blocker. **Failing case:** one reviewer flags a race, another calls it fine,
+and root dismisses it after reading the handler.
+
 "Cannot verify", "suspicious", "would not have raised it", and "inconvenient to
 fix now" are not grounds for removal — the finding stays open.
 

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

@@ -55,7 +55,12 @@ 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.
+checkpoint; `unproven` does not block. Before any re-dispatch, run
+`devrites-engine dispatch <slug> status`, `devrites-engine parallel status --root <repo>
+--slug <slug>`, and `devrites-engine claim list --all`, and reconcile open waves, leases, and
+claims per [`parallel-dispatch.md`](../parallel-dispatch.md#cancellation-and-terminal-reconciliation) § Cancellation.
+**Failing case:** after compaction the root re-dispatches a review cohort whose original
+children still run, and duplicate accounts arrive.
 
 ## Authority and trust
 
@@ -81,16 +86,22 @@ Apply [`core.md` § Precedence](core.md#precedence); authority and evidence diff
 **Default to `/clear`.** First persist missing decisions, assumptions, or questions
 to their owners (`/rite-handoff`); `/compact` preserves unrecorded continuity.
 
-## The "Session hygiene" footer (every rite-* output)
+## The hygiene footer
 
-Every `rite-*` skill ends its output with a one-line **Session hygiene** advisory, plus
-the **single command** that resumes work next session:
+Every `rite-*` reply names the **single command** that resumes work on its action line
+(`Next:`, or `Resume:`/`Fix:` in a stop shape; [`reply-contract.md`](../reply-contract.md))
+and ends with one advisory line after `Record:`:
 
 ```
-Session hygiene: /clear (recommended)   — <one-line why, anchored to what just got persisted>
-Resume next session with: <single command, e.g. /rite-build slice 2>
+↻ Hygiene: </clear | /compact | /rite-handoff> — <why, anchored to what just got persisted>
 ```
 
+A footer may name two of those moves under stated conditions ("/clear between slices;
+/rite-handoff if away").
+
+Besides `/clear`, `/compact`, or `/rite-handoff`, the footer names no command except the
+action-line command unchanged; a different resume command is a competing next action.
+
 This is advice, not a gate. The user can ignore it. It reports a trade-off the model
 cannot inspect directly because no API reports context fullness.
 

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

@@ -2,12 +2,20 @@
 
 > Applies when: always; every workspace rite reads it first.
 
-Each workspace rite reads core first; load phase files from `README.md` on demand.
+Each workspace rite reads core first. Its `loads:` manifest `always` set is its required
+read-set (`devrites-engine context <slug> --skill <name>` where a workspace exists, else
+read the listed files); a trigger's files load when its named condition holds. Load any
+other rule file 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.
 
+Uppercase MUST/MUST NOT/SHOULD/SHOULD NOT/MAY carry RFC 2119 meaning: MUST is a gate;
+a SHOULD deviation records its reason in `decisions.md` (the exception procedure); MAY
+permits. Lowercase "must"/"never" inside a rule, gate, or failing case binds exactly
+as MUST; case never creates a weaker tier. An exception never weakens a core gate.
+
 Repository conventions follow [Precedence](#precedence).
 
 ## Operating rules (every phase)
@@ -143,9 +151,11 @@ Before any `rite-*` skill stops:
   tried, why it failed, what it rules out). Compaction and the next agent must not repeat an
   invalidated approach.
 - Next-action ambiguous? → resolve to one command in `state.md`.
-- HITL pause? → write the `Awaiting human` block to `state.md` and set
-  `Status: awaiting_human` before stopping; resume via `/rite-resolve <qid> "<answer>"`.
-  See [`afk-hitl.md`](afk-hitl.md) for the full AFK / HITL contract.
+- HITL pause? → before stopping, set cursor `status` to `awaiting_human` and write the
+  `Awaiting human` table in `state.md` per its owner,
+  [`state-workspace.md`](../../../rite-spec/reference/state-workspace.md#statemd-template) § state.md template;
+  resume via `/rite-resolve <qid> "<answer>"`. See [`afk-hitl.md`](afk-hitl.md) for the
+  full AFK / HITL contract.
 
 A skill that stops without doing this leaves the workspace incomplete.
 
@@ -153,9 +163,8 @@ A skill that stops without doing this leaves the workspace incomplete.
 
 Long contexts degrade reasoning quality. Act on context at **50-70% used, not 95%**.
 
-Compact utilities end with a one-line `↻ Hygiene:` advisory naming the right move
-(`/clear` vs `/compact`) and the single resume command; other rites name the single
-resume command in their stop output. Full phase-by-phase guidance:
+Every rite names the single resume command on its action line; a `↻ Hygiene:` footer
+advises `/clear`, `/compact`, or `/rite-handoff` and never a competing command. Full phase-by-phase guidance:
 [`context-hygiene.md`](context-hygiene.md).
 
 ## Precedence

package/pack/generated/omp/skills/devrites-lib/reference/standards/definition-of-done.md

@@ -11,7 +11,7 @@ re-judge from this table alone.
 | Required | Owner | Failing case |
 | --- | --- | --- |
 | Each AC names a stored evidence path (command or artifact) | [`testing.md`](testing.md), `rite-prove` | An AC is checked off with no path in `evidence.md` |
-| Every explicit request maps to an artifact, test, or observed command | `rite-prove`, `rite-seal` | Numbered asks counted done by proxy — green suite, manifest presence, effort spent — with no per-requirement evidence map |
+| Every explicit request (each `brief.md` `## Asks` row) maps to an artifact, test, or observed command | `rite-prove`, `rite-seal` | Numbered asks counted done by proxy — green suite, manifest presence, effort spent — with no per-requirement evidence map |
 | Runnable required checks ran to a recorded outcome | [`test-proof-checklist.md`](test-proof-checklist.md), [`debug-recovery.md`](debug-recovery.md) | A failed, timed-out, or unstartable check reported as "unrelated"/omitted instead of a named blocker |
 | Discriminating tests for changed behavior | [`testing.md`](testing.md) | Suite green; revert of the change would still be green |
 | Fresh runtime/build/test/browser records | `rite-prove`, [`browser-proof-checklist.md`](browser-proof-checklist.md) | Proof claimed from stale or unrun commands |

package/pack/generated/omp/skills/devrites-lib/reference/standards/developer-experience.md

@@ -72,7 +72,9 @@ touches:
   silent exit, or "an error occurred" is a defect on a developer-facing path.
 - **Ergonomics & consistency:** does the surface match the project's existing conventions
   (naming, argument order, pagination, error shape)? An inconsistent new endpoint taxes everyone
-  who learned the old ones. Sensible defaults; the common case is one call.
+  who learned the old ones. Sensible defaults; the common case is one call. CLI output
+  honours `NO_COLOR` and non-TTY destinations (no ANSI or spinners in a pipe) and never
+  carries meaning by colour alone; a status only colour conveys is a finding.
 - **Docs accuracy:** examples are copy-pasteable and correct, the signature in the docs matches
   the code, and changed behavior updated its docs in the same change ([`documentation.md`](documentation.md)).
 

package/pack/generated/omp/skills/devrites-lib/reference/standards/duplicate-code.md

@@ -82,6 +82,13 @@ Ranking boosts distant matches across directories or far apart within one file.
 Distance is a triage hint, not proof that two contracts are interchangeable.
 Check whether fixes to one copy should also apply to the other.
 
+A `merge` verdict (cluster or reimplemented-elsewhere twin) states the compared contract
+(inputs, outputs, errors, side effects, ordering), each unit's callers, and the tests
+protecting each copy. Any contract difference is `keep` or `watch`, not merge. When the
+survivor's tests miss the removed copy's callers, the finding adds a characterize-first
+step. A merge without the comparison is admitted only as an FYI lead. **Failing case:** two
+parsers score 0.9; one errors on empty input, the other returns a default; "merge" is wrong.
+
 ## Ignore ledger
 
 `.devrites/dup-ignore` (project-root default; `--ignore-file` overrides) holds
@@ -100,6 +107,10 @@ blind the scan.
 Rules:
 
 - Never add a hash without reading both units — an unread dismissal is a gap.
+- Judge member pairs, not the cluster: a hash is ignored only when every pair is `keep` and
+  one line explains it. A mixed or uncertain cluster gets a finding or `watch`, never an
+  ignore line, whatever the report volume. **Failing case:** A~B is a real copy, B~C is
+  coincidental, and the A~B~C hash lands in the ledger.
 - Write the reason on the same line after `#`; a bare hash is an unexplained
   dismissal and counts as a skipped check.
 - Do not commit-ignore clusters introduced by the *current* diff — a `*` unit

package/pack/generated/omp/skills/devrites-lib/reference/standards/gates.md

@@ -52,6 +52,14 @@ Execution contract: the command runs through the platform shell in the named
 directory with a bounded timeout; pass requires exit 0 **and** output matching
 EXPECT. Output is captured but never persisted — only its digest.
 
+After Vet READY the runnable set is fixed: converting a runnable gate to manual,
+loosening EXPECT, changing CHECK or CWD, or removing a row is Plan repair plus
+re-Vet, never a Prove or Seal edit. A runnable gate that cannot execute stays unmet
+with `unavailable: <reason>`. Prove attests only gates that were manual at Vet,
+checked by diffing `gates.md` against the Vet record. **Failing case:** AC-003's
+runnable gate fails at Prove, the root deletes CHECK/EXPECT and attests "verified
+manually", and `gates status` reads `all-met`.
+
 ## Evidence binding
 
 A successful run writes `EVIDENCE: automatic-evidence=v1; def=<sha256>; …`
@@ -62,7 +70,14 @@ only automatic evidence bound to the current definition counts.
 
 Manual gates are met when checked with non-empty human evidence (anything
 except `pending`); honesty of that evidence stays with the Prove/Seal
-reviewers.
+reviewers. The engine cannot see who attests, so the note must cite the human's
+own words or source (a `q-…` id the human resolved, or their message in this
+session) and name what was observed and where. An agent's own inspection, or a
+question resolved by AFK or autocomplete auto-pick, is not human evidence: an AFK
+run leaves the gate unmet behind an open `gate: validating` question and never
+self-attests. Placeholder or tautological notes (`n/a`, `tbd`, `-`, `ok`, `done`,
+`yes`, the restated gate title) are unmet at Prove and Seal. **Failing case:**
+`gates attest <slug> AC-004 "done"` passes the engine and Seal reaches GO.
 
 ## Commands
 

package/pack/generated/omp/skills/devrites-lib/reference/standards/performance.md

@@ -29,6 +29,17 @@ by source (`Field (CrUX)`, `Lab (Lighthouse)`, `Trace (DevTools)`): field and la
 interchangeable, and static source cannot measure a CWV. The reviewer captures these via the
 browser-proof ladder when a budget exists, then judges them in Measured mode (a
 source-labeled scorecard); with no artifact it runs in Source mode and names the command.
+
+- **Field status is never a pre-release pass.** Missing field data is `unavailable`;
+  origin-level data is not proof for a route; the field window lags a new deploy. The
+  pre-release gate is a lab/trace budget under stated conditions, and the field row
+  reads `pending (field)` until route-level data covers the release. **Failing case:**
+  seal cites origin "good" field data for a route shipped yesterday, or a localhost
+  audit records "field: pass".
+- **INP needs an interaction:** a named scripted interaction (timespan or trace) or
+  field data. A navigation-only lab run records INP `not measured (no interaction)`;
+  TBT may appear only as a labeled proxy.
+
 Baseline checks + measurement commands:
 [`rite-review/reference/performance-checklist.md`](../../../rite-review/reference/performance-checklist.md).
 

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

@@ -31,7 +31,8 @@ A rewrite succeeds only when the source still supports every sentence and the re
 the same decisions from it.
 
 - Preserve every fact, constraint, uncertainty, identifier, count, criterion, evidence link,
-  decision, and voice-bearing detail. Restructure freely; keep the information.
+  decision, ranking, order or causality claim, and voice-bearing detail. Restructure freely;
+  keep the information.
 - Keep quotations, titles, proper names, code spans/fences, CLI output, error strings, and text
   discussed as an example exact unless the user asks to edit that material.
 - Keep YAML frontmatter, markdown tables, URLs, and file paths exact unless the user asked to
@@ -65,8 +66,8 @@ the same decisions from it.
 - **Be specific.** Replace "every / always / never / a lot" with the actual number, file, or
   case when you know it.
 - **Vary rhythm.** Don't stack three staccato fragments or three same-length sentences in a row.
-- **Skip em and en dashes** — a repeated AI tell (matches
-  [`rite-polish/reference/anti-ai-slop.md`](../../../rite-polish/reference/anti-ai-slop.md));
+- **Skip em and en dashes** — a repeated AI tell in DevRites prose (product UI copy is
+  only a lead, per [`rite-polish/reference/anti-ai-slop.md`](../../../rite-polish/reference/anti-ai-slop.md));
   use a comma, period, colon, or parentheses instead.
 - **Trust the reader.** Skip the softening preamble and the recap of what you just said.
 

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

@@ -5,7 +5,9 @@
 > second severity scale.
 
 Load `default.md` for every reviewed file, plus the file matching the file's
-language. A file with no listed language gets `default.md` only.
+language. A file with no listed language gets `default.md` plus a card from
+[`stack-profile.md`](stack-profile.md); `default.md` alone is a disclosed
+`default-only: <reason>` gap, never silent coverage.
 
 | File pattern | Checklist |
 |---|---|
@@ -13,8 +15,11 @@ language. A file with no listed language gets `default.md` only.
 | `*.go` | [`go.md`](go.md) |
 | `*.py` | [`python.md`](python.md) |
 | `*.ts`, `*.tsx`, `*.js`, `*.jsx`, `*.mjs`, `*.cjs` | [`ts-js.md`](ts-js.md) |
+| `*.vue`, `*.svelte`, `*.astro` (script blocks) | [`ts-js.md`](ts-js.md) |
+| resolved manifest declares `react` (not the file extension) | [`react.md`](react.md) |
 | `*.sh`, `*.bash`, `*.zsh`, PKGBUILD, Dockerfile RUN blocks | [`shell.md`](shell.md) |
 | `.github/workflows/*.yml`, `.github/workflows/*.yaml`, `*.gitlab-ci.yml` | [`ci-workflows.md`](ci-workflows.md) |
+| a trigger in `stack-profile.md` fires: multi-runtime language, unlisted language, embedded region, two framework majors, cross-stack serialized boundary | [`stack-profile.md`](stack-profile.md) |
 
 Each checklist lists investigation probes, not automatic findings. Establish the
 applicable contract, reachable path, and concrete effect before reporting a defect.