devrites 4.0.7 → 4.0.8

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
+## [4.0.8](https://github.com/ViktorsBaikers/DevRites/compare/v4.0.7...v4.0.8) (2026-08-08)
+
+### Fixed
+
+* **rite:** require actionable one-shot evidence ([19d996c](https://github.com/ViktorsBaikers/DevRites/commit/19d996c9666febb33e44ecdd91d3254d3a562c8a))
+
 ## [4.0.7](https://github.com/ViktorsBaikers/DevRites/compare/v4.0.6...v4.0.7) (2026-08-08)
 
 ### Fixed

package/README.md

@@ -28,7 +28,7 @@ project-conventional push, tag, or PR action, and archive the workspace.
 Unattended runs may create local WIP checkpoint commits along the way, but they
 remain local unless Ship's disclosed plan includes an approved remote action.
 
-**Status:** [`v4.0.7`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.0.7): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v4.0.8`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.0.8): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 
@@ -101,7 +101,9 @@ Some work needs a different route:
   Ship preflight, discloses the exact Git plan, and waits for a fresh literal
   `GO` plus native approval; without that flag, it stops at Seal GO. A failed
   consumptive proof action never retries blindly: retained evidence drives
-  offline repair and re-vetting, and only the next real attempt needs a new GO.
+  offline repair and re-vetting. Ambiguous retained evidence first drives a vetted
+  boundary-discriminating diagnostic design; only its next real acquisition attempt
+  needs a new GO.
 - [`/rite-upgrade [slug]`](pack/.claude/skills/rite-upgrade/SKILL.md) is a
   compatibility route for an older active workspace that cannot resume. Age or
   cursor form alone never triggers repair; it is not a lifecycle phase.

package/docs/skills.md

@@ -187,7 +187,7 @@ and `Shipped`. Utility commands keep the same compact labels and one-next-action
 
 | Skill | What It Does | Use When |
 |---|---|---|
-| [`rite-prove`](../pack/.claude/skills/rite-prove/SKILL.md) | Positive, discriminating tests + build/runtime/browser evidence. Requires the same candidate digest before/after commands and records the exact binding. Consumptive actions must retain bounded diagnostics through cleanup; a failed action continues offline recovery from that artifact, while any next real execution waits for fresh authorization. | All slices built; ready for full verification. |
+| [`rite-prove`](../pack/.claude/skills/rite-prove/SKILL.md) | Positive, discriminating tests + build/runtime/browser evidence. Requires the same candidate digest before/after commands and records the exact binding. Consumptive actions must retain bounded, causally unique diagnostics through cleanup; ambiguous evidence triggers a vetted diagnostic-amplification design, while any next real execution waits for fresh authorization. | All slices built; ready for full verification. |
 | [`devrites-browser-proof`](../pack/.claude/skills/devrites-browser-proof/SKILL.md) | Browser proof ladder: Playwright MCP → Chrome DevTools MCP → `/run`+`/verify` → project E2E → manual. Auto-emits the structured **Visual Verdict** (per-criterion PASS/FAIL vs `design-brief.md`) for UI slices: consumed by `devrites-frontend-reviewer` and gated at `/rite-seal`. | Scope touches UI. |
 
 ### Polish: normalize, then check the details

package/pack/.claude/agents/devrites-plan-drafter.md

@@ -25,6 +25,13 @@ slices in dependency order. Map every REQ and AC to a slice and executable proof
 name rollback and failure paths; keep acceptance-changing proposals separate. Durable
 proof commands must be portable repository commands, never host-local wrappers,
 user-specific absolute paths, or temporary proof trees.
+For every consumptive action, apply `one-shot-actions.md`: draft a durable bounded
+artifact, a finite injective map from every failure emit seam to a stable non-secret
+boundary ID and offline decision, per-seam fault fixtures, cleanup-survival proof,
+and a collision mutant. If prior retained evidence is missing or ambiguous, draft a
+diagnostic-amplification repair and narrow-Vet proof rather than guessing the
+runtime correction or declaring the old evidence loss terminal. Keep the future
+evidence-acquisition attempt separately gated by fresh human authorization.
 For `plan.md`, include exactly one canonical `Shared contract proof` table when an API,
 event, schema, or other provider/consumer boundary changes. Name a reused canonical artifact
 and asserting provider/consumer tests that both consume it, ordered through slice dependencies.

package/pack/.claude/agents/devrites-plan-reviewer.md

@@ -58,7 +58,10 @@ line, and then assign the band. Do not choose a score and justify it afterward:
    no error handling** is a critical gap. For every consumptive action under
    `one-shot-actions.md`, require durable bounded trust-safe evidence for every
    terminal path plus unknown-well-formed, malformed/hostile, and cleanup-survival
-   fixtures. Missing evidence completeness is `broken`: the plan must not consume
+   fixtures. Require a finite injective map from every failure emit site to one
+   stable non-secret boundary ID and one actionable failure seam, per-seam fault
+   injection, and a negative collision mutant. A shared broad operation/cause is
+   not actionable evidence. Missing evidence completeness is `broken`: the plan must not consume
    the action to discover diagnostics that cleanup can erase.
 
 ## Confidence calibration + verification gate (mandatory)

package/pack/.claude/skills/devrites-debug-recovery/SKILL.md

@@ -63,6 +63,11 @@ has no clear next move.
   retained artifact supplies a new Critical/Important fingerprint, continue
   offline diagnosis, correction, fixtures, and narrow Vet under that fingerprint's
   no-progress budget. Stop for fresh authorization only before the next real action.
+- **Ambiguous retained evidence requires diagnostic amplification, not a guessed
+  runtime fix.** If a trusted in-scope seam can add a stable unique boundary ID,
+  repair its finite map and collision/fault fixtures offline, narrow-Vet it, and
+  stop for fresh authorization before the evidence-acquisition attempt. Missing
+  past evidence is terminal only when no safe amplification seam exists.
 - **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/.claude/skills/devrites-lib/reference/reply-contract.md

@@ -60,7 +60,9 @@ output or an artifact. Use exactly one recommended next action except for
 terminal agent-owned technical exhaustion, which has no runnable action.
 
 Use that terminal case only after three recorded no-progress corrections of the
-exact fingerprint, or when required evidence was irretrievably absent. A spent
+exact fingerprint, or when required evidence was irretrievably absent **and** no safe in-scope diagnostic-amplification seam exists. Loss from the
+past attempt alone is not terminal: repair and Vet a boundary-discriminating
+evidence design, then request fresh authorization for its acquisition attempt. A spent
 consumptive-action authorization plus a retained new fingerprint is not terminal;
 it continues offline recovery and waits for fresh authorization only after repair.
 For a true terminal case use:

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

@@ -27,7 +27,16 @@ the approved `test-plan.md` must bind all of the following:
 4. **Discriminating proof:** fixtures cover success, a known failure, an unknown
    well-formed failure, malformed/hostile input, and cleanup after failure. They
    prove cleanup cannot delete or overwrite the retained failure evidence.
-5. **Recovery sufficiency:** the retained bounded evidence is enough to choose an
+5. **Causal actionability:** every failure record includes a stable non-secret `boundary_id`
+   whose finite map is injective: one retained fingerprint identifies
+   one actionable failure seam and correction class. Broad operation/cause labels
+   are insufficient when multiple emit sites can produce them. `test-plan.md`
+   enumerates every emit site, its boundary ID, expected retained relation, and
+   offline decision.
+6. **Collision proof:** inject a failure at every mapped seam and require its exact
+   boundary ID. Execute a negative mutant that aliases two seams to one retained
+   fingerprint and prove the validator/reviewer rejects it.
+7. **Recovery sufficiency:** the retained bounded evidence is enough to choose an
    offline correction or a truthful terminal classification without consuming
    another attempt.
 
@@ -58,9 +67,29 @@ cap, resume recovery even if a prior writer stored `blocked` / `Next step: none`
 That terminal cursor is valid only for missing retention, a human/safety gate, or
 an actually exhausted fingerprint.
 
-A new real attempt is admissible only after the affected plan and fixtures are
-re-vetted, the failure condition is shown changed, and any required fresh
+A new real attempt is normally admissible only after the affected plan and fixtures
+are re-vetted, the failure condition is shown changed, and any required fresh
 authorization is obtained. Stop at that authorization boundary; never infer it
-from successful offline repair. If the attempt ran without complete retention,
-stop with the observed technical blocker because a blind retry cannot manufacture
-the destroyed evidence.
+from successful offline repair.
+
+## Diagnostic amplification
+
+If a retained artifact is absent or maps one fingerprint to multiple causal
+boundaries, do not guess a runtime correction. The fact that evidence from the
+past attempt is irretrievable does not prove that a safe future evidence-acquisition
+design is unavailable.
+
+When an in-scope trusted seam can add the missing stable discriminator, classify
+the ambiguity as an agent-owned **diagnostic-amplification plan gap**. Without
+executing the action, repair the diagnostic schema, finite boundary map, per-seam
+fault fixtures, cleanup-survival proof, and collision mutant; then run narrow Vet.
+Once READY, stop for fresh authorization before exactly one diagnostic-amplification attempt
+bound to that vetted design and artifact identity. This exception does not
+claim the runtime failure condition changed: the independently proven change is the
+evidence-acquisition invariant, and the attempt's acceptance signal is the promised
+unique retained boundary (or action success).
+
+Terminal `Next: none` is valid only when no safe in-scope diagnostic-amplification
+seam exists, the required change is human/risk/scope owned, or the exact evidence-gap
+fingerprint exhausts bounded recovery. A missing old artifact alone is not terminal,
+and an amplification attempt never inherits authorization from the failed action.

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

@@ -46,6 +46,13 @@ 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
 
 - `blocking` gate fires → synchronous pause.

package/pack/.claude/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/.claude/skills/rite-prove/SKILL.md

@@ -114,7 +114,8 @@ 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
@@ -155,6 +156,11 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    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/.claude/skills/rite-prove/reference/failure-triage.md

@@ -17,6 +17,10 @@ loop to `devrites-debug-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
@@ -24,6 +28,8 @@ loop to `devrites-debug-recovery`.
    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/.claude/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/.claude/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/pack/generated/claude/agents/devrites-plan-drafter.md

@@ -25,6 +25,13 @@ slices in dependency order. Map every REQ and AC to a slice and executable proof
 name rollback and failure paths; keep acceptance-changing proposals separate. Durable
 proof commands must be portable repository commands, never host-local wrappers,
 user-specific absolute paths, or temporary proof trees.
+For every consumptive action, apply `one-shot-actions.md`: draft a durable bounded
+artifact, a finite injective map from every failure emit seam to a stable non-secret
+boundary ID and offline decision, per-seam fault fixtures, cleanup-survival proof,
+and a collision mutant. If prior retained evidence is missing or ambiguous, draft a
+diagnostic-amplification repair and narrow-Vet proof rather than guessing the
+runtime correction or declaring the old evidence loss terminal. Keep the future
+evidence-acquisition attempt separately gated by fresh human authorization.
 For `plan.md`, include exactly one canonical `Shared contract proof` table when an API,
 event, schema, or other provider/consumer boundary changes. Name a reused canonical artifact
 and asserting provider/consumer tests that both consume it, ordered through slice dependencies.

package/pack/generated/claude/agents/devrites-plan-reviewer.md

@@ -58,7 +58,10 @@ line, and then assign the band. Do not choose a score and justify it afterward:
    no error handling** is a critical gap. For every consumptive action under
    `one-shot-actions.md`, require durable bounded trust-safe evidence for every
    terminal path plus unknown-well-formed, malformed/hostile, and cleanup-survival
-   fixtures. Missing evidence completeness is `broken`: the plan must not consume
+   fixtures. Require a finite injective map from every failure emit site to one
+   stable non-secret boundary ID and one actionable failure seam, per-seam fault
+   injection, and a negative collision mutant. A shared broad operation/cause is
+   not actionable evidence. Missing evidence completeness is `broken`: the plan must not consume
    the action to discover diagnostics that cleanup can erase.
 
 ## Confidence calibration + verification gate (mandatory)

package/pack/generated/claude/skills/devrites-debug-recovery/SKILL.md

@@ -63,6 +63,11 @@ has no clear next move.
   retained artifact supplies a new Critical/Important fingerprint, continue
   offline diagnosis, correction, fixtures, and narrow Vet under that fingerprint's
   no-progress budget. Stop for fresh authorization only before the next real action.
+- **Ambiguous retained evidence requires diagnostic amplification, not a guessed
+  runtime fix.** If a trusted in-scope seam can add a stable unique boundary ID,
+  repair its finite map and collision/fault fixtures offline, narrow-Vet it, and
+  stop for fresh authorization before the evidence-acquisition attempt. Missing
+  past evidence is terminal only when no safe amplification seam exists.
 - **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/claude/skills/devrites-lib/reference/reply-contract.md

@@ -60,7 +60,9 @@ output or an artifact. Use exactly one recommended next action except for
 terminal agent-owned technical exhaustion, which has no runnable action.
 
 Use that terminal case only after three recorded no-progress corrections of the
-exact fingerprint, or when required evidence was irretrievably absent. A spent
+exact fingerprint, or when required evidence was irretrievably absent **and** no safe in-scope diagnostic-amplification seam exists. Loss from the
+past attempt alone is not terminal: repair and Vet a boundary-discriminating
+evidence design, then request fresh authorization for its acquisition attempt. A spent
 consumptive-action authorization plus a retained new fingerprint is not terminal;
 it continues offline recovery and waits for fresh authorization only after repair.
 For a true terminal case use:

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

@@ -27,7 +27,16 @@ the approved `test-plan.md` must bind all of the following:
 4. **Discriminating proof:** fixtures cover success, a known failure, an unknown
    well-formed failure, malformed/hostile input, and cleanup after failure. They
    prove cleanup cannot delete or overwrite the retained failure evidence.
-5. **Recovery sufficiency:** the retained bounded evidence is enough to choose an
+5. **Causal actionability:** every failure record includes a stable non-secret `boundary_id`
+   whose finite map is injective: one retained fingerprint identifies
+   one actionable failure seam and correction class. Broad operation/cause labels
+   are insufficient when multiple emit sites can produce them. `test-plan.md`
+   enumerates every emit site, its boundary ID, expected retained relation, and
+   offline decision.
+6. **Collision proof:** inject a failure at every mapped seam and require its exact
+   boundary ID. Execute a negative mutant that aliases two seams to one retained
+   fingerprint and prove the validator/reviewer rejects it.
+7. **Recovery sufficiency:** the retained bounded evidence is enough to choose an
    offline correction or a truthful terminal classification without consuming
    another attempt.
 
@@ -58,9 +67,29 @@ cap, resume recovery even if a prior writer stored `blocked` / `Next step: none`
 That terminal cursor is valid only for missing retention, a human/safety gate, or
 an actually exhausted fingerprint.
 
-A new real attempt is admissible only after the affected plan and fixtures are
-re-vetted, the failure condition is shown changed, and any required fresh
+A new real attempt is normally admissible only after the affected plan and fixtures
+are re-vetted, the failure condition is shown changed, and any required fresh
 authorization is obtained. Stop at that authorization boundary; never infer it
-from successful offline repair. If the attempt ran without complete retention,
-stop with the observed technical blocker because a blind retry cannot manufacture
-the destroyed evidence.
+from successful offline repair.
+
+## Diagnostic amplification
+
+If a retained artifact is absent or maps one fingerprint to multiple causal
+boundaries, do not guess a runtime correction. The fact that evidence from the
+past attempt is irretrievable does not prove that a safe future evidence-acquisition
+design is unavailable.
+
+When an in-scope trusted seam can add the missing stable discriminator, classify
+the ambiguity as an agent-owned **diagnostic-amplification plan gap**. Without
+executing the action, repair the diagnostic schema, finite boundary map, per-seam
+fault fixtures, cleanup-survival proof, and collision mutant; then run narrow Vet.
+Once READY, stop for fresh authorization before exactly one diagnostic-amplification attempt
+bound to that vetted design and artifact identity. This exception does not
+claim the runtime failure condition changed: the independently proven change is the
+evidence-acquisition invariant, and the attempt's acceptance signal is the promised
+unique retained boundary (or action success).
+
+Terminal `Next: none` is valid only when no safe in-scope diagnostic-amplification
+seam exists, the required change is human/risk/scope owned, or the exact evidence-gap
+fingerprint exhausts bounded recovery. A missing old artifact alone is not terminal,
+and an amplification attempt never inherits authorization from the failed action.

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

@@ -46,6 +46,13 @@ 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
 
 - `blocking` gate fires → synchronous pause.

package/pack/generated/claude/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/claude/skills/rite-prove/SKILL.md

@@ -114,7 +114,8 @@ 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
@@ -155,6 +156,11 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    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/claude/skills/rite-prove/reference/failure-triage.md

@@ -17,6 +17,10 @@ loop to `devrites-debug-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
@@ -24,6 +28,8 @@ loop to `devrites-debug-recovery`.
    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/claude/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/claude/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/pack/generated/codex/agents/devrites-plan-drafter.toml

@@ -23,6 +23,13 @@ slices in dependency order. Map every REQ and AC to a slice and executable proof
 name rollback and failure paths; keep acceptance-changing proposals separate. Durable
 proof commands must be portable repository commands, never host-local wrappers,
 user-specific absolute paths, or temporary proof trees.
+For every consumptive action, apply `one-shot-actions.md`: draft a durable bounded
+artifact, a finite injective map from every failure emit seam to a stable non-secret
+boundary ID and offline decision, per-seam fault fixtures, cleanup-survival proof,
+and a collision mutant. If prior retained evidence is missing or ambiguous, draft a
+diagnostic-amplification repair and narrow-Vet proof rather than guessing the
+runtime correction or declaring the old evidence loss terminal. Keep the future
+evidence-acquisition attempt separately gated by fresh human authorization.
 For `plan.md`, include exactly one canonical `Shared contract proof` table when an API,
 event, schema, or other provider/consumer boundary changes. Name a reused canonical artifact
 and asserting provider/consumer tests that both consume it, ordered through slice dependencies.

package/pack/generated/codex/agents/devrites-plan-reviewer.toml

@@ -56,7 +56,10 @@ line, and then assign the band. Do not choose a score and justify it afterward:
    no error handling** is a critical gap. For every consumptive action under
    `one-shot-actions.md`, require durable bounded trust-safe evidence for every
    terminal path plus unknown-well-formed, malformed/hostile, and cleanup-survival
-   fixtures. Missing evidence completeness is `broken`: the plan must not consume
+   fixtures. Require a finite injective map from every failure emit site to one
+   stable non-secret boundary ID and one actionable failure seam, per-seam fault
+   injection, and a negative collision mutant. A shared broad operation/cause is
+   not actionable evidence. Missing evidence completeness is `broken`: the plan must not consume
    the action to discover diagnostics that cleanup can erase.
 
 ## Confidence calibration + verification gate (mandatory)

package/pack/generated/codex/skills/devrites-debug-recovery/SKILL.md

@@ -63,6 +63,11 @@ has no clear next move.
   retained artifact supplies a new Critical/Important fingerprint, continue
   offline diagnosis, correction, fixtures, and narrow Vet under that fingerprint's
   no-progress budget. Stop for fresh authorization only before the next real action.
+- **Ambiguous retained evidence requires diagnostic amplification, not a guessed
+  runtime fix.** If a trusted in-scope seam can add a stable unique boundary ID,
+  repair its finite map and collision/fault fixtures offline, narrow-Vet it, and
+  stop for fresh authorization before the evidence-acquisition attempt. Missing
+  past evidence is terminal only when no safe amplification seam exists.
 - **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/reply-contract.md

@@ -60,7 +60,9 @@ output or an artifact. Use exactly one recommended next action except for
 terminal agent-owned technical exhaustion, which has no runnable action.
 
 Use that terminal case only after three recorded no-progress corrections of the
-exact fingerprint, or when required evidence was irretrievably absent. A spent
+exact fingerprint, or when required evidence was irretrievably absent **and** no safe in-scope diagnostic-amplification seam exists. Loss from the
+past attempt alone is not terminal: repair and Vet a boundary-discriminating
+evidence design, then request fresh authorization for its acquisition attempt. A spent
 consumptive-action authorization plus a retained new fingerprint is not terminal;
 it continues offline recovery and waits for fresh authorization only after repair.
 For a true terminal case use:

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

@@ -27,7 +27,16 @@ the approved `test-plan.md` must bind all of the following:
 4. **Discriminating proof:** fixtures cover success, a known failure, an unknown
    well-formed failure, malformed/hostile input, and cleanup after failure. They
    prove cleanup cannot delete or overwrite the retained failure evidence.
-5. **Recovery sufficiency:** the retained bounded evidence is enough to choose an
+5. **Causal actionability:** every failure record includes a stable non-secret `boundary_id`
+   whose finite map is injective: one retained fingerprint identifies
+   one actionable failure seam and correction class. Broad operation/cause labels
+   are insufficient when multiple emit sites can produce them. `test-plan.md`
+   enumerates every emit site, its boundary ID, expected retained relation, and
+   offline decision.
+6. **Collision proof:** inject a failure at every mapped seam and require its exact
+   boundary ID. Execute a negative mutant that aliases two seams to one retained
+   fingerprint and prove the validator/reviewer rejects it.
+7. **Recovery sufficiency:** the retained bounded evidence is enough to choose an
    offline correction or a truthful terminal classification without consuming
    another attempt.
 
@@ -58,9 +67,29 @@ cap, resume recovery even if a prior writer stored `blocked` / `Next step: none`
 That terminal cursor is valid only for missing retention, a human/safety gate, or
 an actually exhausted fingerprint.
 
-A new real attempt is admissible only after the affected plan and fixtures are
-re-vetted, the failure condition is shown changed, and any required fresh
+A new real attempt is normally admissible only after the affected plan and fixtures
+are re-vetted, the failure condition is shown changed, and any required fresh
 authorization is obtained. Stop at that authorization boundary; never infer it
-from successful offline repair. If the attempt ran without complete retention,
-stop with the observed technical blocker because a blind retry cannot manufacture
-the destroyed evidence.
+from successful offline repair.
+
+## Diagnostic amplification
+
+If a retained artifact is absent or maps one fingerprint to multiple causal
+boundaries, do not guess a runtime correction. The fact that evidence from the
+past attempt is irretrievable does not prove that a safe future evidence-acquisition
+design is unavailable.
+
+When an in-scope trusted seam can add the missing stable discriminator, classify
+the ambiguity as an agent-owned **diagnostic-amplification plan gap**. Without
+executing the action, repair the diagnostic schema, finite boundary map, per-seam
+fault fixtures, cleanup-survival proof, and collision mutant; then run narrow Vet.
+Once READY, stop for fresh authorization before exactly one diagnostic-amplification attempt
+bound to that vetted design and artifact identity. This exception does not
+claim the runtime failure condition changed: the independently proven change is the
+evidence-acquisition invariant, and the attempt's acceptance signal is the promised
+unique retained boundary (or action success).
+
+Terminal `Next: none` is valid only when no safe in-scope diagnostic-amplification
+seam exists, the required change is human/risk/scope owned, or the exact evidence-gap
+fingerprint exhausts bounded recovery. A missing old artifact alone is not terminal,
+and an amplification attempt never inherits authorization from the failed action.

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

@@ -46,6 +46,13 @@ 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
 
 - `blocking` gate fires → synchronous pause.

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

@@ -114,7 +114,8 @@ 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
@@ -155,6 +156,11 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    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

@@ -17,6 +17,10 @@ loop to `devrites-debug-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
@@ -24,6 +28,8 @@ loop to `devrites-debug-recovery`.
    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-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.7",
+  "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",