devrites 7.3.3 → 7.3.4

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

@@ -88,9 +88,9 @@ next sequence continuation through Vet in a second session, then stop.
 
 1. **Orient and parse.** Resolve source per [phase target binding](../devrites-lib/reference/parallel-workspaces.md#phase-target-binding); when a workspace exists,
    require its `state.md` and read its cursor; a fresh idea starts empty at step 2.
-   Before phase-local cold recovery, execute the bounded
-   [global frontier pass](../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier);
-   retain this source's return cursor and pending reviewer handles.
+   After normalizing arguments below, run `devrites-engine frontier <source>`
+   before phase-local cold recovery; execute its actions under the shared
+   [global frontier pass](../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier).
    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
@@ -104,7 +104,7 @@ next sequence continuation through Vet in a second session, then stop.
    Normalize current arguments to idea, `ship_preflight: yes|no`,
    `max_slices: unlimited`, `parallel: N|default`, `profile: standard|full`,
    and `cross_model: yes|no`.
-   **Completion:** normalized state is unambiguous and no sentinel or workspace file has been written.
+   **Completion:** arguments and source authority are unambiguous; local cursor and pending handles remain intact.
 2. **Specify and clarify.** Run `devrites-interview`, `/rite-spec`, and
    `/rite-clarify` as one window. `open` material coverage never arms
    AFK. **Completion:** `Decision coverage: CLEAR` is durable.
@@ -121,12 +121,12 @@ next sequence continuation through Vet in a second session, then stop.
    `/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.
-   Execute the shared [global frontier pass](../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier)
-   at phase entry, before recovery, on returns and before native waits, not only
-   during Build or after Seal. Preserve source-local phase cursors; Autocomplete
-   retains repository scheduling. Apply its protected validation window before
-   landings/checkpoints and account admission. Pass resolved `--parallel N` to
-   Build under its one global cap and existing admission/isolation gates.
+   Run `devrites-engine frontier <source>` at phase entry, before recovery,
+   on returns and before native waits; execute the shared
+   [global frontier pass](../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier),
+   not merely its report. Autocomplete retains repository scheduling and local
+   cursors. Apply its protected validation window and pass resolved `--parallel N`
+   to Build under the same global cap and admission/isolation gates.
    **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:

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

@@ -74,12 +74,12 @@ Workspace files, not chat, carry state. Read/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 |
 
-At every phase entry, before cold/local recovery, on reviewer/planning returns and
-before native waits, Autocomplete executes the bounded
-[global frontier pass](../../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier).
-Keep source-local return cursors and pending handles; apply its protected
-validation window before accepting accounts or landing work. This scheduling
-precedes owner Seal and does not change ordered handoff below.
+At phase entry, before cold/local recovery, on landing/reviewer/planning returns
+and before native waits, run `devrites-engine frontier <source>` and execute the
+shared [global frontier pass](../../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier).
+Its report requires authorized preparation/Vet and mixed selection, not a pause.
+Preserve local cursors, pending handles and protected validation windows;
+scheduling precedes owner Seal without changing ordered handoff below.
 
 Check [stop-conditions.md](stop-conditions.md) before advancing. Discard stale
 pass evidence after source edits. Re-read the selected source before each phase per [phase target binding](../../devrites-lib/reference/parallel-workspaces.md#phase-target-binding). On a cold resume or

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

@@ -4,11 +4,11 @@
 
 Opt-in only. Default `/rite-build` stays [`one-slice-cycle.md`](one-slice-cycle.md).
 
-Autocomplete first executes shared
-[`parallel-workspaces.md`](../../devrites-lib/reference/parallel-workspaces.md):
-it owns global admission, authorized source discovery and controller routing.
-The local selection below applies to standalone Build; mixed selection uses
-that reference and then this same per-slice review/repair/integration lifecycle.
+Autocomplete runs `devrites-engine frontier <source>` and executes shared
+[`parallel-workspaces.md`](../../devrites-lib/reference/parallel-workspaces.md#continuous-global-frontier):
+it owns preparation, global admission and controller routing. Standalone Build
+stays source-local; frontier notices from `parallel select --from-plan` do not
+expand its picks. Autocomplete consumes `frontier-select-command`, then this lifecycle.
 
 ## Entry
 
@@ -161,8 +161,8 @@ means controller; CLI lease `--slice` uses source-qualified foreign keys.
    (imperative summary, never a slice id). Staging branch, durable exact landing
    intent, then FF; retry the same operation after interrupted persistence.
    The engine reconciles only that recorded landing and refuses unrelated
-   HEAD/ref movement. Conflict → `integrate-failed`; classify under repair rounds
-   (siblings stay in place).
+   HEAD/ref movement. Conflict → `integrate-failed`; repair in place, retaining
+   slot/paths while independent safe landings/refill continue.
    Never integrate because a wright returned.
 7. Each landing: FF control (the branch that held `HEAD` when the batch started —
    often `main`/`master`, otherwise whatever the user was on) by one local commit,

package/package.json

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