devrites 4.0.5 → 4.0.7

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

@@ -15,6 +15,9 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
 
 ## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
 **Step 0:** Read `.agents/skills/devrites-lib/reference/standards/core.md` and `.agents/skills/devrites-lib/reference/standards/afk-hitl.md` first.
+When the cursor or approved plan contains a consumptive action, also read
+`.agents/skills/devrites-lib/reference/standards/one-shot-actions.md` before any
+stop/continue or execution decision.
 
 ## Operating rules
 - **Use one initial human window.** Run spec and topology-first clarify; arm AFK
@@ -29,6 +32,11 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
   through repair, Vet, bounded implementation correction, and re-proof inside
   the active run. A nested phase `STOP` or intermediate `Next step` is not a
   user handoff; pause only on the shared real stop conditions.
+- **Do not confuse an action budget with recovery exhaustion.** After a failed
+  consumptive action, zero remaining real attempts blocks only another execution.
+  New retained Critical/Important evidence starts offline repair and narrow Vet
+  inside this Autocomplete invocation. Stop for a fresh GO only after that repair
+  changes the failure condition and Vet is READY.
 - **Budget from the post-vet slice count.** Vet may split/add slices.
   `--max-slices N` may lower the cap for a partial run; otherwise build all.
 - **Parse flags only from this invocation.** `--ship`, `--yolo`, `--max-slices`,
@@ -55,7 +63,12 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
 
 ## Workflow
 1. **Orient + parse args.** Resolve the explicit or active slug, require its
