devrites 6.1.2 → 6.1.4

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

@@ -5,7 +5,7 @@ argument-hint: "[slug] [--cross-model] [--full]"
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"workspaceByRole":{"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"rootOnly":["devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/elicitation.md"],"workspaceByRole":{"doubt-reviewer":["spec.md","architecture.md","plan.md","tasks.md","test-plan.md","decisions.md","state.md"],"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
 > Read-set manifest: `devrites-engine context --skills-root .omp/skills <slug> --phase vet` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
@@ -85,7 +85,9 @@ plan declares a root-authored executable workflow file, read
    Temper — in
    parallel under `skill://devrites-lib/reference/parallel-dispatch.md`; they are
    independent read-only passes on one frozen candidate. Missing
-   required account blocks.
+   required account blocks. Run root steps 2–4, including step 3's preflight
+   commands, on the same frozen candidate while the wave is out; reconcile the
+   accounts when they return.
 1b. **Recovery recheck.** Require valid return cursor, accepted prior finding,
    exact fingerprint/reproduction, repaired candidate identity, changed
    paths/criteria, affected drift/evidence, and the recorded delta self-check.
@@ -108,8 +110,8 @@ plan declares a root-authored executable workflow file, read
    marked as a refinement of an already-pinned clause; the recheck may re-raise
    it only by naming a concrete failure path the declaration omits. A
    `new_failure_mode` finding is never residual-eligible. A fold whose
-   findings are all Suggestion-or-lower rechecks mechanically at the
-   materialization gate — anchors applied, mirrors consistent, invariants
+   findings are all `mechanism` kind or Suggestion-or-lower rechecks mechanically at the
+   materialization gate — anchors applied (a clean `state apply-bundle`), mirrors consistent, invariants
    pass — without a dispatched reviewer; sub-Important findings already
    cannot keep recovery open. Reconcile
    shared artifact/readiness gates, then enter step 8 or the next repair.
@@ -142,7 +144,9 @@ plan declares a root-authored executable workflow file, read
    ownership. The plan's `Shared contract proof` names one reused boundary
    artifact plus two consuming tests for every changed API/event/schema/provider-
    consumer seam, or an explicit no-impact statement. Missing, one-sided,
-   duplicated-contract, vague, or non-consuming proof fails closed.
+   duplicated-contract, vague, or non-consuming proof fails closed. Each slice
+   names a fast writer-safe check its wright can run; proof reachable only through
+   root-owned full gates is a `mechanism` finding.
 
    Technical gaps are `NEEDS REPLAN` and Plan repair — each finding marks
    itself `new_failure_mode` or names the already-pinned clause/fingerprint

package/pack/generated/pi/agents/devrites-plan-drafter.md

@@ -76,10 +76,13 @@ Return this result:
 
 ```yaml
 mode: define | repair
+base_hashes: {}  # <path>: sha256 of the bytes you read, for every replace/patch target
 candidate_files:
   - path: <requested canonical target>
     operation: create | replace | patch
-    content: <complete candidate or exact bounded delta>
+    content: <complete file; create/replace only>
+    hunks: [] # patch only: {id, old_text, new_text}; old_text byte-exact, unique in the pinned file
+retired_ids: [] # tracked IDs (AC/REQ/HZN/SLICE/DEC/...) the delta removes on purpose
 acceptance_map: []
 dependency_order: []
 technical_decisions: []
@@ -89,7 +92,13 @@ applicability_disposition: []
 self_attack_exposures: []
 ```
 
-The root validates the cross-file bundle and persists accepted content.
+The root saves the bundle as JSON and applies it with `devrites-engine state
+apply-bundle <slug> <bundle.json>`, which refuses a stale pin, a missing,
+duplicate, or overlapping `old_text`, an unlisted vanished ID, a new task-graph
+problem, new budget overshoot, or a new dated delta section, and writes nothing on refusal. Pin each
+`base_hashes` entry with `shasum -a 256` (or `sha256sum`) on the exact file you
+read, and prefer short anchored hunks to whole-file `replace`. Patch the owning
+clause in place; never add a dated delta section beside superseded text.
 
 ## Tools / read-write mode
 

package/pack/generated/pi/agents/devrites-slice-wright.md

@@ -103,7 +103,10 @@ unclear boundary is underspecified: return `Escalation` without proceeding.
    - **No process residue.** Do not put `SLICE-###`, slice numbers, or "this slice"
      in product source, tests, comments, or filenames.
 4. **VERIFY (fail-on-red).** Run writer-safe tests/types/lint: `Tests/proof` plus
-   tests of changed code; `## Feature gates` rows are root-owned. Report required
+   tests of changed code; `## Feature gates` rows are root-owned. Writer-safe means
+   local and non-consumptive — syntax/type/lint, unit and self-check suites, and a
+   narrow smoke of the changed path — never only a syntax check; contract text
+   cannot strip it. Report required
    build/browser/E2E as `not-run` (root-owned, artifact-producing gates), and only
    when the exact command, cwd, and prerequisites already appear in the unchanged
    vetted `test-plan.md`; never synthesize or rewrite a root command. Root runs

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

@@ -4,7 +4,9 @@ Host dispatch; DevRites governs.
 
 ## Roster
 
-Review: Spec/Code plus triggered frontend/security/performance; Seal: all applicable roles.
+Review: Spec/Code, triggered frontend/security/performance, and the seal roles that can
+judge the frozen digest (test-analyst, doubt, devex); Seal: all applicable roles, citing
+same-candidate Review accounts.
 
 | Reviewer | Fires | Trigger |
 |---|---|---|
@@ -74,8 +76,10 @@ If the candidate diff has no matching surfaces, record
    and dedupe by evidence/root cause. Account for all seven (and, in `seal.md`, `devrites-proof-runner` and `devrites-doubt-reviewer`) in
    `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.
+   `Not-applicable: <inspected-scope reason>`. Seal cites, rather than re-dispatches, any
+   role `review.md` admitted on the identical candidate under
+   [evidence validity](candidate-integrity.md#evidence-validity); a changed digest or newly
+   triggered surface needs a fresh account. Persist no dispatch telemetry.
 7. Missing profile, null/failure, or malformed output is a `gap`; never
    infer approval or substitute inline review.
 

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

@@ -376,6 +376,14 @@ access, safety and irreversible-action boundaries independently stop work.
   closes every deferred row with a labeled verdict; Seal blocks on any without one.
   **Failing case:** round 4 finds three Important items on clauses untouched since
   round 1 and dispatches another repair.
+- **Recovery findings need a discriminator; recovery scope stays frozen.** While a
+  fingerprint is in recovery, a new Important finding keeps it open or opens another
+  only with an executed reproduction or a quoted AC/INV/PROH/accepted-DEC line whose
+  observable outcome fails; root turns it into a control the next wright must pass.
+  A static counterexample against plan-invented hardening goes to the Review trail or
+  `## Deferred findings` (Review gives it a verdict; Seal blocks without one). A
+  Critical with a concrete failure path always opens a fingerprint. A correction adds
+  no proof site or mechanism its fingerprint's closure does not need. No reviewer is skipped.
 - **Separate consumptive authority from recovery.** Spent one-shot authorization
   blocks another execution, not offline recovery. Retained evidence starts caller-owned
   diagnosis/correction immediately; the next consumptive execution needs fresh authority.
@@ -389,13 +397,19 @@ access, safety and irreversible-action boundaries independently stop work.
   the fingerprint's current *strategy*, not the work. Record that strategy and its
   attempts under `## Dead ends`, then the controlling caller escalates inline in the
   same invocation: re-diagnose from the reproduction and dead ends, take the first
-  class below that still has an untried strategy, run `/rite-plan repair` plus
-  narrow Vet for it, and resume with a fresh three-attempt budget. Classes, in order:
-  (1) **shared root cause**: fix the owner every failing path routes through and
-  enforce it across all callers instead of another local guard; (2) **boundary
-  redesign**: acceptance-preserving reslice or redesign of the failing seam;
-  (3) **diagnostic amplification**: add discriminating probes or fixtures, then
-  correct from that evidence. A recorded strategy, or a rewording of one, never
+  class below that still has an untried strategy, and resume with a fresh
+  three-attempt budget. Re-plan only when the strategy must change a planning
+  input (writer allowlist, interface or contract, slice topology, or a
+  `test-plan.md` proof row): run `/rite-plan repair` plus narrow Vet for it. A
+  strategy that fits the vetted plan, with `devrites-engine check readiness <slug>`
+  still passing, goes straight to the wright with the dead ends in its contract;
+  Build's review and proof still gate it. Classes, in order, cheapest evidence
+  before costliest change: (1) **shared root cause**: fix the owner every failing
+  path routes through and enforce it across all callers instead of another local
+  guard; (2) **diagnostic amplification**: add discriminating probes or fixtures,
+  then correct from that evidence (last for a consumptive action, whose attempt
+  needs fresh authorization); (3) **boundary redesign**: acceptance-preserving
+  reslice or redesign of the failing seam, built on that evidence. A recorded strategy, or a rewording of one, never
   repeats. Escalation never weakens tests, validators or acceptance. Each
   fingerprint gets at most three escalations per activation; record each in
   `drift.md` with its class and strategy.

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

@@ -163,6 +163,9 @@ 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%**.
 
+Read the engine `context` bundle once per phase instead of re-reading the files it
+contains; after compaction re-read the bundle, not its sources.
+
 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).

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

