devrites 5.10.0 → 5.10.2

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

@@ -64,7 +64,9 @@ filled, and recomputes after every completed round (serial slice or parallel
 integrate) until no pending slice remains
 ([`parallel-batch.md` § Dynamic selection](reference/parallel-batch.md#dynamic-selection-and-re-batching)).
 Unattended runs (`/rite-autocomplete`, `.devrites/AFK` `max_parallel`) repeat batches
-inside the same run; HITL stops after each batch. Non-integer/`N≤0`/`N>10` hard refuse.
+inside the same run; HITL stops after each batch. This invocation's `--parallel N`
+is the cap: leftover sentinel `max_parallel` is not consulted. Autocomplete with
+that flag also writes or replaces only `max_parallel: N`. Non-integer/`N≤0`/`N>10` hard refuse.
 All-green (independent review + proof) then integrate as one local `WIP(<slug>):`
 commit per sibling onto the current control branch (never pushed). Do not
 integrate a sibling because the wright returned. A red/gap sibling gets a bounded repair

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

@@ -16,9 +16,10 @@ control; irreversible work (destructive/auth/public API) always pauses.
 The controlling root owns the cap:
 
 1. **Before every dispatch**, re-read `.devrites/AFK`, `state.md`, and the
-   selected slice. When `--parallel N` or sentinel `max_parallel` is greater than
-   1, recompute `N_eff` via `parallel select` before the next dispatch — a prior
-   one-slice round does not keep the run serial. A configured `max_slices` and any existing
+   selected slice. This invocation's `--parallel N` is the cap when present;
+   leftover sentinel `max_parallel` is not consulted in that case. When that
+   flag or sentinel `max_parallel` is greater than 1, recompute `N_eff` via
+   `parallel select` before the next dispatch — a prior one-slice round does not keep the run serial. A configured `max_slices` and any existing
    `afk_slices_remaining` value, including its released bullet form, must each
    be a decimal nonnegative integer. A missing
    `state.md` or malformed configured value fails closed; an omitted cap is the

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

@@ -9,6 +9,7 @@ Opt-in only. Default `/rite-build` stays [`one-slice-cycle.md`](one-slice-cycle.
 | omitted / `--parallel 1` | Serial one-slice |
 | `--parallel N` (**2≤N≤10**) | N is a **cap**, not a quota: run the largest eligible set ≤ N |
 | non-integer / `N≤0` / `N>10` | Hard refuse (no silent clamp) |
+| Autocomplete `--parallel N` | N is the cap for this run; leftover sentinel `max_parallel` is ignored, then `/rite-autocomplete` writes or replaces only `max_parallel: N` |
 | Autocomplete, no flag | Same path, cap from sentinel `max_parallel` else 10; serial only when ineligible |
 
 AFK caps `N`. Charge green siblings once after integrate; abort /
@@ -21,7 +22,8 @@ Size each batch by what is runnable **now**, never by the requested number:
 
 ```text
 N_eff = min(
-  cap                  -- --parallel N | sentinel max_parallel | 10 (autocomplete default)
+  cap                  -- this invocation's --parallel N (wins over leftover sentinel max_parallel)
+                       | else sentinel max_parallel | else 10 (autocomplete default)
   eligible set         -- dependency-satisfied pending slices, pairwise path-disjoint
   AFK headroom         -- remaining max_slices, max_agents, max_minutes, review queue
   host capacity        -- concurrent worktree writers + the runtime isolation table

package/pack/.claude/skills/rite-define/reference/gates.md

@@ -127,6 +127,11 @@ list.
 `escalating` is never in `allow_gates`: specialist routing is not something AFK can
 shortcut.
 
+`/rite-autocomplete` does not add `blocking` to `allow_gates`. It auto-resolves
+open blocking questions that already name a recommended option via
+`devrites-engine state resolve`, then continues. That is an orchestrator
+exception, not an AFK ceiling change.
+
 ## Anti-patterns
 
 - **One gate for everything.** This puts all work behind one reviewer. Pick gates per slice.

package/pack/.claude/skills/rite-define/reference/plan-template.md

@@ -14,7 +14,7 @@ Spec: ./spec.md   Decision coverage: ./decision-coverage.md   Date: <date>
 - Language/runtime/version: <...>
 - Frameworks/libraries: <...>
 - Storage/data: <...>
-- Test commands: <discovered runner commands; discovery contract: rite-prove/reference/test-command-discovery.md>
+- Test commands: <discovered runner commands; discovery contract: .claude/skills/rite-prove/reference/test-command-discovery.md>
 - Target/platform/constraints: <...>
 - Approach-affecting product/constraint unknowns route to `/rite-clarify`;
   `[NEEDS CLARIFICATION]` blocks approval.

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

@@ -86,8 +86,11 @@ Pull these via `Read` when shaping the resolve:
    recommend `/rite-plan repair`. Otherwise → recommend the slice's natural next action
    (typically `/rite-build` for the slice that was awaiting).
    **Completion:** the resolved state contains exactly one next command.
-6. **STOP.** This skill does not run `/rite-build` itself: the user re-enters the
-   workflow explicitly.
+6. **STOP.** User-invoked `/rite-resolve` does not run `/rite-build` itself: the
+   user re-enters the workflow explicitly. A controlling `/rite-autocomplete`
+   caller invokes the same `devrites-engine state resolve` writer internally and
+   continues; it must not emit this skill as a user handoff for a question that
+   already names a ranked recommended option.
 
 > **Mid-flight discipline.** Don't edit `spec.md` / `plan.md` to "incorporate" the
 > answer. That's `/rite-plan repair`. Don't silently retry a build after the answer

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

@@ -56,14 +56,14 @@ max_minutes: 120                     # wall-clock minutes in one host activation
 max_review_queue: 8                  # unresolved review/gate items admitted before fan-out stops
 # max_tokens: 200000                 # optional stricter host-observed token cap
 # max_cost_usd: 10                   # optional stricter host-observed cost cap
-notify: "ntfy.sh/my-topic"           # shell command; examples: rite-build/reference/afk-discipline.md
+notify: "ntfy.sh/my-topic"           # shell command; examples: .claude/skills/rite-build/reference/afk-discipline.md
 allow_gates: [advisory, validating]  # gate severities AFK auto-handles (auto-picks the recommended option)
 continue_sequence: true              # after Seal GO, open the next recorded continuation
 max_workspaces: 5                    # workspaces one armed sequence may open
-max_parallel: 10                     # cap on eligible path-disjoint Build batches (1 = serial)
+max_parallel: 10                     # unattended default cap; `--parallel N` on this invocation wins and may rewrite only this field
 ```
 
-The file is **read-only config**: never rewritten in place. `max_slices` is the initial
+The file is **read-only config**: never rewritten in place, except `/rite-autocomplete --parallel N` writes or replaces only `max_parallel: N`. `max_slices` is the initial
 budget; the mutable remaining count is the `state.md` cursor
 `afk_slices_remaining` (`AFK slices remaining: <n>` in the released bullet
 form), owned by the controlling root. Recognize either spelling and preserve
@@ -119,11 +119,18 @@ candidate manifest to cover the whole recorded chain — run
 - Every human-owned, safety, access, exhaustion, and `NO-GO` condition still stops the
   run exactly as without this field.
 
-`max_parallel` caps a Build batch for unattended runs; `1` forces the serial cycle.
-Unattended runs take the largest eligible set ≤ cap and recompute after every completed
-round (serial slice or parallel integrate)
-([parallel-batch.md § Dynamic selection and re-batching](../../../rite-build/reference/parallel-batch.md#dynamic-selection-and-re-batching));
-an explicit `/rite-build --parallel N` cap wins for that invocation.
+`max_parallel` is the unattended default batch cap only when this invocation does
+not contain `--parallel N`; `1` forces the serial cycle only in that default
+case. An exact `--parallel N` on `/rite-autocomplete` or `/rite-build` is the
+batch cap for this run: do not consult leftover sentinel `max_parallel`, and do
+not treat `max_parallel: 1` as serial. `/rite-autocomplete --parallel N` writes
+or replaces only that field so later ticks keep the cap; `/rite-build --parallel N`
+wins for that invocation without rewriting the sentinel. Never write `max_slices`
+from `--max-slices`. **Failing case:** `/rite-autocomplete --parallel 5` honors a
+leftover `max_parallel: 1` and stays serial.
+Unattended runs take the largest eligible set ≤ that cap and recompute after
+every completed round (serial slice or parallel integrate)
+([parallel-batch.md § Dynamic selection and re-batching](../../../rite-build/reference/parallel-batch.md#dynamic-selection-and-re-batching)).
 
 ## Unattended resource envelope
 
@@ -166,7 +173,18 @@ for the full taxonomy. Summary:
 | blocking | high | sync | 15m | **no** (always pauses) |
 | escalating | novel pattern | sync to specialist | 24h | **no** (always pauses) |
 
-`blocking` and `escalating` always pause regardless of `allow_gates`.
+`blocking` and `escalating` always pause for HITL and for AFK `/rite-build`,
+regardless of `allow_gates`.
+
+**Autocomplete exception.** While `/rite-autocomplete` is the controlling
+caller, an open `gate: blocking` question that already carries a ranked
+recommended option (`proposed:` or option 1 labelled `(Recommended)`) is not a
+user handoff: the orchestrator auto-picks that option through
+`devrites-engine state resolve` and continues, including internal Spec Drift
+Guard when the answer changes ownership or acceptance. Escalating,
+irreversible-risk, access, and blocking questions with no recommended option
+still pause. Putting `blocking` in `allow_gates` does not replace this resolve
+step: an unanswered blocking question still fails Seal.
 
 An open `gate: validating` entry is **merge-blocking by definition**: at `/rite-seal` any
 `questions.md` entry with `gate: validating` and `status: open` is a NO-GO, regardless of

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

@@ -8,8 +8,10 @@ user-invocable: true
 # /rite-autocomplete: full lifecycle, unattended
 
 Run every phase after one clarification window. Irreversible-risk,
-blocking/escalating,<!-- pack-scan-ignore: negated statement: gates are NOT disabled -->
-and NO-GO still pause. Use the Standard native
+escalating,<!-- pack-scan-ignore: negated statement: gates are NOT disabled -->
+access, unanswered blocking with no recommended option, and remaining NO-GO
+still pause. Open blocking questions that already name a ranked recommended
+option auto-resolve; they are not a user handoff. Use the Standard native
 profile by default and Full for high-risk scope or explicit `--full`; see
 [`orchestration-profiles.md`](../devrites-lib/reference/orchestration-profiles.md).
 
@@ -85,25 +87,34 @@ executable controller/harness/bundle bytes or a missing writer, read
 3. **Arm AFK once.** Apply the loop's
    [one-write AFK contract](reference/loop.md#arm-afk-once): preserve valid
    existing bytes or create the sentinel once (`allow_gates: [advisory, validating]`); never
-   rewrite it after Vet. Preserve an existing sentinel byte-for-byte.
+   rewrite it after Vet except to write or replace only `max_parallel: N` when
+   this invocation contains `--parallel N`. Preserve an existing sentinel
+   byte-for-byte otherwise. **Failing case:** leftover `max_parallel: 1` keeps
+   the run serial after `--parallel 5`.
    **Completion:** a valid read-only AFK sentinel exists.
 4. **Drive phases.** Follow [the loop](reference/loop.md): `/rite-spec` →
    `/rite-clarify` → `/rite-temper` → `/rite-define` → `/rite-vet` →
    `/rite-build` batch loop → `/rite-prove` → `/rite-polish` →
    `/rite-review` → `/rite-seal`. Read and execute each skill; durable files, not
    chat, carry state. Apply the mutable post-vet budget before first Build.
-   Build runs the largest eligible path-disjoint batch (cap: `--parallel N`, else
-   sentinel `max_parallel`, else 10) and recomputes after every completed round until no
-   pending slice remains; a one-slice round is serial for that round only, then
+   Build runs the largest eligible path-disjoint batch (cap: this invocation's
+   `--parallel N`, else sentinel `max_parallel`, else 10) and recomputes after
+   every completed round until no pending slice remains; a one-slice round is serial for that round only, then
    selection runs again (host isolation still forces serial when concurrent writers
-   cannot be separated).
+   cannot be separated). When `--parallel N`
+   is present, pass it into `/rite-build` and do not consult leftover sentinel
+   `max_parallel`.
    **Completion:** loop reaches Seal GO or persists a valid stop before any later phase.
 5. **Apply stops.** At every gate use
    [stop-conditions.md](reference/stop-conditions.md). A `blocked` label alone is not a stop condition:
    route agent-owned red results through bounded recovery.
    Red gates block forward advancement and enter caller-owned recovery. Stop on
-   hard risk, human-owned blocking/escalating/NO-GO, or the
-   exact fingerprint's proven exhaustion. Technical exhaustion records terminal
+   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
+   option (`proposed` or option 1 labelled Recommended) auto-resolves through
+   `devrites-engine state resolve` and continues; do not emit `/rite-resolve` as
+   a user handoff. 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` is armed and sequence budget remains, in which case

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

@@ -36,5 +36,8 @@ not pick the option that's merely easiest to implement.
 
 ## When a choice is NOT autocomplete's to make
 
-Human-owned blocking/escalating, irreversible-risk, and access stay human.
-Recommended temper `expand` auto-applies; do not invent product intent.
+Irreversible-risk, escalating, access, and blocking questions with no ranked
+recommended option stay human. A blocking question that already names option 1
+`(Recommended)` or `proposed:` is autocomplete's to resolve: pick that option
+via `devrites-engine state resolve` and continue. Recommended temper `expand`
+auto-applies; do not invent product intent.

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

@@ -17,18 +17,21 @@ allow_gates: [advisory, validating]
 # max_slices / max_agents / max_minutes / max_review_queue omitted: unlimited
 # continue_sequence: true          # opt-in: chain recorded continuations after Seal GO
 # max_workspaces: 5                # sequence budget when chaining
-# max_parallel: 10                 # Build batch cap; 1 = serial (default: eligible, cap 10)
+# max_parallel: 10                 # default cap when this invocation omits `--parallel N`; `--parallel N` wins and rewrites only this field
 # max_tokens: <N>
 # max_cost_usd: <amount>
 # notify: "<cmd>"
 ```
 
-Read an existing sentinel first. Preserve it byte-for-byte when valid; stop if
+Read an existing sentinel first. Preserve it byte-for-byte when valid, 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` /
 `max_minutes` / `max_review_queue` or only `[advisory]`. If absent, write it
-once after clarity. Never write `max_slices` from `--max-slices`.
-It is read-only: never rewrite it after Vet or reset it on resume. Leftover
-`expires_at` is ignored and never rewritten.
+once after clarity, and include `max_parallel: N` when that flag is present.
+Never write `max_slices` from `--max-slices`. It is otherwise read-only: never rewrite it after Vet or reset it on resume. Leftover `expires_at` is ignored
+and never rewritten. **Failing case:** leftover `max_parallel: 1` keeps the run
+serial after `--parallel 5`.
 
 ### Derive the mutable post-vet budget
 
@@ -44,8 +47,13 @@ readiness check first; reject overlap. Do not stop on `max_agents`,
 gets fresh activation-local counters but retains durable slice/recovery state.
 
 When driving `/rite-build`, ignore afk-discipline remaining-0, `--max-slices`,
-and parallel AFK headroom. Close validating questions
-(recommended pick) instead of queuing them.
+and parallel AFK headroom as stop conditions. Pass this invocation's
+`--parallel N` into `/rite-build` when present; leftover sentinel
+`max_parallel` is then not the cap. Close validating questions and blocking questions
+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.
 
 ## Phase arc
 
@@ -58,7 +66,7 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 | 3 | `/rite-temper` | harden, reduce, or expand; irreversible risk still pauses |
 | 4 | `/rite-define` | approved plan/tasks/traceability |
 | 5 | `/rite-vet` | every plan; derive mutable budget after READY |
-| 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap 10; one-slice round when <2 eligible); recompute after each round; charge once per green built slice |
+| 6 | `/rite-build` batch loop | largest eligible path-disjoint set (cap: this invocation's `--parallel N`, else sentinel `max_parallel`, else 10; one-slice round when <2 eligible); recompute after each round; charge once per green built slice |
 | 7 | `/rite-prove` | all slices built; approved proof; recovery on red |
 | 8 | `/rite-polish` | re-prove after code edits |
 | 9 | `/rite-review` | in-scope correction then fresh proof |
@@ -122,16 +130,19 @@ agent-owned earlier-phase gap:
 6. Restore and consume the original cursor when prerequisites are green.
 
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"loop tick sees Workflow Artifact trigger/state","action":"invoke classifier once under owner lock; no actor-history migration","return":"same loop cursor; no budget charge for verify/rerun"} -->
-Ask only for a human-owned decision or mandatory safety/access action. Three
-no-progress corrections of one exact fingerprint exhaust; preserve its
-reproduction and dead ends without another Plan/Vet command.
+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.
 
 ## Continuous caller obligation
 
 No user-facing reply is permitted while durable state contains agent-owned
-`NEEDS_REPLAN`, an intermediate Plan/Vet action, or a distinct retained
-Critical/Important fingerprint below its cap. Invoke the next internal repair
-immediately. A narrow reviewer closing one finding and exposing another
+`NEEDS_REPLAN`, an intermediate Plan/Vet action, a distinct retained
+Critical/Important fingerprint below its cap, or an open blocking question that
+already names a ranked recommended option. Invoke the next internal repair or
+`devrites-engine state resolve` immediately. 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

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

@@ -59,14 +59,21 @@ exhausted.
 <!-- 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
 
-- **Gate severity:** blocking or escalating gate. Validating: auto-pick the
-  recommended option, close the question, continue.
+- **Gate severity:** escalating always stops. Blocking with a ranked recommended
+  option (`proposed` or option 1 labelled Recommended): auto-pick via
+  `devrites-engine state resolve`, then continue internally (including Spec Drift
+  Guard when the answer changes ownership or acceptance). Blocking with no
+  recommended option still stops. Validating: auto-pick the recommended option,
+  close the question, continue.
 - **Temper:** `expand` and extra acceptance auto-apply (record + Drift Guard).
   Irreversible-risk still pauses. `hold-rigor`, `reduce-to-MVP`, and a skip do not pause.
 - **Clarify:** material Partial/Missing/unowned decision coverage or a
   low-confidence high-consequence assumption. Continue the initial interview;
   never arm AFK early.
-- **Seal:** NO-GO, with every blocker and fix direction. Never round up to GO.
+- **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.
 - **Reslice:** execute its marked action before deciding continue/stop.
 - **Slice budget:** do not stop on `--max-slices`. Leftover
   pre-existing remaining value, explicit flag, sentinel cap, or post-vet pending count

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

@@ -64,7 +64,9 @@ filled, and recomputes after every completed round (serial slice or parallel
 integrate) until no pending slice remains
 ([`parallel-batch.md` § Dynamic selection](reference/parallel-batch.md#dynamic-selection-and-re-batching)).
 Unattended runs (`/rite-autocomplete`, `.devrites/AFK` `max_parallel`) repeat batches
-inside the same run; HITL stops after each batch. Non-integer/`N≤0`/`N>10` hard refuse.
+inside the same run; HITL stops after each batch. This invocation's `--parallel N`
+is the cap: leftover sentinel `max_parallel` is not consulted. Autocomplete with
+that flag also writes or replaces only `max_parallel: N`. Non-integer/`N≤0`/`N>10` hard refuse.
 All-green (independent review + proof) then integrate as one local `WIP(<slug>):`
 commit per sibling onto the current control branch (never pushed). Do not
 integrate a sibling because the wright returned. A red/gap sibling gets a bounded repair

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

@@ -16,9 +16,10 @@ control; irreversible work (destructive/auth/public API) always pauses.
 The controlling root owns the cap:
 
 1. **Before every dispatch**, re-read `.devrites/AFK`, `state.md`, and the
-   selected slice. When `--parallel N` or sentinel `max_parallel` is greater than
-   1, recompute `N_eff` via `parallel select` before the next dispatch — a prior
-   one-slice round does not keep the run serial. A configured `max_slices` and any existing
+   selected slice. This invocation's `--parallel N` is the cap when present;
+   leftover sentinel `max_parallel` is not consulted in that case. When that
+   flag or sentinel `max_parallel` is greater than 1, recompute `N_eff` via
+   `parallel select` before the next dispatch — a prior one-slice round does not keep the run serial. A configured `max_slices` and any existing
    `afk_slices_remaining` value, including its released bullet form, must each
    be a decimal nonnegative integer. A missing
    `state.md` or malformed configured value fails closed; an omitted cap is the

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

@@ -9,6 +9,7 @@ Opt-in only. Default `/rite-build` stays [`one-slice-cycle.md`](one-slice-cycle.
 | omitted / `--parallel 1` | Serial one-slice |
 | `--parallel N` (**2≤N≤10**) | N is a **cap**, not a quota: run the largest eligible set ≤ N |
 | non-integer / `N≤0` / `N>10` | Hard refuse (no silent clamp) |
+| Autocomplete `--parallel N` | N is the cap for this run; leftover sentinel `max_parallel` is ignored, then `/rite-autocomplete` writes or replaces only `max_parallel: N` |
 | Autocomplete, no flag | Same path, cap from sentinel `max_parallel` else 10; serial only when ineligible |
 
 AFK caps `N`. Charge green siblings once after integrate; abort /
@@ -21,7 +22,8 @@ Size each batch by what is runnable **now**, never by the requested number:
 
 ```text
 N_eff = min(
-  cap                  -- --parallel N | sentinel max_parallel | 10 (autocomplete default)
+  cap                  -- this invocation's --parallel N (wins over leftover sentinel max_parallel)
+                       | else sentinel max_parallel | else 10 (autocomplete default)
   eligible set         -- dependency-satisfied pending slices, pairwise path-disjoint
   AFK headroom         -- remaining max_slices, max_agents, max_minutes, review queue
   host capacity        -- concurrent worktree writers + the runtime isolation table

package/pack/generated/claude/skills/rite-define/reference/gates.md

@@ -127,6 +127,11 @@ list.
 `escalating` is never in `allow_gates`: specialist routing is not something AFK can
 shortcut.
 
+`/rite-autocomplete` does not add `blocking` to `allow_gates`. It auto-resolves
+open blocking questions that already name a recommended option via
+`devrites-engine state resolve`, then continues. That is an orchestrator
+exception, not an AFK ceiling change.
+
 ## Anti-patterns
 
 - **One gate for everything.** This puts all work behind one reviewer. Pick gates per slice.

package/pack/generated/claude/skills/rite-define/reference/plan-template.md

@@ -14,7 +14,7 @@ Spec: ./spec.md   Decision coverage: ./decision-coverage.md   Date: <date>
 - Language/runtime/version: <...>
 - Frameworks/libraries: <...>
 - Storage/data: <...>
-- Test commands: <discovered runner commands; discovery contract: rite-prove/reference/test-command-discovery.md>
+- Test commands: <discovered runner commands; discovery contract: .claude/skills/rite-prove/reference/test-command-discovery.md>
 - Target/platform/constraints: <...>
 - Approach-affecting product/constraint unknowns route to `/rite-clarify`;
   `[NEEDS CLARIFICATION]` blocks approval.

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

@@ -86,8 +86,11 @@ Pull these via `Read` when shaping the resolve:
    recommend `/rite-plan repair`. Otherwise → recommend the slice's natural next action
    (typically `/rite-build` for the slice that was awaiting).
    **Completion:** the resolved state contains exactly one next command.
-6. **STOP.** This skill does not run `/rite-build` itself: the user re-enters the
-   workflow explicitly.
+6. **STOP.** User-invoked `/rite-resolve` does not run `/rite-build` itself: the
+   user re-enters the workflow explicitly. A controlling `/rite-autocomplete`
+   caller invokes the same `devrites-engine state resolve` writer internally and
+   continues; it must not emit this skill as a user handoff for a question that
+   already names a ranked recommended option.
 
 > **Mid-flight discipline.** Don't edit `spec.md` / `plan.md` to "incorporate" the
 > answer. That's `/rite-plan repair`. Don't silently retry a build after the answer

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

@@ -56,14 +56,14 @@ max_minutes: 120                     # wall-clock minutes in one host activation
 max_review_queue: 8                  # unresolved review/gate items admitted before fan-out stops
 # max_tokens: 200000                 # optional stricter host-observed token cap
 # max_cost_usd: 10                   # optional stricter host-observed cost cap
-notify: "ntfy.sh/my-topic"           # shell command; examples: rite-build/reference/afk-discipline.md
+notify: "ntfy.sh/my-topic"           # shell command; examples: .agents/skills/rite-build/reference/afk-discipline.md
 allow_gates: [advisory, validating]  # gate severities AFK auto-handles (auto-picks the recommended option)
 continue_sequence: true              # after Seal GO, open the next recorded continuation
 max_workspaces: 5                    # workspaces one armed sequence may open
-max_parallel: 10                     # cap on eligible path-disjoint Build batches (1 = serial)
+max_parallel: 10                     # unattended default cap; `--parallel N` on this invocation wins and may rewrite only this field
 ```
 
-The file is **read-only config**: never rewritten in place. `max_slices` is the initial
+The file is **read-only config**: never rewritten in place, except `$rite-autocomplete --parallel N` writes or replaces only `max_parallel: N`. `max_slices` is the initial
 budget; the mutable remaining count is the `state.md` cursor
 `afk_slices_remaining` (`AFK slices remaining: <n>` in the released bullet
 form), owned by the controlling root. Recognize either spelling and preserve
@@ -119,11 +119,18 @@ candidate manifest to cover the whole recorded chain — run
 - Every human-owned, safety, access, exhaustion, and `NO-GO` condition still stops the
   run exactly as without this field.
 
-`max_parallel` caps a Build batch for unattended runs; `1` forces the serial cycle.
-Unattended runs take the largest eligible set ≤ cap and recompute after every completed
-round (serial slice or parallel integrate)
-([parallel-batch.md § Dynamic selection and re-batching](../../../rite-build/reference/parallel-batch.md#dynamic-selection-and-re-batching));
-an explicit `$rite-build --parallel N` cap wins for that invocation.
+`max_parallel` is the unattended default batch cap only when this invocation does
+not contain `--parallel N`; `1` forces the serial cycle only in that default
+case. An exact `--parallel N` on `$rite-autocomplete` or `$rite-build` is the
+batch cap for this run: do not consult leftover sentinel `max_parallel`, and do
+not treat `max_parallel: 1` as serial. `$rite-autocomplete --parallel N` writes
+or replaces only that field so later ticks keep the cap; `$rite-build --parallel N`
+wins for that invocation without rewriting the sentinel. Never write `max_slices`
+from `--max-slices`. **Failing case:** `$rite-autocomplete --parallel 5` honors a
+leftover `max_parallel: 1` and stays serial.
+Unattended runs take the largest eligible set ≤ that cap and recompute after
+every completed round (serial slice or parallel integrate)
+([parallel-batch.md § Dynamic selection and re-batching](../../../rite-build/reference/parallel-batch.md#dynamic-selection-and-re-batching)).
 
 ## Unattended resource envelope
 
@@ -166,7 +173,18 @@ for the full taxonomy. Summary:
 | blocking | high | sync | 15m | **no** (always pauses) |
 | escalating | novel pattern | sync to specialist | 24h | **no** (always pauses) |
 
-`blocking` and `escalating` always pause regardless of `allow_gates`.
+`blocking` and `escalating` always pause for HITL and for AFK `$rite-build`,
+regardless of `allow_gates`.
+
+**Autocomplete exception.** While `$rite-autocomplete` is the controlling
+caller, an open `gate: blocking` question that already carries a ranked
+recommended option (`proposed:` or option 1 labelled `(Recommended)`) is not a
+user handoff: the orchestrator auto-picks that option through
+`devrites-engine state resolve` and continues, including internal Spec Drift
+Guard when the answer changes ownership or acceptance. Escalating,
+irreversible-risk, access, and blocking questions with no recommended option
+still pause. Putting `blocking` in `allow_gates` does not replace this resolve
+step: an unanswered blocking question still fails Seal.
 
 An open `gate: validating` entry is **merge-blocking by definition**: at `$rite-seal` any
 `questions.md` entry with `gate: validating` and `status: open` is a NO-GO, regardless of

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

@@ -8,8 +8,10 @@ user-invocable: true
 # $rite-autocomplete: full lifecycle, unattended
 
 Run every phase after one clarification window. Irreversible-risk,
-blocking/escalating,<!-- pack-scan-ignore: negated statement: gates are NOT disabled -->
-and NO-GO still pause. Use the Standard native
+escalating,<!-- pack-scan-ignore: negated statement: gates are NOT disabled -->
+access, unanswered blocking with no recommended option, and remaining NO-GO
+still pause. Open blocking questions that already name a ranked recommended
+option auto-resolve; they are not a user handoff. Use the Standard native
 profile by default and Full for high-risk scope or explicit `--full`; see
 [`orchestration-profiles.md`](../devrites-lib/reference/orchestration-profiles.md).
 
@@ -85,25 +87,34 @@ executable controller/harness/bundle bytes or a missing writer, read
 3. **Arm AFK once.** Apply the loop's
    [one-write AFK contract](reference/loop.md#arm-afk-once): preserve valid
    existing bytes or create the sentinel once (`allow_gates: [advisory, validating]`); never
-   rewrite it after Vet. Preserve an existing sentinel byte-for-byte.
+   rewrite it after Vet except to write or replace only `max_parallel: N` when
+   this invocation contains `--parallel N`. Preserve an existing sentinel
+   byte-for-byte otherwise. **Failing case:** leftover `max_parallel: 1` keeps
+   the run serial after `--parallel 5`.
    **Completion:** a valid read-only AFK sentinel exists.
 4. **Drive phases.** Follow [the loop](reference/loop.md): `$rite-spec` →
    `$rite-clarify` → `$rite-temper` → `$rite-define` → `$rite-vet` →
    `$rite-build` batch loop → `$rite-prove` → `$rite-polish` →
    `$rite-review` → `$rite-seal`. Read and execute each skill; durable files, not
    chat, carry state. Apply the mutable post-vet budget before first Build.
-   Build runs the largest eligible path-disjoint batch (cap: `--parallel N`, else
-   sentinel `max_parallel`, else 10) and recomputes after every completed round until no
-   pending slice remains; a one-slice round is serial for that round only, then
+   Build runs the largest eligible path-disjoint batch (cap: this invocation's
+   `--parallel N`, else sentinel `max_parallel`, else 10) and recomputes after
+   every completed round until no pending slice remains; a one-slice round is serial for that round only, then
    selection runs again (host isolation still forces serial when concurrent writers
-   cannot be separated).
+   cannot be separated). When `--parallel N`
+   is present, pass it into `$rite-build` and do not consult leftover sentinel
+   `max_parallel`.
    **Completion:** loop reaches Seal GO or persists a valid stop before any later phase.
 5. **Apply stops.** At every gate use
    [stop-conditions.md](reference/stop-conditions.md). A `blocked` label alone is not a stop condition:
    route agent-owned red results through bounded recovery.
    Red gates block forward advancement and enter caller-owned recovery. Stop on
-   hard risk, human-owned blocking/escalating/NO-GO, or the
-   exact fingerprint's proven exhaustion. Technical exhaustion records terminal
+   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
+   option (`proposed` or option 1 labelled Recommended) auto-resolves through
+   `devrites-engine state resolve` and continues; do not emit `$rite-resolve` as
+   a user handoff. 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` is armed and sequence budget remains, in which case

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

@@ -36,5 +36,8 @@ not pick the option that's merely easiest to implement.
 
 ## When a choice is NOT autocomplete's to make
 
-Human-owned blocking/escalating, irreversible-risk, and access stay human.
-Recommended temper `expand` auto-applies; do not invent product intent.
+Irreversible-risk, escalating, access, and blocking questions with no ranked
+recommended option stay human. A blocking question that already names option 1
+`(Recommended)` or `proposed:` is autocomplete's to resolve: pick that option
+via `devrites-engine state resolve` and continue. Recommended temper `expand`
+auto-applies; do not invent product intent.