devrites 6.1.1 → 6.1.3

package/pack/generated/pi/skills/rite-build/reference/parallel-batch.md

@@ -36,14 +36,14 @@ Select **greedily in plan order**: pass every currently dependency-ready pending
 `N_eff = 1` → one serial round; nothing pending → Prove. A cap that cannot be filled
 is normal: take fewer. Serial is this round's size, not the rest of the run.
 
-**Re-batch automatically after every completed round** (parallel integrate+cleanup or
-a serial slice). Re-read `state.md`, pending slices, and the tree, then run
-`parallel select` again: finished work leaves the pending set, and satisfied
-dependencies unlock new slices. Under `.devrites/AFK` and `/rite-autocomplete` the
-repeat is the same run — HITL stops after each batch. `--parallel 5` with one eligible
-slice runs that one; when two to five then become eligible, the next round takes that
-many. **Failing case:** the run stays one-by-one after a serial round even though more
-slices are now eligible under the same cap.
+**Refill per landing; never wait for the batch.** Each sibling lands alone when
+green ([Lifecycle](#lifecycle) step 6). Then re-read `state.md`, pending slices, and
+the tree and run `parallel select --cap N --slug <slug>`: unlanded siblings hold
+their slots and paths, landed ones count as built, and only new picks print;
+`parallel add` starts each from the control tip and its wright dispatches at once.
+No lease → plain `select` + `create`. AFK/autocomplete is one run; HITL stops after
+each landing. **Failing case:** three siblings are green, one is repairing, and no
+new slice starts.
 
 ## Path-disjoint
 
@@ -109,22 +109,27 @@ Lease: `batch_id`, `created_at`, `base_sha`, `n`,
    headroom bounds the batch size — one batch never assumes unbounded reviewers.
 5. Non-green siblings → **repair round** (below) in the same worktrees; lease
    stays `running` — no abort while repair budget remains. A green sibling →
-   `parallel record-green`. No partial integrate. All green → integrate.
+   `parallel record-green`, then step 6 for it alone.
    A recoverable RED blocks integration but does not cancel independent safe running siblings.
    Expected test-first RED is not a terminal gate failure. Cancel only for a shared
    invalid foundation, safety/access failure, resource boundary, or explicit stop;
    preserve completed and in-progress recoverable work and classify each result.
-6. `parallel integrate --apply-to-control` **only after steps 4–5 are green**:
-   each `transfer_commit` descends from `B` and diffs path-exact vs
-   `B`; apply each in plan order as its own local `WIP(<slug>):` commit
-   (imperative summary, never a slice id). Staging branch, then FF. Conflict →
-   reset to `B`, `integrate-failed`; classify under repair rounds (siblings stay
-   in place). Never integrate because a wright returned.
-7. Success: FF control (the branch that held `HEAD` when the batch started —
-   often `main`/`master`, otherwise whatever the user was on) to the integrate
-   tip: N local commits, never pushed; union `touched-files.md`; update
-   state/evidence; AFK +1 per integrated sibling; optional `check candidate`.
-8. Cleanup runs only after `integrate` marks the lease `complete` — work
+6. `parallel integrate --slice <id> --apply-to-control` **only after its steps
+   4–5 are green**: `transfer_commit` descends from the sibling's base and diffs
+   path-exact vs it; apply as its own local `WIP(<slug>):` commit
+   (imperative summary, never a slice id). Staging branch, then FF; the engine
+   refuses (never rewinds) if anything but this lease moved control. Conflict →
+   `integrate-failed`; classify under repair rounds (siblings stay in place).
+   Never integrate because a wright returned.
+7. Each landing: FF control (the branch that held `HEAD` when the batch started —
+   often `main`/`master`, otherwise whatever the user was on) by one local commit,
+   never pushed; union that sibling's paths into `touched-files.md`; update
+   state/evidence; AFK +1 for that sibling; optional `check candidate`. Then
+   refill ([Dynamic selection](#dynamic-selection-and-re-batching)) and start the
+   feature gates on control
+   ([Proof tiers](phase-contract.md#proof-tiers)); the next landing waits for them
+   to pass, the refilled wrights do not.
+8. Cleanup runs only after the last landing marks the lease `complete` — work
    landed in control, so `parallel cleanup` removes worktrees/branches.
    Blocked/human-stopped batches keep lease, worktrees, branches — nothing is
    removed while the batch may resume. `parallel abort` + `cleanup --force`
@@ -191,9 +196,11 @@ Repair rejected work in place; never discard/rebuild while budget remains.
 ## Engine verbs
 
 ```text
-devrites-engine parallel select --cap <1-10> [--root <dir>] [<json-file>|-]
+devrites-engine parallel select --cap <1-10> [--root <dir>] [--slug <slug>] [<json-file>|-]
 devrites-engine parallel create --root <repo> --slug <slug> --batch <id> --base <B> --json <file>|-
+devrites-engine parallel add --root <repo> --slug <slug> --json <file>|-
 devrites-engine parallel record-green --root <repo> --slug <slug> --slice <id> --commit <sha>
+devrites-engine parallel integrate --root <repo> --slug <slug> --slice <id> --apply-to-control
 devrites-engine parallel integrate --root <repo> --slug <slug> --apply-to-control
 devrites-engine parallel status --root <repo> --slug <slug>
 devrites-engine parallel lease-write|lease-read|lease-clear --root <repo> --slug <slug>

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

@@ -42,7 +42,8 @@ Spec Drift Guard still applies.
 6. **Prove.** Against the frozen pre-slice candidate inspect
    test hunks for deletion, skipping/focus, tautology, or weaker expectations.
    Wait for step 5's exact test-analyst account; missing/adverse criterion verdict is
-   Critical. Run only `test-plan.md` repository/CI commands, record output, recheck
+   Critical. Run only `test-plan.md` repository/CI commands ([tier](#proof-tiers)),
+   record output, recheck
    `git diff --name-only`. Missing/weakened/red/source-mutating proof cannot pass.
    Pre-existing/environment-specific claims need a predating same-command,
    same-environment baseline; otherwise unresolved.
@@ -67,6 +68,14 @@ Spec Drift Guard still applies.
 
 One contract builds one slice: preserve TDD, exact paths and independent judgment.
 
+## Proof tiers
+
+With a `test-plan.md` `## Feature gates` section, step 6 runs `Tests/proof` and every
+other row; feature gates run once per parallel landing, on control, while worktree
+wrights continue. The next landing and Prove wait for them; red is a fingerprint
+against slices landed since the last green run. Serial same-worktree mode, and plans
+without the section, run every row each round.
+
 ## Independent Build review
 
 After inspection, freeze full slice scope and cumulative baseline diff. Initial

package/pack/generated/pi/skills/rite-build/reference/spec-drift-guard.md

@@ -82,5 +82,6 @@ The detecting phase owns backtracking and the batch sweep. Save
 `return_phase`/`return_next_action`; consume nested Plan/Vet `STOP` internally, complete
 vetted acceptance-preserving remediation, then restore the cursor and failed step.
 Never hand the human an intermediate command. The shared three-attempt causal-fingerprint
-cap still applies: exhaustion produces one technical blocker, while a genuinely
-human-owned decision uses the question format below.
+cap still applies: a spent strategy escalates and a fully escalated fingerprint parks
+under the [retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve),
+while a genuinely human-owned decision uses the question format below.

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
@@ -144,8 +151,8 @@ TTL is crash recovery, not normal cleanup.
    **Do not land on control until review and proof are both green.** Isolated
    `transfer_commit` stays on the worker branch; same-worktree diffs stay
    uncommitted. Serial: [`checkpoint.md`](checkpoint.md), then host may remove the
-   worktree. Parallel: `record-green` only; land with `parallel integrate
-   --apply-to-control` after the batch; `parallel cleanup` removes worktrees.
+   worktree. Parallel: `record-green`, then `parallel integrate
+   --slice <id> --apply-to-control`; `parallel cleanup` removes worktrees.
 5. Reconcile returned reuse, conventions, principles, sources, assumptions,
    decisions, dead ends, follow-ups, gates, and touched files. Persist the
    relevant facts in canonical artifacts, not the wholesale report. A plan-gap

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
@@ -161,7 +170,7 @@ Pull these via `Read` when shaping the plan:
    meaning-changing mappings block. Then run
    `devrites-engine check task-graph <slug>`; a malformed dependency graph blocks
    before Vet rather than spending a reviewer context on invalid tasks. Resolve each
-   `ADVISORY size:` line now (split, or `Size rationale:`); it never blocks.
+   `ADVISORY size:`/`hub:` line now (split or seam slice, or a rationale); never blocking.
 7. **Readiness gate** (`plan-template.md`): require CLEAR coverage; complete acceptance,
    wiring, shared-contract proof, applicable outputs, and rollback; risk-first acyclic order;
    justified deviations; and every horizon item present, with blockers resolved, planning

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

@@ -74,7 +74,7 @@ themselves. The workspace is the canonical store; the handoff is the chat-only d
 6. **In-flight work.** Every dispatch wave opened or sealed without a return (`devrites-engine
    dispatch <slug> status`), running writer handle, held claim id plus paths (`devrites-engine
    claim list --all`), and consumptive action started, each `terminal: yes|unknown` (`yes` only with
-   an admitted return, release, or proof of stop). The live handle exists only in chat. Any
+   an admitted return, release, `dead` claim, or proof of stop). The live handle exists only in chat. Any
    `unknown` row makes item 1 a reconcile step (`dispatch <slug> status`, `parallel status`,
    `claim list --all`), never a writer command: otherwise the next session dispatches a second writer.
 7. **How to resume:** fixed boilerplate (see template below).

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-plan/reference/slicing.md

@@ -168,3 +168,8 @@ Order by dependency, but minimize coupling. A slice that needs three other slice
 is a smell: look for a thinner cut that stands alone. An edge exists only when this slice
 reads something the other produces: write it as `SLICE-001 (via <interface>)`. If you
 cannot name what crosses, drop the edge; a shallow, wide graph runs in parallel.
+
+Slices sharing a file never build side by side: put a hub file's shared edit
+(registry, command table, test harness) in one seam slice the others depend on.
+`check task-graph` prints the `schedule:` and `ADVISORY hub:` lines; inseparable
+writes get `Serial rationale: <why>`. Never merge slices or drop acceptance to widen it.

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/pack/generated/pi/skills/rite-vet/reference/artifacts.md

@@ -103,6 +103,14 @@ From /rite-vet on <iso>. Runner + conventions: <detected framework + command>.
 Link any disposable parser fixture. Preflight values are planning evidence, not post-build proof;
 Prove recaptures the observed command, candidate identity, and result.
 
+## Feature gates
+| Gate | Command | Cwd | Expected |
+|---|---|---|---|
+| <full suite / workspace lint / audit> | <exact command> | <path> | <exit/output> |
+
+Whole-repository rows only: Build runs them per landing
+([tiers](../../rite-build/reference/phase-contract.md#proof-tiers)), Prove on the final candidate.
+
 Commands in this durable artifact are portable repository commands: no RTK or local shell
 aliases, user-specific absolute paths, or temporary proof trees. Evidence records
 the command actually executed.

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

@@ -30,7 +30,7 @@ Before implementation review, check for work beyond the settled spec.
    (over-budget `tasks.md`/`plan.md` from slice or AC count) is a scope finding, not a
    `Budget override`: route to `/rite-plan course-correct` (`MVP cut`) with the
    continuation sequence named; do not vet the whole epic. An `ADVISORY size:`
-   slice without `Size rationale:` is a non-blocking Suggestion to split it.
+   or `hub:` line without its rationale is a non-blocking Suggestion to split or seam it.
 4. **Built-in check.** For each new pattern/infra/concurrency approach, invoke
    `devrites-source-driven` inline to verify current framework/runtime support and cite it. Custom
    work where a built-in suffices is a scope-reduction finding.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.1.1",
+  "version": "6.1.3",
   "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",