@@ -124,6 +124,9 @@ an error because the runner can never execute it.
   (an invariant the output must always satisfy) over example (one concrete
   input/output case). An example-shaped oracle on a property-shaped outcome is
   a weak gate — reviewers flag it even when it passes.
+- One CHECK, one oracle: never chain another artifact's self-test before the
+  AC's oracle with `&&` — give the self-test its own gate, so a red self-test
+  never hides the AC's own result.
 - When an outcome becomes impossible, `gates abandon` it and route the
   handoff — never delete the row to make the ledger pass.
 - The gate set is the coverage denominator: it never shrinks to reach

package/pack/generated/pi/skills/devrites-lib/reference/standards/testing.md

@@ -250,6 +250,13 @@ Dismiss an irrelevant case with a reason; silently omitting an applicable case i
 - A flaky test is a broken test. Isolate and fix it immediately; don't paper over it with
   retries or `sleep`. **Failing case:** a known-flaky test is left with retries so the
   suite is paper-green at Prove/Seal → NO-GO.
+- **A diagnostic rerun is allowed, never proof.** Rerun a timing-shaped failure on
+  the unchanged candidate to classify it flaky or deterministic before a repair;
+  record it as diagnostic, never as a pass.
+- **Attributable RED.** A negative control or mutant counts RED only on a positive
+  marker from the targeted assertion; a setup, construction, or observation failure
+  is never credited as RED. Prove the classifier with an injected setup failure
+  that must stay uncredited.
 - **A retry-only pass is `flaky`, never green.** A pass earned by rerun on an unchanged
   candidate digest (no admitted correction between attempts), or by a runner retry
   setting, is `flaky`: record every attempt with the first attempt's outcome. It never

