devrites 4.0.7 → 4.0.9

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

@@ -46,6 +46,13 @@ no-progress corrections. A retained fingerprint with remaining offline budget is
 not terminal merely because `state.md` was written by the failed action or a prior
 session ended.
 
+Past evidence being irretrievable is not by itself terminal. When an in-scope
+trusted diagnostic seam can make the next retained fingerprint uniquely
+actionable, Autocomplete must run diagnostic-amplification Plan repair and narrow
+Vet inline, then pause for a fresh GO before the single evidence-acquisition
+attempt. Use `Next: none` only after proving no safe in-scope amplification seam
+exists, a real human/risk/scope gate owns it, or bounded recovery is exhausted.
+
 ## Stop on gate severity
 
 - `blocking` gate fires → synchronous pause.

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

@@ -14,7 +14,9 @@ first**; if none, tell the user to run `$rite-spec <feature>`.
 
 The root owns gates/workspace; a
 fresh-context [`devrites-slice-wright`](.codex/agents/devrites-slice-wright.toml)
-writes source and tests. Apply the readiness, selection, host, HITL/AFK,
+writes product source and tests. Exact Vet-ready executable workflow artifacts use
+[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md).
+Apply the readiness, selection, host, HITL/AFK,
 dispatch, doubt, fail-on-red, record, and stop checks. See
 [`reference/wright-dispatch.md`](reference/wright-dispatch.md).
 
@@ -61,7 +63,9 @@ reads named on-demand rules while writing; root reads them for doubt/record gate
   principle was broken**; a fresh violation is handled like any irreversible-risk item: a
   human-approved, scoped exception in the register or a stop, never folded into the slice. No
   `.devrites/principles.md` → none declared → nothing to honor.
-- **You never edit source.** You write only `.devrites/` bookkeeping. Follow the
+- **You never edit product source/tests.** You write `.devrites/` bookkeeping and,
+  only through `workflow-artifacts.md`, an exact Vet-ready executable workflow-artifact set.
+  Follow the
   host gate in `wright-dispatch.md` before every build or recovery dispatch. On a
   supported host, the wright is the only writer of code and tests. Codex gives
   the root workspace permission only so that native writer dispatch can execute;
@@ -69,6 +73,11 @@ reads named on-demand rules while writing; root reads them for doubt/record gate
   list directly in the task, dispatch the exact `devrites-slice-wright`, then
   compare `git diff --name-only` with those task paths. Any extra source file is
   a hard STOP.
+- **Executable workflow-artifact branch.** If every implementation target is an
+  exact admitted path under the active `.devrites/work/<slug>/`, the controlling
+  root materializes and proves that atomic set itself. It does not dispatch the wright,
+  decrement/count a product slice, update the candidate manifest, or execute the
+  consumptive action. After narrow Vet, restore the caller cursor.
 
 ## Workflow
 

package/pack/generated/codex/skills/rite-build/reference/phase-contract.md

@@ -8,16 +8,30 @@ See [`one-slice-cycle.md`](one-slice-cycle.md); candidate lifecycle is
    `Readiness inputs SHA-256`, all applicable exact reviewer accounts,
    ID-and-meaning traceability, and green proof preflight; run
    `devrites-engine check readiness <slug>`. Any miss/nonzero stops.
-2. **Select one slice.** Restate goal, acceptance criteria, exclusions, and exact
+2. **Select one target.** Restate goal, acceptance criteria, exclusions, and exact
    source/test paths. Before dispatch, validate relevant `assumptions.md` rows
    against live evidence. If one is disproved and changes acceptance, architecture,
    scope, or proof, use the Spec Drift Guard/plan recovery; a human-owned unknown
    stops. Resolve HITL before source work. AFK answers only permitted gates;
    human-owned or irreversible risk persists a question and stops for `$rite-resolve`.
-3. **Dispatch the sole writer.** Apply [`wright-dispatch.md`](wright-dispatch.md).
+   If the target is only an exact Vet-ready executable workflow-artifact set under
+   the active feature workspace, apply
+   [`workflow-artifacts.md`](../../devrites-lib/reference/standards/workflow-artifacts.md)
+   instead of treating it as a product slice.
+3. **Dispatch or materialize.** Product source/tests apply [`wright-dispatch.md`](wright-dispatch.md).
    Put the smallest exact project-relative source/test path list directly in the task;
