devrites 5.4.0 → 5.5.0

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

@@ -57,7 +57,7 @@ Pull these via `Read` when the diff demands them:
 
 0. Read `.claude/skills/devrites-lib/reference/standards/core.md` first (the always-on operating rules); pull the
    on-demand rules above as the diff demands them.
-1. Read `spec.md`, `tasks.md`, `state.md`, `decisions.md`, `evidence.md`,
+1. Read `spec.md`, `tasks.md`, `state.md`, `decisions.md`,
    `touched-files.md`, `.devrites/principles.md` (if present: the binding invariants to score
    the diff against), and the `git diff`. For "what would this change break"
    questions, apply `.claude/skills/devrites-lib/reference/standards/tooling.md`: use
@@ -66,7 +66,14 @@ Pull these via `Read` when the diff demands them:
    current API, context7 if available can confirm the signature. Run
    `devrites-engine check candidate <slug>` and require its digest to match the
    single `evidence.md` binding and the `browser-evidence.md` binding when that
-   file exists. A missing, malformed, or open candidate returns to Polish/Prove.
+   file exists. Read those ledgers via the bounded advisory read
+   (`workspace-artifact-schema.md` § Read next by phase): binding line, `EVID-###`
+   index, then bodies for this candidate's AC/slice IDs only. A missing,
+   malformed, or open candidate returns to Polish/Prove.
+   Read `touched-files.md` `## Review trail` and `eng-review.md` `## Deferred findings`:
+   every deferred row is an input finding for the step-3 cohort (quoted in the owning
+   reviewer's brief without severity) and ends in `review.md` with its own label and
+   action tag — never silently dropped.
 2. **Review tests first:** do they prove the acceptance criteria? Missing,
    weak, or wrong tests are the first findings.
    **Completion:** every acceptance criterion maps to a proven test or a labeled finding.
@@ -74,7 +81,8 @@ Pull these via `Read` when the diff demands them:
    one axis and fail the other: code that follows every project standard but
    implements the wrong thing (Code-review pass, Spec fail), or code that does exactly
    what the spec asked but breaks project conventions (Spec pass, Code-review fail).
-   Separate contexts prevent one axis from masking the other:
+   Separate contexts prevent one axis from masking the other. This is the initial
+   full pass; a correction uses step 7's bounded recheck:
    - Freeze that closed digest and give the same digest to **two** read-only reviewers in
      parallel, each with its own narrow brief and no
      cross-pollination — and evaluate the frontend (step 4), security (step 5),
@@ -88,17 +96,10 @@ Pull these via `Read` when the diff demands them:
        missing spec` and do not infer requirements from the diff."
      - **Code-review axis** → `devrites-code-reviewer`: "Apply your full documented
        discipline (tests-first, correctness, readability, architecture, maintainability,
-       standards) on the active feature workspace + diff. Cite file:line per finding;
-       skip what tooling already enforces. Also flag the AI-codegen smells (silent/empty
-       catch, defensive try-catch bloat + redundant logging, single-use factory / needless
-       indirection, dependency creep where an in-repo option exists, a 100-line function
-       where 20 would do) and the silent-failure bugs (a missing value coerced to 0/''/[],
-       a dropped Result/err return, off-by-one / boundary, logic that contradicts the
-       comment/docstring/name). Per hunk, check whether working code was deleted that the
-       task did not ask to remove. Score the diff against `.devrites/principles.md`: a change
-       that breaks a declared invariant with no recorded, human-approved exception is a Critical.
-       Distinguish hard documented-standard violations from baseline smells; smells are judgment
-       calls unless a DevRites or project standard makes them binding."
+       standards) on the feature workspace + diff. Cite file:line; skip tooling-enforced
+       checks. Apply canonical anti-slop and silent-failure lenses; inspect each hunk
+       for unrequested deletion. Unexcepted `.devrites/principles.md` violations are
+       Critical. Distinguish binding standards from judgment-only baseline smells."
    - **Do NOT merge or re-rank** their findings. Present them under separate
      `## Spec` and `## Code review` sub-sections in `review.md`. Surface contradictions
      between the axes explicitly (e.g. "Spec axis says complete, Code-review axis says
@@ -131,9 +132,15 @@ Pull these via `Read` when the diff demands them:
 7. Reconcile and accept only in-scope fixes. Consolidate them into one bounded
    wright correction; never edit source in the reviewing context. Any correction
    updates the candidate manifest, returns through affected Prove, and then starts
-   a fresh Review on the new digest. Do not carry a prior reviewer account across it.
+   a fresh Review binding on the new digest. Dispatch affected exact reviewers on
+   all their open findings and the dependency/regression closure under
+   [evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
+   Cite unchanged sub-scope coverage only with its original identity and explicit
+   justification; never relabel old accounts. Changed contracts or uncertain impact
+   require the full applicable pass.
 8. The root updates `review.md` and `state.md`, writing exactly one candidate
-   binding in `review.md` for the digest given to every reviewer.
+   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.
 

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

@@ -7,8 +7,8 @@ user-invocable: true
 
 # /rite-seal: GO / NO-GO
 
-Verify the final candidate and write `seal.md`; `/rite-ship` alone performs
-authorized irreversible actions and close-out.
+Verify final candidate in `seal.md`; `/rite-ship` owns authorized irreversible
+actions and close-out.
 
 ## Authority
 
@@ -36,6 +36,7 @@ The host runs/reconciles named read-only reviewers; engine checks invariants.
 | Any acceptance criterion, resolved prohibition, or declared key link lacks proof | **NO-GO** |
 | Evidence is stale, or native diff review plus the exact test analyst finds weakened tests | **NO-GO: Critical** |
 | Any exact required reviewer account is missing or silent | **NO-GO** |
+| Any deferred finding (`touched-files.md` `## Review trail`, `eng-review.md` `## Deferred findings`) lacks a `review.md` verdict | **NO-GO** |
 | Any `gate: validating` question remains open | **NO-GO** |
 | Material UI acceptance lacks or fails required browser proof | **NO-GO** |
 | Unresolved drift, unsafe migration/removal, or unapproved principle violation remains | **NO-GO** |
@@ -52,18 +53,17 @@ Follow [`reference/phase-contract.md`](reference/phase-contract.md)
 
 1. read workspace and final diff;
 2. recheck the canonical candidate/bindings and approved repository/CI proof;
-3. dispatch exact proof, spec, test, doubt, and applicable review agents in
-   parallel under `../devrites-lib/reference/parallel-dispatch.md` — independent
-   read-only verdicts on one frozen candidate;
+3. admit valid Spec/Code accounts; dispatch remaining required exact roles under
+   `../devrites-lib/reference/parallel-dispatch.md` on the same frozen candidate;
 4. reconcile their read-only verdicts against source and immutable evidence;
 5. draft GO/NO-GO `seal.md` with acceptance, tests, decisions, and seven accounts;
 6. write exactly one candidate binding, then run
    `devrites-engine check seal <slug>` for structure and identity, never semantics.
 
-Any candidate correction returns through affected Prove and a fresh Review before
-Seal starts again.
+Corrections return through affected Prove/Review before restarting Seal under
+[evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
 
-Only repository scripts/CI authorize commands; never guess them.
+Only repository scripts/CI authorize commands; never guess.
 
 ## On GO
 

package/pack/.claude/skills/rite-seal/reference/final-evidence.md

@@ -1,6 +1,6 @@
 # Final evidence check
 
-Map every `spec.md` promise to fresh observed proof.
+Map spec promises to valid observed proof.
 
 ## Acceptance
 
@@ -11,7 +11,7 @@ inspection alone, and generic "tests pass" do not count.
 
 Apply [`testing.md`'s positive, discriminating proof](../../devrites-lib/reference/standards/testing.md#positive-discriminating-proof),
 including invalid-result exclusions and static/textual criterion boundaries.
-Unsupported behavioral claims remain unproven: NO-GO.
+Unproven behavior: NO-GO.
 
 ## Cross-check
 
@@ -25,11 +25,12 @@ recovery evidence or an evidence-backed dismissal; a generic green suite cannot
 
 Run `devrites-engine check candidate <slug>` and require its digest to match the
 single evidence/review bindings and browser binding when present. Diff tests,
-dispatch exact `devrites-test-analyst`, run approved repository commands, then
-require the same candidate digest and no source mutation. Deleted/skipped/focused/
+dispatch exact `devrites-test-analyst`; apply
+[evidence validity](../../devrites-lib/reference/candidate-integrity.md#evidence-validity)
+to approved proof, then require unchanged digest/sources. Deleted/skipped/focused/
 weakened/tautological tests are Critical.
 
-After the native semantic verdicts are recorded in `seal.md`, run:
+After recording verdicts in `seal.md`, run:
 
 ```bash
 devrites-engine check seal "<slug>"

package/pack/.claude/skills/rite-seal/reference/phase-contract.md

@@ -1,27 +1,29 @@
 # rite-seal phase contract
 
-Seal's candidate action follows
-[`candidate-integrity.md`](../../devrites-lib/reference/candidate-integrity.md).
-
 1. **Read.** Resolve the explicit slug or `.devrites/ACTIVE`, require its
    `state.md`, then read required workspace artifacts, conditional
    browser/design/devex evidence, and final diff.
 2. **Recheck identity and real proof.** Run
    `devrites-engine check candidate <slug>` and require its exact digest to match
    the single evidence/review bindings and the browser binding when present.
-   Apply `spec-grammar.md`'s Native grammar re-read checklist, then run only
-   `test-plan.md`'s repository/CI commands against that frozen digest. Rerun the
+   Apply `spec-grammar.md`'s Native grammar re-read checklist and
+   [evidence validity](../../devrites-lib/reference/candidate-integrity.md#evidence-validity).
+   Run required `test-plan.md` commands unless valid observed proof already satisfies
+   them under that contract. Rerun the
    candidate check afterward and require the identical digest and no source
    mutation. Capture command, cwd, exit, decisive output, and identity.
    Missing/red/mismatched blocks; unavailable is `cannot_verify`, never pass.
 3. **Judge acceptance.** Dispatch exact `devrites-proof-runner` on immutable
-   proof and exact `devrites-spec-reviewer` on the same candidate. Reconcile every
+   proof; admit valid same-candidate `devrites-spec-reviewer` evidence from Review
+   or dispatch that exact reviewer. Reconcile every
    AC/REQ/scenario/key link by ID and meaning; missing/stale/self-attested/mismatched is NO-GO.
 4. **Judge tests.** Diff baseline/candidate tests for deletion, skip/focus,
    tautology, or weakening; dispatch exact `devrites-test-analyst`. Missing or
    adverse account, or green tests not asserting mapped behavior, is Critical.
 5. **Resolve gates.** Open blocking/escalating/validating questions and drift
    block. Each stood decision needs a reconciled exact `devrites-doubt-reviewer` verdict.
+   Every deferred finding (`touched-files.md` `## Review trail`, `eng-review.md`
+   `## Deferred findings`) needs its `review.md` verdict; a row without one blocks.
 6. **Risk and native review.** Apply [`risk-and-rollback.md`](risk-and-rollback.md)
    and the [`review roster`](../../devrites-lib/reference/parallel-dispatch.md) on
    the candidate. Admit each result through
@@ -31,17 +33,15 @@ Seal's candidate action follows
 7. **Route corrections.** Reconcile cited findings/disagreements, but do not
    edit the candidate or manifest in Seal. Route an accepted correction through
    one bounded wright, update the manifest, run affected Prove, complete a fresh
-   Review, then restart Seal on the new digest.
-8. **Draft, then check deterministic invariants.** Write `seal.md` from
+   Review under evidence validity, then restart Seal on the new digest.
+8. **Draft/check.** Write `seal.md` from
    [`seal-template.md`](seal-template.md) with the GO/NO-GO rationale, acceptance map,
    test-analysis account, stood-decision verdicts, all seven reviewer accounts,
    and exactly one `Candidate SHA-256: <64 lowercase hex>` line. Then run:
    ```bash
    devrites-engine check seal "<slug>"
    ```
-   This checks structure and exact candidate bindings, not prose or semantics. Blocks exit `3`;
-   invalid state exits `2`. GO sets `Next step: /rite-ship`; NO-GO names the
-   smallest fix. Never commit, push, tag, publish, deploy, or close here.
+   Structure/bindings only: blocks exit `3`, invalid state `2`. GO sets
+   `Next step: /rite-ship`; NO-GO names the fix. No commit/push/tag/publish/deploy/close.
 
-> When tempted to round NO-GO up to GO or average away reviewer disagreement,
-> load [`anti-patterns.md`](anti-patterns.md).
+Apply [`anti-patterns.md`](anti-patterns.md); never average away disagreement.

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

@@ -80,6 +80,9 @@ if absent, route to `/rite-spec <feature>`. Ship only with current **GO** in `se
    to move `.devrites/work/<slug>` → `.devrites/archive/<slug>` and clear `ACTIVE`
    only if it names this slug; preserve another active feature's cursor.
    Preserve every `.md`; stable hierarchical instructions need no active-workspace sync.
+   Report the recorded `Next step` verbatim — the exact `/rite-spec <parent>-<n> "<objective>"`
+   when a continuation sequence remains — so the next increment starts from one line,
+   never from chat memory.
 
 > **Mid-flight discipline.** No seal GO, skipped type-GO, out-of-manifest stage, or
 > deleted workspace. Stop and use [`anti-patterns`](reference/anti-patterns.md).

package/pack/.claude/skills/rite-ship/reference/close-out.md

@@ -5,8 +5,13 @@ deleted. DevRites keeps the audit trail; it just moves out of the live path.
 
 ## What close-out does
 
-1. **Mark done.** Set `state.md` → `Phase: done`, `Status: done`, and a `Next step`
-   of `/rite-spec <next feature>`.
+1. **Mark done.** Set `state.md` → `Phase: done`, `Status: done`, and a `Next step`.
+   When this workspace's `decisions.md` records an unfinished
+   [continuation sequence](../../rite-plan/reference/slicing.md#continuation-workspaces),
+   that step is the **exact** next command — `/rite-spec <parent>-<n> "<objective>"` —
+   and the ship reply prints the same line. Otherwise it stays
+   `/rite-spec <next feature>`. Nothing spawns the continuation automatically:
+   the recorded command is the handoff, so the human starts each increment knowingly.
 2. **Archive.** Run the deterministic script:
    ```bash
    devrites-engine state close <slug>
@@ -25,6 +30,15 @@ can also fail. Inspect the actual live path, archive and cursor before reporting
 retrying. Record the command/error and observed locations; never claim restored state
 from an attempted rollback or repeat a move against an unverified destination.
 
+## Sequence predecessors
+
+A deferred-ship sequence leaves earlier milestones sealed and unarchived in
+`.devrites/work/`. The release ship's disclosed plan may close them
+(`devrites-engine state close '<slug>'` per predecessor) after the release commit
+lands; each close is safe because `ACTIVE` names the release workspace. Closing is
+bookkeeping only: the release commit already carries their bytes, and their audit
+records move intact.
+
 ## Why archive, not delete
 
 - The `.md` files (`spec`, `decisions`, `assumptions`, `evidence`, `seal`, `ship`, …)

package/pack/.claude/skills/rite-ship/reference/git-ship.md

@@ -12,11 +12,13 @@ Acceptance criteria proven: <n / total>
 Branch:   <target branch>
 Candidate paths: <exact project-relative paths>
 Checkpoint collapse: <exact `git reset --soft '<merge-base>'` command | skip>
+Collapse slugs: <active slug plus every recorded sequence slug in the range | n/a>
 Stage plan: <exact argv-safe `git add -- '<path>'` command for every manifest row>
 Commit:   <exact git commit command>
 Push:     <exact git push command | skip>
 Tag:      <exact git tag command | skip>
 PR:       <exact PR command, target, title, and body source | skip>
+Close:    <exact `devrites-engine state close '<slug>'` for each sealed sequence predecessor | skip>
 
 Type "GO" exactly to approve this attempt once. Anything else cancels.
 ```
@@ -45,9 +47,12 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 1. **Analyze checkpoint history without mutating it.** Read the upstream, merge
    base, commit OIDs, and full subjects. If no checkpoint commit exists, disclose
    `skip`. A collapse is eligible only when every commit in its range has the exact
-   `WIP(<active-slug>):` prefix for the validated active slug. A different slug,
-   missing colon, broad `WIP(` match, ordinary commit, or mixed history blocks;
-   never reinterpret the range.
+   `WIP(<slug>):` prefix for the validated active slug — or, for a release ship of a
+   deferred-ship sequence, for a slug recorded in the parent's `decisions.md`
+   sequence whose workspace is sealed in this run
+   ([afk-hitl.md § Sequence continuation](../../devrites-lib/reference/standards/afk-hitl.md#sequence-continuation-continue_sequence-max_workspaces));
+   disclose the exact slug set. A different slug, missing colon, broad `WIP(` match,
+   ordinary commit, or mixed history blocks; never reinterpret the range.
 2. **Verify the candidate.** Rerun `devrites-engine check candidate <slug>` and
    `devrites-engine check seal <slug>`, compare every binding, require the
    candidate worktree paths to be unchanged, and inspect the existing staged
@@ -62,8 +67,8 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
 
 1. **Optional checkpoint collapse.** If and only if the prompt disclosed it,
    recheck that `HEAD`, merge base, and every subject are unchanged and that each
-   subject starts exactly `WIP(<slug>):` for the active slug, then run the exact
-   disclosed `git reset --soft "$mb"`. Otherwise skip. Any different or mixed
+   subject starts exactly `WIP(<slug>):` for the disclosed slug set, then run the
+   exact disclosed `git reset --soft "$mb"`. Otherwise skip. Any different or mixed
    subject blocks without mutation.
 2. **Exact staging.** Run `git add -- "$path"` once for each disclosed manifest
    row, passing each validated project-relative path as its own quoted argv
@@ -95,6 +100,10 @@ Pre-GO is read-only. Do not run the disclosed collapse or staging commands.
    Any mismatch stops; do not reinterpret it.
 8. **Push** to the project-conventional target branch.
 9. **Tag / PR** only when project convention requires it; otherwise skip.
+10. **Close sealed predecessors** only when the prompt disclosed them: run the
+    exact `devrites-engine state close '<slug>'` once per predecessor. Each is safe
+    because `ACTIVE` names the release workspace; a nonzero exit stops the rest and
+    is reported, never retried against an unverified destination.
 
 Record SHA(s), branch, and tag/PR URL in `ship.md`.
 

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

@@ -50,6 +50,12 @@ load a routed standard to discover required behavior, not to prescribe implement
    problem in one sentence. **Completion:** it includes both.
 1a. **Dedupe.** Search local issues/PRDs, work, and archive. On a close match ask
    extend/adopt/new, then record the choice; otherwise continue silently.
+   A recorded [feature-sequence continuation](../rite-plan/reference/slicing.md#continuation-workspaces)
+   is a **new** workspace (`<parent>-2`): carry the parent slug and position into
+   `brief.md`, read the parent artifacts as design input, and do not route to
+   `/rite-plan revise` on the parent. When the ask is open and archived work records
+   an unfinished sequence, propose that next continuation (slug + objective) as the
+   recommended option instead of a fresh slug.
 2. **Investigate:** follow [investigation](reference/investigation.md) through its
    complete findings and done-when gate. Discover the project's **test /
    build/typecheck/lint** commands, frontend/backend systems, and declared project guidance

package/pack/.claude/skills/rite-spec/reference/state-workspace.md

@@ -172,6 +172,12 @@ Ordinary workspace creation preserves the field without initializing,
 increasing, renaming, or deleting it. Released bullet workspaces spell it `AFK
 slices remaining`; preserve that presentation rather than migrating it.
 
+When the brief records a [sequence continuation](../../rite-plan/reference/slicing.md#continuation-workspaces),
+seed the `sequence_parent`, `sequence_position`, `sequence_workspaces_remaining`,
+and — for the release entry — `sequence_role` rows at creation per that contract.
+Without them `state merge-manifest` cannot walk the chain and the release-union
+gate never engages.
+
 ## questions.md entry format
 
 ```markdown

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

@@ -16,7 +16,10 @@ Use the supplied slug or `.devrites/ACTIVE`; require its authoritative
 `state.md` and read the cursor directly. Read question, evidence, and risk
 artifacts only as needed. Never infer lifecycle state from `README.md` or chat.
 
-If no workspace exists, recommend `/rite-spec <feature>` and stop.
+If no workspace exists: when archived workspaces record an unfinished
+[continuation sequence](../rite-plan/reference/slicing.md#continuation-workspaces),
+list each next command (`/rite-spec <parent>-<n> "<objective>"`); otherwise
+recommend `/rite-spec <feature>`. Then stop.
 
 If `state.md` is unreadable/malformed: report a gap with the defect and stop — never infer the phase from other files; `/rite-doctor`/`/rite-upgrade` own repair.
 

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

@@ -7,8 +7,7 @@ user-invocable: true
 
 # /rite-temper: review scope and risk before planning
 
-Review a readied spec for outcome ambition, scope, pre-mortem risks, and unnecessary
-solution surface. Fold accepted decisions into the canonical contract before
+Review the readied spec for ambition, scope, pre-mortem risk and unnecessary surface. Fold accepted decisions into the canonical contract before
 `/rite-define`. This step is optional for small work and skips low-stakes specs, but
 `/rite-autocomplete` always invokes it. **Read the active workspace first**; if there
 is no readied `spec.md`, tell the user to run `/rite-spec`. Review depth follows
@@ -58,6 +57,10 @@ the spec applicability map triggers that risk family.
    First, the **one-sentence-intent test**: state the whole change's intent in a single sentence.
    If you can't without an "and" that joins two unrelated outcomes, it is **two features**: the
    scope-creep signal; recommend splitting or narrowing the spec before continuing.
+   Apply the same test to size: a spec whose honest decomposition would exceed the
+   [feature ceiling](../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
+   (roughly ten slices or more than ~20 acceptance criteria) is a feature sequence;
+   recommend the thinnest shippable subset now and name the continuations as Non-goals.
    Then consider the 10-star outcome for the underlying problem and choose **exactly one**
    scope mode (`expand` opt-in · `selective` · `hold-rigor` · `reduce-to-MVP`) with its
    rationale and the condition that would change the choice. `$ARGUMENTS` `--mode` is a
@@ -106,19 +109,19 @@ the spec applicability map triggers that risk family.
    and closed gates. Partial/Missing, an unowned material assumption, or an open
    blocking/escalating question routes `/rite-clarify`/HITL. Only after the
    matrix is re-closed may the phase advance.
-   Update `state.md`: `Phase: temper`,
-   `Next step: /rite-define`; on a blocking pause (expand / irreversible / a dimension still below
-   bar) write the `Awaiting human` block + `Status: awaiting_human` before stopping.
+   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.
 7. **Adversarial verification loop:** ask the exact
    [`devrites-strategy-reviewer`](../../agents/devrites-strategy-reviewer.md)
    through the native fresh-context contract in
    [`agents.md`](../devrites-lib/reference/standards/agents.md), with **only** the hardened
-   spec + rubric: no authoring reasoning. Resolve
-   actionable findings by editing `spec.md`/`strategy.md`, re-dispatch; **cap ≤3 iterations**. A
-   dimension still below bar after 3 is classified by decision ownership: a product/scope/risk
-   choice becomes a blocking question; an objective spec defect stays blocked with the exact
-   required edit and routes to `/rite-spec`, not `/rite-resolve`. Irreversible-risk findings
-   always pause. If the named agent is unavailable, stop for HITL. After an accepted edit to a
+   spec + rubric, no authoring reasoning. Fold technical findings into one correction;
+   exact strategy reviewer rechecks open findings and affected coverage/regressions under
+   [the canonical retry contract](../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve):
+   Product/scope choices and unapproved irreversible risk remain human gates;
+   technical exhaustion preserves blocker/reproduction.
+   If the named agent is unavailable, stop for HITL. After an accepted edit to a
    coverage-bound input, repeat step 6's native coverage revalidation before handoff.
 8. **STOP.** Report the mode, the scope deltas, and the floor verdict; recommend `/rite-define`.
 

package/pack/.claude/skills/rite-temper/reference/anti-patterns.md

@@ -1,29 +1,30 @@
 # /rite-temper: anti-patterns
 
-Universal rationalizations + red flags live in
-[`../../devrites-lib/reference/standards/anti-patterns.md`](../../devrites-lib/reference/standards/anti-patterns.md): read it when the
-reluctance is broader than this phase. Below are the temper-specific ones.
+For cross-phase issues, read [universal anti-patterns](../../devrites-lib/reference/standards/anti-patterns.md).
 
 ## Phase rationalizations
 
 | Excuse | Rebuttal |
 |---|---|
-| "I'll write all the findings into `strategy.md` and let the user read it." | The artifact is the *output* of an interactive review, not a substitute for it. A finding's path to "done" goes **through `AskUserQuestion`**, one at a time, with a recommendation + why. Dumping findings into one write and moving on is the exact failure mode this skill exists to prevent. |
+| "I'll write all the findings into `strategy.md` and let the user read it." | Fold and recheck objective corrections preserving scope, behavior, and risk policy. Ask human-owned strategy/acceptance choices with recommendations and await answers. Recording alone resolves nothing; never silently expand or trim the spec. |
 | "Bigger is better: let's add the extra capability while we're thinking big." | Ambition belongs on the **outcome**, not the **solution surface**. A speculative capability/abstraction is gold plating. Expand the problem + acceptance; never the machinery. |
 | "The user obviously wants the ambitious version. I'll add it to the spec." | Expansion is **opt-in**, recorded, and confirmed (HITL) or paused (AFK). Adding acceptance the human didn't approve is silent scope growth: route it through the Spec Drift Guard or don't add it. |
 | "It's over-scoped, I'll just trim those criteria." | Reducing scope is **still a spec change**. Cut acceptance only as a recorded Spec-Drift-Guard decision, and park the rest in Non-goals with a revisit note: never a silent trim. |
-| "This dimension is weak but the others are strong: net it's fine." | The gate is the **floor**, not the average. A spec `broken` on risk does not pass because it's `strong` on clarity. |
-| "I can see it's adequate. I'll note the band, evidence is obvious." | Cite the evidence (the spec line or its absence) **before** the band. Score-first-justify-later is how a reviewer rationalizes a spec it already likes. |
+| "This dimension is weak but the others are strong: net it's fine." | The gate is the **floor**, not the average; strong clarity cannot offset broken risk. |
+| "I can see it's adequate. I'll note the band, evidence is obvious." | Cite spec evidence **before** the band; never score first and rationalize later. |
 | "It's a strategy doc, the implementation concerns don't apply yet." | Cross-cutting concerns (security/data/observability/modifiability) are where strategy breaks down. Address each or mark it explicitly N/A: silent omission is a gap. |
-| "This greenfield design is elegant." | Elegant for a codebase that doesn't exist. Ground ambition in the real seams + blast radius; flag a new dependency / second design system for an explicit decision. |
+| "This greenfield design is elegant." | Ground ambition in live seams/blast radius; a new dependency or second design system needs an explicit decision. |
 
 ## Red flags
-- `strategy.md` written but `spec.md` acceptance/Non-goals **not** updated: the build follows
-  the spec, so the review changed nothing.
-- An `expand` decision auto-applied in AFK (it must pause), or any irreversible-risk touch that
-  didn't pause.
+- An accepted strategy change recorded in `strategy.md` but not reflected in its
+  owning spec acceptance/Non-goals. A clean review does not require gratuitous spec edits.
+- An `expand` decision auto-applied in AFK, an unapproved risk-policy change, or an
+  irreversible operation without its required authorization.
 - A pre-mortem with risks listed but no mitigation + owning slice: a risk without an owner is a
   wish.
-- The reviewer loop running past 3 iterations, or the reviewer being handed the author's
-  reasoning (defeats the fresh-context point).
+- Repeating an exhausted causal failure under the shared no-progress rule in
+  [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md), or stopping a
+  distinct cause solely because the total review round exceeds three.
+- The reviewer being handed the author's reasoning as independent evidence
+  (defeats the fresh-context point).
 - The skill writing a `plan.md`, slicing, or touching code. That's `/rite-define` / `/rite-build`.

package/pack/.claude/skills/rite-temper/reference/review-dimensions.md

@@ -61,7 +61,6 @@ justifies it. Review a borderline dimension twice if needed and use the **lower*
   irreversibility & #9 convention-fit both touch codebase realism; #1 ambition & #2 scope both
   touch over/under-reach). Don't fail two dimensions for the *same* root cause: cite the
   evidence once and assign one band so one problem does not create two floor failures.
-- Below-bar dimension after the ≤3-iteration reviewer loop → classify by decision ownership:
-  product/scope/risk uncertainty becomes a blocking question; an objective prose/coverage defect
-  routes back to `/rite-spec` without inventing a human decision. Irreversible-risk findings
-  always pause regardless of band.
+- Below-bar blocks readiness; objective fixes return to the caller under
+  [the canonical retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
+  Human-owned scope/risk choices keep their gate; exhaustion blocks technically.

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

@@ -29,7 +29,7 @@ references, and only current phase contracts needed for the observed gap.
   a current rule, exact workspace evidence, affected gate, owning rite, exact paths, and
   the smallest behavior-neutral delta.
 - Existing rites own semantic changes. Upgrade may sequence `/rite-clarify`,
-  `/rite-plan repair`, `/rite-converge`, `/rite-vet`, `/rite-prove`, `/rite-polish`,
+  `/rite-plan repair|revise|course-correct`, `/rite-converge`, `/rite-vet`, `/rite-prove`, `/rite-polish`,
   `/rite-review`, and `/rite-seal`; it never reimplements them or starts Build or Ship.
   `/rite-doctor` owns install/config diagnosis.
 - An admitted candidate route may name only the exact current gate artifacts its owner
@@ -50,7 +50,9 @@ references, and only current phase contracts needed for the observed gap.
    Archive-only is `current`; otherwise require contained regular `state.md` and read its
    cursor. A damaged/mismatched install stops at Doctor; missing live work routes
    `/rite-spec`; `done` is `current`. An unknown cursor is `unsupported`.
-1. **Freeze preservation evidence.** Record `git status --short`, cursor form/fields, and
+1. **Freeze preservation evidence.** Record `git status --short`, cursor form/fields,
+   `devrites-engine orient <slug>` (cursor, `task_graph`, `artifact_budgets`,
+   `bulk_files`), and
    hashes of completed-slice fields, candidate gate artifacts, existing answers/decisions,
    and protected history. Inventory every path that could change; absence is evidence,
    never permission to synthesize history. For a post-Build workspace, also retain the
@@ -69,6 +71,13 @@ references, and only current phase contracts needed for the observed gap.
    one at a time:
    - decision coverage or a material assumption → `/rite-clarify`;
    - stale/inconsistent planning or traceability with settled intent → `/rite-plan repair`;
+   - over-budget `state.md` or planning artifacts carrying checkpoint narrative, or
+     packets/traces in the workspace root → `/rite-plan revise` (verbatim relocation to
+     `history/` / `packets/`, current view only; IDs, meaning, answers and decisions
+     unchanged; nothing deleted);
+   - unbuilt slices beyond the [feature ceiling](../rite-plan/reference/slicing.md#feature-ceiling-split-an-epic-never-override-the-budget)
+     → `/rite-plan course-correct` (`MVP cut` plus the named continuation sequence;
+     built slices and their evidence stay);
    - live code and recorded intent disagreement → `/rite-converge`;
    - any changed planning input or readiness defect → `/rite-vet`;
    - a missing/malformed strict manifest, missing/malformed/mismatched evidence binding,

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

@@ -7,10 +7,9 @@ user-invocable: true
 
 # /rite-vet: review the plan before build
 
-Vet every plan before code for scope, architecture, quality, proof, performance,
-failure modes, and writer safety. Cite findings; fold accepted technical
-hardening into planning artifacts; design Build tests. Temper owns product
-scope, Vet owns implementation; current `$ARGUMENTS` (`--full`) feeds the depth triggers in
+Vet every plan's scope, architecture, quality, proof, performance, failures and writer
+safety. Fold cited technical findings; design Build tests. Temper owns product;
+Vet owns implementation; current `$ARGUMENTS` (`--full`) feeds the depth triggers in
 `reference/depth.md`; profiles never remove the exact plan-reviewer gate
 ([orchestration-profiles.md](../devrites-lib/reference/orchestration-profiles.md)).
 
@@ -36,8 +35,8 @@ plan declares a root-authored executable workflow file, read
 
 - Review implementation, not ambition. Challenge creep, complexity, proof, and
   risk without changing accepted product scope.
-- Root alone asks, decides, folds, writes, and sets readiness. Reviewers judge;
-  they add no route policy. Cite every finding and confidence; suppress
+- Root owns decisions/writes/readiness; reviewers judge without route policy.
+  Cite findings/confidence; suppress
   unverified or confidence ≤4 findings under `review-axes.md`.
   Lens arrows in `eng-lenses.md` are heuristics; band findings only under the
   four `review-axes.md` names.
@@ -47,8 +46,6 @@ plan declares a root-authored executable workflow file, read
   `NOTICE.md` generator regions, CI/hook config named in repo docs) require explicit
   human approval before plan slices may edit them. A slice touching a protected path
   without approval → Vet **NEEDS CLARIFICATION**.
-  **Failing case:** plan edits another feature's `state.md` without recorded approval →
-  fail closed.
 - Use the lowest axis band; never average or round thin to ready. Search before
   asking and resolve reversible technical choices. Ask only human-owned choices.
 - Preserve a valid technical return cursor. Agent-owned `NEEDS REPLAN` returns
@@ -91,7 +88,11 @@ plan declares a root-authored executable workflow file, read
    changed clause — enumerate dependents via the dep graph and traceability
    refs, not only patched sites. Otherwise record one no-progress outcome. A
    different Critical/Important invariant needs exact evidence and a new
-   fingerprint; a Suggestion, Nit, or FYI cannot keep recovery open. A packet
+   fingerprint; a Suggestion, Nit, or FYI cannot keep recovery open. Reviewer
+   `Late:` rows on unchanged clauses follow the canonical
+   [late-finding rule](../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve):
+   Critical with a failure path → new fingerprint; otherwise `eng-review.md`
+   `## Deferred findings` (mechanism rows become one proof row at step 6). A packet
    marked `convergence_pressure` accepts an explicit, bounded declared
    residual/limitation folded into the contract text as closure for a finding
    marked as a refinement of an already-pinned clause; the recheck may re-raise
@@ -101,7 +102,10 @@ plan declares a root-authored executable workflow file, read
    materialization gate — anchors applied, mirrors consistent, invariants
    pass — without a dispatched reviewer; sub-Important findings already
    cannot keep recovery open. Reconcile
-   shared artifact/readiness gates and return to caller or next repair.
+   shared artifact/readiness gates, then enter step 8 or the next repair.
+   Do not fall through to steps 2–7. Retain evidenced unchanged coverage; changed
+   global contract/uncertain impact requires full applicable review. Reopen historical
+   findings only for affected invariants/dependencies.
 2. **Challenge scope.** Apply review-axes §0 and search accepted decisions.
    Harden to the smallest contract-complete plan, using marked topology action.
    Then verify bidirectional ID-and-meaning traceability across spec/plan/
@@ -133,7 +137,11 @@ plan declares a root-authored executable workflow file, read
    Technical gaps are `NEEDS REPLAN` and Plan repair — each finding marks
    itself `new_failure_mode` or names the already-pinned clause/fingerprint
    it refines, making alias-detection and `convergence_pressure` eligibility
-   mechanical. Product/risk gaps are
+   mechanical — and carries `kind: contract | mechanism`
+   (`review-axes.md` § Finding kind). Only `contract` findings open a Plan
+   repair; a `mechanism` finding is closed by one `test-plan.md` proof row
+   at step 6 and leaves readiness intact when nothing else is open.
+   Product/risk gaps are
    `NEEDS CLARIFICATION` and Clarify. Neither becomes a Build qid.
 5. **Review axes.** Apply `review-axes.md` through `eng-lenses.md`. Fold verified
    behavior-preserving technical findings; walk only human-owned decisions.
@@ -155,12 +163,11 @@ plan declares a root-authored executable workflow file, read
    that new fingerprint as progress. Then close matrix and rerun ID/meaning audit.
 8. **Build readback and readiness.** Add a cited five-line readback to
    `eng-review.md` (artifacts.md §7 rows 1–5): outcome/ACs; IN/OUT/must-NOT; UI direction and architecture/
-   critical flow; slice order/first slice; decisive proof/action-time gates. A
-   fresh implementer must need no product, architecture, or proof invention.
+   critical flow; slice order/first slice; decisive proof/action-time gates. No implementer should need to invent product, architecture, or proof.
    Contradiction, ownerlessness, or material ambiguity blocks via Clarify or Plan.
 
    Write exactly one `Implementation readiness: READY`, `NEEDS CLARIFICATION`,
-   or `NEEDS REPLAN`. Root alone sets READY after every account, checklist,
+   or `NEEDS REPLAN`. Root sets READY after every account, checklist,
    preflight, and sweep is green. Write phase/next step and emit one
    `Readiness inputs SHA-256` with
    `devrites-engine check readiness --emit-binding <slug>`; normal readiness check
@@ -177,7 +184,7 @@ plan declares a root-authored executable workflow file, read
 > Do not replace interactive review with artifacts, change acceptance through
 > hardening, score without source evidence, or ignore unexplained complexity.
 
-## Phase exit (observable)
+## Phase exit
 
 **Complete when:** `eng-review.md` records exactly one readiness verdict, readiness
 binding SHA-256 passes, and every required reviewer account is admitted.