devrites 6.0.2 → 6.0.4

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

@@ -94,13 +94,15 @@ Lease: `batch_id`, `created_at`, `base_sha`, `n`,
    <id>`; a malformed contract is dropped from the batch and recorded as a
    gap, not dispatched.
 2. Write lease; freeze `B=HEAD`; `parallel create` worktrees.
-3. Dispatch ≤10 wrights in parallel (cwd=worktree; allowlist; prove `HEAD==B`).
+3. Dispatch ≤10 wrights in parallel (cwd=worktree; allowlist; prove `HEAD==B`;
+   one `--slice` per sibling on the wave).
 4. Inspect each returned path list, cumulative diff from `B`, transfer identity,
    and required result fields against the immutable contract. Reject malformed,
    stale, or out-of-scope work. Apply
    [independent Build review](phase-contract.md#independent-build-review): first
-   full inventory, then bounded owning-role rechecks after repairs. Gap or
-   Critical/Important → `gap`; else approved proof → `green|red|gap`.
+   full inventory, then bounded owning-role rechecks after repairs. Run approved
+   proof in the same window as that review. Gap or Critical/Important → `gap`;
+   else proof → `green|red|gap`.
    Reviewer fan-out for a batch is itself batched under
    [`parallel-dispatch.md`](../../devrites-lib/reference/parallel-dispatch.md#scale-limits)
    (≈4 concurrent read-only reviewers, 8 only with disjoint paths), and `max_agents`

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

@@ -14,6 +14,8 @@ Spec Drift Guard still applies.
    `Implementation readiness: READY`, current `Readiness inputs SHA-256`, exact
    required accounts, ID/meaning traceability and green proof preflight.
    Run `devrites-engine check readiness <slug>`; any miss/nonzero blocks.
+   Non-empty `orient` `inflight_waves` is reconciled first: `dispatch return` each
+   role whose account is in hand, else `dispatch abandon --reason` and re-dispatch.
 2. **Select.** Pick the lowest pending slice whose `depends_on` are all built, using
    `orient` `task_graph.slices` plus the `state.md` built list — never by scanning
    `tasks.md`; then `observe slice` it. Restate its goal, ACs, exclusions and exact paths. Include
@@ -33,11 +35,13 @@ Spec Drift Guard still applies.
    spending review. Then compare returned paths and `git diff --name-only` with the
    contract for semantics diff-scope cannot judge (stale/partial/malformed work;
    preserved user work). Restoration uses the bounded wright.
-5. **Review.** Apply [Independent Build review](#independent-build-review).
+5. **Review.** Apply [Independent Build review](#independent-build-review). Run step 6
+   proof in the same window on the same frozen candidate; both gate step 7, and a
+   repair or source-mutating proof voids both.
    Missing verdicts, principle breaches and open Critical/Important block acceptance.
 6. **Prove.** Against the frozen pre-slice candidate inspect
    test hunks for deletion, skipping/focus, tautology, or weaker expectations.
-   Use step 5's exact test-analyst account; missing/adverse criterion verdict is
+   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
    `git diff --name-only`. Missing/weakened/red/source-mutating proof cannot pass.
    Pre-existing/environment-specific claims need a predating same-command,
@@ -70,7 +74,7 @@ inventory: one full-diff `devrites-code-reviewer`, one `devrites-test-analyst`,
 and one exact `devrites-doubt-reviewer` per stood decision that meets
 `devrites-doubt` § When to use (boundary, data model, auth, public API, migration,
 user flow, assumption tests cannot prove); other stood decisions are recorded in
-`decisions.md` without dispatch. Dispatch fresh,
+`decisions.md` without dispatch. Bundles take `--slice <SLICE-ID>`. Dispatch fresh,
 read-only under [`parallel-dispatch.md`](../../devrites-lib/reference/parallel-dispatch.md).
 Wait for every required account to become terminal; missing/gap needs a valid result.
 Fold supported in-scope Critical/Important findings by cause into one inventory.

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

@@ -22,7 +22,9 @@ phases. Never silently code against a known-wrong plan.
 4. Local repair that preserves behavior/scope/architecture/data/UX/security/migration?
      YES, active-slice technical/tool failure → log it and use Build's bounded debug
        recovery. Do not ask for retry authorization and do not re-plan unless the
-       durable remaining-work instructions are wrong.
+       durable remaining-work instructions are wrong. A Workflow Artifact byte fix
+       that keeps every admission row is this case: `OFFLINE_RECOVERY`, then
+       `/rite-vet`'s bytes-only recheck — never `/rite-plan repair`.
      YES, durable plan is wrong → run the batch sweep below, log every
        violation, save the caller's return cursor, then invoke `/rite-plan repair` and `/rite-vet` inline
        without a question — ONE folded repair for all open entries, ONE

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

@@ -55,8 +55,9 @@ worktrees stay forbidden.
 2. Include goal, verbatim acceptance, exclusions, context,
    `test-plan.md` proof commands, applicable standards, and the exact
    `WIP(<slug>):` subject (no slice id). Build the wright's read-set with
-   `devrites-engine context <slug> --phase build --role slice-wright --trigger <set>`
-   and hand it the bundle path; evaluate each trigger condition and pass those
+   `devrites-engine context <slug> --phase build --role slice-wright --slice <SLICE-ID> --trigger <set>`
+   and hand it the bundle path (over-budget artifacts arrive as anchor indexes;
+   read owning sections live). Evaluate each trigger condition and pass those
    that fire (TDD slice → `tdd`, AFK run → `afk`, UI work → `frontend`, …).
    The command prints `unselected=[...]`; an omitted applicable trigger is a gap.
    For each triggered
@@ -80,8 +81,14 @@ is never a task path; see [Workflow Artifact admission](../../devrites-lib/refer
 Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
-<slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and
-`return` on completion (auto-records dispatch/return metrics). Use
+<slice-id> --role slice-wright --slice <SLICE-ID>`, then `start` with the host handle, `seal`, and
+`return` on completion (auto-records dispatch/return metrics). Every 5 wright
+rounds on one slice, `open` blocks for a reslice review: propose an
+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
+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
 substitute a generic agent. Opt-in `/rite-build --parallel N` fans out only under
