devrites 7.1.1 → 7.1.2

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

@@ -2,14 +2,12 @@
 
 > Applies when: always; every workspace rite reads it first.
 
-Each workspace rite reads core first. Its `loads:` manifest `always` set is its required
-read-set (`devrites-engine context --skills-root .agents/skills <slug> --skill <name>` where a workspace exists, else
-read the listed files); a trigger's files load when its named condition holds. Load any
-other rule file from `README.md` on demand.
+Read core first, then the `loads:` manifest `always` set (via
+`devrites-engine context --skills-root .agents/skills <slug> --skill <name>` with a workspace, else listed files).
+Load trigger files when their named condition holds; other `README.md` rules on demand.
 
-Rules are cited as `core.md #N` (CORE-N). Numbering is stable: text may be
-reworded, an ID never changes meaning. Other files name the ID instead of
-repeating the rule.
+Cite rules as `core.md #N` (CORE-N), not repeated text. IDs keep their meaning
+even when reworded.
 
 Uppercase MUST/MUST NOT/SHOULD/SHOULD NOT/MAY carry RFC 2119 meaning: MUST is a gate;
 a SHOULD deviation records its reason in `decisions.md` (the exception procedure); MAY
@@ -20,9 +18,9 @@ Repository conventions follow [Precedence](#precedence).
 
 ## Operating rules (every phase)
 
-1. **Right step, right time:** use the smallest workflow and load only relevant
-   files. Batch independent reads and cover the relevant code, not just the first
-   match. Prefer an available code index for structure; see
+1. **Right step, right time:** use the smallest workflow/relevant read-set. Batch
+   independent reads; cover relevant code beyond the first match. Prefer an
+   available structural code index; see
    [`tooling.md`](tooling.md) and [`code-index.md`](code-index.md).
 2. **No silent assumptions:** surface material assumptions; ask when the answer
    changes scope, architecture, data model, UX, security, migration risk, or
@@ -32,12 +30,14 @@ Repository conventions follow [Precedence](#precedence).
    when the answer changes the product.
 4. **Keep the spec current:** change spec / plan only through the Spec Drift Guard;
    never code against a known-wrong plan. A later phase MUST NOT rewrite a sealed
-   artifact in place so the code "matches." Append a dated delta through the
-   owning rite, or record drift. **Failing case:** Build edits `spec.md`
+   artifact so the code "matches." Record drift and route to the owning rite;
+   an authorized owner repair reconciles the current owning clause in place and
+   preserves rationale/history in `decisions.md`, not an adjacent dated delta. **Failing case:** Build edits `spec.md`
    acceptance criteria to fit the implementation.
-5. **One slice at a time:** leave one vertical slice working and proven, then
-   stop. HITL never auto-continues; AFK runs to its slice budget
-   ([`afk-hitl.md`](afk-hitl.md)).
+5. **One slice at a time:** prove each vertical slice working.
+   Standalone HITL stops after one slice; standalone AFK runs to its slice budget
+   ([`afk-hitl.md`](afk-hitl.md)). Active `$rite-autocomplete` returns green
+   checkpoints internally and continues the lifecycle to completion or a genuine stop.
 6. **Evidence over confidence:** tests, builds, runtime, screenshots beat
    assertions; record commands and output. Tag how each claim was known:
    `observed` (you ran or read the evidence), `inferred` (deduced — name the
@@ -69,51 +69,50 @@ Each gate is declared as **Name · Precondition · Satisfying observation (exact
 
 Verdict discipline — no vacuous verdicts:
 
-- The precondition asserts the artifact **exists and is non-empty**, not merely that its
-  path resolves. **Failing case:** a phase passes its prerequisite gate, then dies
-  mid-analysis reading a missing spec.
+- The precondition asserts the artifact **exists and is non-empty**, not just a
+  resolved path. **Failing case:** prerequisite passes, analysis dies on a missing spec.
 - A verdict is **PASS**, **FAIL**, or **NOT-RUN**. A NOT-RUN carries its named marker
   (`unavailable: <reason>`, `unproven`, `partial: <what ran>`) in the consuming artifact;
   it never renders as clean and never goes silent. **Failing case:** a review sub-step
   that never ran is simply omitted from the summary, which reads as a clean run.
-- A PASS is valid only when the observation states a **positive count of items actually
-  checked**; zero checked items is FAIL. **Failing case:** an unparseable checklist yields
-  an empty result set and a green verdict over zero evidence.
+- PASS needs a **positive count of items actually checked**; zero is FAIL.
+  **Failing case:** an unparseable checklist produces an empty green result.
 - Scope-bearing gates name their **baseline** and fail only on issues attributable to the
   change; "could not run" (timeout, unreachable, parse failure) is never recorded as
   "failed". **Failing case:** a dependency gate reddens on a pre-existing advisory
   unrelated to the diff.
-- Failure behavior is **abort** (stop; the blocked step is named) or **record-and-continue**
-  (the FAIL/NOT-RUN is recorded with its marker and the run proceeds). Both are legal;
-  silent is not.
+- Failure behavior is **abort** (name blocked step and stop) or **record-and-continue**
+  (record FAIL/NOT-RUN with its marker, proceed). Never silent.
 
 <!-- root-only -->
 ## Caller-owned technical backtracking
 
 When a rite invokes an earlier rite inline to repair an agent-owned technical gap, the original rite stays the controlling caller: a nested `STOP` is a phase boundary, not user-facing. The caller re-reads `state.md`, follows the return cursor/`next_action`, and resumes unless a human-owned, safety, access, budget, or parked-recovery stop is active ([Persistence before stopping](#persistence-before-stopping-handoff-discipline)). Derive `parked-recovery` from the fingerprint's recorded no-progress attempts and escalations, not from a stale `state.md` label; one consumed authorization doesn't exhaust offline recovery from retained new evidence.
 
-An intermediate `Next step` is cold-resume metadata. Do not ask the human to
-copy routine `$rite-plan repair`, `$rite-vet`, `$rite-build`, or proof-rerun
-commands during the active recovery chain. Only the controlling caller emits
-the final response; standalone phase invocations still stop normally.
+Under active `$rite-autocomplete`, green slice/phase checkpoints and their recorded
+`next_action` are internal continuation edges, not final replies. Consume them and
+technical backtracking until requested completion or a genuine stop; tool progress never yields control.
+
+Intermediate `Next step` is cold-resume metadata, not a human copy/paste request
+for routine `$rite-plan repair`, `$rite-vet`, `$rite-build`, or proof reruns during
+active recovery. Only the caller emits the final response; standalone phases stop normally.
 <!-- /root-only -->
 
 <!-- root-only -->
 ## Final response
 
-Immediately before its final response, each rite loads
-[`reply-contract.md`](../reply-contract.md) then uses the compact form: evidenced
-claims plus one next action.
+Immediately before its final response, the controlling caller or standalone rite loads
+[`reply-contract.md`](../reply-contract.md): compact evidenced claims, one next action.
 <!-- /root-only -->
 
 ## Rationalization guard
 
-On an excuse, apply its matching
-[`anti-patterns.md` rebuttal](anti-patterns.md#universal-rationalizations) before continuing.
+Before continuing on an excuse, apply its
+[`anti-patterns.md` rebuttal](anti-patterns.md#universal-rationalizations).
 
 ## Rule summary (load the full file when in scope)
 
-These universal musts link to their full rules; load depth only when needed.
+Universal musts; load linked rules when needed.
 
 - **Fail fast, no silent catches.** Validate early; catch narrow, recover or
   rethrow with context; fail closed on auth/permission/transaction. →
@@ -136,7 +135,7 @@ These universal musts link to their full rules; load depth only when needed.
 - **Measure before you optimize.** An optimisation without a measurement is a
   guess that adds complexity. → [`performance.md`](performance.md)
 - **Names reveal intent.** No `process()` / `handle()` / `data` / `temp`.
-  One concept, one word, across the codebase. → [`coding-style.md`](coding-style.md)
+  One word per concept codebase-wide. → [`coding-style.md`](coding-style.md)
 - **Comments explain *why*, not *what*.** Rename before you comment; delete
   commented-out code. → [`coding-style.md`](coding-style.md)
 - **Write like a human, not a model.** Cut filler, fake contrast/profundity,
@@ -167,19 +166,21 @@ Before any `rite-*` skill stops:
   [--unset key]`; a new ledger section via `state append <slug> <ledger> --heading "<id>"
   --body-file <path|->`. Never splice workspace Markdown with an ad-hoc script or regex.
 
-A skill that stops without doing this leaves the workspace incomplete.
+Stopping without this leaves an incomplete workspace.
 <!-- /root-only -->
 
 ## Context hygiene (end of every phase)
 
 Long contexts degrade reasoning quality. Act on context at **50-70% used, not 95%**.
 
-Read the engine `context` bundle once per phase instead of re-reading the files it
-contains; after compaction re-read the bundle, not its sources.
+Read the engine `context` bundle once per phase, not its sources; after compaction
+re-read the bundle.
 
 <!-- root-only -->
-Every rite names the single resume command on its action line; a `↻ Hygiene:` footer
-advises `/clear`, `/compact`, or `$rite-handoff` and never a competing command. Full phase-by-phase guidance:
+Only controlling-caller final replies or standalone rites name a resume command
+on the action line; nested phases persist it internally, not as a handoff.
+A `↻ Hygiene:` footer advises `/clear`, `/compact`, or `$rite-handoff`, never a
+competing command. Phase guidance:
 [`context-hygiene.md`](context-hygiene.md).
 <!-- /root-only -->
 

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

@@ -140,30 +140,28 @@ next sequence continuation through Vet in a second session, then stop.
    product scope is never auto-resolved by a recommended option; it stops for a human.
    A spent strategy escalates; parked recovery records
    `Next step: $rite-autocomplete`, never a routine phase command. **Completion:** no stop is active, or its cursor and reason are durable.
-6. **Seal boundary.** Without a ship flag, leave the sealed workspace unshipped and
-   open the next recorded continuation
+6. **Seal boundary.** With or without a ship flag, leave intermediate sealed
+   workspaces unshipped and open the next recorded continuation
    ([loop.md § Sequence continuation](reference/loop.md#sequence-continuation))
    unless `continue_sequence: false`, the sequence budget is spent, or no entry
-   remains; then stop at Seal GO with `$rite-ship`. Report the sequence position on
-   every stop.
-   With a ship flag, perform Ship preflight, disclose the exact Git plan, and stop for
-   fresh literal `GO` plus native approval. **Completion:** performed no Git action before fresh literal `GO` plus native approval.
+   remains. At that boundary without a ship flag, stop at Seal GO with `$rite-ship`.
+   Report sequence position at every stop. Only at that boundary, with a ship flag, perform Ship preflight,
+   disclose the exact Git plan, and stop for fresh literal `GO` plus native approval. **Completion:** performed no Git action before fresh literal `GO` plus native approval.
 
 ## Reply and resume
 
-HITL Build returns after one slice; Autocomplete ignores `--max-slices` and
-keeps chaining pending slices. One Autocomplete invocation owns all internal
-backtracking. Context pressure, compaction, or a nested completion footer does
+HITL Build returns after one slice; Autocomplete ignores `--max-slices`, chaining
+pending slices. Each Autocomplete invocation owns internal backtracking. Context pressure, compaction, or a nested completion footer does
 not create a stop; persist and resume the cursor.
 
-Reply only at a final state, never as mid-run progress: a text-only turn ends
-the run, so after a compaction or phase change keep calling tools. Use one terse line:
+Reply only at final state: text-only turns end the run. Keep
+calling tools after compaction or phase changes. Use one line:
 
 ```text
 Autocomplete: <slug>
 spec <done|stopped> · clarify <clear|stopped> · temper <done|stopped> · define <done|stopped> · vet <ready|stopped> · build <n/N|stopped> · prove <done|stopped> · polish <done|stopped> · review <done|stopped> · seal <GO|NO-GO|stopped>
 ```
 
-Final state is `Shipped`, `Stopped`, `Awaiting human`, `NO-GO`, or `GO`; do not
-write a narrative recap. Require a clean or accepted baseline, land a local
-unpushed checkpoint after each green check, and never auto-pass a red gate.
+Final state: `Shipped`, `Stopped`, `Awaiting human`, `NO-GO`, or `GO`; no narrative
+recap. Require clean or accepted baseline; land local unpushed checkpoints after
+each green check; never auto-pass red gates.

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

@@ -1,7 +1,6 @@
 # The autocomplete loop: arm AFK, drive every phase
 
-Autocomplete sequences existing `/rite-*` workflows without pausing between
-routine phases. Acceptance-preserving Reslice authority is
+Autocomplete chains existing `/rite-*` workflows without routine-phase pauses. Acceptance-preserving Reslice authority is
 `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
 <!-- BEGIN RESLICE ROUTE-TO-ACTION -->
@@ -23,7 +22,7 @@ allow_gates: [advisory, validating]
 # notify: "<cmd>"
 ```
 
-Read an existing sentinel first. Preserve it byte-for-byte when valid, except
+Read existing sentinel first. Preserve valid bytes, except
 when this invocation contains `--parallel N`: then write or replace only
 `max_parallel: N` and leave every other key unchanged. Stop if the sentinel is
 malformed. Do not stop because it names `max_slices` / `max_agents` /
@@ -41,10 +40,9 @@ remaining. AFK configuration itself stays unchanged.
 
 ### Admit each unattended cycle
 
-Before every phase, review fan-out, recovery, or writer dispatch: cheapest
+Before each phase, review fan-out, recovery, or writer dispatch: cheapest
 readiness check first; reject overlap. Do not stop on `max_agents`,
-`max_minutes`, or `max_review_queue`. Count every leaf result. A new activation
-gets fresh activation-local counters but retains durable slice/recovery state.
+`max_minutes`, or `max_review_queue`. Count every leaf result. New activations reset activation-local counters, retaining durable slice/recovery state.
 
 [Build return](../../rite-build/reference/output.md#caller-owned-continuation).
 Pass `--parallel N`; ignore leftover cap/headroom, remaining-0,
@@ -57,7 +55,7 @@ without recommendations, and Seal judgment (`slice: seal`) still pause.
 
 ## Phase arc
 
-Workspace files carry state; chat does not. Read and execute each phase skill:
+Workspace files, not chat, carry state. Read/execute each phase skill:
 
 | Step | Phase | Completion / edge |
 | --- | --- | --- |
@@ -73,9 +71,8 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 10 | `$rite-seal` | GO/NO-GO; no Git |
 | 11 | `$rite-ship` | only after GO; `--ship` never authorizes Git; stop at literal-GO/native approval |
 
-Before advancing, check
-[stop-conditions.md](stop-conditions.md). After source edits, discard stale pass
-evidence. Re-read the active workspace before each phase. On a cold resume or
+Check [stop-conditions.md](stop-conditions.md) before advancing. Discard stale
+pass evidence after source edits. Re-read active workspace before each phase. On a cold resume or
 new activation, run `devrites-engine check regression <slug>`: `BLOCKED` names a
 durable fact lost since the last checkpoint — restore or route it through its
 owning phase before continuing; `unproven` does not block. After each phase's
@@ -92,37 +89,35 @@ step 10 does not end the run: leave the sealed workspace unshipped with its
 (`$rite-spec <parent>-<n> "<objective>"` from the parent's `decisions.md` sequence)
 and re-enter step 1. Spend one workspace per opened continuation.
 
-When that workspace already exists because a [lookahead](lookahead.md) session
-planned it, do not specify it again. Wait while `devrites-engine claim check
---workspace <child>` exits 3 (a live lookahead holds it), then set
-`.devrites/ACTIVE` to the child and resume from its cursor at step 1. A
-predecessor replan since its Vet blocks the child's readiness with
-`DRV-GATE-READINESS-STALE`; route that to `$rite-vet` before Build.
-
-Spend accounting is durable in `state.md` cursors, not chat. Before invoking the
-continuation, ensure the current workspace's `sequence_workspaces_remaining` is
-set — absent, write `max_workspaces - 1` and `sequence_position: 1` first — and
-`> 0`. `$rite-spec` seeds the child's sequence cursor at creation per the
+For a child already planned by [lookahead](lookahead.md), do not re-specify.
+Wait while `devrites-engine claim check --workspace <child>` exits 3 (live
+lookahead), then set `.devrites/ACTIVE` to the child and resume its cursor at
+step 1. A predecessor replan since its Vet blocks child readiness with
+`DRV-GATE-READINESS-STALE`; route to `$rite-vet` before Build.
+
+Before invoking a continuation, require durable `state.md`
+`sequence_workspaces_remaining > 0`; if absent, first write
+`max_workspaces - 1` and `sequence_position: 1`. `$rite-spec` seeds the child's sequence cursor at creation per the
 [continuation contract](../../rite-plan/reference/slicing.md#continuation-workspaces);
-after the child's `state.md` exists, verify it — `sequence_parent` = the current
-slug, `sequence_position` = parent position + 1,
+verify the created child's `state.md`: `sequence_parent` = current slug,
+`sequence_position` = parent position + 1,
 `sequence_workspaces_remaining` = parent remaining − 1, and — when the recorded
 entry is the sequence's release milestone — `sequence_role: release` (gates then
-require the union manifest). On resume, a child whose
-fields are missing is re-seeded from its `brief.md` parent/position and the
-parent's counter (same values, never a second charge); a child with no recorded
-parent/position is not a sequence member and the chain stops.
-
-Stop instead when: no recorded next entry; the cap or review-queue bound is
-reached; a human-owned, safety, access, or parked-recovery stop fires; or Seal returns
-`NO-GO`. On stop, report the sequence position, the sealed-but-unshipped workspaces, and
-the single release command (`$rite-autocomplete <release milestone> --ship`, or
+require the union manifest). On resume, re-seed missing child fields from its `brief.md` parent/position and
+parent counter (same values, no second charge). No recorded parent/position
+means no sequence membership: stop the chain.
+
+Stop sequence continuation when: `continue_sequence: false`; no recorded next
+entry (the final milestone); the `max_workspaces` cap is reached; or a genuine
+human-owned, safety, access, or parked-recovery stop fires. `max_review_queue`
+never stops Autocomplete; agent-owned Seal `NO-GO` enters recovery, not a handoff.
+Intermediate sealed milestones continue without `--ship` and without Git mutation. On stop, report sequence position, sealed/unshipped workspaces, and
+one release command (`$rite-autocomplete <release milestone> --ship`, or
 `$rite-ship` for the current sealed workspace when the sequence is complete).
 
 ## Backtrack without handing off
 
-The active Autocomplete root remains caller whenever a later phase exposes an
-agent-owned earlier-phase gap:
+Autocomplete remains caller for agent-owned earlier-phase gaps:
 
 1. Save the originating phase/action unless a valid native return cursor exists.
 2. On cold resume, reconcile the terminal cursor against durable fingerprint
@@ -152,6 +147,8 @@ and park it after three escalations while independent work continues.
 
 ## Continuous caller obligation
 
+Green slice/phase checkpoints consume their recorded `next_action` internally;
+only the caller replies finally at completion or a genuine stop.
 No user-facing reply is permitted while durable state contains agent-owned
 `NEEDS_REPLAN`, an intermediate Plan/Vet action, a distinct retained
 Critical/Important fingerprint below its cap or with an escalation left, runnable
@@ -162,7 +159,6 @@ already names a ranked recommended option. Invoke the next internal repair or
 `state resolve` exits 1 on every call and the loop re-invokes it without end. A narrow reviewer closing one finding and exposing another
 Critical/Important invariant is progress, not exhaustion.
 
-The number of completed repair/Vet cycles is not a stop condition. Context
-pressure, compaction, session duration, and nested completion do not convert an
-internal checkpoint into a handoff. Persist it and resume until the requested
-rest point or a shared human/safety/access/parked-recovery condition.
+The number of completed repair/Vet cycles, context pressure, compaction, session
+duration, and nested completion never turn checkpoints into handoffs. Persist and
+resume to the requested rest point or shared human/safety/access/parked-recovery stop.

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

@@ -1,9 +1,8 @@
 # Stop conditions: when autocomplete pauses
 
-On a real stop, write `state.md` as `awaiting_human` or `blocked`, persist the
-reason, and include one resume command. Agent-owned recovery never ends the run:
-a spent strategy escalates and a fully escalated fingerprint parks while other
-work continues ([retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve)).
+On real stops, persist `state.md` `awaiting_human` or `blocked`, reason, and one
+resume command. Agent-owned recovery never ends the run: spent strategies
+escalate; fully escalated fingerprints park while other work continues ([retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve)).
 `--ship` never bypasses a stop.
 
 Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
@@ -16,7 +15,7 @@ Authority: `.agents/skills/devrites-lib/reference/standards/acceptance-preservin
 
 ## Always stop
 
-Regardless of flags or AFK ceiling:
+Flags/AFK ceiling never override:
 
 - destructive data migration;
 - auth/authz boundary change;
@@ -24,8 +23,8 @@ Regardless of flags or AFK ceiling:
 - external-service contract change; or
 - filesystem destruction outside the workspace.
 
-Red proof cannot advance. Run bounded Debug Recovery and escalate spent
-strategies; a fully escalated fingerprint parks unless the remaining owner is human.
+Red proof cannot advance. Run bounded Debug Recovery; escalate spent strategies.
+Fully escalated fingerprints park unless remaining owner is human.
 
 ## Not stops: internal technical routing
 
@@ -34,13 +33,12 @@ forward work, persists the return cursor, and invokes Plan repair plus Recovery
 Vet inline. The same applies to nested `STOP`/`Next step` when its decision is
 agent-owned.
 
-Agent-owned backtracking is not a stop condition while the exact causal
-fingerprint has budget. Invoke the earlier phase, affected Vet, remediation, and
-proof; then resume the origin. Three no-progress corrections of that exact
-fingerprint spend only its current strategy: escalate to the next correction
-class inline (shared root cause, diagnostic amplification, boundary redesign)
-with a fresh budget, never asking permission. After three escalations in this
-activation the fingerprint parks; finish all independent work, then stop once.
+Agent-owned backtracking is not a stop condition while its exact causal
+fingerprint has budget: invoke earlier phase, affected Vet, remediation, proof;
+resume origin. Three no-progress corrections spend only that fingerprint's current
+strategy: escalate inline to the next class (shared root cause, diagnostic
+amplification, boundary redesign) with fresh budget, without permission. After
+three escalations per activation it parks; finish independent work, then stop once.
 Preserve reproduction, attempts, and dead ends; never offer `$rite-plan unblock`
 or another routine phase command. A new user-issued `$rite-autocomplete`
 reopens parked fingerprints with fresh escalation; wakes and compaction do not.
@@ -52,11 +50,10 @@ It blocks another execution; retained new Critical/Important evidence still
 enters offline recovery. After affected Vet is READY, pause for fresh action
 authorization and never reuse old GO.
 
-Past evidence being irretrievable is not by itself terminal. If an in-scope
-trusted seam can uniquely discriminate the next failure, run diagnostic-
-amplification Plan repair and narrow Vet inline, then pause for fresh GO before
-one evidence-acquisition attempt. Without a safe seam, escalate to the next
-class or park; only a real human/risk/scope gate stops for a human.
+Past evidence being irretrievable is not by itself terminal. If an in-scope trusted seam
+uniquely discriminates the next failure, run diagnostic-amplification Plan repair
+and narrow Vet inline; pause for fresh GO before one evidence-acquisition attempt.
+Without a safe seam, escalate or park; only a real human/risk/scope gate stops for a human.
 
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"classifier returns owner-busy, exhausted, or existing hard gate","action":"escalate BLOCKED_EXHAUSTED; on WAIT_ACTIVE_OWNER run independent work and recheck; stop on exact BLOCKED_GATE result","return":"unchanged cursor plus fixed route-owned output"} -->
 ## Other stop classes
@@ -76,10 +73,9 @@ class or park; only a real human/risk/scope gate stops for a human.
 - **Clarify:** material `open`/unowned decision coverage or a
   low-confidence high-consequence assumption. Continue the initial interview;
   never arm AFK early.
-- **Seal:** remaining NO-GO after recommended-option questions are closed, with
-  every remaining blocker and fix direction. Never round up to GO. An open
-  recommended-option blocking question is not a Seal stop: resolve it, recover
-  agent-owned findings, then re-enter Seal. A first NO-GO is not a stop either:
+- **Seal:** report remaining NO-GO with every blocker/fix direction; never round
+  up to GO. Resolve recommended-option blocking questions internally; recover
+  agent-owned findings and re-enter Seal. A first NO-GO is not a stop:
   recover every agent-owned blocker (missing or unbound proof, a reviewer gap root
   can close, a finding with a fix direction, a missing `review.md` verdict), then
   re-enter Seal. The unattended `N` to accepting Important risks means repair, not
@@ -97,23 +93,26 @@ class or park; only a real human/risk/scope gate stops for a human.
 - **Resource envelope:** overlapping run or missing AFK after arm still stops.
   Do not stop on `--max-slices`, `max_agents`, `max_minutes`, or `max_review_queue`.
 - **Confidence:** intent still cannot become testable acceptance after interview.
-- **Repeated failure:** not a stop. Escalate; a fully escalated fingerprint parks,
-  and the run stops only once no independent work remains.
-- **Resolver failure:** `devrites-engine state resolve` not found, or nonzero exit.
-  Never hand-edit `questions.md`/`state.md` in its place. Not found stops at once;
-  nonzero allows one identical re-run (the fingerprint is command + exit code +
-  decisive stderr line; an unchanged re-run is not a correction, so no further
-  attempts). Then stop `blocked` with the exact command, exit code, and stderr line,
-  and resume action `$rite-doctor`.
+- **Repeated failure:** not a stop. Escalate; fully escalated fingerprints park.
+  Stop only when no independent work remains.
+- **Resolver failure:** `devrites-engine state resolve` missing or nonzero.
+  Never hand-edit `questions.md`/`state.md` instead. Missing stops immediately;
+  nonzero permits one identical re-run (fingerprint: command + exit code + decisive
+  stderr line; unchanged re-run is no correction, no further attempts). Then stop
+  `blocked`: exact command, exit code, stderr line; resume via `$rite-doctor`.
 
 ## Final GO and durable stop
 
-`--ship`/`--yolo` never authorizes Git. With a flag, complete Ship preflight,
-disclose the exact plan, and stop for literal `GO` plus native approval. Without
-one, stop at Seal GO with `$rite-ship`. Seal GO, AFK, prior approval, and flags
-never satisfy Ship approval.
+With a recorded continuation, no opt-out, and workspace budget, Seal GO stays
+internal: continue without `--ship`, leaving milestones sealed/unshipped. Only the
+final milestone, explicit `continue_sequence: false`, or exhausted sequence cap
+ends green sequence continuation.
 
-A cold-resumable stop records `state.md` status, exact reason, and one resume
-action: the human-owned action, or `$rite-autocomplete` to reopen parked
-fingerprints; the owning question/drift/seal entry explains it. The user-facing line says what stopped
-and, only when applicable, what human action resumes it.
+There, `--ship`/`--yolo` requires [Ship preflight](../../rite-ship/reference/git-ship.md#before-type-go):
+disclose exact plan; stop for fresh literal `GO` plus native approval.
+Without flags, stop at Seal GO with `$rite-ship`. Seal GO never authorizes Git
+or satisfies Ship approval; neither do AFK, prior approval, or flags.
+
+Record cold-resumable `state.md` stops: status, exact reason, one resume action
+(human-owned or `$rite-autocomplete` to reopen parked fingerprints). Explain in
+owning question/drift/seal entry. Tell user what stopped and any required human action.

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

@@ -147,21 +147,18 @@ Pull these via `Read` when shaping the plan:
    cross-slice boundary names producer, consumer, invariant, integration step, and proof.
    Map each applicable topology/data/integration risk to a slice, failure/recovery path,
    and discriminating proof; a risk cannot live only in the architecture narrative.
-4a. **Persist traceability natively.** The drafter proposes and root writes
+4a. **Persist traceability natively.** Drafter proposes; root writes
    `traceability.md` (`AC/REQ ID → slice → proof → evidence ID → files → status`).
-   Re-read spec, tasks, and proof fields: every ID must exist and every mapping
-   preserve meaning, not just labels. Reject orphans, inventions, and false mappings;
-   `$rite-prove` and `$rite-seal` read this file directly. Reference the plan's
-   `Shared contract proof` rows from existing slice/proof mappings; do not create a second
-   traceability system.
-5. **Complexity and deviations gate:** justify anything outside DevRites defaults (new dep,
-   extra abstraction, second design system) in the plan; if you can't justify it, simplify.
-   **Principles conformance:** read `.devrites/principles.md` (if present) and confirm the
-   approach honors every declared invariant. A plan that conflicts with one is not "a deviation
-   to justify away": either reshape the approach to conform, or, when the conflict is genuine and
-   intended, route it through the Spec Drift Guard plus a recorded decision and a scoped principle
-   exception a human approves. Never ready a plan that silently violates an invariant. (Re-scored
-   as a blocking gate at `$rite-vet`; no file → none declared → nothing to check.)
+   Re-read spec/tasks/proof: require real IDs, meaning-preserving mappings, not
+   just labels. Reject orphans/inventions/false mappings. `$rite-prove` and
+   `$rite-seal` read it directly. Reference plan `Shared contract proof` rows from
+   existing slice/proof mappings; never create a second traceability system.
+5. **Complexity and deviations gate:** justify deviations from DevRites defaults
+   (new dep, extra abstraction, second design system) in plan; else simplify.
+   **Principles conformance:** honor all `.devrites/principles.md` invariants
+   (absent → none). Reshape conflicts; intended genuine conflicts need Spec Drift
+   Guard, a recorded decision, and a human-approved scoped principle exception.
+   Never ready silent violations; `$rite-vet` re-scores this blocking gate.
 6. **Write** `architecture.md`, `plan.md`, `tasks.md`, and `traceability.md` — save the
    accepted bundle under `packets/` and apply it with `devrites-engine state
    apply-bundle <slug> <bundle.json>` before root reconciliation edits; update
@@ -169,27 +166,31 @@ Pull these via `Read` when shaping the plan:
    `flows.md` (**Mermaid-first**). If a richer reviewable visual earns it, emit
    `visual/<flow>.html` + `visual/<flow>.outline.md` after loading matching playbooks from
    [`../devrites-lib/reference/visual-playbooks/index.md`](../devrites-lib/reference/visual-playbooks/index.md)
-   (progressive; never preload all seven), link the pair from `flows.md`, treat outline as
-   SSOT (outline wins), and never require Lavish or a new phase.
-6a. **Cross-artifact gate.** Read spec, tasks, and traceability together: every
-   buildable AC/REQ maps to an existing slice/proof, every slice maps to real
-   acceptance, and names/prose agree. Missing, duplicate, contradictory, or
-   meaning-changing mappings block. Then run
+   (progressive; never preload all seven), link both from `flows.md`; outline is
+   SSOT (wins). No Lavish or new phase required.
+6a. **Cross-artifact gate.** Read spec/tasks/traceability together: each buildable
+   AC/REQ maps to existing slice/proof; each slice maps to real acceptance;
+   names/prose agree. Missing, duplicate, contradictory, or meaning-changing
+   mappings block. Run
    `devrites-engine check task-graph <slug> --strict`; a malformed dependency graph, or a
    shared path written by `hubAdvisoryMin`+ slices with no `Serial rationale:`, blocks
-   before Vet rather than spending a reviewer context on invalid tasks. Resolve each
+   before Vet; no reviewer context for invalid tasks. Resolve each
    `ADVISORY size:`/`hub:`/`chain:` line now (split or seam slice, or a rationale);
    `--strict` refuses the contended plan, the default run only advises.
 7. **Readiness gate** (`plan-template.md`): require CLEAR coverage; complete acceptance,
    wiring, shared-contract proof, applicable outputs, and rollback; risk-first acyclic order;
    justified deviations; and every horizon item present, with blockers resolved, planning
    items resolved/validly spiked, and local/action entries bounded and owned.
-   **Stop and confirm** before code. Render the review-before-code
-   digest first: `Intent` (one sentence from the spec), `Done means` (acceptance coverage x/y),
-   `Plan sanity` (slice count + riskiest boundary/gate), `Expected build interruptions`
-   (`none` or only justified action-time gates), and `Build exactly this?` (yes → approve;
-   no → `$rite-plan revise`). When the human confirms the plan, write `Plan approved: <iso>` to
-   `state.md` (see [state-workspace](../rite-spec/reference/state-workspace.md)).
+   **Standalone: stop and confirm** before code. Render digest: `Intent` (one
+   spec sentence), `Done means` (AC coverage x/y), `Plan sanity` (slice count +
+   riskiest boundary/gate), `Expected build interruptions` (`none` or justified
+   action-time gates), `Build exactly this?` (yes → approve; no → `$rite-plan revise`).
+   Human confirmation writes `Plan approved: <iso>` to `state.md`
+   ([state-workspace](../rite-spec/reference/state-workspace.md)).
+   Under active `$rite-autocomplete`, once this readiness gate is green and no
+   unresolved human-owned decision, irreversible-risk, scope, or access gate remains,
+   root writes autonomous approval to existing `Plan approved: <iso>` cursor and records Autocomplete provenance and rationale in `decisions.md`;
+   never claim human approval. Return internally for `$rite-vet`. Plan approval grants no protected-path, Git, or safety authority.
 
 ## tasks.md slice format
 

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

@@ -172,8 +172,13 @@ Before classifying any Reslice, read `.agents/skills/devrites-lib/reference/stan
    the previous vet verdict: set `Phase: plan`, `Next step: $rite-vet`, and, when
    `eng-review.md` exists, set `Implementation readiness: NEEDS REPLAN`. Never retain READY
    across changed planning inputs. Preserve `Plan approved` only for behavior/acceptance-neutral
-   technical repair; clear it for a contract-changing or newly blocking horizon item and
-   reconfirm only after Clarify and Vet close it. If you stopped for drift,
+   technical repair; clear it for a contract-changing or newly blocking horizon item.
+   Settle human decisions and restore current `CLEAR` coverage through Clarify,
+   then obtain renewed Plan approval BEFORE Vet using only
+   [`rite-define`'s readiness/approval rule](../rite-define/SKILL.md), not its initial
+   decomposition. Under active Autocomplete, retain that rule's explicit autonomous
+   provenance in `decisions.md` — never claim human approval. Approval grants no
+   protected-path, Git, or safety authority. If you stopped for drift,
    mark the `drift.md` entry resolved. Never remove or overwrite a valid caller
    return cursor while writing the Plan checkpoint.
 6. After editing `brief.md`, `spec.md`, `decisions.md`, `assumptions.md`, or `questions.md`,

package/pack/generated/codex/skills/rite-plan/reference/replan-and-repair.md

@@ -19,8 +19,11 @@ First (or fresh) breakdown into vertical slices. Use `task-breakdown.md` +
 
 A slice proved too large (couldn't build+prove in one cycle, or its goal has multiple
 "and"s). Split into thinner end-to-end slices, preserving acceptance coverage: split
-**by the sizing rule, not to a target count**. Update `tasks.md`; renumber; fix
-dependency edges.
+**by the sizing rule, not to a target count**. Update `tasks.md` under the canonical
+[ID contract](../../devrites-lib/reference/workspace-artifact-schema.md#id-contract):
+preserve unaffected IDs; never renumber or fill retired gaps. New meanings get the
+next unused IDs; record relationships in `decisions.md` or `drift.md` before updating
+downstream dependency edges and traceability.
 
 ## repair (after Spec Drift Guard)