devrites 5.8.0 → 5.9.0

package/pack/generated/pi/skills/rite-plan/reference/slicing.md

@@ -106,8 +106,8 @@ Make each continuation cheap and drift-free:
 - Phases chain automatically only **inside** one workspace (`/rite-autocomplete`
   drives spec → clarify → temper → define → vet → build × slices → prove → polish →
   review → seal; plain HITL chains plan↔vet inline and stops at each other boundary).
-  Crossing into the next continuation is a new invocation by design, so the human sees
-  each delivered increment before the next one starts.
+  Next continuation is a new invocation by default. Same-run chaining is
+  `continue_sequence: true` (Deferred-ship).
 
 ### Release milestone (full-picture gate)
 
@@ -138,7 +138,8 @@ product:
   product picture across milestones; Polish folds each milestone's deltas.
 - **Deferred-ship sequence** (`.devrites/AFK` `continue_sequence: true`, `max_workspaces: N`):
   milestones are sealed but not shipped, and the armed run opens the next recorded
-  continuation automatically; per-slice `WIP(<slug>)` checkpoints still land locally,
+  continuation automatically; local `WIP(<slug>):` checkpoints still land with
+  human summaries (never a slice id),
   so the tree stays clean. One release ship at the end collapses the sequence's
   checkpoints into the single release commit, pushes/tags it, and may archive the
   sealed predecessors. Because no milestone boundary was shipped, later work can touch

package/pack/generated/pi/skills/rite-polish/SKILL.md

@@ -91,7 +91,9 @@ Incomplete comparison is **not** agreement. Record axis deltas in `polish-report
    affected real re-proof using the approved commands, fresh proof-runner
    validation, refreshed evidence/browser bindings, and an updated candidate
    manifest. Record a **`Re-verification:`** line in `polish-report.md`. Close
-   the candidate for Review only after these checks are green.
+   the candidate for Review only after these checks are green. Then checkpoint
+   remaining candidate diffs per
+   [`checkpoint.md`](../rite-build/reference/checkpoint.md).
 7. **Aggregate output:** each phase appends to the single `polish-report.md`.
 
 ## Refinement modes

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

@@ -106,6 +106,9 @@ test changes.
    attempt. Never guess the runtime fix or reuse old GO.
 10. **Record.** Root updates `evidence.md`, optional `browser-evidence.md`,
     traceability, and state, with exactly one observed candidate binding.
+    After independent validators are green, checkpoint remaining candidate
+    diffs per [`checkpoint.md`](../rite-build/reference/checkpoint.md). A wright
+    correction during Recover red does not commit on control until this step.
 
 > Do not claim an unobserved pass, skip browser proof, or proceed with pending
 > slices. Load `reference/anti-patterns.md` when tempted to do so.

package/pack/generated/pi/skills/rite-review/SKILL.md

@@ -142,7 +142,9 @@ Pull these via `Read` when the diff demands them:
    binding in `review.md` for the current digest, distinguishing fresh accounts from
    cited unchanged sub-scope evidence and reconciling complete coverage.
    **Completion:** the records name the reviewed candidate identity and every accepted
-   correction has affected proof plus a fresh Review.
+   correction has affected proof plus a fresh Review. Then checkpoint remaining
+   candidate diffs per [`checkpoint.md`](../rite-build/reference/checkpoint.md);
+   a wright correction does not commit on control until that Review is green.
 
 ## Finding labels
 

package/pack/generated/pi/skills/rite-temper/SKILL.md

@@ -27,8 +27,8 @@ the spec applicability map triggers that risk family.
 - **Raise outcome ambition without expanding the solution unnecessarily.** Solve the
   underlying problem without adding speculative capability or abstraction.
 - **Route every scope change through the Spec Drift Guard.** A scope change takes effect
-  only when `spec.md` records the confirmed decision. Expansion is **opt-in** (HITL
-  confirm; AFK pauses: see autocomplete policy). Nothing auto-grows into the build.
+  only when `spec.md` records the confirmed decision. HITL confirms expand;
+  autocomplete auto-applies it. Irreversible-risk still pauses.
 - **Apply maximum caution to hard-to-reverse changes.** Auth, migration, public API, and
   data-model changes always pause under the irreversible-risk list.
 - **Honest verdict.** Never round "needs work" up to "ready"; record every scope call's *why*.
@@ -89,8 +89,8 @@ the spec applicability map triggers that risk family.
    `AskUserQuestion`, one at a time, best-guess + **why**. Each material scope call ends as a
    **recorded decision**: a resolved `questions.md` qid (HITL) or a `decisions.md` ADR (AFK):
    so the review leaves an auditable record outside chat. (AFK gate policy —
-   [`reference/significance.md`](reference/significance.md) — `hold-rigor` + `reduce-to-MVP`
-   auto-apply, **any `expand` is a blocking pause**, irreversible-risk always pauses.)
+   [`reference/significance.md`](reference/significance.md) — autocomplete applies
+   the recommended mode including `expand`; irreversible-risk always pauses.)
    Apply objective clarity, mitigation, and assumption fixes directly.
 6. **Write `strategy.md` + fold back:** [`reference/strategy-template.md`](reference/strategy-template.md).
    **Choose the drift path based on whether a plan exists:** *no `plan.md` yet* (the normal pre-define
@@ -110,8 +110,8 @@ the spec applicability map triggers that risk family.
    blocking/escalating question routes `/rite-clarify`/HITL. Only after the
    matrix is re-closed may the phase advance.
    Set `Phase: temper`; `Next step: /rite-define` only after verification.
-   Human-owned expansion/unapproved irreversible choices set `Awaiting human` +
-   `Status: awaiting_human`; objective below-bar findings continue correction.
+   Unapproved irreversible choices set `Awaiting human`. Autocomplete expand does
+   not. Objective below-bar findings continue correction.
 7. **Adversarial verification loop:** ask the exact
    [`devrites-strategy-reviewer`](.pi/agents/devrites-strategy-reviewer.md)
    through the native fresh-context contract in

package/pack/generated/pi/skills/rite-temper/reference/significance.md

@@ -41,6 +41,6 @@ seal can see the call was made deliberately.
 
 ## In `/rite-autocomplete`
 Autocomplete runs the significance test every feature. On skip → straight to `/rite-define`
-(no pause). On fire → run the full review under the AFK gate ceiling: `hold-rigor` and
-`reduce-to-MVP` auto-apply (they never grow acceptance); **any `expand` is a blocking pause**;
-irreversible-risk findings always pause. Expansion is never auto-grown unattended.
+(no pause). On fire → run the full review and auto-apply the recommended mode, including
+`expand` and extra acceptance (record the ADR; fold via Spec Drift Guard).
+Irreversible-risk findings always pause.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "5.8.0",
+  "version": "5.9.0",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code, Codex, omp, and pi",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",