@@ -106,17 +113,24 @@ TTL is crash recovery, not normal cleanup.
    Reject a result that omits any required key — the bookkeeping arrays count
    whether empty or filled — or adds a path. Root never widens scope or edits
    source.
-2. Inspect the test diff for deletion, skipping, focus markers, or loosened
+2. Run `devrites-engine check windows <slug>` on the wright's diff (`--worktree`
+   in the same tree; `--base <B> --cwd <worktree>` for a parallel transfer
+   commit). Each unwaived hit is repaired through the bounded wright or gets a
+   reasoned `windows.md` row before review; never waive to reach green. Then
+   inspect the test diff for deletion, skipping, focus markers, or loosened
    assertions. Dedicated test analysis treats weakening as Critical.
    Confirm a test for a data/integration/topology risk can actually exhibit that risk;
    mocks that erase it and one-root proof offered for another root are unproven.
 3. Apply [independent Build review](phase-contract.md#independent-build-review)
-   before proof. Human choices return; technical failures follow
+   and, in the same window, run only repository proof already approved by
+   `test-plan.md` against the same frozen candidate; neither waits for the
+   other. Human choices return; technical failures follow
    [the canonical retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
    Derive accounting from recorded reproductions, corrections, and decisive rechecks.
-4. Run only repository proof already approved by `test-plan.md`, then inspect
-   `git diff --name-only` again in case a proof tool changed source.
-   **Do not land on control until review and proof are green.** Isolated
+4. After proof, inspect `git diff --name-only` again in case a proof tool changed
+   source; a change rejects that candidate and voids the concurrent review. A
+   repair wright voids both; rerun both on the new candidate.
+   **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

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

@@ -158,7 +158,8 @@ Pull these via `Read` when shaping the plan:
    acceptance, and names/prose agree. Missing, duplicate, contradictory, or
    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.
+   before Vet rather than spending a reviewer context on invalid tasks. Resolve each
+   `ADVISORY size:` line now (split, or `Size rationale:`); it never blocks.
 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-plan/SKILL.md

@@ -81,7 +81,8 @@ Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standard
      `/rite-spec`, and stop.
    See [replan-and-repair](reference/replan-and-repair.md) for each mode's steps.
 2a. **Draft fresh.** Dispatch `devrites-plan-drafter` in `repair` mode with frozen mode,
-   affected artifacts, settled contract, and failure/drift. Await one atomic, read-only
+   affected artifacts, settled contract, and failure/drift; a slice-bound repair
+   builds its bundle with `--slice <SLICE-ID>` per affected slice. Await one atomic, read-only
    the drafter's `candidate_files` bundle; human choices return separately.
    When the observed failure is missing or ambiguous consumptive-action evidence,
    require the drafter to apply [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md) and return the bounded

package/pack/generated/pi/skills/rite-pressure-test/SKILL.md

@@ -18,7 +18,8 @@ first and write only workspace/ticket artifacts.
 - Search `decisions.md`, accepted ADRs, and relevant archives for rejected directions;
   revive one only with evidence that answers its recorded reason, citing both.
 - Generate 3-5 different shapes, including obvious, smaller, and different-boundary/data/
-  flow options. Use named lenses— inversion, constraint removal, audience shift, 10×, or
+  flow options, plus a **do-nothing baseline** (cost of not building) that every option
+  must beat. Use named lenses— inversion, constraint removal, audience shift, 10×, or
   expert practice—without padding. Borrow analogous mechanisms, not branding.
 - For each, name concrete entities/flows/surfaces, optimization, rough cost, and main risk.
 
@@ -27,7 +28,9 @@ first and write only workspace/ticket artifacts.
 - Weigh options against the goal, constraints, and existing codebase conventions.
 - Prefer felt pain over nice-to-have. Rank differentiation: new capability > 10× gain >
   new audience > new context > better UX > cheaper; do not dress a vitamin as a painkiller.
-- Recommend one, with the reason and the key trade-off accepted.
+- Recommend one, with the reason and the key trade-off accepted. When no option beats
+  the do-nothing baseline, recommend **Kill**: record the reason in `decisions.md` and
+  do not route to `/rite-spec`.
 - Note what would change the recommendation (the decision's hinge).
 
 ## Premise evidence floor
@@ -65,7 +68,7 @@ Done: pressure test complete for <goal>.
 Changed: workspace only
 Evidence: options compared <n>; recommendation <option>; hinge <condition>; premises <supported/assumption/refuted + sources>
 Open: <none | unresolved premise and resolving evidence>
-Next: <when supported: /rite-spec <feature>; when Hold: none — requires <resolving evidence>>
+Next: <when supported: /rite-spec <feature>; when Hold: none — requires <resolving evidence>; when Kill: none — not building: <reason>>
 Record: <investigation-map.md path | questions.md id (Hold) | not applicable>
 ↻ Hygiene: /clear before starting the lifecycle
 ```

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

@@ -173,7 +173,15 @@ plan declares a root-authored executable workflow file, read
    `devrites-engine gates lint <slug> --strict` and resolve every finding before
    READY; the readiness check refuses a missing or malformed ledger but does not
    replace this oracle-quality gate.
-7. **Narrow recheck after edits.** Dispatch the exact plan reviewer once per
+7. **Narrow recheck after edits.** A slice-bound recheck builds its bundle and
+   opens its wave with `--slice <SLICE-ID>` per affected slice (every 5 rechecks
+   per slice need a reslice review, as in Build). **Workflow Artifact bytes-only:**
+   after `OFFLINE_RECOVERY`, a correction leaving every admission/`WA-*` row
+   unchanged records `Workflow Artifact reviewed identity: <re-preflight identity
+   digest>` below the admission block; when `check drift` reports only
+   `reviewed-identity-only`, the reviewer is one fresh `devrites-code-reviewer` on
+   the prior-source→re-preflight diff against those rows (no drafter or plan
+   reviewer); green proceeds to step 8. Otherwise dispatch the exact plan reviewer once per
    fold — one dispatch covering every open fingerprint, preserving
    per correction/fingerprint accounting (each checked individually with its
    accepted findings, changed paths/criteria, new identity, and recorded delta

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

@@ -29,7 +29,8 @@ Before implementation review, check for work beyond the settled spec.
    [feature ceiling](../../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
    (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.
+   continuation sequence named; do not vet the whole epic. An `ADVISORY size:`
+   slice without `Size rationale:` is a non-blocking Suggestion to split 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.
@@ -197,7 +198,10 @@ Use standard `AskUserQuestion`:
    recovery owner, test, handling, and user-visible/silent result. No test + no handling +
    silent = **Critical** (`artifacts.md`).
 4. **Dependency safety:** verify graph/order and shared file/state/contract/lock/port/queue/env
-   conflicts. Correct the plan; native host scheduling needs no lane artifact.
+   conflicts. Each `Dependencies` edge must genuinely gate its slice (consumes an
+   output, interface, or state the predecessor produces); remove an ordering-only
+   edge, since it silently shrinks the parallel set. Correct the plan; native host
+   scheduling needs no lane artifact.
 5. **Build-entry preflight:** commands/cwds, tools, package state, parser/browser smoke,
    prerequisites, and provenance ([`artifacts.md`](artifacts.md)).
 6. **Implementation readiness:** goal-backward coverage, wiring, dependency simulation,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.0.2",
+  "version": "6.0.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",