devrites 4.0.6 → 4.0.8

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,17 @@ 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.
+
+Past evidence being irretrievable is not by itself terminal. When an in-scope
+trusted diagnostic seam can make the next retained fingerprint uniquely
+actionable, Autocomplete must run diagnostic-amplification Plan repair and narrow
+Vet inline, then pause for a fresh GO before the single evidence-acquisition
+attempt. Use `Next: none` only after proving no safe in-scope amplification seam
+exists, a real human/risk/scope gate owns it, or bounded recovery is exhausted.
 
 ## Stop on gate severity
 

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

@@ -81,6 +81,10 @@ Pull `development-workflow.md` via `Read` when reshaping slice cadence or DoD cr
    `devrites-plan-drafter` in `repair` mode with only the selected mode, affected artifact
    paths, settled contract, and observed failure/drift. Await one atomic `plan-candidate`;
    the drafter writes nothing and returns human-owned choices separately.
+   When the observed failure is missing or ambiguous consumptive-action evidence,
+   require the drafter to apply `one-shot-actions.md` and return the bounded
+   diagnostic-amplification design, injective boundary map, per-seam fixtures, and
+   collision mutant. Past evidence loss alone is not a terminal conclusion.
 3. Reason about dependencies: [dependency-graph](reference/dependency-graph.md).
    Reconcile `plan.md`'s canonical `Shared contract proof`: changed provider/consumer
    boundaries keep one reused contract artifact ahead of both asserting tests, and unaffected

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

@@ -86,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
@@ -111,11 +114,15 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    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,
+   sanitization, injective boundary map, per-seam fault fixtures, collision mutant,
+   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.
+   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:
@@ -145,6 +152,15 @@ 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.
+   If the retained fingerprint is missing or ambiguous, the lost past evidence
+   does not prove that no safe future acquisition design exists. Treat an in-scope
+   discriminator as a diagnostic-amplification Plan gap: repair and narrow-Vet the
+   boundary map and collision proof inline, then stop for fresh GO before one
+   evidence-acquisition attempt. Do not guess the runtime fix or reuse the old GO.
 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

@@ -11,15 +11,25 @@ loop to `devrites-debug-recovery`.
 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.
+   If consumptive evidence maps to multiple causal seams, this is a
+   diagnostic-amplification plan gap: design and Vet an injective boundary
+   discriminator offline instead of guessing a runtime correction or declaring
+   the cleaned-away past state terminal.
 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 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.
+   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.
+   A separately authorized diagnostic-amplification attempt may acquire the missing
+   discriminator after its evidence design passes Vet; it is not a blind rerun.
 
 ## 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

@@ -100,8 +100,10 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    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
+   cleanup ordering, terminal-path coverage, a finite injective boundary map,
+   per-boundary fault fixtures, and an executed collision mutant in `test-plan.md`.
+   Every retained failure fingerprint must identify one actionable seam; a broad
+   operation/cause shared by multiple emit sites is a gap. 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,

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

@@ -35,7 +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>
+One-shot evidence completeness: <n/a | pass: action + retained artifact + bounds/sanitization + injective boundary map + per-seam/collision/cleanup fixtures | gap: exact missing proof>
 
 ## 3. Axis findings (floor-gated)
 | Axis | Floor band | Findings (sev · confidence) |
@@ -96,9 +96,9 @@ aliases, user-specific absolute paths, or temporary proof trees. Evidence record
 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> |
+| Action | Why one-shot/consumptive | Retained artifact | Bounds + sanitization | Boundary map + collision proof | 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> | <every emit seam -> stable boundary ID; per-seam injection + alias mutant rejected> | <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

package/package.json

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