devrites 5.10.2 → 5.12.0

package/pack/generated/pi/skills/devrites-lib/reference/standards/verification-methods.md

@@ -0,0 +1,110 @@
+# Verification methods and coverage
+
+> Applies when: choosing how to check work — Prove, Review, Seal, Vet oracles,
+> audit sweeps, or any claim that a scope was verified.
+
+A check earns its place by what it can catch. This file is the selection
+discipline: distinct methods, an explicit coverage denominator, honest status
+vocabulary, and named fallbacks when a capability is missing. The `gates.md`
+acceptance ledger ([`gates.md`](gates.md)) binds runnable oracles to evidence;
+this file governs how methods are *chosen* and how coverage is *counted*.
+
+## A method is distinct only when its failure target differs
+
+A method names five things: the **failure** it hunts, the **procedure**, the
+**oracle** that separates pass from fail, the **material/scope** inspected, and
+the **evidence** it leaves. Count distinct failure targets supported by the
+observed checks, not command or tool names. Re-running the same check with
+cosmetic flags adds no method. If tests, build, and lint all stop at the same
+dead import, those runs supply no evidence of their later checks.
+
+Overlapping detection does not make different checks identical: executed tests
+asserting retry exhaustion, a build checking interface compatibility, and lint
+checking unsafe shell interpolation can support three distinct targets. Record
+each target and observation; neither three command names nor a shared ability
+to catch bad imports decides the count.
+
+Different methods may share the authoritative oracle (the spec, the ledger,
+the diff). Inventing a second expected answer to look independent is not
+independence. Where a requirement supports it, prefer complementary families:
+
+- **functional** — execute the behavior at boundaries and failure paths;
+- **structural** — inspect the changed surface, its interfaces, and callers;
+- **adversarial** — metamorphic properties, differential baselines, fault
+  injection, or a different render/interaction path.
+
+## Enumerate the denominator before claiming coverage
+
+Before work is called covered, write the inventory it must cover: every
+unit × check × environment row. Examples of rows a denominator may need:
+
+- Code: changed behaviors, affected callers, edge cases, supported runtimes.
+- UI: routes × viewport boundaries × interactive states (loading, empty,
+  error, disabled, success, focus) × agreed browsers.
+- Fixed-layout documents: every page × required visual check on the final
+  render — a thumbnail sheet or extraction pass is not visual inspection.
+- Reflowable documents: content units × renderer/viewport/font states;
+  reflow invalidates prior visual coverage even when the text is unchanged.
+- Data: schema, reconciliation, missing-data treatment, transformation classes.
+
+Two rules keep the denominator honest:
+
+1. **Never shrink it to reach 100%.** An exclusion needs a recorded decision
+   with authority; a unit that cannot be inspected stays visible as missing.
+   A percentage without the inventory proves nothing.
+2. **Sampling is not coverage.** A sample can surface a defect; only a row per
+   required unit satisfies a complete-inspection claim. If exhaustive coverage
+   exceeds budget, narrow scope with the human — do not quietly redefine done.
+
+## Status and result are separate facts
+
+Record two fields per row, never one:
+
+- **status** — `fresh` (run on this candidate), `reused` (carried forward after
+  a recorded applicability check), `failed` (the check ran and could not
+  complete — environment, timeout, parse), `missing` (never run), `blocked`
+  (cannot run: no tool, no authority).
+- **result** — `pass`, `fail`, `unverified`.
+
+A missing check is not a negative result; a failed check is not an unavailable
+tool; freshness alone is not a pass. Only applicable `fresh` or `reused`
+evidence with a supported `pass` satisfies a required row. Reuse keeps the
+original observation and records the new applicability check separately —
+see [`candidate-integrity.md`](../candidate-integrity.md#evidence-validity).
+When change impact cannot be bounded, recheck the full affected scope.
+
+## Judge evidence before counting a method
+
+Before any check counts, answer five questions:
+
+1. What distinct failure could this method reveal?
+2. What material and environment did it actually inspect?
+3. What independent observation separates pass from fail?
+4. Where is the observation recorded, and which candidate does it bind?
+5. What does this method not establish?
+
+Duplicate answers mean one method, not two. A property no available tool can
+verify is `unverified` — name the fallback, never manufacture a pass.
+
+## Capability fallbacks
+
+A missing capability gets a named fallback, not a fabricated check:
+
+| Missing | Honest fallback |
+| --- | --- |
+| Network | Dated local sources with their limits stated; a decision that needs current facts blocks or narrows scope with approval. |
+| Question tool | Numbered text options with a marked recommendation and a free-text path; a skipped answer stays `unanswered` ([`elicitation.md`](elicitation.md)). |
+| Fresh-context reviewer | `gap` under [`agents.md`](agents.md) result admission; required review waits for an authorized reviewer — self-review is labeled, never relabeled independent. |
+| Delegation permission | No dispatch. Prepare a neutral handoff; never bypass the restriction through another CLI.<!-- pack-scan-ignore: defensive rule prohibiting bypass, not instructing it --> |
+| Renderer/vision | Mechanical checks run; the visual-coverage rows stay `blocked` until real inspection or a recorded narrower scope. |
+| Budget | Stop or reduce scope with approval; failed attempts stay in the record, never deleted to look clean. |
+
+## Exercise the recipient's path
+
+Verification ends at the artifact as its recipient meets it: install the
+package, open the archive, run the binary, follow the entry point, navigate
+the UI. Installation, host discovery, activation, and actual behavior are four
+different facts — each proves only itself. Check relative paths, bundled
+resources, links, metadata, licensing, and instructions on the packaged form,
+from a clean location where feasible. A check run only against the working
+tree proves the working tree.

package/pack/generated/pi/skills/devrites-lib/reference/standards/windows.md

@@ -0,0 +1,51 @@
+# Windows — the deferral ledger
+
+> Applies when: a change introduces a deferral marker (TODO, FIXME, XXX, HACK,
+> a skipped test, a stub body) or `windows.md` waivers are authored or judged.
+
+`windows.md` is the broken-windows ledger. A review finding can describe a new
+`TODO`, a skipped test, or a stubbed body; this artifact makes the register
+countable instead: every deferral marker the change *introduces* must either
+be removed or carry an explicit waiver row, or `check windows` fails. The
+target is not zero deferrals — it is zero *silent* deferrals. Pre-existing
+markers on the baseline are pre-existing debt and are never attributed to the
+current change; only added lines count.
+
+Optional until a marker is introduced: a feature with no new markers needs no
+`windows.md`. Once any hit exists, Seal treats an unwaived marker as NO-GO.
+
+## Grammar
+
+```markdown
+- <project-relative path> | <marker token> | <reason>
+```
+
+- One waiver per row; each row waives exactly one hit at that path carrying
+  that marker. Five new TODOs in one file need five rows — a blanket row
+  cannot cover them.
+- `marker token` is the literal marker the checker reported (`TODO`, `t.Skip(`,
+  `NotImplementedError`, `panic("TODO`, …).
+- `reason` must be non-empty and should name the follow-up owner or slice; a
+  row with an empty reason warns and waives nothing.
+- Rows never suppress coverage — they explain it. Reviewers still judge
+  whether the deferral itself is acceptable.
+
+## Command
+
+```text
+devrites-engine check windows <slug> [--worktree|--staged|--base <ref>]
+```
+
+Exit `0` when no marker is introduced or every hit is waived; `3` when any
+introduced marker lacks a waiver or the workspace/ledger is unreadable; `2`
+on usage errors. The check parses the unified diff (`-U0`) for added lines,
+treats untracked files as wholly new, ignores binary files, deletions, and
+`.devrites/` paths, and runs on worktree, staged, or base-reference diffs.
+
+## Reviewer posture
+
+A waived marker is disclosed, not approved. The Seal reviewer asks whether
+each deferral belongs in this change at all, whether the reason is honest
+(owner and follow-up named, not "later"), and whether the diff could simply
+remove the marker instead. A waiver that exists only to silence the gate is
+an `Important` finding.

package/pack/generated/pi/skills/devrites-lib/reference/standards/workflow-artifacts.md

@@ -1,5 +1,7 @@
 # Workflow Artifact identity
 
+> Applies when: a plan declares root-authored executable workflow files.
+
 Workflow Artifact plans/isolates/proves; never enters product candidate/readiness/
 built count or authorizes consumption. Module owns semantics; callers retain only
 link and entry/return.

package/pack/generated/pi/skills/devrites-lib/reference/workspace-artifact-schema.md

@@ -24,10 +24,10 @@ accept safe legacy basenames. Ordinary phases never rename them.
 | clarify | spec artifacts plus `decision-coverage.md` |
 | temper | clarified spec artifacts plus `strategy.md` when temper runs |
 | define/plan | clarified spec artifacts plus `architecture.md`, `plan.md`, `tasks.md`, `traceability.md` |
-| vet/build/converge | plan artifacts plus `eng-review.md`, `test-plan.md`; Build creates and maintains `touched-files.md` after its first green slice |
+| vet/build/converge | plan artifacts plus `eng-review.md`, `test-plan.md`, `gates.md`; Build creates and maintains `touched-files.md` after its first green slice |
 | prove/polish/review | vetted plan artifacts plus `evidence.md`, `touched-files.md` |
 | seal/ship/done | proof artifacts plus `review.md`, `seal.md`; Ship writes `ship.md` |
-| conditional | `flows.md` when diagrams clarify; `visual/` HTML+`.outline.md` companions when a richer reviewable visual earns it (optional; never readiness-required); `design-brief.md` and `browser-evidence.md` for UI; `drift.md` for drift; `polish-report.md` for polish; `handoff.md` only when requested; `references.md` + `references/` when references exist; `investigation-map.md` for pressure-test; `dogfood.md` for dogfood; `packets/` for by-reference dispatch packets and admitted accounts (≤ 64 KiB each; older closed rounds may be deleted; never transcripts); `history/` for verbatim relocated checkpoint narrative (append-only, never a read-next) |
+| conditional | `flows.md` when diagrams clarify; `visual/` HTML+`.outline.md` companions when a richer reviewable visual earns it (optional; never readiness-required); `design-brief.md` and `browser-evidence.md` for UI; `drift.md` for drift; `polish-report.md` for polish; `handoff.md` only when requested; `references.md` + `references/` when references exist; `investigation-map.md` for pressure-test; `dogfood.md` for dogfood; `windows.md` when the diff introduces deferral markers (waiver ledger for `check windows`); `packets/` for by-reference dispatch packets and admitted accounts (≤ 64 KiB each; older closed rounds may be deleted; never transcripts); `history/` for verbatim relocated checkpoint narrative (append-only, never a read-next); `readiness-inputs.json` as the advisory per-input drift baseline written by `check drift --record` after Vet's binding (never a gate input; regenerated, not hand-edited); `notes.md` for anchored notes bound to verbatim code quotes (engine-regraded; non-exact anchors block seal) |
 
 ## What each file owns
 
@@ -43,7 +43,7 @@ accept safe legacy basenames. Ordinary phases never rename them.
 | `visual/<name>.html` | optional portable human-viewable visualization; pair with sibling `.outline.md`; self-contained preferred | 400 lines |
 | `visual/<name>.outline.md` | required machine dual-read companion for the sibling HTML; outline wins on conflict; never a candidate path | 200 lines |
 | `visual/README.md` | optional index of visuals in the workspace | 80 lines |
-| `decisions.md` | ADR-style `DEC-###` log: status, context, options, decision, consequences, related IDs | 200 lines |
+| `decisions.md` | ADR-style `DEC-###` log: status, context, options, decision, consequences, related IDs; optional `Files:`/`Tags:` fields make entries queryable by path or theme | 200 lines |
 | `assumptions.md` | assumptions with confidence, owner, validation status | 160 lines |
 | `questions.md` | current `q-YYYY-MM-DD-NNN` (or released `Q-###`) open/resolved questions, gate, answer, impact | 180 lines |
 | `plan.md` | technical approach, slice strategy, canonical shared-contract proof, validation strategy, rollback | 220 lines |
@@ -51,6 +51,7 @@ accept safe legacy basenames. Ordinary phases never rename them.
 | `traceability.md` | matrix: AC/REQ ID, slice IDs, test/proof, evidence ID, touched files, status | 220 lines |
 | `eng-review.md` | vetted scope/architecture/quality/performance, failure modes, preflight, stable-input binding, `## Deferred findings` (late rows: severity · site · role · kind · round) for Review | 240 lines |
 | `test-plan.md` | executable proof commands, preflight/provenance contract, acceptance and interaction coverage | 260 lines |
+| `gates.md` | machine-checked acceptance ledger: one gate per required outcome — runnable `CHECK`/`EXPECT`/`CWD` or manual `EVIDENCE`; engine-bound evidence, `ABANDON:` handoffs | 200 lines |
 | `state.md` | compact cursor table/key-values; no narrative log | 120 lines |
 | `evidence.md` | `EVID-###` command/action, result, timestamp if available, related AC/slice IDs, limitation | 280 lines |
 | `browser-evidence.md` | UI route/viewports/screenshots/console/network/interactions and Visual Verdict | 220 lines |
@@ -63,6 +64,8 @@ accept safe legacy basenames. Ordinary phases never rename them.
 | `review.md` | reconciled Review verdict: `## Spec` and `## Code review` accounts, deferred-finding labels/actions, drift | 240 lines |
 | `seal.md` | seal preflight, exact reviewer roster accounts, GO/NO-GO verdict and disclosures | 200 lines |
 | `ai-spec.md` | model/RAG/agent/eval/LLM-output scope for AI surfaces | 160 lines |
+| `windows.md` | deferral-marker waiver ledger: one `- path | marker | reason` row per introduced marker; `check windows` fails on unwaived hits | 120 lines |
+| `notes.md` | `NOTE-###` anchored notes — rationale/warnings bound to a verbatim quote in one repository file; `note check` regrades anchors and drift blocks seal | 160 lines |
 
 For visual pairs load only matching [playbooks](visual-playbooks/index.md); use
 the [required outline headings](visual-playbooks/outline-template.md).
@@ -158,6 +161,23 @@ Apply [[`context-hygiene.md`](standards/context-hygiene.md) dispatch packets](st
 for byte-size checks and lossless retrieval; budget overrides neither rewrite protected
 history nor require loading it all.
 
+## Anchored notes
+
+`notes.md` carries agent-authored knowledge bound to code it describes — a rationale,
+warning, or review stop that must not silently drift when the code moves or changes.
+Write it only through `devrites-engine note add <slug> <subject> <quote> <title>
+[body]`: the engine assigns `NOTE-###` IDs, stores the subject path and verbatim
+`quote`, and keeps the file parseable. One note per fact; quote the smallest
+contiguous run that identifies the anchor (identifiers, literals, signatures —
+whitespace is normalized, other edits stale it).
+
+`note list` and `note check` regrade every anchor: `exact` (quote found in subject),
+`moved` (quote lives in exactly one other file — `note check --repair` rewrites the
+subject), `stale`/`ambiguous`/`lost` otherwise. Dependency and workspace trees
+(`node_modules`, `.devrites`, vendor, build output) never count as relocation.
+`check seal` refuses malformed notes and non-exact anchors; fix or `note rm` them,
+never attest past them.
+
 ## Native readiness ownership
 
 `decision-coverage.md` owns topology; `test-plan.md`, executable proof; `eng-review.md`,
@@ -214,6 +234,11 @@ unless the stated reason makes the boundary irreducible.
 
 ## Read next by phase
 
+Run `devrites-engine next <slug>` at phase entry for the minimal remaining path
+(current phase, open questions, missing artifacts, next `/rite-*` command), then
+read the phase row below — or hand `devrites-engine context <slug> --phase <p>`
+to the engine and read the bundle it emits.
+
 | Phase | Read |
 | --- | --- |
 | spec | `README.md`, `brief.md`, `spec.md`, `references.md`, `questions.md` |

package/pack/generated/pi/skills/devrites-prose-craft/SKILL.md

@@ -3,6 +3,8 @@ name: devrites-prose-craft
 description: Rewrite prose to remove AI tells while preserving meaning and voice. Use for artifacts, replies, commits, or PR copy; not code comments or UI craft.
 user-invocable: false
 ---
+<!-- loads: {"always":["devrites-lib/reference/standards/prose-style.md"],"triggers":{"word-choice":["devrites-prose-craft/reference/banned-phrases.md"],"structure":["devrites-prose-craft/reference/structures.md"],"examples":["devrites-prose-craft/reference/examples.md"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-prose-craft` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # devrites-prose-craft: prose that reads human
 
@@ -56,7 +58,7 @@ In detect-only, report Tier 1A (figurative filler) separately from Tier 1B (word
 - Always read [`prose-style.md`](../devrites-lib/reference/standards/prose-style.md) for the two
   registers, preservation contract, and core checks.
 - Load [`reference/banned-phrases.md`](reference/banned-phrases.md) when word choice or tone is
-  the problem.
+  the problem (trigger `word-choice`).
 - Load [`reference/structures.md`](reference/structures.md) when sentence shape, rhythm, or
   formatting is the problem.
 - Load [`reference/examples.md`](reference/examples.md) when the target artifact's shape is

package/pack/generated/pi/skills/devrites-source-driven/SKILL.md

@@ -3,6 +3,8 @@ name: devrites-source-driven
 description: Verify uncertain framework or library behavior in installed source or official docs. Use for unfamiliar APIs; not internal code.
 user-invocable: false
 ---
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/tooling.md"],"triggers":{"agents":["devrites-lib/reference/standards/agents.md"]},"workspace":["state.md","spec.md","plan.md","decisions.md","evidence.md","references.md"],"workspaceByRole":{"evidence-scout":["state.md","spec.md","plan.md","references.md"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-source-driven` bundles every file named below into one deduplicated read.
 
 # devrites-source-driven: verify, don't guess
 

package/pack/generated/pi/skills/devrites-ux-shape/SKILL.md

@@ -3,6 +3,8 @@ name: devrites-ux-shape
 description: Shape UX/UI direction, states, and interactions before code. Use for screens, forms, dashboards, or settings; not for implementation or polish.
 user-invocable: false
 ---
+<!-- loads: {"always":["devrites-ux-shape/reference/brief-template.md","devrites-ux-shape/reference/visual-direction-probe.md","rite-build/reference/frontend-trigger.md","devrites-frontend-craft/reference/design-references.md","devrites-frontend-craft/reference/quality-standards.md"],"triggers":{"afk":["devrites-lib/reference/standards/afk-hitl.md"]}} -->
+> Read-set manifest: `devrites-engine context [slug] --skill devrites-ux-shape` bundles every file named below into one deduplicated read. Trigger names map to the conditional rules in the sections that follow.
 
 # devrites-ux-shape: plan the UX/UI before code
 

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

@@ -5,6 +5,8 @@ argument-hint: "[verb [args...]]"
 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.
 
 # /rite: DevRites menu + router
 

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

@@ -4,6 +4,8 @@ description: Adopt an existing codebase into DevRites by reverse-engineering cur
 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":{}} -->
+> 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.
 
 # /rite-adopt: onboard existing code
 

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

@@ -5,6 +5,10 @@ argument-hint: "[idea] [--ship|--yolo] [--max-slices N] [--parallel N] [--full]
 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.
+
+
 # /rite-autocomplete: full lifecycle, unattended
 
 Run every phase after one clarification window. Irreversible-risk,
@@ -21,7 +25,8 @@ Read [`core.md`](../devrites-lib/reference/standards/core.md) and [`afk-hitl.md`
 [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md) before any stop/continue or execution decision involving a
 consumptive action. Before honoring a terminal cursor that names missing
 executable controller/harness/bundle bytes or a missing writer, read
-[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md). Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
+[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
+(trigger `workflow-artifacts` — only when a workspace declares them). Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standards/acceptance-preserving-reslice.md`.
 
 <!-- BEGIN RESLICE ROUTE-TO-ACTION -->
 - `FOLD` → keep Plan repair/affected Vet internal; no stop solely for topology/count.

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

@@ -75,7 +75,13 @@ Workspace files carry state; chat does not. Read and execute each phase skill:
 
 Before advancing, check
 [stop-conditions.md](stop-conditions.md). After source edits, discard stale pass
-evidence. Re-read the active workspace before each phase.
+evidence. Re-read the active workspace before each phase. On a cold resume or
+new activation, run `devrites-engine check regression <slug>`: `BLOCKED` names a
+durable fact lost since the last checkpoint — restore or route it through its
+owning phase before continuing; `unproven` does not block. After each phase's
+durable advance lands (green check loop, checkpoint commit), run
+`devrites-engine check regression <slug> --update` to ratchet the progress
+floor; `--update` never excuses an unreconciled regression.
 
 ## Sequence continuation
 

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

@@ -5,6 +5,10 @@ argument-hint: "[--parallel N] [slice number or name]"
 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"],"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.
+
+
 # /rite-build: one verified slice
 
 HITL stops; a later user invocation starts the next slice.
@@ -17,7 +21,8 @@ caps and pause rules. Every wright returns after one slice.
 Root owns gates/bookkeeping; fresh
 [`devrites-slice-wright`](.pi/agents/devrites-slice-wright.md) writes source/tests.
 Workflow Artifacts use
-[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md).
+[`workflow-artifacts.md`](../devrites-lib/reference/standards/workflow-artifacts.md)
+(trigger `workflow-artifacts` — only when the plan declares them).
 Execute [`reference/phase-contract.md`](reference/phase-contract.md)
 ([`one-slice-cycle.md`](reference/one-slice-cycle.md),
 [`afk-discipline.md`](reference/afk-discipline.md)); dispatch uses
@@ -32,23 +37,32 @@ Wright applies anti-slop; root verifies returns and never patches source.
 
 ## Invariants
 
-- Default: one slice; writers serial on control. Parallel only via `--parallel N`
-  under [`reference/parallel-batch.md`](reference/parallel-batch.md). Same-worktree
-  multi-writer / root-emulated concurrency forbidden. Native-worktree pilot =
-  single-slice isolation when `wright-dispatch.md` preflight + reconcile hold.
-- Exact feature scope only; reject out-of-allowlist diffs; record adjacent issues.
-- Re-prove affected behavior after edits; reuse observations only under
-  [evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
+- Default: one slice; writers serial on control (core.md #5). Parallel only via
+  `--parallel N` under [`reference/parallel-batch.md`](reference/parallel-batch.md).
+  Same-worktree multi-writer / root-emulated concurrency forbidden.
+  Native-worktree pilot = single-slice isolation when `wright-dispatch.md`
+  preflight + reconcile hold.
+- Exact feature scope only (core.md #7); reject out-of-allowlist diffs
+  (`devrites-engine check diff-scope <slug> --allow <contract-paths>`); record
+  adjacent issues. An adjacent issue or non-obvious rationale bound to specific
+  code anchors as a note — `devrites-engine note add <slug> <file> "<verbatim
+  quote>" <title>` — so refactors regrade it instead of losing it
+  ([`notes.md`](../devrites-lib/reference/workspace-artifact-schema.md#anchored-notes)).
+- Re-prove affected behavior after edits (core.md #6); reuse observations only
+  under [evidence validity](../devrites-lib/reference/candidate-integrity.md#evidence-validity).
 - Unplanned dependency/design-system/gap/repair → Vet/Spec Drift Guard batch
   sweep: every contract-assumption violation recorded before one folded
   repair+vet. Ask only for licensing/cost/security/product or explicit
-  architecture-policy decisions.
-- Root never edits product source/tests (`.devrites/` + Workflow Artifact only).
-  Wright is sole product writer; extras in returned paths/`git diff --name-only` hard-stop.
+  architecture-policy decisions (core.md #8).
+- Root never edits product source/tests (`.devrites/` + Workflow Artifact only;
+  [agents.md](../devrites-lib/reference/standards/agents.md) source-writing
+  boundary). Wright is sole product writer; extras in returned paths/`git diff
+  --name-only` hard-stop via `check diff-scope`.
 - Principles bind; irreversible conflict needs human exception or stop.
-- Evidence beats confidence. Never weaken tests, skip TDD, widen writers, or
-  self-approve. Drift → [`spec-drift-guard.md`](reference/spec-drift-guard.md);
-  checkpoint → [`checkpoint.md`](reference/checkpoint.md).
+- Evidence beats confidence (core.md #6). Never weaken tests, skip TDD, widen
+  writers, or self-approve. Drift →
+  [`spec-drift-guard.md`](reference/spec-drift-guard.md); checkpoint →
+  [`checkpoint.md`](reference/checkpoint.md).
 - Async readiness waits during slice work follow
   [`debug-recovery.md`](../devrites-lib/reference/standards/debug-recovery.md)
   (bounded poll + last-signal artifact; no blind sleep as primary strategy).

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

@@ -42,6 +42,12 @@ BODY
 
 **Local-only:** never push or let scratch work trigger CI.
 
+After the commit lands, run `devrites-engine check regression <slug> --update`
+to ratchet the workspace progress baseline — the landed slice, newly checked
+acceptance criteria, and resolved questions become the new floor that later
+checks compare against. A `BLOCKED` compare before that ratchet means durable
+facts were lost this cycle; restore or route them before landing the commit.
+
 ## Restore
 After a crash, a fresh session may read the last `WIP(<slug>)` body as crash context.
 Authoritative state remains in `.devrites/`: validate the body against that workspace;

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

@@ -53,7 +53,11 @@ duplicates, absolutes, `.devrites/**`. Empty pairwise intersection required.
 **SSOT:** `devrites-engine check path-disjoint [--root <dir>] [<json-file>|-]`
 (N≥2 only; pass `--root`). Input is `{"slices":[{"id":"SLICE-002","paths":["src/policy.rs","src/policy/mod.rs"]}]}`
 (or a top-level array) built from each candidate's `Files likely touched`.
-Exit `0` → fan-out; else force serial. Inspect-time
+Exit `0` proves path disjointness only; fan-out also requires independent
+validation. A shared interface change and its implementers that must compile
+together form one validation unit, even in different files. Repair the slice
+contract into one bounded slice or sequence compatible steps before dispatch;
+do not label coupled siblings independently green. Else force serial. Inspect-time
 overlap → sibling **gap** (a shared path is a contract defect). **Failing
 case:** two parallel wrights share a path and fan-out proceeds without that
 check.
@@ -77,6 +81,9 @@ Lease: `batch_id`, `created_at`, `base_sha`, `n`,
    candidates from `orient` `task_graph.slices` + built list, each candidate's
    `Files likely touched` via `observe slice`, then
    `parallel select --cap N` (pairwise disjointness is inside that verb).
+   Preflight each selected slice with `devrites-engine check slice <slug>
+   <id>`; a malformed contract is dropped from the batch and recorded as a
+   gap, not dispatched.
 2. Write lease; freeze `B=HEAD`; `parallel create` worktrees.
 3. Dispatch ≤10 wrights in parallel (cwd=worktree; allowlist; prove `HEAD==B`).
 4. Inspect each returned path list, cumulative diff from `B`, transfer identity,
@@ -141,7 +148,9 @@ Repair rejected work in place; never discard/rebuild while budget remains.
   `devrites/parallel/<slug>/<old-batch>/<slice>` ref. If the inventory proves the accepted
   approach unsound and no corrected decomposition exists, that is exhaustion
   → blocked, preserve, STOP. **Reviewer stall/cancel or missing
-  verdict** → re-dispatch the reviewer, not the wright. **Product/policy/
+  verdict** → reconcile the old host handle under
+  [terminal reconciliation](../../devrites-lib/reference/parallel-dispatch.md#cancellation-and-terminal-reconciliation)
+  before re-dispatching the reviewer, not the wright. **Product/policy/
   irreversible** → stops for the human.
 - Dispatch one fresh repair-all `devrites-slice-wright` (cwd=worktree; step 3
   rules) with the original contract + complete inventory +

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

@@ -6,7 +6,8 @@ Opt-in `--parallel N` replaces steps 2–8 with [`parallel-batch.md`](parallel-b
 Spec Drift Guard still applies.
 
 1. **Gate.** Read core, `.devrites/ACTIVE`, then `devrites-engine orient <slug>`
-   and the Build read-next in
+   (`devrites-engine next <slug>` prints the minimal remaining path) and the
+   Build read-next in
    [`workspace-artifact-schema.md`](../../devrites-lib/reference/workspace-artifact-schema.md#read-next-by-phase):
    the selected slice via `devrites-engine observe slice <slug> <SLICE-ID>`, not whole
    `tasks.md`; over-budget or `bulk_files` artifacts are read by anchor only. Require
@@ -26,9 +27,12 @@ Spec Drift Guard still applies.
    dispatch the exact `devrites-slice-wright` fresh. Root never writes product
    paths; wright cannot widen scope; missing profile blocks.
 <!-- workflow-artifact-adapter: {"module":"devrites-lib/reference/standards/workflow-artifacts.md","entry":"Build gate enters or resumes transaction","action":"invoke canonical operation table; reconcile exact result","return":"same slice/checkpoint cursor or Plan/Vet route"} -->
-4. **Inspect.** Wait; compare returned paths and `git diff --name-only` with the
-   contract. Reject stale/partial/malformed/out-of-scope work; preserve user work.
-   Restoration uses the bounded wright.
+4. **Inspect.** Wait; run `devrites-engine check diff-scope <slug> --allow
+   <contract-paths>` for the mechanical returned-paths ⊆ contract check **before**
+   any reviewer dispatch — a violation returns through the bounded wright without
+   spending review. Then compare returned paths and `git diff --name-only` with the
+   contract for semantics diff-scope cannot judge (stale/partial/malformed work;
+   preserved user work). Restoration uses the bounded wright.
 5. **Review.** Apply [Independent Build review](#independent-build-review).
    Missing verdicts, principle breaches and open Critical/Important block acceptance.
 6. **Prove.** Against the frozen pre-slice candidate inspect

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

@@ -42,7 +42,11 @@ worktrees stay forbidden.
 
 ## Prepare
 
-1. Derive the smallest exact project-relative source/test path list; reject
+1. Run `devrites-engine check slice <slug> <SLICE-ID>` first — it fails a
+   malformed contract (missing goal, empty/invalid Writer allowlist,
+   unresolvable `Satisfies` AC ids, empty proof field) before a wright
+   context is spent; a failure is a gap, not a dispatch. Then 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
@@ -50,7 +54,12 @@ worktrees stay forbidden.
    its rejection here is not a blocker.
 2. Include goal, verbatim acceptance, exclusions, context,
    `test-plan.md` proof commands, applicable standards, and the exact
-   `WIP(<slug>):` subject (no slice id). For each triggered
+   `WIP(<slug>):` subject (no slice id). Build the wright's read-set with
+   `devrites-engine context <slug> --phase build --role slice-wright --trigger <set>`
+   and hand it the bundle path; evaluate each trigger condition and pass those
+   that fire (TDD slice → `tdd`, AFK run → `afk`, UI work → `frontend`, …).
+   The command prints `unselected=[...]`; an omitted applicable trigger is a gap.
+   For each triggered
    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.
@@ -62,17 +71,34 @@ worktrees stay forbidden.
 
 ## Run
 
-Ask the host for the exact writer in fresh context and wait. Use at most one writer
-across all linked worktrees for this workspace. Never run two writers in one worktree,
-run isolated and same-worktree writers concurrently, or substitute a generic agent.
-Opt-in `/rite-build --parallel N` fans out only under [`parallel-batch.md`](parallel-batch.md).
+Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
+claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
+`devrites-engine claim check --session <id> <task-paths>` — a held claim from a
+live foreign session releases the retained claim and stops the dispatch, per
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+for the exact writer in fresh context and wait. Track it through the
+launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
+<slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and
+`return` on completion (auto-records dispatch/return metrics). Use
+at most one writer across all linked worktrees for this workspace. Never run two
+writers in one worktree, run isolated and same-worktree writers concurrently, or
+substitute a generic agent. Opt-in `/rite-build --parallel N` fans out only under
+[`parallel-batch.md`](parallel-batch.md).
+
+After `claim add`, every terminal path releases the claim with
+`devrites-engine claim release --session <id> --id <claim-id>`: successful
+return, rejected result, gap, stop, or launch failure. TTL is crash recovery,
+not normal cleanup.
 
 ## Inspect and prove
 
 1. Compare the returned file list and `git diff --name-only` with task paths.
+   `devrites-engine check diff-scope <slug> --allow <task-paths>` is the
+   mechanical subset gate — run it before any reviewer dispatch; a violation
+   restores through the bounded wright without spending review.
    Reject a result that omits any required key — the bookkeeping arrays count
-   whether empty or filled — or adds a path. Restore only through the same bounded
-   wright; root never widens scope or edits source.
+   whether empty or filled — or adds a path. Root never widens scope or edits
+   source.
 2. Inspect the test diff for deletion, skipping, focus markers, or loosened
    assertions. Dedicated test analysis treats weakening as Critical.
    Confirm a test for a data/integration/topology risk can actually exhibit that risk;

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

@@ -5,6 +5,10 @@ argument-hint: "[feature-slug]"
 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.
+
+
 # /rite-clarify: resolve product decisions
 
 Run this required pass between spec and strategy. If the spec covers every material

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

@@ -5,6 +5,10 @@ argument-hint: "[feature-slug]"
 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.
+
+
 # /rite-converge: compare live code with intent
 
 Read `spec.md`, `plan.md`, and `tasks.md` as the **sole source of intent** (with
@@ -89,7 +93,13 @@ Pull on demand:
    acceptance criterion / scenario, every plan touch-point, and every existing slice's stated
    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, await their dossiers, then reconcile the cited facts in the root
+   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
+   [`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
    context. **Completion:** every inventory unit is classified once with live-code evidence.
 5. **Enqueue the remainder as new slices.** For each *partial* or *absent* unit, append a
    `## SLICE-###` (continue the numbering after the highest existing id), each with a `Satisfies:` line tracing to the AC/REQ it closes and a
@@ -102,7 +112,9 @@ Pull on demand:
    update `state.md` to `Phase: plan`, `Next step: /rite-vet`, and set an existing
    `eng-review.md` field to `Implementation readiness: NEEDS REPLAN`. When nothing was unmet,
    leave the plan/vet verdict untouched and set `Next step: /rite-prove`. Append
-   `decisions.md` for any material call.
+   `decisions.md` for any material call. When slices were appended, run
+   `devrites-engine check task-graph <slug>` before invoking Vet; failure stays in
+   Converge for correction and never spends a Vet reviewer context.
 7. **STOP.** Report units assessed, built / partial / absent counts, slices appended, and any
    principle violation found. A direct invocation that appended slices becomes
    the caller for the mandated next step: save a return cursor