devrites 4.0.9 → 4.0.10

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.10](https://github.com/ViktorsBaikers/DevRites/compare/v4.0.9...v4.0.10) (2026-08-08)
+
+### Fixed
+
+* **rite:** reopen stale writer stops ([aebb7fb](https://github.com/ViktorsBaikers/DevRites/commit/aebb7fb5b3510d068172aa1ec9f654063f39d545))
+
 ## [4.0.9](https://github.com/ViktorsBaikers/DevRites/compare/v4.0.8...v4.0.9) (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.9`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.0.9): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v4.0.10`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v4.0.10): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 
@@ -103,7 +103,9 @@ Some work needs a different route:
   consumptive proof action never retries blindly: retained evidence drives
   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.
+  needs a new GO. After an upgrade introduces a supported workflow-artifact writer,
+  Autocomplete reopens a stale missing-writer stop once instead of preserving the
+  obsolete recovery count.
 - [`/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; 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. 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/standards/afk-hitl.md

@@ -259,6 +259,12 @@ changes, not a request for permission to retry.
   recorded no-progress corrections still has recovery budget, even when an older
   `state.md` says `Next step: none`. Resume it; do not treat session age or the
   prior action's spent authorization as exhaustion.
+- **Treat a newly supported writer route as progress once.** For exact Vet-ready
+  workflow artifacts, apply `workflow-artifacts.md` when prior attempts only asked
+  a read-only role or product wright for implementation and evidence records
+  **no controlling-root materialization attempt**. Preserve the old attempts, but
+  do not count them against the new root-materialization fingerprint. Record the
+  migration; after a root attempt exists, normal fingerprint accounting applies.
 - **Classify exhaustion:** human-owned contract/risk/access gaps open their gate. Otherwise
   preserve reproduction/dead ends, set `Status: blocked` and `Next step: none — technical recovery exhausted for <causal fingerprint>; requires new evidence or changed failure conditions`.
   Do not emit `/rite-plan unblock`, another phase command, a question, or

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

@@ -20,6 +20,25 @@ technical-recovery exhaustion, while the vetted behavior and exact paths are
 complete. The root may not invent unresolved protocol choices; those return to
 Plan/Vet.
 
+## Cold-resume migration
+
+A **stale writer-exhaustion cursor** must reopen when all of these are durable:
+
+- Vet accepted the exact workflow-artifact paths and complete executable contract;
+- the recorded blocker is only missing implementation bodies or a writable actor;
+- prior no-progress attempts asked a read-only drafter/reviewer for bodies or sent
+  `.devrites/**` paths toward the product wright; and
+- evidence records **no controlling-root materialization attempt** for that exact set.
+
+This is a changed routing condition, not another correction attempt against the
+old unsupported-writer fingerprint. Preserve that history, close or supersede its
+terminal claim, record one new root-materialization fingerprint, and materialize
+directly even when all product slices are built or the AFK slice budget is zero.
+Do not consume product-slice budget, reopen an answered human gate, or require GO
+for this offline work. After any controlling-root attempt is recorded, this
+migration cannot apply again; route its observed atomic/proof failure under the
+new fingerprint instead.
+
 ## Admission
 
 Before writing:

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

@@ -18,6 +18,10 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
 When the cursor or approved plan contains a consumptive action, also read
 `.claude/skills/devrites-lib/reference/standards/one-shot-actions.md` before any
 stop/continue or execution decision.
+When a blocked cursor names missing executable controller/harness/bundle bytes or
+a missing writer under the active feature workspace, read
+`.claude/skills/devrites-lib/reference/standards/workflow-artifacts.md` before honoring
+the terminal cursor or its recovery count.
 
 ## Operating rules
 - **Use one initial human window.** Run spec and topology-first clarify; arm AFK
@@ -67,6 +71,11 @@ stop/continue or execution decision.
    terminal `next_action`, reconcile retained consumptive-action artifacts and
    per-fingerprint attempts from `drift.md` / `evidence.md`. A distinct retained
    fingerprint below its no-progress cap reopens caller-owned offline recovery;
+   a stale pre-ownership workflow-artifact writer stop reopens under
+   `workflow-artifacts.md` when no controlling-root materialization attempt exists.
+   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.
    reconstruct any missing return cursor only from the current phase plus the
    exact approved action in `test-plan.md` / evidence, never from chat or guesswork.
    The idea + flags: `--ship` / `--yolo` (continue through ship preflight, then stop

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

@@ -64,6 +64,17 @@ 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.
 
+Also reconcile a **stale writer-exhaustion cursor** against
+`workflow-artifacts.md`. When exact Vet-ready workflow-artifact paths and behavior
+exist, the old attempts only targeted the read-only drafter/reviewer or product
+wright, and there is **no controlling-root materialization attempt**, supported
+root ownership is a changed routing condition. Preserve the old fingerprint,
+record the new materialization fingerprint, and run that offline branch directly;
+do not charge or require product-slice/AFK budget, re-ask a resolved question, or
+request GO. Once a root materialization attempt exists, never apply this migration
+again—route its observed failure normally. This reconciliation runs even when all
+product slices are already built, before selecting the next forward phase.
+
 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

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

@@ -46,6 +46,14 @@ 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.
 
+A pre-ownership workflow-artifact writer stop is not unchanged evidence when the
+current contract supplies controlling-root materialization. Prior drafter/wright refusals do not count
+as root materialization attempts. Reopen only when exact paths and executable
+behavior passed Vet and there is **no controlling-root materialization attempt**;
+record the routing migration so it cannot reset again. Missing product slices,
+unresolved protocol choices, or a recorded root attempt remain under their normal
+gate/fingerprint rules.
+
 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

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

@@ -259,6 +259,12 @@ changes, not a request for permission to retry.
   recorded no-progress corrections still has recovery budget, even when an older
   `state.md` says `Next step: none`. Resume it; do not treat session age or the
   prior action's spent authorization as exhaustion.
+- **Treat a newly supported writer route as progress once.** For exact Vet-ready
+  workflow artifacts, apply `workflow-artifacts.md` when prior attempts only asked
+  a read-only role or product wright for implementation and evidence records
+  **no controlling-root materialization attempt**. Preserve the old attempts, but
+  do not count them against the new root-materialization fingerprint. Record the
+  migration; after a root attempt exists, normal fingerprint accounting applies.
 - **Classify exhaustion:** human-owned contract/risk/access gaps open their gate. Otherwise
   preserve reproduction/dead ends, set `Status: blocked` and `Next step: none — technical recovery exhausted for <causal fingerprint>; requires new evidence or changed failure conditions`.
   Do not emit `/rite-plan unblock`, another phase command, a question, or

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

@@ -20,6 +20,25 @@ technical-recovery exhaustion, while the vetted behavior and exact paths are
 complete. The root may not invent unresolved protocol choices; those return to
 Plan/Vet.
 
+## Cold-resume migration
+
+A **stale writer-exhaustion cursor** must reopen when all of these are durable:
+
+- Vet accepted the exact workflow-artifact paths and complete executable contract;
+- the recorded blocker is only missing implementation bodies or a writable actor;
+- prior no-progress attempts asked a read-only drafter/reviewer for bodies or sent
+  `.devrites/**` paths toward the product wright; and
+- evidence records **no controlling-root materialization attempt** for that exact set.
+
+This is a changed routing condition, not another correction attempt against the
+old unsupported-writer fingerprint. Preserve that history, close or supersede its
+terminal claim, record one new root-materialization fingerprint, and materialize
+directly even when all product slices are built or the AFK slice budget is zero.
+Do not consume product-slice budget, reopen an answered human gate, or require GO
+for this offline work. After any controlling-root attempt is recorded, this
+migration cannot apply again; route its observed atomic/proof failure under the
+new fingerprint instead.
+
 ## Admission
 
 Before writing:

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

@@ -18,6 +18,10 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
 When the cursor or approved plan contains a consumptive action, also read
 `.claude/skills/devrites-lib/reference/standards/one-shot-actions.md` before any
 stop/continue or execution decision.
+When a blocked cursor names missing executable controller/harness/bundle bytes or
+a missing writer under the active feature workspace, read
+`.claude/skills/devrites-lib/reference/standards/workflow-artifacts.md` before honoring
+the terminal cursor or its recovery count.
 
 ## Operating rules
 - **Use one initial human window.** Run spec and topology-first clarify; arm AFK
@@ -67,6 +71,11 @@ stop/continue or execution decision.
    terminal `next_action`, reconcile retained consumptive-action artifacts and
    per-fingerprint attempts from `drift.md` / `evidence.md`. A distinct retained
    fingerprint below its no-progress cap reopens caller-owned offline recovery;
+   a stale pre-ownership workflow-artifact writer stop reopens under
+   `workflow-artifacts.md` when no controlling-root materialization attempt exists.
+   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.
    reconstruct any missing return cursor only from the current phase plus the
    exact approved action in `test-plan.md` / evidence, never from chat or guesswork.
    The idea + flags: `--ship` / `--yolo` (continue through ship preflight, then stop

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

@@ -64,6 +64,17 @@ 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.
 
+Also reconcile a **stale writer-exhaustion cursor** against
+`workflow-artifacts.md`. When exact Vet-ready workflow-artifact paths and behavior
+exist, the old attempts only targeted the read-only drafter/reviewer or product
+wright, and there is **no controlling-root materialization attempt**, supported
+root ownership is a changed routing condition. Preserve the old fingerprint,
+record the new materialization fingerprint, and run that offline branch directly;
+do not charge or require product-slice/AFK budget, re-ask a resolved question, or
+request GO. Once a root materialization attempt exists, never apply this migration
+again—route its observed failure normally. This reconciliation runs even when all
+product slices are already built, before selecting the next forward phase.
+
 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

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

@@ -46,6 +46,14 @@ 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.
 
+A pre-ownership workflow-artifact writer stop is not unchanged evidence when the
+current contract supplies controlling-root materialization. Prior drafter/wright refusals do not count
+as root materialization attempts. Reopen only when exact paths and executable
+behavior passed Vet and there is **no controlling-root materialization attempt**;
+record the routing migration so it cannot reset again. Missing product slices,
+unresolved protocol choices, or a recorded root attempt remain under their normal
+gate/fingerprint rules.
+
 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

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

@@ -259,6 +259,12 @@ changes, not a request for permission to retry.
   recorded no-progress corrections still has recovery budget, even when an older
   `state.md` says `Next step: none`. Resume it; do not treat session age or the
   prior action's spent authorization as exhaustion.
+- **Treat a newly supported writer route as progress once.** For exact Vet-ready
+  workflow artifacts, apply `workflow-artifacts.md` when prior attempts only asked
+  a read-only role or product wright for implementation and evidence records
+  **no controlling-root materialization attempt**. Preserve the old attempts, but
+  do not count them against the new root-materialization fingerprint. Record the
+  migration; after a root attempt exists, normal fingerprint accounting applies.
 - **Classify exhaustion:** human-owned contract/risk/access gaps open their gate. Otherwise
   preserve reproduction/dead ends, set `Status: blocked` and `Next step: none — technical recovery exhausted for <causal fingerprint>; requires new evidence or changed failure conditions`.
   Do not emit `$rite-plan unblock`, another phase command, a question, or

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

@@ -20,6 +20,25 @@ technical-recovery exhaustion, while the vetted behavior and exact paths are
 complete. The root may not invent unresolved protocol choices; those return to
 Plan/Vet.
 
+## Cold-resume migration
+
+A **stale writer-exhaustion cursor** must reopen when all of these are durable:
+
+- Vet accepted the exact workflow-artifact paths and complete executable contract;
+- the recorded blocker is only missing implementation bodies or a writable actor;
+- prior no-progress attempts asked a read-only drafter/reviewer for bodies or sent
+  `.devrites/**` paths toward the product wright; and
+- evidence records **no controlling-root materialization attempt** for that exact set.
+
+This is a changed routing condition, not another correction attempt against the
+old unsupported-writer fingerprint. Preserve that history, close or supersede its
+terminal claim, record one new root-materialization fingerprint, and materialize
+directly even when all product slices are built or the AFK slice budget is zero.
+Do not consume product-slice budget, reopen an answered human gate, or require GO
+for this offline work. After any controlling-root attempt is recorded, this
+migration cannot apply again; route its observed atomic/proof failure under the
+new fingerprint instead.
+
 ## Admission
 
 Before writing:

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

@@ -18,6 +18,10 @@ default and **Full** for high-risk scope or explicit `--full`; profiles are defi
 When the cursor or approved plan contains a consumptive action, also read
 `.agents/skills/devrites-lib/reference/standards/one-shot-actions.md` before any
 stop/continue or execution decision.
+When a blocked cursor names missing executable controller/harness/bundle bytes or
+a missing writer under the active feature workspace, read
+`.agents/skills/devrites-lib/reference/standards/workflow-artifacts.md` before honoring
+the terminal cursor or its recovery count.
 
 ## Operating rules
 - **Use one initial human window.** Run spec and topology-first clarify; arm AFK
@@ -67,6 +71,11 @@ stop/continue or execution decision.
    terminal `next_action`, reconcile retained consumptive-action artifacts and
    per-fingerprint attempts from `drift.md` / `evidence.md`. A distinct retained
    fingerprint below its no-progress cap reopens caller-owned offline recovery;
+   a stale pre-ownership workflow-artifact writer stop reopens under
+   `workflow-artifacts.md` when no controlling-root materialization attempt exists.
+   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.
    reconstruct any missing return cursor only from the current phase plus the
    exact approved action in `test-plan.md` / evidence, never from chat or guesswork.
    The idea + flags: `--ship` / `--yolo` (continue through ship preflight, then stop

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

@@ -64,6 +64,17 @@ 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.
 
+Also reconcile a **stale writer-exhaustion cursor** against
+`workflow-artifacts.md`. When exact Vet-ready workflow-artifact paths and behavior
+exist, the old attempts only targeted the read-only drafter/reviewer or product
+wright, and there is **no controlling-root materialization attempt**, supported
+root ownership is a changed routing condition. Preserve the old fingerprint,
+record the new materialization fingerprint, and run that offline branch directly;
+do not charge or require product-slice/AFK budget, re-ask a resolved question, or
+request GO. Once a root materialization attempt exists, never apply this migration
+again—route its observed failure normally. This reconciliation runs even when all
+product slices are already built, before selecting the next forward phase.
+
 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

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

@@ -46,6 +46,14 @@ 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.
 
+A pre-ownership workflow-artifact writer stop is not unchanged evidence when the
+current contract supplies controlling-root materialization. Prior drafter/wright refusals do not count
+as root materialization attempts. Reopen only when exact paths and executable
+behavior passed Vet and there is **no controlling-root materialization attempt**;
+record the routing migration so it cannot reset again. Missing product slices,
+unresolved protocol choices, or a recorded root attempt remain under their normal
+gate/fingerprint rules.
+
 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

package/package.json

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