devrites 6.0.4 → 6.1.1

package/pack/generated/pi/skills/overhaul/SKILL.md

@@ -101,24 +101,24 @@ deployment, or anything the user did not start with this command.
 
 ## Step 1 — Audit
 
-1. Dispatch `recon` ([`overhaul-recon`](.pi/agents/overhaul-recon.md)); admit its inventory,
+1. Dispatch `recon` ([`overhaul-recon`](../../agents/overhaul-recon.md)); admit its inventory,
    components, lanes, partitions, contract seeds and journeys into `coverage.json`,
    `stack-profiles.json` and `contracts.json`, and record the applicability matrix
    in `coverage.json` ([`references/audit-domains.md`](references/audit-domains.md#applicability-matrix)).
 2. Compose profiles per component ([`references/stack-profiles.md`](references/stack-profiles.md));
    research unknown stacks through the unknown-stack procedure.
 3. Launch the concurrent engineering wave: when both lanes apply,
-   [`overhaul-frontend-engineer`](.pi/agents/overhaul-frontend-engineer.md) and
-   [`overhaul-backend-engineer`](.pi/agents/overhaul-backend-engineer.md) go out in the same dispatch
+   [`overhaul-frontend-engineer`](../../agents/overhaul-frontend-engineer.md) and
+   [`overhaul-backend-engineer`](../../agents/overhaul-backend-engineer.md) go out in the same dispatch
    batch before you await either. Fill remaining slots with
-   [`overhaul-boundary`](.pi/agents/overhaul-boundary.md), [`overhaul-craft`](.pi/agents/overhaul-craft.md) and
-   [`overhaul-specialist`](.pi/agents/overhaul-specialist.md) in bounded waves; reserve verifier and
+   [`overhaul-boundary`](../../agents/overhaul-boundary.md), [`overhaul-craft`](../../agents/overhaul-craft.md) and
+   [`overhaul-specialist`](../../agents/overhaul-specialist.md) in bounded waves; reserve verifier and
    critic capacity first. Domain floor: [`references/audit-domains.md`](references/audit-domains.md).
    Without real concurrency: `BLOCKED_PARALLEL_CAPABILITY`; offer degraded
    sequential review only when fresh contexts can still be started one at a time.
 4. Admit every receipt with `devrites-engine overhaul admit receipt`; anchor every
    quoted location with `devrites-engine overhaul admit anchor`; send serious or
-   ambiguous candidates to [`overhaul-verifier`](.pi/agents/overhaul-verifier.md) (`finding-verify`)
+   ambiguous candidates to [`overhaul-verifier`](../../agents/overhaul-verifier.md) (`finding-verify`)
    in lane batches of up to 8. Run coverage critics after waves, launch the gaps they
    name without waiting for verifiers, and run a final-clean critic before calling
    coverage complete.
@@ -143,7 +143,7 @@ deployment, or anything the user did not start with this command.
    reconfirmation otherwise), the re-hashed plan digest, the task closure, the current
    plan revision, no later stop, and for PR or branch scope a checked-out `HEAD` equal
    to the pinned head. Record it in `approval.json`.
-2. Execute the approved DAG with [`overhaul-implementer`](.pi/agents/overhaul-implementer.md): one
+2. Execute the approved DAG with [`overhaul-implementer`](../../agents/overhaul-implementer.md): one
    writer per path, independent frontend and backend tasks concurrently, TDD per
    [`references/repair-and-measurement.md`](references/repair-and-measurement.md).
    Admit patches only when observed changed paths equal the contract.
@@ -166,14 +166,14 @@ revocation stays in force.
 
 | Role | Agent | Mode |
 | --- | --- | --- |
-| Reconnaissance and coverage mapper | [`overhaul-recon`](.pi/agents/overhaul-recon.md) | read-only |
-| Frontend engineering reviewer | [`overhaul-frontend-engineer`](.pi/agents/overhaul-frontend-engineer.md) | read-only |
-| Backend engineering reviewer | [`overhaul-backend-engineer`](.pi/agents/overhaul-backend-engineer.md) | read-only |
-| Boundary and contract reviewer | [`overhaul-boundary`](.pi/agents/overhaul-boundary.md) | read-only |
-| Frontend craft, interaction and accessibility | [`overhaul-craft`](.pi/agents/overhaul-craft.md) | read-only |
-| Language, risk and other-lane specialist | [`overhaul-specialist`](.pi/agents/overhaul-specialist.md) | read-only |
-| Frontend or backend remediation implementer | [`overhaul-implementer`](.pi/agents/overhaul-implementer.md) | writes approved paths only |
-| Verifier, critic and final challenger | [`overhaul-verifier`](.pi/agents/overhaul-verifier.md) | read-only |
+| Reconnaissance and coverage mapper | [`overhaul-recon`](../../agents/overhaul-recon.md) | read-only |
+| Frontend engineering reviewer | [`overhaul-frontend-engineer`](../../agents/overhaul-frontend-engineer.md) | read-only |
+| Backend engineering reviewer | [`overhaul-backend-engineer`](../../agents/overhaul-backend-engineer.md) | read-only |
+| Boundary and contract reviewer | [`overhaul-boundary`](../../agents/overhaul-boundary.md) | read-only |
+| Frontend craft, interaction and accessibility | [`overhaul-craft`](../../agents/overhaul-craft.md) | read-only |
+| Language, risk and other-lane specialist | [`overhaul-specialist`](../../agents/overhaul-specialist.md) | read-only |
+| Frontend or backend remediation implementer | [`overhaul-implementer`](../../agents/overhaul-implementer.md) | writes approved paths only |
+| Verifier, critic and final challenger | [`overhaul-verifier`](../../agents/overhaul-verifier.md) | read-only |
 
 Dispatch each role as its named agent with a packet
 ([`references/orchestration.md`](references/orchestration.md)). The agents keep every

package/pack/generated/pi/skills/overhaul/references/audit-domains.md

@@ -267,7 +267,7 @@ Review real source semantics under the active client profiles:
 
 ## Frontend craft, interaction and accessibility
 
-The craft role ([`overhaul-craft`](.pi/agents/overhaul-craft.md)) examines the existing brief and
+The craft role ([`overhaul-craft`](../../../agents/overhaul-craft.md)) examines the existing brief and
 design system, hierarchy, typography, spacing, density, tokens, theming, semantics,
 focus, keyboard operation, touch and pointer, zoom and reflow, responsive or native
 layout, localization and long or RTL content; every UI state (loading, empty, error,
@@ -309,7 +309,7 @@ major restructuring.
 
 ## Cross-layer contracts
 
-The boundary role ([`overhaul-boundary`](.pi/agents/overhaul-boundary.md)) owns the live graph of
+The boundary role ([`overhaul-boundary`](../../../agents/overhaul-boundary.md)) owns the live graph of
 API operations, events and messages, server actions, IPC/FFI, shared models,
 generated clients and the critical journeys consuming them, and checks both
 producer and consumer: schema, version, enum and nullability; numeric, ID and date

package/pack/generated/pi/skills/overhaul/references/orchestration.md

@@ -31,11 +31,11 @@ directory names or file extensions. One package or file can serve several lanes.
 
 | Lane | Owns | Agent |
 | --- | --- | --- |
-| Frontend engineering | Client correctness, state/data flow, component architecture, framework idioms, client security, frontend performance and tests (web, native, desktop, game UI) | [`overhaul-frontend-engineer`](.pi/agents/overhaul-frontend-engineer.md) |
-| Backend engineering | Service, domain, API, job, data, concurrency, authorization and service performance, including server parts of full-stack frameworks | [`overhaul-backend-engineer`](.pi/agents/overhaul-backend-engineer.md) |
-| Boundary / integration | Producer/consumer contracts, shared packages, serialization, trust transitions, deployment skew | [`overhaul-boundary`](.pi/agents/overhaul-boundary.md) |
-| Frontend craft | Design system fit, interaction states, keyboard/focus, accessibility, responsive and motion evidence | [`overhaul-craft`](.pi/agents/overhaul-craft.md) |
-| Other | Build tooling, CI, infrastructure, libraries, data/ML workloads, operations readiness, public API and CLI experience, documentation — explicit extra profiles, never forced into frontend/backend | [`overhaul-specialist`](.pi/agents/overhaul-specialist.md) |
+| Frontend engineering | Client correctness, state/data flow, component architecture, framework idioms, client security, frontend performance and tests (web, native, desktop, game UI) | [`overhaul-frontend-engineer`](../../../agents/overhaul-frontend-engineer.md) |
+| Backend engineering | Service, domain, API, job, data, concurrency, authorization and service performance, including server parts of full-stack frameworks | [`overhaul-backend-engineer`](../../../agents/overhaul-backend-engineer.md) |
+| Boundary / integration | Producer/consumer contracts, shared packages, serialization, trust transitions, deployment skew | [`overhaul-boundary`](../../../agents/overhaul-boundary.md) |
+| Frontend craft | Design system fit, interaction states, keyboard/focus, accessibility, responsive and motion evidence | [`overhaul-craft`](../../../agents/overhaul-craft.md) |
+| Other | Build tooling, CI, infrastructure, libraries, data/ML workloads, operations readiness, public API and CLI experience, documentation — explicit extra profiles, never forced into frontend/backend | [`overhaul-specialist`](../../../agents/overhaul-specialist.md) |
 
 Frontend and backend engineering are always different agent invocations with
 different active profiles, even in a same-language codebase. The boundary reviewer
@@ -277,10 +277,14 @@ correctness gate.
 ## Admission tool
 
 `devrites-engine overhaul admit receipt <run> <receipt.json> [--observed <paths.txt>]` checks one
-receipt against its dispatch packet: run, role, lane and snapshot match; timestamps
+receipt against its dispatch packet: the file is the attempt's own
+`<run>/receipts/<run_id>__<task_id>__<attempt_id>__<role>.json` (not a copy elsewhere
+or a symlink, and the attempt's recorded `receipt` when it has one); run, role, lane
+and snapshot match; timestamps
 and an allowed `outcome` are present; `no-findings` names inspected ranges; a writer's
 claimed paths stay inside its task contract and equal the observed paths.
 `devrites-engine overhaul admit anchor <tree> <proposals.json>` checks that every quoted location in
 `{"findings": [...]}` matches its file lines under the reviewed tree. It never edits
 canonical records; record its verdict in a staged generation. Exit codes: 0
-admissible or anchored, 1 reject, 2 usage or I/O error, 3 duplicate or late receipt.
+admissible or anchored, 1 reject, 2 usage or I/O error (including an extra or
+misspelled argument), 3 duplicate or late receipt.

package/pack/generated/pi/skills/overhaul/references/records.md

@@ -123,14 +123,19 @@ verifier attempt, repository-relative locations (external ones are labels, never
 host paths); `revisions.plan.file` equal to `revisions/plan-r<rev>.json`, required
 once approvals or writers exist; plan digest pins; known, acyclic dependencies;
 allowed paths that are exact files inside the repository (no `*` or `?`, no
-directories, no `.git`, no symlink or traversal escape); a separate verifier role;
+directories, no `.git` component or run-area path in any letter case or through a
+symlink, no symlink or traversal escape); a separate verifier role;
 approval and `accept-degradation` events with quote and trusted channel, approvals
 matching the plan digest, closure and current revision, none active after a later
 stop; a scorecard only with `revisions.rubric` and the same verdict as `run.json`;
+`READY_FOR_USER_REVIEW` only with a scorecard whose verdict is `MEETS_TARGETS`, and
+`COMPLETED_WITH_APPROVED_DEGRADATION` only with `MEETS_TARGETS_WITH_APPROVED_DEGRADATION`,
+each listing every audit gate (plus every repair gate outside assessment-only runs) as
+`PASS` or `NOT_APPLICABLE` (`G-CONCURRENCY` may be `WAIVED_OPERATIONAL` for the degraded outcome);
 no approval or writer in an assessment-only run; unchanged `run_id`, `repo_root`,
 `mode` and `assessment_only`; writers authorized for their task; one live writer
-per path (case-folded, symlink-resolved); no `dispatched`, `running` or `returned`
-attempt once the outcome leaves `RUNNING`; one outcome per approved task at the end;
+per path (case-folded, symlink-resolved); every attempt `admitted`, `rejected` or
+`cancelled` once the outcome leaves `RUNNING` (`timed-out` and `unknown` are not settled); one outcome per approved task at the end;
 a coverage denominator that never shrinks; append-only cycles, findings history and
 approval events; immutable revisions; view stamps; manifest integrity; stale stages
 and interrupted publishes. Across records: every finding's `domain` is a score key;

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

@@ -6,7 +6,7 @@ user-invocable: true
 disable-model-invocation: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md"],"triggers":{"intent":["devrites-lib/reference/intent-map.md"],"menu":["rite/reference/menu.md"],"dispatch":["devrites-lib/reference/parallel-dispatch.md"],"reply":["devrites-lib/reference/reply-contract.md"]}} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --skill rite` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # /rite: DevRites menu + router
 
@@ -74,9 +74,10 @@ What each verb does lives once, in the Menu below; this table is the invocation
 Both forms call the same skill. The menu supports discovery; `/rite-<verb>` is the direct form.
 
 `use <slug>` is handled **inline**. There is no `rite-use` skill. Confirm
-`.devrites/work/<slug>/` exists, then re-point `.devrites/ACTIVE` to `<slug>` and report
+`<slug>` is a safe slug and `.devrites/work/<slug>/state.md` is a contained regular file, then re-point `.devrites/ACTIVE` to `<slug>` and report
 the now-active feature. It is cheap context-switching only: no re-spec, no phase run. If
-the workspace is missing, list the slugs under `.devrites/work/` and stop.
+the workspace or its `state.md` is missing, list the slugs under `.devrites/work/` that have
+`state.md` and stop.
 
 `guide` is an inline walkthrough for the first feature. Agree on one **real, small**
 change, then run spec → clarify → temper → define → vet → build → prove → polish → review → seal →

package/pack/generated/pi/skills/rite/reference/menu.md

@@ -32,14 +32,15 @@ Phase-ordered `/rite` reference. Load only for command detail or phase connectio
   `/rite-define` (plan) → `/rite-vet` (engineering review; light or full) →
   `/rite-build` ×N (all slices) → `/rite-prove` (once all built) →
   `/rite-polish` (always: code + UI if UI) → `/rite-review` → `/rite-seal` → `/rite-ship`.
-- **Existing codebase**: `/rite-adopt` → `/rite-clarify` → `/rite-define` → `/rite-vet` → build.
+- **Existing codebase**: `/rite-adopt` → `/rite-spec` → `/rite-clarify` → `/rite-define` → `/rite-vet` → build.
 - **Drift mid-build**: classify → bounded recovery for objective defects, `/rite-plan`
   repair for a wrong durable plan, or one user decision for real product/risk drift.
 - **Older workspace cannot resume**: `/rite-upgrade` audits first → only proven gaps use
-  Clarify/Plan repair/Converge/Vet or Prove/Polish/Review/Seal → resume. It never
-  migrates cursor format or invents a prior pass.
-- **Resumed / adopted / stalled**: `/rite-converge` (assess live code vs intent → append the
-  remaining slices) → `/rite-vet` → `/rite-build` ×N → continue at `/rite-prove`.
+  Clarify/Plan repair/Converge/Vet or Prove/Polish/Review/Seal → resume. A cursor with
+  no `schema` row needs `devrites-engine migrate <slug>` first; upgrade never migrates
+  cursor format itself or invents a prior pass.
+- **Resumed / stalled, or adopted after Define** (has `plan.md` + `tasks.md`): `/rite-converge`
+  (assess live code vs intent → append the remaining slices) → `/rite-vet` → `/rite-build` ×N → continue at `/rite-prove`.
 
 ## Rules this menu obeys
 

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

@@ -5,7 +5,7 @@ argument-hint: "[path or area to adopt] [+ what you want to build next]"
 user-invocable: true
 ---
 <!-- loads: {"always":["rite-adopt/reference/adoption.md","rite-adopt/reference/anti-patterns.md","rite-polish/reference/ledger.md"],"triggers":{"security":["devrites-lib/reference/standards/security.md"]}} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-adopt` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --skill rite-adopt` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # /rite-adopt: onboard existing code
 
@@ -48,7 +48,8 @@ parallel convention system.
    resistance. Never create convention bands, scores, or a command cache.
 6. A genuine non-negotiable invariant may be proposed for
    `.devrites/principles.md`; the human must ratify it.
-7. Set the next step to `/rite-clarify` and stop. Do not plan or build.
+7. Set the next step to `/rite-spec <slug>` and stop; Spec extends this workspace and owns
+   `brief.md`, `checklists/`, and `spec_gate`. Do not plan or build.
 
 > Refuse the rationalizations in [`anti-patterns`](reference/anti-patterns.md).
 
@@ -59,5 +60,5 @@ Done: adopted <scope> into <slug>.
 Changed: <workspace artifacts>; project guidance <proposed | unchanged>
 Evidence: <source/CI paths inspected>
 Open: <questions | none>
-Next: /rite-clarify
+Next: /rite-spec <slug>
 ```

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/one-shot-actions.md","devrites-lib/reference/orchestration-profiles.md","devrites-lib/reference/standards/acceptance-preserving-reslice.md","rite-autocomplete/reference/decision-policy.md","rite-autocomplete/reference/loop.md","rite-autocomplete/reference/stop-conditions.md"],"triggers":{"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"]},"workspace":["state.md","spec.md","plan.md","tasks.md","questions.md","decisions.md","drift.md","evidence.md","test-plan.md"]} -->
-> Read-set manifest: `devrites-engine context <slug> --phase autocomplete` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase autocomplete` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-autocomplete: full lifecycle, unattended
@@ -49,14 +49,16 @@ executable controller/harness/bundle bytes or a missing writer, read
   likewise internal when current authority resolves it.
 - Always follow agent-owned backward edges through repair, affected Vet,
   correction, and proof. A nested `STOP`/`Next step` is not a user handoff.
-  Pause only for a shared human/safety/access/exhaustion condition.
+  Pause only for a shared human/safety/access condition.
 - **Do not confuse an action budget with recovery exhaustion.** Spent action
   authority blocks another real execution, not offline correction of retained
   Critical/Important evidence. Stop for fresh GO only after changed conditions
   and READY Vet.
-- Every exact causal fingerprint gets at most three no-progress corrections.
-  Closing one is progress; a distinct Critical/Important invariant has its own
-  budget. Lower severity cannot prolong recovery.
+- Every exact causal fingerprint gets three no-progress corrections per strategy.
+  A spent strategy escalates to a new correction class inline; after three
+  escalations it parks while independent work continues. Never ask permission to
+  retry. Closing one is progress; a distinct Critical/Important invariant has its
+  own budget. Lower severity cannot prolong recovery.
 - Do not stop on `--max-slices`, sentinel `max_slices`, `max_agents`,
   `max_minutes`, or `max_review_queue`. Count failed, malformed, and
   unavailable leaf calls.
@@ -79,7 +81,7 @@ executable controller/harness/bundle bytes or a missing writer, read
    Before honoring `blocked` with terminal `next_action`,
    reconcile retained consumptive evidence and fingerprint attempts from
    `drift.md`/`evidence.md`; a retained fingerprint below its cap resumes offline
-   recovery.
+   recovery, and this new invocation reopens each parked fingerprint.
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"lifecycle cursor encounters admitted set or resumable journal","action":"invoke classifier; execute returned route internally","return":"saved phase/action; zero intermediate reply"} -->
    Reconstruct a missing return cursor only from
    the current phase and exact approved action in `test-plan.md`/evidence, never
@@ -118,20 +120,21 @@ executable controller/harness/bundle bytes or a missing writer, read
    route agent-owned red results through bounded recovery.
    Red gates block forward advancement and enter caller-owned recovery. Stop on
    hard risk, escalating, irreversible-risk, access, blocking with no
-   recommended option, remaining NO-GO, or the exact fingerprint's proven
-   exhaustion. An open blocking question that already names a ranked recommended
+   recommended option, remaining NO-GO, or parked fingerprints with no
+   independent work left. An open blocking question that already names a ranked recommended
    option (`proposed` or option 1 labelled Recommended) auto-resolves through
    `devrites-engine state resolve` and continues (a missing or failing resolver is
    the bounded resolver-failure stop); do not emit `/rite-resolve` as
    a user handoff. Exception: a question whose answer would add acceptance or
    product scope is never auto-resolved by a recommended option; it stops for a human.
-   Technical exhaustion records terminal
-   `Next step: none`, never a routine phase command. **Completion:** no stop is active, or its cursor and reason are durable.
-6. **Seal boundary.** Without a ship flag, stop at Seal GO with `/rite-ship` —
-   unless `continue_sequence: false` or sequence budget is spent; otherwise
-   leave the sealed workspace unshipped and open the next recorded continuation
-   ([loop.md § Sequence continuation](reference/loop.md#sequence-continuation));
-   report the sequence position on every stop.
+   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
+   ([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.
 

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

@@ -53,7 +53,8 @@ and parallel AFK headroom as stop conditions. Pass this invocation's
 that already name a ranked recommended option (recommended pick via
 `devrites-engine state resolve`) instead of queuing them or handing
 `/rite-resolve` to the user. Escalating, irreversible-risk, access, and
-blocking with no recommended option still pause.
+blocking with no recommended option still pause, as does Seal's judgment-only
+validating question (`slice: seal`).
 
 ## Phase arc
 
@@ -107,7 +108,7 @@ 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 exhaustion condition fires; or Seal returns
+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
 `/rite-ship` for the current sealed workspace when the sequence is complete).
@@ -139,14 +140,16 @@ agent-owned earlier-phase gap:
 Ask only for a human-owned decision or mandatory safety/access action. An open
 blocking question with `proposed` or option 1 labelled Recommended is not that
 decision: resolve it and continue. Three no-progress corrections of one exact
-fingerprint exhaust; preserve its reproduction and dead ends without another
-Plan/Vet command.
+fingerprint spend only its strategy: escalate inline per the
+[retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve),
+and park it after three escalations while independent work continues.
 
 ## Continuous caller obligation
 
 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 an open blocking question that
+Critical/Important fingerprint below its cap or with an escalation left, runnable
+work independent of a parked fingerprint, or an open blocking question that
 already names a ranked recommended option. Invoke the next internal repair or
 `devrites-engine state resolve` immediately, unless that writer already hit the
 [resolver-failure stop](stop-conditions.md#other-stop-classes). **Failing case:**
@@ -156,4 +159,4 @@ 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/exhaustion condition.
+rest point or a shared human/safety/access/parked-recovery condition.

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

@@ -1,10 +1,10 @@
 # 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 only when an actual human/safety/access
-action can change it. Exhausted agent-owned recovery records terminal
-`Next step: none` and no runnable recovery command. `--ship` never bypasses a
-stop.
+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)).
+`--ship` never bypasses a stop.
 
 Authority: `.pi/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
@@ -24,8 +24,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; stop after proven
-exhaustion unless the remaining owner is human.
+Red proof cannot advance. Run bounded Debug Recovery and escalate spent
+strategies; a fully escalated fingerprint parks unless the remaining owner is human.
 
 ## Not stops: internal technical routing
 
@@ -36,13 +36,16 @@ 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. Stop only after three no-progress corrections of
-that exact fingerprint or a real human/safety/access gate. Preserve reproduction,
-attempts, and dead ends; never offer `/rite-plan unblock` or another routine
-phase command. Reinvocation with unchanged evidence does not reset the cap.
-`unchanged` means the same fingerprint already has three recorded no-progress
-corrections. Closure is progress; a separately evidenced Critical/Important
-invariant starts its own cap and cannot extend the closed one.
+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, boundary redesign, diagnostic amplification)
+with a fresh budget, never asking permission. After three escalations in this
+activation the fingerprint parks; finish all 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.
+Closure is progress; a separately evidenced Critical/Important invariant starts
+its own cap and cannot extend the closed one.
 
 Spent consumptive-action authorization is not technical-recovery exhaustion.
 It blocks another execution; retained new Critical/Important evidence still
@@ -52,9 +55,8 @@ 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. Use terminal none only when no safe in-scope
-seam exists, a real human/risk/scope gate owns it, or bounded recovery is
-exhausted.
+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.
 
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"classifier returns owner-busy, exhausted, or existing hard gate","action":"stop on exact WAIT_ACTIVE_OWNER, BLOCKED_EXHAUSTED, or BLOCKED_GATE result","return":"unchanged cursor plus fixed route-owned output"} -->
 ## Other stop classes
@@ -66,7 +68,8 @@ exhausted.
   would add acceptance or product scope is never auto-picked, even with a
   recommended option; it stops for a human. Blocking with no
   recommended option still stops. Validating: auto-pick the recommended option,
-  close the question, continue.
+  close the question, continue — except Seal's judgment-only acceptance question
+  (`slice: seal`), which only a human answers; it stops.
 - **Temper:** `expand` and extra acceptance stop: ask through `AskUserQuestion`, hold the
   fold, and continue only after a human resolves the qid (an ADR is not that answer).
   Irreversible-risk still pauses. `hold-rigor`, `reduce-to-MVP`, and a skip do not pause.
@@ -85,7 +88,8 @@ exhausted.
 - **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:** the exact fingerprint's bounded recovery is exhausted.
+- **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 +
@@ -100,7 +104,7 @@ 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.
 
-A cold-resumable stop records `state.md` status, exact reason, and either one
-human-owned resume action or `none — technical recovery exhausted`; the owning
-question/drift/seal entry explains it. The user-facing line says what stopped
+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.

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/code-navigation.md","devrites-lib/reference/standards/agents.md","rite-build/reference/phase-contract.md","rite-build/reference/one-slice-cycle.md","rite-build/reference/wright-dispatch.md","rite-build/reference/checkpoint.md","rite-build/reference/spec-drift-guard.md","rite-build/reference/output.md","rite-build/reference/anti-patterns.md"],"rootOnly":["rite-build/reference/phase-contract.md","rite-build/reference/wright-dispatch.md","rite-build/reference/checkpoint.md","rite-build/reference/output.md","rite-build/reference/afk-discipline.md","rite-build/reference/checkpoint-protocol.md","rite-build/reference/parallel-batch.md","devrites-lib/reference/standards/afk-hitl.md","devrites-lib/reference/standards/workflow-artifacts.md"],"triggers":{"afk":["rite-build/reference/afk-discipline.md","devrites-lib/reference/standards/afk-hitl.md","rite-build/reference/checkpoint-protocol.md"],"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"coding":["devrites-lib/reference/standards/coding-style.md"],"debug-recovery":["devrites-lib/reference/standards/debug-recovery.md"],"dod":["devrites-lib/reference/standards/definition-of-done.md"],"errors":["devrites-lib/reference/standards/error-handling.md"],"frontend":["rite-build/reference/frontend-trigger.md"],"parallel":["rite-build/reference/parallel-batch.md"],"patterns":["devrites-lib/reference/standards/patterns.md"],"principles":["devrites-lib/reference/standards/principles.md"],"security":["devrites-lib/reference/standards/security.md"],"tdd":["rite-build/reference/tdd.md","devrites-lib/reference/standards/testing.md"],"workflow-artifacts":["devrites-lib/reference/standards/workflow-artifacts.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md","strategy.md"],"workspaceByRole":{"code-reviewer":["spec.md","plan.md","tasks.md","test-plan.md","architecture.md","decisions.md","state.md"],"doubt-reviewer":["spec.md","plan.md","tasks.md","state.md","decisions.md"],"slice-wright":["brief.md","spec.md","architecture.md","plan.md","tasks.md","test-plan.md","state.md","decisions.md","assumptions.md","questions.md"],"test-analyst":["spec.md","tasks.md","test-plan.md","state.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase build` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase build` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-build: one verified slice
@@ -19,7 +19,7 @@ caps and pause rules. Every wright returns after one slice.
 ([`one-slice-cycle.md`](reference/one-slice-cycle.md)).
 
 Root owns gates/bookkeeping; fresh
-[`devrites-slice-wright`](.pi/agents/devrites-slice-wright.md) writes source/tests.
+[`devrites-slice-wright`](../../agents/devrites-slice-wright.md) writes source/tests.
 Workflow Artifacts use
 [`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
 (trigger `workflow-artifacts` — only when the plan declares them).

package/pack/generated/pi/skills/rite-build/reference/afk-discipline.md

@@ -69,13 +69,16 @@ wrong contract or proof path — agent-owned recovery; never advance on broken s
 The fail-on-red path:
 
 1. Continue the same wright under `devrites-debug-recovery`, carrying exact output and dead
-   ends; cap writer + recovery at three no-progress attempts per exact causal fingerprint.
+   ends; cap writer + recovery at three no-progress attempts per exact causal fingerprint
+   and strategy.
    A correction that closes the reproduction is progress; a different evidenced
    Critical/Important invariant starts a separate fingerprint.
 2. Green → record the slice. Product-contract/irreversible ambiguity → write the genuine
    human gate. Missing human-only credential/permission → write a human-intervention gate.
-3. Any other exhausted objective failure → set `Status: blocked`, preserve the reproduction,
-   set `Next step: none — technical recovery exhausted for <causal fingerprint>; requires new evidence or changed failure conditions`, and STOP without a qid or runnable phase command. Reinvocation with the unchanged fingerprint remains blocked and does not reset the cap.
+3. Any other spent strategy → escalate inline to the next correction class; after three
+   escalations park the fingerprint and build every slice that does not depend on it,
+   per the [retry contract](../../devrites-lib/reference/standards/afk-hitl.md#retry-cap-no-progress-loops-and-self-resolve).
+   Never ask a qid or permission to retry; never hand back a routine phase command.
 4. Fire `notify:` only for an actual `awaiting_human` transition.
 
 AFK never starts the next slice while checks are red and never asks the human to approve

package/pack/generated/pi/skills/rite-build/reference/parallel-batch.md

@@ -182,11 +182,11 @@ Repair rejected work in place; never discard/rebuild while budget remains.
   exhaustion. Use plan path only if inventory proves the approach unsound.
 - Stop under the canonical retry/authority/resource conditions, or when evidence
   proves the approach unsound and no in-scope corrected decomposition exists.
-- Exhaustion is not abort: record one technical blocker (`Status: blocked`;
-  `Next step: none — technical recovery exhausted; requires new evidence or changed failure conditions`), preserve
-  lease/worktrees/branches, STOP — same fingerprint stays blocked on
-  reinvoke; new evidence resumes repair in place. Human-owned decisions use
-  the drift-guard question and wait.
+- A spent strategy is not abort: escalate per the canonical retry contract,
+  preserving lease/worktrees/branches; a fully escalated fingerprint parks and
+  the batch keeps its independent members. Repair resumes in place on
+  escalation or reinvocation. Human-owned decisions use the drift-guard
+  question and wait.
 
 ## Engine verbs
 
@@ -229,6 +229,6 @@ isolation cannot be established.
 
 ## Host
 
-pi: N concurrent `subagent` wrights (`acceptEdits`, cwd=worktree). Codex: require
+pi: N concurrent `subagent` wrights (cwd=worktree). Codex: require
 host-explicit concurrent worktree writers + native reconcile; else force serial.
 Never two writers in one worktree; never root-emulated concurrency.

package/pack/generated/pi/skills/rite-build/reference/wright-dispatch.md

@@ -11,6 +11,15 @@ Claude grants only the exact wright `acceptEdits`; Codex uses its workspace root
 the exact `:workspace` wright, and read-only specialists. Never bypass/substitute
 the wright or recreate an engine bridge.
 
+## Standalone correction
+
+`/rite-quick`, `/rite-dogfood`, and `/rite-pr-feedback` fixes have no `tasks.md`
+slice, so skip Prepare's `check slice`, `context --slice`, and the build `dispatch`
+wave. Give the wright an inline contract: goal, acceptance check, exact
+project-relative paths, and proof command. With an active workspace, `claim add`
+those paths first. On return, compare its file list and `git diff --name-only`
+with the paths; reject any extra path.
+
 ## Isolated writer-worktree pilot
 
 Use native isolation only when the current host exposes an explicit named-writer
@@ -55,7 +64,7 @@ worktrees stay forbidden.
 2. Include goal, verbatim acceptance, exclusions, context,
    `test-plan.md` proof commands, applicable standards, and the exact
    `WIP(<slug>):` subject (no slice id). Build the wright's read-set with
-   `devrites-engine context <slug> --phase build --role slice-wright --slice <SLICE-ID> --trigger <set>`
+   `devrites-engine context --skills-root .pi/skills <slug> --phase build --role slice-wright --slice <SLICE-ID> --trigger <set>`
    and hand it the bundle path (over-budget artifacts arrive as anchor indexes;
    read owning sections live). Evaluate each trigger condition and pass those
    that fire (TDD slice → `tdd`, AFK run → `afk`, UI work → `frontend`, …).
@@ -64,6 +73,8 @@ worktrees stay forbidden.
    topology/data/integration standard, include only the feature-specific owner/invariant,
    failure or partial-state case, recovery rule, and required proof from the vetted plan.
    Do not paste the whole standard or silently omit an applicable risk.
+   Quote every active `decisions.md` carry-forward constraint whose `Files:`
+   overlap the task paths (or that names no files).
    A new path requires a new bounded contract; the wright cannot widen the task.
 3. Record `git diff --name-only` before dispatch so unrelated work remains
    distinguishable. For an isolated pilot, also record committed base SHA and exact
@@ -141,3 +152,11 @@ TTL is crash recovery, not normal cleanup.
    escalation without the checked-assumption list (verified|falsified) is
    malformed; root sweeps the unchecked remainder per
    [`spec-drift-guard.md`](spec-drift-guard.md) before repair.
+6. **Learning edge.** A correction accepted with a confirmed cause (a review,
+   gate, or proof rejection plus its fix) becomes a carry-forward constraint so
+   later slices start where this one ended: append one line under
+   `decisions.md` `## Carry-forward constraints` —
+   `- <rule> — from <SLICE-ID> (<evidence ref>); Files: <paths>`. Record the
+   derived rule, not the output, at the scope its evidence supports: "this
+   button is blue" never becomes "buttons are blue". Never edit `tasks.md` mid-build (it is a
+   readiness input). **Failing case:** slice 3 repeats a defect slice 2 fixed.

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/afk-hitl.md","rite-clarify/reference/decision-coverage.md","rite-clarify/reference/anti-patterns.md"],"triggers":{"agents":["devrites-lib/reference/standards/agents.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md"],"workspaceByRole":{"evidence-scout":["brief.md","spec.md","state.md","questions.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase clarify` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase clarify` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-clarify: resolve product decisions

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

@@ -6,7 +6,7 @@ user-invocable: true
 ---
 
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/spec-grammar.md","devrites-lib/reference/standards/agents.md","devrites-lib/reference/standards/tooling.md","devrites-lib/reference/standards/testing.md","rite-converge/reference/convergence-assessment.md","rite-converge/reference/anti-patterns.md","rite-build/reference/spec-drift-guard.md"],"triggers":{"applicability":["devrites-lib/reference/standards/repository-topology.md","devrites-lib/reference/standards/data-integrity.md","devrites-lib/reference/standards/integration-reliability.md"],"principles":["devrites-lib/reference/standards/principles.md"],"workflow-artifacts":["devrites-lib/reference/workspace-artifact-schema.md"]},"workspace":["brief.md","spec.md","state.md","decisions.md","assumptions.md","questions.md","decision-coverage.md","architecture.md","plan.md","tasks.md","traceability.md","eng-review.md","test-plan.md","gates.md","evidence.md"],"workspaceByRole":{"evidence-scout":["spec.md","plan.md","tasks.md","state.md","evidence.md"]}} -->
-> Read-set manifest: `devrites-engine context <slug> --phase converge` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --phase converge` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 
 # /rite-converge: compare live code with intent
@@ -101,9 +101,10 @@ Pull on demand:
    Produces. A principle violated in the current code is its own top-severity gap.
    Dispatch up to three independent inventory partitions to `devrites-evidence-scout` on the
    same live-code snapshot — build each scout's read-set once with
-   `devrites-engine context <slug> --phase converge --role evidence-scout` and hand it the
-   bundle path; run the wave through
-   `devrites-engine dispatch <slug> open|start|seal|return` (per
+   `devrites-engine context --skills-root .pi/skills <slug> --phase converge --role evidence-scout --out
+   ctx/converge-evidence-scout.p<n>.bundle.md` and hand it the bundle path; run the wave
+   through `devrites-engine dispatch <slug> open|start|seal|return` with one lane label
+   per partition (`--role evidence-scout.p1 --role evidence-scout.p2 ...`, per
    [`parallel-dispatch.md`](../devrites-lib/reference/parallel-dispatch.md)), which
    auto-records dispatch/return metrics. Await their
    dossiers, then reconcile the cited facts in the root

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

@@ -6,7 +6,7 @@ user-invocable: true
 disable-model-invocation: true
 ---
 <!-- loads: {"always":["devrites-lib/reference/standards/core.md"],"triggers":{"security":["devrites-lib/reference/standards/security.md"]},"workspace":[]} -->
-> Read-set manifest: `devrites-engine context [slug] --skill rite-customize` bundles every file named below into one deduplicated read.
+> Read-set manifest: `devrites-engine context --skills-root .pi/skills <slug> --skill rite-customize` (no workspace: `--out <path>`) bundles every file named below into one deduplicated read.
 
 # /rite-customize: native project customization