devrites 4.0.4 → 4.0.6

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

@@ -5,6 +5,9 @@ the reason and one resume command when an actual human/safety/access action can
 change the state, notify if configured, and stop. Exhausted agent-owned
 technical recovery is terminal for its unchanged causal fingerprint: record
 `Next step: none` and no runnable recovery command. `--ship` cannot bypass them.
+Closure of a prior fingerprint is progress, not exhaustion. A separately evidenced
+Critical/Important failed invariant starts its own bounded fingerprint; it never
+resets or extends the budget of the one just closed.
 
 ## Always stop (irreversible-risk list: from `afk-hitl.md`)
 
@@ -24,8 +27,10 @@ Agent-owned backtracking is not a stop condition while its causal-fingerprint
 budget remains. The active caller invokes the earlier phase inline, follows Vet
 and any bounded remediation, then resumes the originating phase. Persist
 `Next step` for crash recovery, but do not surface it as a command the human must
-submit. Stop only when recovery is exhausted or the remaining choice is a real
-human/safety/access gate.
+submit. Use the repaired finding's narrow Vet recheck to distinguish resolution,
+the same decisive failure, and a genuinely new Critical/Important invariant.
+Stop only after three no-progress attempts on the exact same fingerprint or when
+the remaining choice is a real human/safety/access gate.
 
 On technical exhaustion, preserve the fingerprint, reproduction, attempts, and
 dead ends, then stop without `$rite-plan unblock` or another phase command.

package/pack/generated/codex/skills/rite-build/reference/afk-discipline.md

@@ -71,7 +71,9 @@ tests, types, or lint are red:
 The fail-on-red path:
 
 1. Continue the same wright under `devrites-debug-recovery`, carrying exact output and dead
-   ends; cap writer + recovery at three total attempts per root cause.
+   ends; cap writer + recovery at three no-progress attempts per exact causal fingerprint.
+   A correction that closes the reproduction is progress; a different evidenced
+   Critical/Important invariant starts a separate fingerprint.
 2. Green → record the slice. Product-contract/irreversible ambiguity → write the genuine
    human gate. Missing human-only credential/permission → write a human-intervention gate.
 3. Any other exhausted objective failure → set `Status: blocked`, preserve the reproduction,

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

@@ -33,8 +33,10 @@ See [`one-slice-cycle.md`](one-slice-cycle.md); candidate lifecycle is
    is not success.
 
    Technical failure uses bounded `devrites-debug-recovery`: reapply the host gate
-   before an accepted in-slice correction, keep one root cause/three total attempts,
-   and never rerun an unchanged check. Ask humans only for product decisions,
+   before an accepted in-slice correction, keep one exact fingerprint/three
+   no-progress attempts, and never rerun an unchanged check. A closed reproduction
+   is progress; a different Critical/Important invariant gets its own fingerprint.
+   Ask humans only for product decisions,
    irreversible risk, or genuinely human-only access.
 7. **Record.** After green proof, upsert `touched-files.md`'s authoritative candidate
    manifest from the actual scoped diff with explicit `present`/`deleted` rows;

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

@@ -38,6 +38,8 @@ Pull these via `Read` when relevant:
   webhook / config / error messages / getting-started): **measure** the DX scorecard (run the flow,
   measure time-to-hello-world, and capture verbatim error text), rather than asserting it.
 - `definition-of-done.md`: acceptance, proof, gates, scope, rollback/docs.
+- `one-shot-actions.md`: pre-attempt evidence completeness and no-rerun handling for
+  consumptive proof actions.
 
 
 ## Operating rules
@@ -60,7 +62,10 @@ Pull these via `Read` when relevant:
 - **Prove remains the controlling caller during technical backtracking.** Save
   its return cursor, invoke Plan/Vet or bounded remediation inline, consume each
   nested phase boundary, then resume the failed Prove step. Never make the human
-  submit an agent-owned repair, re-vet, or proof-rerun command.
+  submit an agent-owned repair, re-vet, or proof-rerun command. Apply `afk-hitl.md`
+  progress accounting: only three no-progress attempts on the exact same fingerprint
+  exhaust recovery; a closed prior finding or a genuinely new
+  Critical/Important fingerprint continues inside this invocation.
 
 ## Released-workspace refresh entry
 