-   `state.md`, and read the cursor directly.
+   `state.md`, and read the cursor directly. Before honoring `blocked` with a
+   terminal `next_action`, reconcile retained consumptive-action artifacts and
+   per-fingerprint attempts from `drift.md` / `evidence.md`. A distinct retained
+   fingerprint below its no-progress cap reopens caller-owned offline recovery;
+   reconstruct any missing return cursor only from the current phase plus the
+   exact approved action in `test-plan.md` / evidence, never from chat or guesswork.
    The idea + flags: `--ship` / `--yolo` (continue through ship preflight, then stop
    for literal-GO and native approval), `--max-slices N` (optional lower safety cap for a partial run; default =
    the plan's slice count, i.e. run all planned slices). Parse only the current
@@ -90,7 +103,9 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
    before any later phase runs; the cursor names the last completed phase and the
    effective remaining budget.
 5. **Apply stop conditions at every gate** ([reference/stop-conditions.md](reference/stop-conditions.md)):
-   on hard-risk / blocking / escalating / NO-GO / budget-exhausted / still-low-confidence
+   first route an agent-owned red technical result through the loop's bounded
+   recovery; its `blocked` label alone is not a stop condition. After that, on
+   hard-risk / human-owned blocking / escalating / NO-GO / budget-exhausted / still-low-confidence
    → write `state.md` (`Status`, `Next step`), surface *why*, and **STOP**.
    Exhausted agent-owned technical recovery uses the terminal `Next step: none`
    marker and never hands the user `$rite-plan unblock` or another routine
@@ -120,7 +135,9 @@ Do not write a narrative recap.
 ## Clean baseline and checkpoint mode
 - Before autonomy, require a clean or accepted baseline; refuse unrelated dirty work and record plan artifacts.
 - Arm `.devrites/CHECKPOINT`; `$rite-ship` collapses its local-only proven-slice checkpoints.
-- Stop on risky steps, red gates, NO-GO, stale evidence, or exhausted budget.
+- Red gates block forward advancement and enter caller-owned bounded recovery.
+  Stop only when the shared stop contract classifies risk/HITL or the exact
+  fingerprint's recovery budget is exhausted.
 - One autocomplete pass spans the lifecycle. Each wright returns after one slice;
   explicit `.devrites/AFK` lets the Build root chain green slices under cap/pause rules;
   otherwise HITL stops.

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

@@ -57,6 +57,13 @@ Read each phase's `SKILL.md` and execute that workflow. Workspace files such as
 When a later phase finds an agent-owned technical gap in an earlier phase, the
 Autocomplete root remains the caller:
 
+On cold resume, reconcile the terminal cursor against durable fingerprint
+accounting first. A retained distinct fingerprint with fewer than three
+no-progress corrections is unfinished recovery, not an unchanged terminal stop.
+Restore `return_phase` from the current phase and `return_next_action` only from
+the exact approved action recorded in `test-plan.md` / evidence; ambiguity returns
+to the applicable Vet contract and never licenses execution.
+
 1. Save the originating phase/action in the native return cursor unless a valid
    one already exists.
 2. Invoke the required repair, Vet, remediation, and proof skills inline. After
@@ -71,6 +78,10 @@ Autocomplete root remains the caller:
    a genuinely new Critical/Important fingerprint. Charge only a no-progress
    outcome against the same fingerprint; lower-severity novelty cannot prolong
    the chain.
+   For a failed consumptive action, its spent authorization blocks only another
+   real execution. A retained artifact that identifies a new fingerprint is the
+   offline reproduction input: diagnose, repair, and narrow-Vet it now, then pause
+   for fresh authorization before any next consumptive execution.
 5. When the prerequisite chain is green, restore and consume the return cursor,
    resume the originating phase, and continue the forward table.
 

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

@@ -9,6 +9,12 @@ Closure of a prior fingerprint is progress, not exhaustion. A separately evidenc
 Critical/Important failed invariant starts its own bounded fingerprint; it never
 resets or extends the budget of the one just closed.
 
+An exhausted consumptive-action authorization is not technical-recovery
+exhaustion. It blocks another real action, but retained evidence of a new
+Critical/Important fingerprint must enter offline caller-owned recovery while its
+own no-progress budget remains. After affected Vet is READY, pause for fresh action
+authorization; never execute from the old GO.
+
 ## Always stop (irreversible-risk list: from `afk-hitl.md`)
 
 Regardless of `allow_gates` or `--ship`:
@@ -35,6 +41,10 @@ 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.
 Reinvocation with unchanged evidence remains blocked and does not reset the cap.
+Here `unchanged` means the same fingerprint already has three recorded
+no-progress corrections. A retained fingerprint with remaining offline budget is
+not terminal merely because `state.md` was written by the failed action or a prior
+session ended.
 
 ## Stop on gate severity
 

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
@@ -84,7 +86,10 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
 
 ## Workflow
 0. Read core, load relevant rules above, then resolve the active slug,
-   require its `state.md`, and read the cursor directly.
+   require its `state.md`, and read the cursor directly. On a blocked Prove cold
+   resume, reconcile any retained consumptive-action artifact against recorded
+   no-progress corrections before accepting `next_action: none`; a distinct
+   fingerprint below its cap resumes offline triage without another real action.
 1. **Confirm all slices built.** Read `spec.md`, `tasks.md`, `state.md`,
    `test-plan.md`, and the full diff.
    A missing `test-plan.md` enters caller-owned Vet backtracking; invoke Vet
@@ -107,6 +112,16 @@ 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. Consuming its authorization blocks only another real
+   execution. If the artifact identifies a new Critical/Important fingerprint,
+   continue offline recovery inside this Prove invocation; do not label the new
+   fingerprint exhausted because the action budget is zero.
 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:
@@ -136,6 +151,10 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    Vet inside this invocation, and resume the exact failed proof rung. Ask only
    for a human-owned decision; causal-fingerprint exhaustion stops once with a
    technical blocker rather than another phase command.
+   For a consumptive-action failure, use fixtures or another non-consumptive
+   reproduction to fix and re-vet the retained fingerprint. Once the failure
+   condition is demonstrably changed, stop at the fresh-authorization boundary;
+   only a new human GO may admit the next real attempt.
 8. The root updates `evidence.md`, `browser-evidence.md` (when present),
    `traceability.md`, and `state.md`. Record exactly one binding for the observed
    digest in evidence and browser evidence. New proof goes to canonical

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

@@ -4,17 +4,26 @@ 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).
-   - environment/setup (missing dep, wrong node/ruby) → fix setup or record blocker.
+   - environment/setup (missing dep, wrong node/ruby) → fix it when agent-owned;
+     record a blocker only for human/access ownership, scope overflow, or exhausted
+     fingerprint recovery.
    - flaky (passes on re-run, timing/order) → note it; don't paper over with retries.
    - external dependency down → record blocker; don't fake the result.
 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. Its spent
+   action authorization does not stop offline recovery: a retained new fingerprint
+   enters caller-owned diagnosis, correction, fixtures, and narrow Vet immediately.
 
 ## Rules
 - Quote the real error text; don't paraphrase it away.

package/pack/generated/codex/skills/rite-spec/reference/state-workspace.md

@@ -131,6 +131,13 @@ resume. Never overwrite an existing valid return cursor, and preserve every
 unrelated Markdown byte. `$rite-clarify` applies its stricter native cursor
 protocol below.
 
+On cold resume, a terminal `next_action` is a claim to verify, not a counter.
+Reconcile the exact fingerprint and its attempts in `drift.md` / `evidence.md`.
+If a consumptive action retained a distinct fingerprint below the no-progress
+cap, rewrite the cursor into caller-owned recovery and preserve or reconstruct
+the return rows only from the current phase and approved recorded action. The
+spent action authorization blocks another execution, not that rewrite.
+
 `afk_slices_remaining` is mutable runtime state, not `.devrites/AFK`
 configuration. Only the controlling root writes it under the shared
 [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md#the-sentinel-devritesafk)

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
@@ -97,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.5",
+  "version": "4.0.7",
   "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",