-   dispatch the exact `devrites-slice-wright` fresh. Root never writes, wright never
-   widens, and a missing profile stops.
+   dispatch the exact `devrites-slice-wright` fresh. Root never writes those product
+   paths, wright never widens, and a missing profile stops.
+   For the workflow-artifact branch, the controlling root writes only the admitted
+   `.devrites/work/<slug>/` paths, proves the complete atomic set, rechecks an
+   identical product candidate, records hashes/evidence, and runs narrow Vet. Do not
+   dispatch any agent as a substitute writer and do not charge a product slice.
+
+### Executable workflow-artifact branch
+
+The controlling root materializes the exact admitted workflow-artifact set and
+**does not dispatch the wright**. This branch never changes product slice state or
+the candidate manifest; it returns through narrow Vet before any consumptive action.
 4. **Inspect the return.** Wait; compare its file list and `git diff --name-only`
    with the contract. Reject stale, partial, malformed, or out-of-scope work.
    Preserve user work; source restoration uses the same bounded wright.

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

@@ -15,6 +15,10 @@ the wright or recreate an engine bridge.
 
 1. Derive the smallest exact project-relative source/test path list; reject
    directories/globs, traversal, symlink escapes, duplicates, and `.devrites/**`.
+   A target composed only of vetted executable workflow artifacts routes to the
+   controlling root under
+   [`workflow-artifacts.md`](../../devrites-lib/reference/standards/workflow-artifacts.md);
+   its rejection here is not a blocker.
 2. Put it in the task with goal, verbatim acceptance, exclusions, context,
    `test-plan.md` proof commands, and applicable standards.
    A new path requires a new bounded contract; the wright cannot widen the task.

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

@@ -81,6 +81,16 @@ Pull `development-workflow.md` via `Read` when reshaping slice cadence or DoD cr
    `devrites-plan-drafter` in `repair` mode with only the selected mode, affected artifact
    paths, settled contract, and observed failure/drift. Await one atomic `plan-candidate`;
    the drafter writes nothing and returns human-owned choices separately.