@@ -104,6 +109,13 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    substituted commands, malformed manifests, zero-test/skipped/filtered results used as
    behavioral proof, success inferred only from exit status, and any source drift. Static
    gates prove only their named static criterion.
+   Immediately before any consumptive action, apply `one-shot-actions.md` to the
+   live candidate: require the vetted retained-artifact identity, bounds,
+   sanitization, terminal-path fixtures, and cleanup-survival proof. A missing,
+   stale, or disposable-only evidence surface returns to Vet inline and consumes
+   no attempt. Record the admitted artifact identity before execution. After a
+   failed consumptive action, triage from that artifact; never reproduce it by
+   rerunning the action.
 4. **UI feature?** The root applies the browser proof ladder with
    `design-brief.md`, `references.md`, the requested routes, browser harness, and
    allowed scratch path:

package/pack/generated/codex/skills/rite-prove/reference/failure-triage.md

@@ -4,7 +4,10 @@ When a test/build/runtime/browser check fails, triage before fixing. Delegates t
 loop to `devrites-debug-recovery`.
 
 ## Triage ladder
-1. **Reproduce:** run the failing command again; capture the exact error (quote it).
+1. **Reproduce:** for a repeatable command, run it again and capture the exact
+   error (quote it). For a consumptive action under
+   [`one-shot-actions.md`](../../devrites-lib/reference/standards/one-shot-actions.md),
+   never rerun it: use the retained bounded artifact as the reproduction input.
 2. **Classify** the failure:
    - test is right, code is wrong → fix the code (in scope).
    - test is wrong/outdated → that may be **spec drift** (acceptance criteria wrong).
@@ -14,13 +17,17 @@ loop to `devrites-debug-recovery`.
 3. **Isolate:** minimize to the smallest failing case; bisect the diff if needed.
 4. **Fix within scope:** the current slice/feature only. If the fix reaches outside
    scope, stop and record a blocker in `state.md` (then `$rite-plan unblock`).
-5. **Re-run** the same command; confirm green; record both attempts in `evidence.md`.
+5. **Re-run** the same command when it is repeatable; confirm green and record both
+   attempts in `evidence.md`. A consumptive action needs re-vetted evidence
+   completeness and any fresh authorization before a new attempt.
 
 ## Rules
 - Quote the real error text; don't paraphrase it away.
 - Don't loosen/delete a failing assertion to get green: investigate whether it's drift.
 - Don't add blanket retries/sleeps to hide flakiness.
-- Three failed fix attempts on the same root cause consume the shared recovery
-  cap: preserve the reproduction and dead ends, then stop once as a technical
-  blocker. Ask only when the remaining decision is human-owned.
+- Three no-progress attempts on the exact same causal fingerprint consume the
+  shared recovery cap. A recheck that closes the reproduction is progress; a
+  different evidenced Critical/Important invariant gets its own fingerprint.
+  Preserve the reproduction and dead ends, then stop once as a technical blocker.
+  Ask only when the remaining decision is human-owned.
 - A failure you can't fix in scope is a recorded **blocker**, not a silent skip.

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

@@ -20,7 +20,8 @@ but every profile keeps the exact plan-reviewer gate.
 Pull the standard named by the active axis: `principles.md`, `patterns.md`,
 `coding-style.md`, `testing.md`, `spec-grammar.md`, `performance.md`,
 `error-handling.md`, `development-workflow.md`, `afk-hitl.md`,
-`developer-experience.md`, `elicitation.md`, and `definition-of-done.md`.
+`one-shot-actions.md`, `developer-experience.md`, `elicitation.md`, and
+`definition-of-done.md`.
 
 
 ## Operating rules
@@ -43,6 +44,9 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
 - **Honor a recovery origin.** Preserve a valid technical-backtracking return
   cursor throughout review. Agent-owned `NEEDS REPLAN` returns internally to the
   controlling caller; it never becomes a request for the human to invoke Plan.
+- **Recovery recheck is bounded.** A valid technical-backtracking cursor plus a
+  recorded open fingerprint enters the Recovery recheck below. Recovery recheck
+  does not start another Full Vet or repeat unaffected axes/reviewers.
 
 ## Workflow
 0. **Read `.agents/skills/devrites-lib/reference/standards/core.md`** first.
