devrites 4.1.0 → 4.2.0

package/pack/generated/codex/skills/rite-vet/reference/artifacts.md

@@ -3,6 +3,14 @@
 `eng-review.md` records review; `test-plan.md` drives Build. Fold accepted findings
 into `plan.md`/`tasks.md`; prose alone never changes Build.
 
+Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → fold technical topology; invalidate Vet/readiness; affected Vet before Build.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → affected Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
 ## `eng-review.md`: the record
 Write/update `.devrites/work/<slug>/eng-review.md`; never clobber.
 
@@ -146,8 +154,7 @@ Conflicts: Lanes A and B both touch models/ — sequential or coordinate.
 ```
 
 ## Fold-back: the part the build follows
-Vet *is* the plan-hardening phase, so behavior-preserving refinements are written **directly**;
-acceptance/behavior changes route through the **Spec Drift Guard**.
+Vet hardens the plan. Use the marked action before fold-back.
 
 - **Write directly into `plan.md` / `tasks.md`** (single canonical writer: you, not the reviewer):
   - `plan.md` §Scope boundaries ← "NOT in scope" items.
@@ -161,10 +168,7 @@ acceptance/behavior changes route through the **Spec Drift Guard**.
     failure-mode coverage, tightened slice scope, a split of a refactor+behavior slice into two.
     Adjust a slice's `Gate:` upward when vet reveals higher stakes (e.g. an unflagged migration).
   - Re-run the `plan.md` Readiness gate after edits; it must still pass.
-- **Route through the Spec Drift Guard** (record `drift.md` + a recorded decision, then `$rite-plan
-  repair` for any structural reslice) for anything that **changes an acceptance criterion, product
-  behavior, or the spec**, including a scope reduction that drops a criterion. A folded change with
-  no recorded decision is the batch-dump failure.
+- **Reslice:** marked action only; no local predicate.
 - **`decisions.md`:** one ADR per material call: `context · decision · why-not-the-alternative ·
   what-would-change-it`.
 - **`assumptions.md`:** every "we'll probably need X" demoted to an explicit assumption-to-verify,

package/pack/generated/codex/skills/rite-vet/reference/depth.md

@@ -10,6 +10,14 @@ A four-section deep-dive on a one-file reversible plan is wasteful; rubber-stamp
 migration-touching plan is dangerous. Match the effort to the stakes, but **always** leave a
 recorded engineering verdict and a coverage plan.
 
+Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → fold technical topology; invalidate Vet/readiness; affected Vet before Build.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → affected Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
 ## Full pass when ANY trips
 - **Irreversible-risk contact:** the plan touches anything on the `afk-hitl.md` irreversible-risk
   list: destructive data migration, auth/authz boundary, public-API break, external-service
@@ -19,7 +27,7 @@ recorded engineering verdict and a coverage plan.
   `../../devrites-lib/reference/standards/tooling.md`) or an honest estimate) crosses
   module/service boundaries or has many dependents.
 - **Complexity:** `plan.md` touches **>8 files** or adds **>2 new services/modules/classes**.
-- **Multi-slice / multi-day**, or a new dependency / pattern / second design system.
+- **Multi-slice / multi-day work**, new dependency/pattern/design system. Slice count alone never creates a human pause.
 - **The user asked**, or `--full`.
 
 Full pass = §0 scope challenge + all four axes (each walked finding-by-finding) + the failure-mode
@@ -46,8 +54,7 @@ triggers above, **never skipped**. Under the AFK gate ceiling:
 - **Auto-apply (no pause):** hardening findings: added test requirements, error-handling /
   failure-mode coverage, tightened scope, reuse-over-rebuild, dependency-order fixes
   (these never grow acceptance). Record the rationale in `decisions.md`.
-- **Blocking pause:** any finding that **grows scope, adds a slice, changes an acceptance
-  criterion, or alters product behavior**.
+- **Topology findings:** marked action; slice count alone never pauses.
 - **Always pause:** irreversible-risk findings, and any axis still below bar after the
   ≤3-iteration reviewer loop.
 - **Cross-model** is off by default; it runs only if `--cross-model` was explicitly armed.

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

@@ -3,6 +3,14 @@
 Run blocking §0, then the four axes and required outputs. Apply
 [`eng-lenses.md`](eng-lenses.md) throughout; calibrate every finding before presenting it.
 
+Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+
+<!-- BEGIN RESLICE ROUTE-TO-ACTION -->
+- `FOLD` → fold technical topology; invalidate Vet/readiness; affected Vet before Build.
+- `GUARD_AND_REPAIR` → no planning writes; Spec Drift Guard → Clarify → Plan repair → affected Vet.
+- `BLOCKED_INPUT` → no planning writes; exact diagnostic; recover input; reclassify.
+<!-- END RESLICE ROUTE-TO-ACTION -->
+
 ---
 
 ## §0. Scope challenge (blocking gate)
@@ -13,11 +21,11 @@ the settled spec requires.
 1. **What exists?** Find existing code/flows for each sub-problem (use the index per
    [`tooling.md`](../../devrites-lib/reference/standards/tooling.md)). Can the plan capture their outputs instead of building parallel work?
    Reuse → extend → build new; list missed reuse.
-2. **Minimum diff.** Find the smallest acceptance-complete change. Flag non-blocking work;
-   cutting acceptance requires Drift Guard.
+2. **Minimum diff.** Find the smallest contract-complete change. Flag non-blocking work;
+   use the marked action for topology cuts.
 3. **Complexity smell.** **>8 files** or **>2 new services/modules/classes** needs a justified
-   complexity gate; otherwise harden to the smallest acceptance-preserving plan. Ask only if
-   reduction changes acceptance or architecture policy.
+   complexity gate; otherwise harden to the smallest contract-complete plan. Use the
+   marked action for topology reduction.
 4. **Built-in check.** For each new pattern/infra/concurrency approach, dispatch
    `devrites-source-driven` 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": "4.1.0",
+  "version": "4.2.0",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code and Codex",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",