+   When the observed failure is missing or ambiguous consumptive-action evidence,
+   require the drafter to apply `one-shot-actions.md` and return the bounded
+   diagnostic-amplification design, injective boundary map, per-seam fixtures, and
+   collision mutant. Past evidence loss alone is not a terminal conclusion.
+   The drafter never supplies implementation bodies. Bind the exact active
+   `.devrites/work/<slug>/` targets and complete executable contract; after Vet
+   READY, the controlling root materializes the exact vetted workflow-artifact paths
+   under
+   [`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
+   without dispatching the product wright.
 3. Reason about dependencies: [dependency-graph](reference/dependency-graph.md).
    Reconcile `plan.md`'s canonical `Shared contract proof`: changed provider/consumer
    boundaries keep one reused contract artifact ahead of both asserting tests, and unaffected

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

@@ -40,6 +40,8 @@ Pull these via `Read` when relevant:
 - `definition-of-done.md`: acceptance, proof, gates, scope, rollback/docs.
 - `one-shot-actions.md`: pre-attempt evidence completeness and no-rerun handling for
   consumptive proof actions.
+- `workflow-artifacts.md`: exact root-owned executable proof/controller/harness
+  artifacts under the active feature workspace.
 
 
 ## Operating rules
@@ -57,8 +59,11 @@ Pull these via `Read` when relevant:
   [`agents.md`](../devrites-lib/reference/standards/agents.md). The root owns exact
   vetted gate execution, browser capability, the evidence verdict, and canonical
   writes. The proof runner is read-only and validates immutable logs/artifacts.
-  Every accepted source/test correction is one bounded
+  Every accepted product source/test correction is one bounded
   `devrites-slice-wright` task, never an inline edit.
+  Exact Vet-ready executable workflow artifacts under the active `.devrites/**`
+  workspace follow `workflow-artifacts.md` and are materialized by the controlling
+  root; they are not product writer work.
 - **Prove remains the controlling caller during technical backtracking.** Save
   its return cursor, invoke Plan/Vet or bounded remediation inline, consume each
   nested phase boundary, then resume the failed Prove step. Never make the human
@@ -114,7 +119,8 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    gates prove only their named static criterion.
    Immediately before any consumptive action, apply `one-shot-actions.md` to the
    live candidate: require the vetted retained-artifact identity, bounds,
-   sanitization, terminal-path fixtures, and cleanup-survival proof. A missing,
+   sanitization, injective boundary map, per-seam fault fixtures, collision mutant,
+   terminal-path fixtures, and cleanup-survival proof. A missing,
    stale, or disposable-only evidence surface returns to Vet inline and consumes
    no attempt. Record the admitted artifact identity before execution. After a
    failed consumptive action, triage from that artifact; never reproduce it by
@@ -155,6 +161,11 @@ failure is a blocker; this Upgrade admission never authorizes source or test cha
    reproduction to fix and re-vet the retained fingerprint. Once the failure
    condition is demonstrably changed, stop at the fresh-authorization boundary;
    only a new human GO may admit the next real attempt.
+   If the retained fingerprint is missing or ambiguous, the lost past evidence
+   does not prove that no safe future acquisition design exists. Treat an in-scope
+   discriminator as a diagnostic-amplification Plan gap: repair and narrow-Vet the
+   boundary map and collision proof inline, then stop for fresh GO before one
+   evidence-acquisition attempt. Do not guess the runtime fix or reuse the old GO.
 8. The root updates `evidence.md`, `browser-evidence.md` (when present),
    `traceability.md`, and `state.md`. Record exactly one binding for the observed
    digest in evidence and browser evidence. New proof goes to canonical

package/pack/generated/codex/skills/rite-prove/reference/failure-triage.md

@@ -17,6 +17,10 @@ loop to `devrites-debug-recovery`.
    - flaky (passes on re-run, timing/order) → note it; don't paper over with retries.
    - external dependency down → record blocker; don't fake the result.
 3. **Isolate:** minimize to the smallest failing case; bisect the diff if needed.
+   If consumptive evidence maps to multiple causal seams, this is a
+   diagnostic-amplification plan gap: design and Vet an injective boundary
+   discriminator offline instead of guessing a runtime correction or declaring
+   the cleaned-away past state terminal.
 4. **Fix within scope:** the current slice/feature only. If the fix reaches outside
    scope, stop and record a blocker in `state.md` (then `$rite-plan unblock`).
 5. **Re-run** the same command when it is repeatable; confirm green and record both
@@ -24,6 +28,8 @@ loop to `devrites-debug-recovery`.
    completeness and any fresh authorization before a new attempt. Its spent
    action authorization does not stop offline recovery: a retained new fingerprint
    enters caller-owned diagnosis, correction, fixtures, and narrow Vet immediately.
+   A separately authorized diagnostic-amplification attempt may acquire the missing
+   discriminator after its evidence design passes Vet; it is not a blind rerun.
 
 ## Rules
 - Quote the real error text; don't paraphrase it away.

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

@@ -100,8 +100,10 @@ Pull the standard named by the active axis: `principles.md`, `patterns.md`,
    discriminating assertion and decisive signal, not merely a command or expected exit zero.
    Identify every consumptive action under `one-shot-actions.md`. Before admitting
    it, require the exact durable retention surface, trust-safe diagnostic schema,
-   cleanup ordering, terminal-path coverage, and discriminating fixtures in
-   `test-plan.md`. Missing or stale one-shot evidence completeness is a technical
+   cleanup ordering, terminal-path coverage, a finite injective boundary map,
+   per-boundary fault fixtures, and an executed collision mutant in `test-plan.md`.
+   Every retained failure fingerprint must identify one actionable seam; a broad
+   operation/cause shared by multiple emit sites is a gap. Missing or stale one-shot evidence completeness is a technical
    preflight gap; do not spend the action to learn what cleanup would erase.
    Preflight observes; it need not make future behavior pass.
 2c. **Implementation-readiness audit.** Goal-backward map every REQ/AC/NFR, interaction,

package/pack/generated/codex/skills/rite-vet/reference/artifacts.md

@@ -35,7 +35,7 @@ Inventory/currentness: <pass/gaps> · slice order/independence: <pass/gaps> ·
 UX/spec/architecture: <pass/n-a/gaps> · operations/rollout/rollback: <pass/n-a/gaps>
 
 Shared contract proof: <pass | gap: missing/one-sided/duplicated-contract/vague/non-consuming>
-One-shot evidence completeness: <n/a | pass: action + retained artifact + bounds/sanitization + cleanup-survival fixtures | gap: exact missing proof>
+One-shot evidence completeness: <n/a | pass: action + retained artifact + bounds/sanitization + injective boundary map + per-seam/collision/cleanup fixtures | gap: exact missing proof>
 
 ## 3. Axis findings (floor-gated)
 | Axis | Floor band | Findings (sev · confidence) |
@@ -96,9 +96,9 @@ aliases, user-specific absolute paths, or temporary proof trees. Evidence record
 the command actually executed.
 
 ## Consumptive action gates
-| Action | Why one-shot/consumptive | Retained artifact | Bounds + sanitization | Terminal-path fixtures | Cleanup survival | Retry authority |
-|---|---|---|---|---|---|---|
-| <exact approved action or n/a> | <one attempt/quota/state/evidence deletion> | <durable operator-controlled path/schema> | <size/cardinality + known/unknown/malformed handling> | <success/known/unknown/hostile> | <assertion> | <none/fresh human authorization> |
+| Action | Why one-shot/consumptive | Retained artifact | Bounds + sanitization | Boundary map + collision proof | Terminal-path fixtures | Cleanup survival | Retry authority |
+|---|---|---|---|---|---|---|---|
+| <exact approved action or n/a> | <one attempt/quota/state/evidence deletion> | <durable operator-controlled path/schema> | <size/cardinality + known/unknown/malformed handling> | <every emit seam -> stable boundary ID; per-seam injection + alias mutant rejected> | <success/known/unknown/hostile> | <assertion> | <none/fresh human authorization> |
 
 Every behavioral row names a positive, discriminating assertion and the decisive output it
 produces. A command or expected exit zero alone is not a behavioral assertion; static gates

package/package.json

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

package/scripts/codex-generate.sh

@@ -95,7 +95,7 @@ This project has DevRites installed for both Claude Code and Codex.
 - Custom Codex subagents generated from the DevRites review agents live in `.codex/agents`.
 - In DevRites guidance, **invoke** means run a skill inline in the current context; **dispatch** means start a fresh agent with `spawn_agent`, wait for it, and reconcile its result.
 - Dispatch every exact named `devrites-<role>` required by the active workflow in a fresh subagent thread, wait for it, and reconcile its result. If that role is unavailable, stop for HITL; never skip it, never substitute a generic/default child, and never execute the specialist role in the root context.
-- The root uses the workspace-capable `devrites-orchestrator` profile because Codex children cannot elevate above the parent permission ceiling. This permission is for native writer dispatch and workflow artifacts; the root must never edit source or tests itself.
+- The root uses the workspace-capable `devrites-orchestrator` profile because Codex children cannot elevate above the parent permission ceiling. This permission is for native writer dispatch and exact path-bounded executable workflow artifacts under the active `.devrites/work/<slug>/`; the root must never edit product source or tests itself.
 - Every generated specialist is hook-free. `devrites-slice-wright` alone uses `default_permissions = ":workspace"`; every other specialist uses `default_permissions = ":read-only"`. Exact paths are instruction-enforced: put the project-relative paths in the task, wait for the wright, compare its file list and `git diff --name-only` with that contract, and reject any extra path. Never bypass the wright, widen its contract, or edit source in the root; the root must never recreate an engine dispatch bridge.
 - A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Native host permission and sandbox prompts remain authoritative and cannot be inferred or bypassed.