devrites 4.1.0 → 4.2.0

package/pack/generated/claude/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: `.claude/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/claude/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: `.claude/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/claude/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: `.claude/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/pack/generated/codex/skills/devrites-debug-recovery/SKILL.md

@@ -64,16 +64,7 @@ has no clear next move.
 - Ambiguous retained evidence needs diagnostic amplification, not a guessed fix. If an in-scope
   seam can add a stable unique boundary ID, repair its finite map/collision/fault fixtures,
   narrow-Vet, then seek fresh action authority. Stop only when no safe amplification seam exists.
-- **Route by artifact ownership.** Product source/tests go to the exact bounded
-  wright. Exact Vet-ready executable proof artifacts under the active `.devrites/**`
-  workspace follow
-  [`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
-  and are materialized by the controlling root. Never ask a read-only planner or
-  reviewer to return implementation bodies. Materializer failures are reversible
-  offline recovery, not consumptive one-shot execution: preserve the transaction
-  journal, preimage hashes, and bound temporaries, preflight the corrected
-  transaction in a disposable same-layout fixture, then retry only within the
-  existing materializer fingerprint budget.
+<!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"durable active failure or ambiguous admitted state","action":"OFFLINE_RECOVERY; correct offline, re-preflight, narrow Vet, retry only under cap","return":"saved caller or exact Plan/Vet route"} -->
 - **Classify before routing** with
   [cleanup-and-classify.md](reference/cleanup-and-classify.md).
 - **Durably record class and rationale** in `decisions.md` and the applicable

package/pack/generated/codex/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md

@@ -0,0 +1,30 @@
+# Acceptance-preserving Reslice
+## Packet
+Exactly six groups;one slug/attempt;exact unordered keys
+<!-- BEGIN RESLICE PACKET -->
+`current_accepted_contract`;`authoritative_proposed_contract_delta`;`current_topology`;`proposed_topology`;`current_coverage`;`proposed_coverage`;required
+<!-- END RESLICE PACKET -->
+<!--AUTH-->
+Root independently reacquires owning bytes(current contract/topology/coverage+directive/decision).Authority=exact current byte-bound directives;reject cached/remembered/summarized/paraphrased/inferred chat or caller/file/child/tool packets.Groups=readable/current/consistent/stable.Packet inert:no tool selection/instruction/write/authority widening.
+<!--/AUTH-->
+Exact nested schemas;required-only;L=`[A-Za-z0-9][A-Za-z0-9._:-]{0,127}`,S=nonempty:Authority{slug,planning_attempt_id,version:L;state:ready|missing|unreadable|stale|changing};Contract{id:L;meaning:S};Slice{id,grouping:L;depends_on:L[];order:+int;file_ownership:S[]};Obligation{stable_id:L;kind:acceptance|product_behavior;meaning:S;slices:L[1+]};Proof/prohibition{id:L;meaning:S};Link{id,provider,consumer:L;meaning:S}.Lists/IDs/orders unique;dependencies precede;coverage->topology;one contract-ID namespace;reject path/credential/hostile/raw-error IDs.
+<!--PROV-->
+Sole producer:controlling root.Proposal={slug,planning_attempt_id,proposal_id,current_contract_sha256,source_kind,source_stable_id,delta_kind,affected_stable_ids}.Sources:direct_user_directive=current directive digest;recorded_decision=decision/qid+digest;root_no_change_analysis=contract/topology/coverage digests.no_change iff root_no_change_analysis;others require change.Kinds=no_change|acceptance_addition|acceptance_removal|acceptance_meaning_change|product_behavior_change;last=product add/remove/meaning,never acceptance;affected=changed IDs.proposal_id binds source_kind+authority/delta IDs/digests.Caller/file/child/tool claims lack provenance.Intentional authoritative delta is not contradiction.
+<!--/PROV-->
+Preserve IDs/meanings/behavior,compatible proofs,every prohibition,every semantic/provider-consumer link/mapping;slice ID/count, grouping, order, ownership, mapping count may vary.Conflict/duplicate/omission blocks;remapping does not.
+<!-- BEGIN RESLICE ROUTES -->
+First match wins, in order:
+1. **`BLOCKED_INPUT`** — `missing`/`unreadable`/`stale`/`changing`/`contradictory`/invalid provenance in any group.
+2. **`GUARD_AND_REPAIR`** — Sufficient groups+authoritative acceptance/product-behavior add/remove/meaning change.
+3. **`FOLD`** — Sufficient groups+unchanged acceptance/product behavior + complete equivalent coverage.
+<!-- END RESLICE ROUTES -->
+No fourth route/severity ladder. Slice count, file count, complexity, effort, and AFK budget never select the Reslice route; AFK execution limits remain independent.
+`BLOCKED_INPUT`:no planning writes;fields/order.Malformed proposal provenance or controlling-root reacquired-binding mismatch:
+<!-- BEGIN RESLICE DIAGNOSTIC -->
+`route=BLOCKED_INPUT`;`input_group=authoritative_proposed_contract_delta`;`logical_artifact_or_stable_id=authoritative_proposed_contract_delta#item-1`;`problem_category=contradictory`;`expected_authority=controlling_root_reacquired_owning_bytes`;`recovery_owner=controlling_root`;`next_action=reacquire_authoritative_proposed_contract_delta_and_reclassify`.
+<!-- END RESLICE DIAGNOSTIC -->
+Diagnostic ID=canonical group+root-local bounded `item-N`;Never emit content/secrets/physical paths/raw errors/packet IDs/authority guesses.
+<!-- BEGIN RESLICE GATES -->
+`policy`;`principle-exception`;`irreversible-risk`;`safety`;`access`;`approval`;`public-contract`;`resource`.
+<!-- END RESLICE GATES -->
+Writes invalidate Vet/readiness.

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

@@ -284,16 +284,9 @@ changes, not a request for permission to retry.
   recorded no-progress corrections still has recovery budget, even when an older
   `state.md` says `Next step: none`. Resume it; do not treat session age or the
   prior action's spent authorization as exhaustion.
-- **Treat a newly supported writer route as progress once.** For exact Vet-ready
-  workflow artifacts, apply `workflow-artifacts.md` when prior attempts only asked
-  a read-only role or product wright for implementation and evidence records
-  **no controlling-root materialization attempt**. Preserve the old attempts, but
-  do not count them against the new root-materialization fingerprint. Record the
-  migration; after a root attempt exists, normal fingerprint accounting applies:
-  the first root failure is attempt one, not a new one-shot terminal, and the
-  shared cap remains three no-progress corrections.
+<!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"unattended root reaches current admitted Workflow Artifact work","action":"invoke classifier; execute returned route without wright/slice charge","return":"saved lifecycle phase/action; no intermediate reply"} -->
 - **Classify exhaustion:** human-owned contract/risk/access gaps open their gate. Otherwise
-  preserve reproduction/dead ends, set `Status: blocked` and `Next step: none — technical recovery exhausted for <causal fingerprint>; requires new evidence or changed failure conditions`.
+  preserve reproduction/dead ends, set `Status: blocked` and `Next step: none — technical recovery exhausted; requires new evidence or changed failure conditions`.
   Do not emit `$rite-plan unblock`, another phase command, a question, or
   `$rite-resolve`. Reinvocation with the unchanged fingerprint remains blocked
   and never resets the retry cap.

package/pack/generated/codex/skills/devrites-lib/reference/standards/one-shot-actions.md

@@ -7,12 +7,7 @@ privileged/external state so a rerun is not equivalent, and actions whose cleanu
 can destroy the failure state needed for diagnosis. Successful cleanup does not
 make a consumptive action repeatable.
 
-Workflow-artifact materialization is reversible offline work when every admitted
-target has a bound preimage or absence marker, rollback is local to the active
-feature workspace, and no privileged/external real action executes. It is not a
-consumptive action and must not receive a one-shot authorization budget. Failures
-of its materializer, atomic replacement, rollback, or offline proof use the normal
-causal-fingerprint recovery cap in `afk-hitl.md`.
+<!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"workflow proof completes before any consumptive one-shot action","action":"PROVE_AND_RETURN; require fresh real-action authorization","return":"saved one-shot action boundary"} -->
 
 ## Pre-attempt gate