@@ -57,12 +61,26 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    `.agents/skills/devrites-lib/reference/standards/tooling.md`) for placement / blast-radius / reuse checks.
 1. **Set review depth. Never skip this step.** Apply
    [`reference/depth.md`](reference/depth.md) exactly. Every plan leaves a recorded
-   engineering verdict and `test-plan.md` coverage map.
-1a. **Independent pass at every depth.** Freeze the candidate; dispatch exact
+   engineering verdict and `test-plan.md` coverage map. For an admitted Recovery
+   recheck, retain the prior depth and proceed to step 1b instead of starting a new
+   depth/pass.
+1a. **Independent pass at every initial depth.** Freeze the candidate; dispatch exact
    `devrites-plan-reviewer` fresh/read-only and validate its report. Add exact
    `devrites-devex-reviewer` for developer surfaces and require the current exact
    `devrites-strategy-reviewer` verdict after significant Temper. Missing accounts
    block; never substitute inline work.
+1b. **Recovery recheck.** Require the valid return cursor, prior accepted findings,
+   exact open fingerprint/reproduction, repaired candidate identity, changed
+   paths/criteria, and affected evidence from `drift.md` / `evidence.md`. Freeze
+   that packet and dispatch each exact owning reviewer once, fresh/read-only and
+   limited to those inputs. Do not rerun unaffected reviewers or the broad steps
+   2-4 inventory. Mark the prior fingerprint resolved only when discriminating
+   evidence closes its reproduction; otherwise record one no-progress outcome.
+   A newly caused or exposed Critical or Important finding may block only with a
+   different failed invariant, exact evidence in the changed/affected boundary,
+   and a new fingerprint. A Suggestion, Nit, or FYI cannot keep recovery open.
+   Reconcile the common artifact/readiness gates below, then return to the caller
+   or its next repair; never convert the nested result into a human command.
 2. **Scope challenge (blocking gate):** apply §0 of
    [`reference/review-axes.md`](reference/review-axes.md). Search accepted ADRs and
    relevant workspace `decisions.md` files directly. Harden to the smallest
@@ -80,6 +98,11 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    unmeasurable conflict = gap. Record complete SHA-256 provenance inputs. Require
    every behavioral mapping to name a positive,
    discriminating assertion and decisive signal, not merely a command or expected exit zero.
+   Identify every consumptive action under `one-shot-actions.md`. Before admitting
+   it, require the exact durable retention surface, trust-safe diagnostic schema,
+   cleanup ordering, terminal-path coverage, and discriminating fixtures in
+   `test-plan.md`. Missing or stale one-shot evidence completeness is a technical
+   preflight gap; do not spend the action to learn what cleanup would erase.
    Preflight observes; it need not make future behavior pass.
 2c. **Implementation-readiness audit.** Goal-backward map every REQ/AC/NFR, interaction,
    edge/prohibition, and decision-coverage row to a slice and executable proof. Verify

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

@@ -35,6 +35,7 @@ Inventory/currentness: <pass/gaps> · slice order/independence: <pass/gaps> ·
 UX/spec/architecture: <pass/n-a/gaps> · operations/rollout/rollback: <pass/n-a/gaps>
 
 Shared contract proof: <pass | gap: missing/one-sided/duplicated-contract/vague/non-consuming>
+One-shot evidence completeness: <n/a | pass: action + retained artifact + bounds/sanitization + cleanup-survival fixtures | gap: exact missing proof>
 
 ## 3. Axis findings (floor-gated)
 | Axis | Floor band | Findings (sev · confidence) |
@@ -94,6 +95,11 @@ Commands in this durable artifact are portable repository commands: no RTK or lo
 aliases, user-specific absolute paths, or temporary proof trees. Evidence records
 the command actually executed.
 
+## Consumptive action gates
+| Action | Why one-shot/consumptive | Retained artifact | Bounds + sanitization | Terminal-path fixtures | Cleanup survival | Retry authority |
+|---|---|---|---|---|---|---|
+| <exact approved action or n/a> | <one attempt/quota/state/evidence deletion> | <durable operator-controlled path/schema> | <size/cardinality + known/unknown/malformed handling> | <success/known/unknown/hostile> | <assertion> | <none/fresh human authorization> |
+
 Every behavioral row names a positive, discriminating assertion and the decisive output it
 produces. A command or expected exit zero alone is not a behavioral assertion; static gates
 prove only their named static criterion.

package/package.json

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