package/pack/generated/pi/skills/rite-autocomplete/reference/stop-conditions.md

@@ -38,7 +38,7 @@ Agent-owned backtracking is not a stop condition while the exact causal
 fingerprint has budget. Invoke the earlier phase, affected Vet, remediation, and
 proof; then resume the origin. Three no-progress corrections of that exact
 fingerprint spend only its current strategy: escalate to the next correction
-class inline (shared root cause, boundary redesign, diagnostic amplification)
+class inline (shared root cause, diagnostic amplification, boundary redesign)
 with a fresh budget, never asking permission. After three escalations in this
 activation the fingerprint parks; finish all independent work, then stop once.
 Preserve reproduction, attempts, and dead ends; never offer `/rite-plan unblock`

package/pack/generated/pi/skills/rite-build/SKILL.md

@@ -27,6 +27,9 @@ Execute [`reference/phase-contract.md`](reference/phase-contract.md)
 ([`one-slice-cycle.md`](reference/one-slice-cycle.md),
 [`afk-discipline.md`](reference/afk-discipline.md)); dispatch uses
 [`reference/wright-dispatch.md`](reference/wright-dispatch.md).
+Every wright contract names the writer-safe checks the wright runs (syntax/type/lint,
+unit and self-check suites, a narrow local smoke) and never forbids them; only
+artifact-producing, consumptive, or full canonical gates stay root-owned.
 
 ## Required rules
 

