devrites 4.0.11 → 4.0.12

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.12](https://github.com/ViktorsBaikers/DevRites/compare/v4.0.11...v4.0.12) (2026-08-09)
+
+### Fixed
+
+* **rite:** keep internal replans in autocomplete ([9dbbd30](https://github.com/ViktorsBaikers/DevRites/commit/9dbbd30d6fbb088f2b175b6c4af06a9d7e5e9114))
+
 ## [4.0.11](https://github.com/ViktorsBaikers/DevRites/compare/v4.0.10...v4.0.11) (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.11`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.0.11): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v4.0.12`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.0.12): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 
@@ -107,6 +107,8 @@ Some work needs a different route:
   Autocomplete reopens a stale missing-writer stop once instead of preserving the
   obsolete recovery count. The first real root-materializer failure then counts as
   attempt one under normal fingerprint recovery; it is not terminal by itself.
+  Likewise, an internal `NEEDS_REPLAN` result stays inside Autocomplete: it runs
+  the next Plan repair and narrow Vet without returning a command to the user.
 - [`/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

@@ -222,7 +222,7 @@ and `Shipped`. Utility commands keep the same compact labels and one-next-action
 
 | Skill | What It Does | Use When |
 |---|---|---|
-| [`rite-autocomplete`](../pack/.claude/skills/rite-autocomplete/SKILL.md) | Runs the whole lifecycle unattended (spec → clarify → … → seal → ship), choosing the recommended option at each soft gate and recording the rationale in `decisions.md`. A vague prompt triggers one up-front spec/clarify window; after decision coverage is CLEAR it runs without per-phase iteration, pausing only for genuine product/scope/policy decisions, irreversible risk, human-only access/actions, NO-GO, or budget exhaustion. Objective red checks use bounded technical recovery, including cold-resume recovery from retained one-shot evidence and one-time migration of stale missing-writer stops when an upgraded contract supplies the first supported workflow-artifact writer. That migration applies once, but the first real materializer failure is only attempt one under normal bounded recovery. Spending an action authorization blocks only another real execution, not offline repair. Default stops at Seal GO; `--ship` (alias `--yolo`) reaches Ship preflight but still requires a fresh literal `GO` and native approval. | "Autocomplete", "do the whole thing", "run the full cycle", "one-shot this feature". |
+| [`rite-autocomplete`](../pack/.claude/skills/rite-autocomplete/SKILL.md) | Runs the whole lifecycle unattended (spec → clarify → … → seal → ship), choosing the recommended option at each soft gate and recording the rationale in `decisions.md`. A vague prompt triggers one up-front spec/clarify window; after decision coverage is CLEAR it runs without per-phase iteration, pausing only for genuine product/scope/policy decisions, irreversible risk, human-only access/actions, NO-GO, or budget exhaustion. Objective red checks use bounded technical recovery, including cold-resume recovery from retained one-shot evidence and one-time migration of stale missing-writer stops when an upgraded contract supplies the first supported workflow-artifact writer. That migration applies once, but the first real materializer failure is only attempt one under normal bounded recovery. Internal `NEEDS_REPLAN` and newly discovered agent-owned review findings remain caller-owned backward edges rather than user-facing stops. Spending an action authorization blocks only another real execution, not offline repair. Default stops at Seal GO; `--ship` (alias `--yolo`) reaches Ship preflight but still requires a fresh literal `GO` and native approval. | "Autocomplete", "do the whole thing", "run the full cycle", "one-shot this feature". |
 | [`rite-zoom-out`](../pack/.claude/skills/rite-zoom-out/SKILL.md) | Map the modules, callers, callees, and decisions in an unfamiliar area using the project's domain glossary. | Explicit-only: `/rite-zoom-out` / `/rite zoom-out`. |
 | [`rite-prototype`](../pack/.claude/skills/rite-prototype/SKILL.md) | Throwaway code answering ONE design question: logic harness OR 2 to 4 UI variations on one route. | Explicit-only: `/rite-prototype` / `/rite prototype`. |
 | [`rite-handoff`](../pack/.claude/skills/rite-handoff/SKILL.md) | Compact chat session → handoff doc. References existing `.devrites/work/<slug>/` artifacts by path. | Explicit-only: `/rite-handoff` / `/rite handoff`. |

package/pack/.claude/skills/devrites-lib/reference/reply-contract.md

@@ -6,6 +6,12 @@ artifact.
 
 Keep the reply compact and evidence-backed:
 
+When an active rite is the controlling caller, Intermediate `NEEDS_REPLAN`, a
+nested phase `STOP`, and a routine Plan/Vet `Next step` are not eligible completion
+states. Return them to the caller without a user-facing reply. Autocomplete may
+use the shapes below only after its requested rest point or a shared genuine
+human/safety/access/exhausted-recovery stop is reached.
+
 ```text
 Done: <result in one sentence>
 Changed: <artifact or source paths>

package/pack/.claude/skills/devrites-lib/reference/standards/context-hygiene.md

@@ -54,6 +54,15 @@ Resume next session with: <single command, e.g. /rite-build slice 2>
 This is advice, not a gate. The user can ignore it. It reports a trade-off the model
 cannot inspect directly because no API reports context fullness.
 
+### Autocomplete exception
+
+Do not emit the footer or a resume command for a nested phase controlled by
+Autocomplete. An intermediate `NEEDS_REPLAN`, Plan/Vet checkpoint, or new
+agent-owned fingerprint must continue in the same invocation under the caller
+contract. If the host compacts, persist the current checkpoint and resume from it;
+context pressure is never permission to turn routine backtracking into a user
+handoff.
+
 ## When NOT to recommend `/clear` or `/compact`
 
 - The current phase is read-only and cheap (`/rite-status`, `/rite` menu): no

package/pack/.claude/skills/devrites-lib/reference/standards/core.md

@@ -40,7 +40,10 @@ Repository conventions follow [Precedence](#precedence).
 ## Lifecycle rest points
 
 Before advancing a phase, run `devrites-engine check readiness <slug>` for
-structure; exact agents/checklists own semantics. Persist and stop on block.
+structure; exact agents/checklists own semantics. Standalone rites persist and stop
+on block. Under an active controlling caller, an agent-owned technical block is a
+persisted backward edge: return it to that caller instead of producing a
+user-facing stop.
 After native proof/review, `/rite-seal` runs `devrites-engine check seal <slug>`
 for structure/freshness, not prose. HITL/blocked stops follow
 [Persistence before stopping](#persistence-before-stopping-handoff-discipline).

package/pack/.claude/skills/rite-autocomplete/SKILL.md

@@ -36,6 +36,11 @@ the terminal cursor or its recovery count.
   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.
+- **Treat technical readiness as routing, not completion.** `NEEDS_REPLAN` is a backward edge
+  to Plan repair and narrow Vet; `NEEDS_CLARIFICATION` is likewise internal when
+  decision coverage can be resolved from existing authority. Neither state may
+  end Autocomplete unless its underlying fingerprint is actually exhausted or a
+  human/safety/access decision is required.
 - **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
@@ -73,6 +78,9 @@ the terminal cursor or its recovery count.
    fingerprint below its no-progress cap reopens caller-owned offline recovery;
    a stale pre-ownership workflow-artifact writer stop reopens under
    `workflow-artifacts.md` when no controlling-root materialization attempt exists.
+   A `NEEDS_REPLAN` cold resume with a valid technical return cursor immediately
+   invokes Plan repair and Recovery Vet before selecting a forward phase or
+   emitting any reply.
    That materialization runs directly as non-consumptive prerequisite recovery,
    even with no pending product slice or AFK budget; it does not re-ask an answered
    human gate.

package/pack/.claude/skills/rite-autocomplete/reference/loop.md

@@ -104,6 +104,24 @@ for a human-owned decision or mandatory safety/access action. Exhausted
 agent-owned recovery stops once with its reproduction and dead ends, never with
 another routine Plan/Vet command.
 
+## Continuous caller obligation
+
+No user-facing reply is permitted while the durable state contains an
+agent-owned `NEEDS_REPLAN`, an intermediate Plan/Vet `next_action`, or a distinct
+Critical/Important fingerprint with remaining recovery budget. Invoke the exact
+next Plan repair and Recovery Vet immediately. A narrow reviewer closing its input
+finding and exposing another Critical/Important invariant is progress: close the
+old fingerprint, open the new one, and continue without handing a command to the
+user.
+
+The number of completed repair/Vet cycles is not a stop condition and cannot be
+used as a surrogate recovery budget. Only three no-progress corrections of the
+same exact fingerprint exhaust. Context pressure, compaction, session duration,
+or a nested skill's completion footer also cannot convert an internal checkpoint
+into a stop; persist the checkpoint and resume from it inside the same controlling
+invocation. Autocomplete may emit its final reply only after reaching its requested
+rest point or one of the shared human/safety/access/exhaustion stop conditions.
+
 ## Between phases
 
 - Re-read the active workspace before each phase (don't trust chat memory).

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

@@ -29,6 +29,11 @@ on exhaustion, stop as a technical blocker unless human-owned.
 
 ## Not a stop: agent-owned backtracking
 
+`NEEDS_REPLAN` is not a stop condition under an active Autocomplete caller. It
+blocks forward advancement, persists the return cursor, and immediately routes
+Plan repair plus Recovery Vet. The same applies to any intermediate nested
+`STOP`/`Next step` whose underlying decision is agent-owned.
+
 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

package/pack/.claude/skills/rite-vet/SKILL.md

@@ -144,8 +144,12 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    After each fold-back rerun step 2a; missing/meaning-changing mappings block.
    Keep `state.md` non-READY for step 6.
 6. **One narrow recheck after edits.** If the candidate changed, dispatch exact
-   `devrites-plan-reviewer` once with accepted findings, changed paths/criteria,
-   and new identity. No full or third loop; if it changes the plan, repeat step 5.
+   `devrites-plan-reviewer` once per correction/fingerprint with accepted findings,
+   changed paths/criteria, and new identity. Within that same correction, no full
+   or third loop; if it changes the plan, repeat step 5. If the recheck closes its
+   input fingerprint but discovers a distinct Critical/Important invariant, return
+   that new fingerprint to the controlling caller as progress. It may start the
+   next bounded Plan/Recovery-Vet cycle; the prior reviewer count is not exhaustion.
    Then close the matrix and rerun step 2a's ID-and-meaning audit.
 
 6a. **Build readback.** From the final owning artifacts, add a cited five-line

package/pack/generated/claude/skills/devrites-lib/reference/reply-contract.md

@@ -6,6 +6,12 @@ artifact.
 
 Keep the reply compact and evidence-backed:
 
+When an active rite is the controlling caller, Intermediate `NEEDS_REPLAN`, a
+nested phase `STOP`, and a routine Plan/Vet `Next step` are not eligible completion
+states. Return them to the caller without a user-facing reply. Autocomplete may
+use the shapes below only after its requested rest point or a shared genuine
+human/safety/access/exhausted-recovery stop is reached.
+
 ```text
 Done: <result in one sentence>
 Changed: <artifact or source paths>

package/pack/generated/claude/skills/devrites-lib/reference/standards/context-hygiene.md

@@ -54,6 +54,15 @@ Resume next session with: <single command, e.g. /rite-build slice 2>
 This is advice, not a gate. The user can ignore it. It reports a trade-off the model
 cannot inspect directly because no API reports context fullness.
 
+### Autocomplete exception
+
+Do not emit the footer or a resume command for a nested phase controlled by
+Autocomplete. An intermediate `NEEDS_REPLAN`, Plan/Vet checkpoint, or new
+agent-owned fingerprint must continue in the same invocation under the caller
+contract. If the host compacts, persist the current checkpoint and resume from it;
+context pressure is never permission to turn routine backtracking into a user
+handoff.
+
 ## When NOT to recommend `/clear` or `/compact`
 
 - The current phase is read-only and cheap (`/rite-status`, `/rite` menu): no

package/pack/generated/claude/skills/devrites-lib/reference/standards/core.md

@@ -40,7 +40,10 @@ Repository conventions follow [Precedence](#precedence).
 ## Lifecycle rest points
 
 Before advancing a phase, run `devrites-engine check readiness <slug>` for
-structure; exact agents/checklists own semantics. Persist and stop on block.
+structure; exact agents/checklists own semantics. Standalone rites persist and stop
+on block. Under an active controlling caller, an agent-owned technical block is a
+persisted backward edge: return it to that caller instead of producing a
+user-facing stop.
 After native proof/review, `/rite-seal` runs `devrites-engine check seal <slug>`
 for structure/freshness, not prose. HITL/blocked stops follow
 [Persistence before stopping](#persistence-before-stopping-handoff-discipline).

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

@@ -36,6 +36,11 @@ the terminal cursor or its recovery count.
   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.
+- **Treat technical readiness as routing, not completion.** `NEEDS_REPLAN` is a backward edge
+  to Plan repair and narrow Vet; `NEEDS_CLARIFICATION` is likewise internal when
+  decision coverage can be resolved from existing authority. Neither state may
+  end Autocomplete unless its underlying fingerprint is actually exhausted or a
+  human/safety/access decision is required.
 - **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
@@ -73,6 +78,9 @@ the terminal cursor or its recovery count.
    fingerprint below its no-progress cap reopens caller-owned offline recovery;
    a stale pre-ownership workflow-artifact writer stop reopens under
    `workflow-artifacts.md` when no controlling-root materialization attempt exists.
+   A `NEEDS_REPLAN` cold resume with a valid technical return cursor immediately
+   invokes Plan repair and Recovery Vet before selecting a forward phase or
+   emitting any reply.
    That materialization runs directly as non-consumptive prerequisite recovery,
    even with no pending product slice or AFK budget; it does not re-ask an answered
    human gate.

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

@@ -104,6 +104,24 @@ for a human-owned decision or mandatory safety/access action. Exhausted
 agent-owned recovery stops once with its reproduction and dead ends, never with
 another routine Plan/Vet command.
 
+## Continuous caller obligation
+
+No user-facing reply is permitted while the durable state contains an
+agent-owned `NEEDS_REPLAN`, an intermediate Plan/Vet `next_action`, or a distinct
+Critical/Important fingerprint with remaining recovery budget. Invoke the exact
+next Plan repair and Recovery Vet immediately. A narrow reviewer closing its input
+finding and exposing another Critical/Important invariant is progress: close the
+old fingerprint, open the new one, and continue without handing a command to the
+user.
+
+The number of completed repair/Vet cycles is not a stop condition and cannot be
+used as a surrogate recovery budget. Only three no-progress corrections of the
+same exact fingerprint exhaust. Context pressure, compaction, session duration,
+or a nested skill's completion footer also cannot convert an internal checkpoint
+into a stop; persist the checkpoint and resume from it inside the same controlling
+invocation. Autocomplete may emit its final reply only after reaching its requested
+rest point or one of the shared human/safety/access/exhaustion stop conditions.
+
 ## Between phases
 
 - Re-read the active workspace before each phase (don't trust chat memory).

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

@@ -29,6 +29,11 @@ on exhaustion, stop as a technical blocker unless human-owned.
 
 ## Not a stop: agent-owned backtracking
 
+`NEEDS_REPLAN` is not a stop condition under an active Autocomplete caller. It
+blocks forward advancement, persists the return cursor, and immediately routes
+Plan repair plus Recovery Vet. The same applies to any intermediate nested
+`STOP`/`Next step` whose underlying decision is agent-owned.
+
 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

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

@@ -144,8 +144,12 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    After each fold-back rerun step 2a; missing/meaning-changing mappings block.
    Keep `state.md` non-READY for step 6.
 6. **One narrow recheck after edits.** If the candidate changed, dispatch exact
-   `devrites-plan-reviewer` once with accepted findings, changed paths/criteria,
-   and new identity. No full or third loop; if it changes the plan, repeat step 5.
+   `devrites-plan-reviewer` once per correction/fingerprint with accepted findings,
+   changed paths/criteria, and new identity. Within that same correction, no full
+   or third loop; if it changes the plan, repeat step 5. If the recheck closes its
+   input fingerprint but discovers a distinct Critical/Important invariant, return
+   that new fingerprint to the controlling caller as progress. It may start the
+   next bounded Plan/Recovery-Vet cycle; the prior reviewer count is not exhaustion.
    Then close the matrix and rerun step 2a's ID-and-meaning audit.
 
 6a. **Build readback.** From the final owning artifacts, add a cited five-line

package/pack/generated/codex/skills/devrites-lib/reference/reply-contract.md

@@ -6,6 +6,12 @@ artifact.
 
 Keep the reply compact and evidence-backed:
 
+When an active rite is the controlling caller, Intermediate `NEEDS_REPLAN`, a
+nested phase `STOP`, and a routine Plan/Vet `Next step` are not eligible completion
+states. Return them to the caller without a user-facing reply. Autocomplete may
+use the shapes below only after its requested rest point or a shared genuine
+human/safety/access/exhausted-recovery stop is reached.
+
 ```text
 Done: <result in one sentence>
 Changed: <artifact or source paths>

package/pack/generated/codex/skills/devrites-lib/reference/standards/context-hygiene.md

@@ -54,6 +54,15 @@ Resume next session with: <single command, e.g. $rite-build slice 2>
 This is advice, not a gate. The user can ignore it. It reports a trade-off the model
 cannot inspect directly because no API reports context fullness.
 
+### Autocomplete exception
+
+Do not emit the footer or a resume command for a nested phase controlled by
+Autocomplete. An intermediate `NEEDS_REPLAN`, Plan/Vet checkpoint, or new
+agent-owned fingerprint must continue in the same invocation under the caller
+contract. If the host compacts, persist the current checkpoint and resume from it;
+context pressure is never permission to turn routine backtracking into a user
+handoff.
+
 ## When NOT to recommend `/clear` or `/compact`
 
 - The current phase is read-only and cheap (`$rite-status`, `$rite` menu): no

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

@@ -40,7 +40,10 @@ Repository conventions follow [Precedence](#precedence).
 ## Lifecycle rest points
 
 Before advancing a phase, run `devrites-engine check readiness <slug>` for
-structure; exact agents/checklists own semantics. Persist and stop on block.
+structure; exact agents/checklists own semantics. Standalone rites persist and stop
+on block. Under an active controlling caller, an agent-owned technical block is a
+persisted backward edge: return it to that caller instead of producing a
+user-facing stop.
 After native proof/review, `$rite-seal` runs `devrites-engine check seal <slug>`
 for structure/freshness, not prose. HITL/blocked stops follow
 [Persistence before stopping](#persistence-before-stopping-handoff-discipline).

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

@@ -36,6 +36,11 @@ the terminal cursor or its recovery count.
   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.
+- **Treat technical readiness as routing, not completion.** `NEEDS_REPLAN` is a backward edge
+  to Plan repair and narrow Vet; `NEEDS_CLARIFICATION` is likewise internal when
+  decision coverage can be resolved from existing authority. Neither state may
+  end Autocomplete unless its underlying fingerprint is actually exhausted or a
+  human/safety/access decision is required.
 - **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
@@ -73,6 +78,9 @@ the terminal cursor or its recovery count.
    fingerprint below its no-progress cap reopens caller-owned offline recovery;
    a stale pre-ownership workflow-artifact writer stop reopens under
    `workflow-artifacts.md` when no controlling-root materialization attempt exists.
+   A `NEEDS_REPLAN` cold resume with a valid technical return cursor immediately
+   invokes Plan repair and Recovery Vet before selecting a forward phase or
+   emitting any reply.
    That materialization runs directly as non-consumptive prerequisite recovery,
    even with no pending product slice or AFK budget; it does not re-ask an answered
    human gate.

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

@@ -104,6 +104,24 @@ for a human-owned decision or mandatory safety/access action. Exhausted
 agent-owned recovery stops once with its reproduction and dead ends, never with
 another routine Plan/Vet command.
 
+## Continuous caller obligation
+
+No user-facing reply is permitted while the durable state contains an
+agent-owned `NEEDS_REPLAN`, an intermediate Plan/Vet `next_action`, or a distinct
+Critical/Important fingerprint with remaining recovery budget. Invoke the exact
+next Plan repair and Recovery Vet immediately. A narrow reviewer closing its input
+finding and exposing another Critical/Important invariant is progress: close the
+old fingerprint, open the new one, and continue without handing a command to the
+user.
+
+The number of completed repair/Vet cycles is not a stop condition and cannot be
+used as a surrogate recovery budget. Only three no-progress corrections of the
+same exact fingerprint exhaust. Context pressure, compaction, session duration,
+or a nested skill's completion footer also cannot convert an internal checkpoint
+into a stop; persist the checkpoint and resume from it inside the same controlling
+invocation. Autocomplete may emit its final reply only after reaching its requested
+rest point or one of the shared human/safety/access/exhaustion stop conditions.
+
 ## Between phases
 
 - Re-read the active workspace before each phase (don't trust chat memory).

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

@@ -29,6 +29,11 @@ on exhaustion, stop as a technical blocker unless human-owned.
 
 ## Not a stop: agent-owned backtracking
 
+`NEEDS_REPLAN` is not a stop condition under an active Autocomplete caller. It
+blocks forward advancement, persists the return cursor, and immediately routes
+Plan repair plus Recovery Vet. The same applies to any intermediate nested
+`STOP`/`Next step` whose underlying decision is agent-owned.
+
 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

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

@@ -144,8 +144,12 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    After each fold-back rerun step 2a; missing/meaning-changing mappings block.
    Keep `state.md` non-READY for step 6.
 6. **One narrow recheck after edits.** If the candidate changed, dispatch exact
-   `devrites-plan-reviewer` once with accepted findings, changed paths/criteria,
-   and new identity. No full or third loop; if it changes the plan, repeat step 5.
+   `devrites-plan-reviewer` once per correction/fingerprint with accepted findings,
+   changed paths/criteria, and new identity. Within that same correction, no full
+   or third loop; if it changes the plan, repeat step 5. If the recheck closes its
+   input fingerprint but discovers a distinct Critical/Important invariant, return
+   that new fingerprint to the controlling caller as progress. It may start the
+   next bounded Plan/Recovery-Vet cycle; the prior reviewer count is not exhaustion.
    Then close the matrix and rerun step 2a's ID-and-meaning audit.
 
 6a. **Build readback.** From the final owning artifacts, add a cited five-line

package/package.json

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