package/pack/generated/pi/skills/rite-build/reference/one-slice-cycle.md

@@ -22,7 +22,8 @@ DISPATCH  → hand the slice contract to devrites-slice-wright (fresh context).
             — dispatch the initial read-only reviews of distinct decisions in parallel
             (independent claims, fresh contexts); wright fixes stay serial — writers share files
 PROVE     → root, concurrent with the reviews on the same frozen candidate:
-            required build/browser/E2E, then returned-diff/path recheck; fail-on-red
+            required build/browser/E2E (narrow self-check/smoke first, full gate only
+            after it is green, long runs in the background), then returned-diff/path recheck; fail-on-red
             (red/gap → repair wright, then re-review and re-prove; do not commit yet)
 RECORD    → orchestrator: after green verification, update state.md/evidence.md and
             upsert the authoritative candidate manifest from the actual scoped diff

package/pack/generated/pi/skills/rite-build/reference/wright-dispatch.md

@@ -76,6 +76,11 @@ worktrees stay forbidden.
    Quote every active `decisions.md` carry-forward constraint whose `Files:`
    overlap the task paths (or that names no files).
    A new path requires a new bounded contract; the wright cannot widen the task.
+   Name the writer-safe commands the wright must run (syntax/type/lint, unit and
+   self-check suites, a narrow local smoke of the changed path) and never forbid
+   them: a wright that cannot execute writes blind and its failures surface a
+   whole review round later. Only artifact-producing, consumptive, or full
+   canonical feature gates stay root-owned.
 3. Record `git diff --name-only` before dispatch so unrelated work remains
    distinguishable. For an isolated pilot, also record committed base SHA and exact
    baseline status before asking the host for isolation. **Failing case:** paths that
@@ -99,6 +104,8 @@ acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record
 `## <DRIFT-ID> — <SLICE-ID> reslice review` with why no smaller split exists and
+a spec trace of the slice's obligations (hardening no AC/INV/PROH requires moves to
+a sibling slice dependents do not need, still gated before Seal), and
 reopen with `--reslice-review <DRIFT-ID>`. Use
 at most one writer across all linked worktrees for this workspace. Never run two
 writers in one worktree, run isolated and same-worktree writers concurrently, or

package/pack/generated/pi/skills/rite-define/SKILL.md

@@ -77,6 +77,13 @@ Pull these via `Read` when shaping the plan:
    `devrites-plan-drafter` in `define` mode for one atomic candidate bundle:
    `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` with proof mapping.
    Validate its bounded result; it does not write/ask, and returns human choices to root.
+   In the same parallel wave, dispatch one `devrites-evidence-scout` per external
+   capability the plan will rest on — OS/SDK/native API, permission or sandbox,
+   file format, toolchain, or third-party behavior — that neither live code nor a
+   cited dossier already proves (at most three, as in Spec). Fold each dossier
+   before step 2a: cite a proven capability in `architecture.md`; an unproven or
+   contradicted one becomes a risk spike ordered before its dependent slices,
+   never an assumption the build discovers.
 2. **Reconcile architecture + approach** against live seams; root writes at step 6.
    `architecture.md` owns layers/boundaries/integrations/data/dependencies/risks/impact;
    `plan.md` owns build strategy. Use the code index for structure/impact
@@ -148,7 +155,9 @@ Pull these via `Read` when shaping the plan:
    intended, route it through the Spec Drift Guard plus a recorded decision and a scoped principle
    exception a human approves. Never ready a plan that silently violates an invariant. (Re-scored
    as a blocking gate at `/rite-vet`; no file → none declared → nothing to check.)
-6. **Write** `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md`; update
+6. **Write** `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` — save the
+   accepted bundle under `packets/` and apply it with `devrites-engine state
+   apply-bundle <slug> <bundle.json>` before root reconciliation edits; update
    `state.md` (phase: plan → next `/rite-vet`). When diagrams clarify, also write optional
    `flows.md` (**Mermaid-first**). If a richer reviewable visual earns it, emit
    `visual/<flow>.html` + `visual/<flow>.outline.md` after loading matching playbooks from

package/pack/generated/pi/skills/rite-plan/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[mode: decompose|reslice|repair|reorder|split|unblock|course-cor
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/standards/acceptance-preserving-reslice.md","devrites-lib/reference/standards/tooling.md","devrites-lib/reference/standards/agents.md","rite-plan/reference/slicing.md","rite-plan/reference/replan-and-repair.md","rite-plan/reference/dependency-graph.md","rite-plan/reference/task-breakdown.md","rite-plan/reference/anti-patterns.md","rite-define/reference/plan-template.md"],"triggers":{"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.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","drift.md"],"workspaceByRole":{"plan-drafter":["brief.md","spec.md","plan.md","tasks.md","decision-coverage.md","questions.md","decisions.md","assumptions.md","architecture.md","state.md","drift.md"]}} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/standards/acceptance-preserving-reslice.md","devrites-lib/reference/standards/tooling.md","devrites-lib/reference/standards/agents.md","rite-plan/reference/slicing.md","rite-plan/reference/replan-and-repair.md","rite-plan/reference/dependency-graph.md","rite-plan/reference/task-breakdown.md","rite-plan/reference/anti-patterns.md","rite-define/reference/plan-template.md"],"triggers":{"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.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","drift.md"],"workspaceByRole":{"evidence-scout":["spec.md","architecture.md","decisions.md","state.md"],"plan-drafter":["brief.md","spec.md","plan.md","tasks.md","decision-coverage.md","questions.md","decisions.md","assumptions.md","architecture.md","state.md","drift.md"]}} -->
 > Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase plan` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
@@ -95,15 +95,21 @@ Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standard
    never re-derives them by exhaustive search. It also carries a bounded
    self-attack over the delta (`self_attack_exposures`), catching the shallow
    next-round findings before Vet's dispatch rather than after a full loop.
-   Root dispositions every exposure — fold as a finding, accept as a declared
+   During recovery, a non-Critical exposure off the failing fingerprint's causal
+   path goes to `eng-review.md` `## Deferred findings` (Review gives it a verdict;
+   Seal blocks without one), so a repair never widens past its fingerprint.
+   Root dispositions every other exposure — fold as a finding, accept as a declared
    residual, or reject with reason; none silently drops.
    Packet mechanics: dedupe at assembly — findings with an identical
    required-fix and site set merge into one entry that closes all their
    fingerprints. The packet may carry digest-pinned site excerpts so the
-   drafter spot-verifies anchors instead of re-scanning whole files, and root
-   may partition findings into anchor-disjoint clusters with one drafter per
-   cluster in parallel — findings sharing any anchor or mirrored clause stay
-   in one cluster, and each bundle applies independently. A `partial`-
+   drafter spot-verifies anchors instead of re-scanning whole files. Root
+   partitions findings into anchor-disjoint clusters — findings sharing any
+   anchor or mirrored clause stay in one cluster — and, with two or more,
+   dispatches one drafter per cluster in one parallel wave within the scale
+   limits. Every cluster pins the same base; their bundles apply together in
+   one `state apply-bundle` call, and an overlap refusal merges those clusters
+   for the re-dispatch. A `partial`-
    continuation re-dispatch continues the same packet; it does not advance the
    same-seam counter. Count consecutive repair packets whose findings' cited clause sets overlap
    the immediately previous packet's — the overlap is the seam. Carry it as an explicit
@@ -142,9 +148,14 @@ Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standard
 4. Re-slice using vertical-slice rules: [slicing](reference/slicing.md) and
    [task-breakdown](reference/task-breakdown.md). Prefer thin, shippable, verifiable.
    **Completion:** every slice is independently shippable/provable or carries an irreducibility reason.
-5. Reconcile the candidate against steps 3 and 4, then the root updates `plan.md`, `tasks.md`,
-   `state.md`, and appends rationale to `decisions.md`. A rejected candidate
-   (malformed bundle, stale or non-unique anchor) or a drafter `Outcome: gap`
+5. Reconcile the candidate's meaning against steps 3 and 4, save each bundle
+   under `packets/`, and apply its hunks with `devrites-engine state apply-bundle
+   <slug> <bundle.json>...` (all-or-nothing; `--dry-run` previews); never
+   hand-copy hunks or stage file copies. Rewrite each owning clause in place; never
+   append a dated delta or fold section beside the clause it supersedes (apply-bundle
+   refuses one). Then update `state.md` and append
+   rationale to `decisions.md`. A rejected candidate
+   (malformed bundle, stale or non-unique anchor, any apply-bundle refusal) or a drafter `Outcome: gap`
    is one no-progress outcome on every open fingerprint in the fold; the
    re-dispatch packet must name the rejection so the same hunks don't recur.
    A gap naming genuinely human-owned information routes to `/rite-clarify`.

package/pack/generated/pi/skills/rite-polish/SKILL.md

@@ -77,8 +77,10 @@ Incomplete comparison is **not** agreement. Record axis deltas in `polish-report
    captures.
 3. **Always** read [`reference/code.md`](reference/code.md) and assess **Phase 1
    (code polish)**; if backend was touched, assess **Phase 2 (backend polish)** from
-   the same file. Reconcile the findings, then send accepted corrections as one bounded
-   wright contract: build its read-set with
+   the same file. Assess step 4's UI phases on the same frozen digest while the
+   code assessment runs, reconcile both, then send every accepted code and UI
+   correction as one bounded wright contract (normalize corrections before polish
+   ones): build its read-set with
    `devrites-engine context --skills-root .pi/skills <slug> --phase polish --role slice-wright`, run the
    single-agent wave through `devrites-engine dispatch <slug> open|start|seal|return`
    (auto-records dispatch/return metrics), and gate returned paths
@@ -91,8 +93,8 @@ Incomplete comparison is **not** agreement. Record axis deltas in `polish-report
    its `FAIL` and `PARTIAL` rows are the normalize/quality-bar worklist**: identify the root
    cause of each (a missing state, an off-token CTA, or an anti-slop hit) rather than
    hiding it with decoration. Assess **Phase 3 (normalize)** → **Phase 4 (UI polish)**,
-   then send accepted UI
-   corrections to the wright (which invokes the relevant craft skill). Honor argument modes:
+   and fold accepted UI
+   corrections into step 3's single wright contract (the wright invokes the relevant craft skill). Honor argument modes:
    - `bolder | quieter | distill | harden`: passed to Phase 4 as the
      emphasis dial.
    - `normalize-only`: assess Phase 3 and stop (no Phase 4).

package/pack/generated/pi/skills/rite-prove/SKILL.md

@@ -76,7 +76,8 @@ test changes.
    command, cwd, prerequisites, exit, and sanitized
    decisive output, plus the test selector, runner counts
    (collected/ran/passed/failed/skipped), and attempt number with first-attempt
-   outcome; output and exit come from one execution. Run relevant suite plus build/typecheck/lint. Recheck the
+   outcome; output and exit come from one execution. Run relevant suite plus build/typecheck/lint,
+   concurrently when they share no build directory, port, or lock. Recheck the
    candidate and require identical digest/no source mutation. Reject substituted
    commands, malformed manifests, zero-test/skipped/filtered behavioral claims,
    exit-status-only claims, status-masking forms, and source drift. A retry-only
@@ -109,7 +110,7 @@ test changes.
    described screenshots, console/network, interaction, target comparisons, and
    every required state. Material mismatch fails.
 7. **Independent validation.** Fresh read-only `devrites-proof-runner` and
-   `devrites-spec-reviewer` judge the same candidate/commands/evidence/acceptance map.
+   `devrites-spec-reviewer`, in one parallel wave, judge the same candidate/commands/evidence/acceptance map.
    Neither runs commands; reject missing/stale, invented-ID, label-only or self-attested reports.
 8. **Map proof.** Reconcile verdicts under [acceptance-proof.md](reference/acceptance-proof.md).
    Every criterion/scenario/interaction/key link needs discriminating evidence or a

package/pack/generated/pi/skills/rite-review/SKILL.md

@@ -79,7 +79,8 @@ Pull these via `Read` when the diff demands them:
    reviewer's brief without severity) and ends in `review.md` with its own label and
    action tag — never silently dropped. Hand each lane reviewer the
    `devrites-engine recall --paths <its touched paths>` pointers as prior context, not findings.
-2. **Review tests first:** do they prove the acceptance criteria? Missing,
+2. **Review tests first** while the step-3 cohort runs — launch it first; this
+   root pass needs none of its output: do they prove the acceptance criteria? Missing,
    weak, or wrong tests are the first findings.
    **Completion:** every acceptance criterion maps to a proven test or a labeled finding.
 3. **Review spec and code separately in parallel.** A change can pass
@@ -100,6 +101,10 @@ Pull these via `Read` when the diff demands them:
        (scope creep / drift), (c) criteria implemented incorrectly. Quote the spec
        line per finding. If the spec is missing or unreadable, report `Review gap:
        missing spec` and do not infer requirements from the diff."
+     - **Seal roles** → `devrites-test-analyst`, plus `devrites-doubt-reviewer` per
+       stood decision and `devrites-devex-reviewer` when triggered, join this cohort on
+       the same digest. Their findings join step 7's single correction, and Seal cites
+       their unchanged same-candidate accounts instead of re-dispatching them.
      - **Code-review axis** → `devrites-code-reviewer`: "Apply your full documented
        discipline (tests-first, correctness, readability, architecture, maintainability,
        standards) on the feature workspace + diff. Cite file:line; skip tooling-enforced

package/pack/generated/pi/skills/rite-seal/SKILL.md

@@ -61,8 +61,8 @@ Follow [`reference/phase-contract.md`](reference/phase-contract.md)
 
 1. read workspace and final diff;
 2. recheck the canonical candidate/bindings and approved repository/CI proof;
-3. admit valid Spec/Code accounts; dispatch remaining required exact roles under
-   `../devrites-lib/reference/parallel-dispatch.md` on the same frozen candidate,
+3. admit every valid same-candidate Review account; dispatch remaining required exact roles under
+   `../devrites-lib/reference/parallel-dispatch.md` in one wave, proof-runner included, on the same frozen candidate,
    code review through its § Engineering lanes;
 4. reconcile their read-only verdicts against source and immutable evidence;
 5. draft GO/NO-GO `seal.md` with acceptance, tests, decisions, and seven roster accounts plus proof-runner and doubt-reviewer

package/pack/generated/pi/skills/rite-seal/reference/phase-contract.md

@@ -13,12 +13,18 @@
    candidate check afterward and require the identical digest and no source
    mutation. Capture command, cwd, exit, decisive output, and identity.
    Missing/red/mismatched blocks; unavailable is `cannot_verify`, never pass.
+Steps 3–6 share one dispatch wave: launch every role they still need
+(proof-runner, test-analyst, doubt-reviewer, roster) together, admit valid
+same-candidate Review accounts instead, and do the root work of steps 4–6 while
+the wave runs.
+
 3. **Judge acceptance.** Dispatch exact `devrites-proof-runner` on immutable
    proof; admit valid same-candidate `devrites-spec-reviewer` evidence from Review
    or dispatch that exact reviewer. Reconcile every
    AC/REQ/scenario/key link by ID and meaning; missing/stale/self-attested/mismatched is NO-GO.
 4. **Judge tests.** Diff baseline/candidate tests for deletion, skip/focus,
-   tautology, or weakening; dispatch exact `devrites-test-analyst`. Missing or
+   tautology, or weakening; admit the same-candidate `devrites-test-analyst` account
+   from Review or dispatch that exact analyst. Missing or
    adverse account, or green tests not asserting mapped behavior, is Critical.
 5. **Resolve gates.** Open blocking/escalating/validating questions and drift
    block. Each stood decision needs a reconciled exact `devrites-doubt-reviewer` verdict.

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

@@ -5,7 +5,7 @@ argument-hint: "[slug] [--cross-model] [--full]"
 user-invocable: true
 ---
 
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"workspaceByRole":{"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/parallel-dispatch.md","devrites-lib/reference/standards/gates.md","rite-vet/reference/review-axes.md","rite-vet/reference/artifacts.md","rite-vet/reference/depth.md","rite-vet/reference/eng-lenses.md","rite-vet/reference/anti-patterns.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"assumption-delta":["devrites-lib/reference/standards/assumption-checkpoints.md"],"cross-model":["rite-vet/reference/cross-model.md"],"devex":["devrites-lib/reference/standards/developer-experience.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"elicitation":["devrites-lib/reference/standards/elicitation.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"grammar":["devrites-lib/reference/standards/spec-grammar.md"],"one-shot":["devrites-lib/reference/standards/one-shot-actions.md"],"performance":["devrites-lib/reference/standards/performance.md"],"principles":["devrites-lib/reference/standards/principles.md"],"reslice":["devrites-lib/reference/standards/acceptance-preserving-reslice.md"],"testing":["devrites-lib/reference/standards/testing.md"],"workflow":["devrites-lib/reference/standards/development-workflow.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"],"yagni":["devrites-lib/reference/standards/patterns.md","devrites-lib/reference/standards/coding-style.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","strategy.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md"],"rootOnly":["devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/elicitation.md"],"workspaceByRole":{"doubt-reviewer":["spec.md","architecture.md","plan.md","tasks.md","test-plan.md","decisions.md","state.md"],"devex-reviewer":["spec.md","plan.md","tasks.md","decisions.md","state.md"],"plan-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","decision-coverage.md","architecture.md","decisions.md","state.md"],"strategy-reviewer":["brief.md","spec.md","plan.md","decisions.md","decision-coverage.md","strategy.md","state.md"]}} -->
 > Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase vet` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
@@ -85,7 +85,9 @@ plan declares a root-authored executable workflow file, read
    Temper — in
    parallel under `../devrites-lib/reference/parallel-dispatch.md`; they are
    independent read-only passes on one frozen candidate. Missing
-   required account blocks.
+   required account blocks. Run root steps 2–4, including step 3's preflight
+   commands, on the same frozen candidate while the wave is out; reconcile the
+   accounts when they return.
 1b. **Recovery recheck.** Require valid return cursor, accepted prior finding,
    exact fingerprint/reproduction, repaired candidate identity, changed
    paths/criteria, affected drift/evidence, and the recorded delta self-check.
@@ -108,8 +110,8 @@ plan declares a root-authored executable workflow file, read
    marked as a refinement of an already-pinned clause; the recheck may re-raise
    it only by naming a concrete failure path the declaration omits. A
    `new_failure_mode` finding is never residual-eligible. A fold whose
-   findings are all Suggestion-or-lower rechecks mechanically at the
-   materialization gate — anchors applied, mirrors consistent, invariants
+   findings are all `mechanism` kind or Suggestion-or-lower rechecks mechanically at the
+   materialization gate — anchors applied (a clean `state apply-bundle`), mirrors consistent, invariants
    pass — without a dispatched reviewer; sub-Important findings already
    cannot keep recovery open. Reconcile
    shared artifact/readiness gates, then enter step 8 or the next repair.
@@ -142,7 +144,9 @@ plan declares a root-authored executable workflow file, read
    ownership. The plan's `Shared contract proof` names one reused boundary
    artifact plus two consuming tests for every changed API/event/schema/provider-
    consumer seam, or an explicit no-impact statement. Missing, one-sided,
-   duplicated-contract, vague, or non-consuming proof fails closed.
+   duplicated-contract, vague, or non-consuming proof fails closed. Each slice
+   names a fast writer-safe check its wright can run; proof reachable only through
+   root-owned full gates is a `mechanism` finding.
 
    Technical gaps are `NEEDS REPLAN` and Plan repair — each finding marks
    itself `new_failure_mode` or names the already-pinned clause/fingerprint

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.1.2",
+  "version": "6.1.4",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code, Codex, omp, pi, and Devin CLI",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",