devrites 2.4.0 → 2.5.1

package/CHANGELOG.md

@@ -2,11 +2,31 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
-## [2.4.0](https://github.com/ViktorsBaikers/DevRites/compare/v2.3.0...v2.4.0) (2026-06-27)
+## [2.5.1](https://github.com/ViktorsBaikers/DevRites/compare/v2.5.0...v2.5.1) (2026-06-28)
+
+### Fixed
+
+* **rite:** ask HITL build gaps inline instead of deferring to resolve ([33266f1](https://github.com/ViktorsBaikers/DevRites/commit/33266f19d9ad30f53fc8ef267f486a5562be61c7))
+
+## [2.5.0](https://github.com/ViktorsBaikers/DevRites/compare/v2.4.0...v2.5.0) (2026-06-28)
+
+### Added
+
+* **installer:** prune files dropped from the pack on update ([830352a](https://github.com/ViktorsBaikers/DevRites/commit/830352ae19b2726cadd627ab7ca4f12b1b85c7fc))
+
+### Fixed
+
+* **devrites:** close skill-pack SSOT drift + consolidate review dispatch ([649db40](https://github.com/ViktorsBaikers/DevRites/commit/649db4040a120d04c35e91b8f69d51f610df9a5f))
+
+## [2.4.0](https://github.com/ViktorsBaikers/DevRites/compare/v2.3.0...v2.4.0) (2026-06-28)
 
 ### Added
 
-* **devrites:** enforce the doubt gate from invocation through seal ([0397cca](https://github.com/ViktorsBaikers/DevRites/commit/0397cca2158ed1e798c29122485d4e2b69ea4f80))
+* **devrites:** enforce the doubt gate from invocation through seal ([6ff29d0](https://github.com/ViktorsBaikers/DevRites/commit/6ff29d0caa3384d6ba85f480369d0fb01d80fad1))
+
+### Fixed
+
+* **devrites:** calibrate doubt-coverage and close per-slice skip ([5bc09eb](https://github.com/ViktorsBaikers/DevRites/commit/5bc09eb94062f728bd855a2a581784e4e1197522))
 
 ## [2.3.0](https://github.com/ViktorsBaikers/DevRites/compare/v2.2.0...v2.3.0) (2026-06-23)
 

package/README.md

@@ -101,7 +101,7 @@ Full diagram set (lifecycle, polish orchestrator, review fan-out, debug loop,
 rules carrier, workspace state, namespace map) →
 [`docs/flow.md`](docs/flow.md).
 
-**Status:** [`v2.4.0`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v2.4.0) — see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v2.5.1`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v2.5.1) — see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 ## Contents
 

package/install.sh

@@ -162,7 +162,7 @@ mkdir -p "$TMP_GEN_DIR"
 cleanup() { rm -f "$MANIFEST_TMP"; rm -rf "$TMP_GEN_DIR"; }
 trap cleanup EXIT
 
-N_INSTALL=0; N_OVERWRITE=0; N_SKIP=0
+N_INSTALL=0; N_OVERWRITE=0; N_SKIP=0; N_PRUNE=0
 
 # install_file SRC RELDEST — copy one file, honoring conflict + manifest rules.
 install_file() {
@@ -325,6 +325,35 @@ case "$ALIAS_MODE" in
 esac
 DR_INSTALL_FLAGS="$(printf '%s' "$DR_INSTALL_FLAGS" | sed 's/^ //')"
 
+# ---- prune files dropped since the previous install ----------------------
+# install_file only adds/overwrites; a file the prior manifest tracked but the
+# current pack no longer ships would orphan on an in-place update (the path
+# update.sh takes: download release → re-run install.sh --force). Remove
+# exactly those: managed paths only (listed in the OLD manifest, absent from the
+# new one), never unmanaged user files and never .devrites/ runtime state.
+if [ -f "$PREV_MANIFEST" ]; then
+  while IFS= read -r _rel; do
+    case "$_rel" in ''|\#*) continue ;; esac           # skip comments + blank lines
+    case "$_rel" in .devrites/*) continue ;; esac       # never touch runtime state
+    grep -Fxq -- "$_rel" "$MANIFEST_TMP" && continue    # still shipped → keep
+    _dead="$TARGET/$_rel"
+    [ -e "$_dead" ] || continue                         # already gone
+    if [ "$DRYRUN" -eq 1 ]; then
+      dr_say "  [prune] $_rel ${DR_Y}(dropped from pack)${DR_R}"
+    else
+      rm -f "$_dead"
+      # tidy now-empty parent dirs, bounded strictly below .claude/
+      _d="$(dirname "$_dead")"
+      while [ "$_d" != "$TARGET/.claude" ] && [ "$_d" != "$TARGET" ] && [ "$_d" != "/" ]; do
+        rmdir "$_d" 2>/dev/null || break
+        _d="$(dirname "$_d")"
+      done
+      dr_say "  [prune] $_rel"
+    fi
+    N_PRUNE=$((N_PRUNE+1))
+  done < "$PREV_MANIFEST"
+fi
+
 # ---- write manifest ------------------------------------------------------
 if [ "$DRYRUN" -eq 0 ]; then
   mkdir -p "$TARGET/.claude"
@@ -340,7 +369,7 @@ fi
 # ---- summary -------------------------------------------------------------
 dr_say ""
 dr_ok "DevRites $([ "$DRYRUN" -eq 1 ] && echo 'plan complete (dry run)' || echo installed)"
-dr_say "  installed: $N_INSTALL   overwritten: $N_OVERWRITE   skipped(conflict): $N_SKIP"
+dr_say "  installed: $N_INSTALL   overwritten: $N_OVERWRITE   skipped(conflict): $N_SKIP   pruned: $N_PRUNE"
 dr_say ""
 dr_say "${DR_B}Commands:${DR_R} /rite  /rite-spec  /rite-define  /rite-plan  /rite-build  /rite-prove  /rite-polish  /rite-review  /rite-seal  /rite-status"
 dr_say "${DR_B}Utilities:${DR_R} /rite-pressure-test  /rite-zoom-out  /rite-prototype  /rite-handoff"

package/pack/.claude/agents/devrites-security-auditor.md

@@ -20,16 +20,12 @@ Workspace `.devrites/work/<slug>/`: read `spec.md` (data model / API / affected
 `decisions.md`, `touched-files.md`. Run `git diff` and read the touched files.
 
 ## Audit (feature scope, OWASP-oriented)
-- **Injection** — parameterized queries; no string-built SQL/shell/HTML; output encoding.
-- **Access control** — server-side authz on every sensitive action; no trusting
-  client-supplied IDs/roles; no IDOR.
-- **Auth / session / secrets** — secure handling; nothing sensitive in code, logs, or
-  responses.
-- **Sensitive data** — least exposure; encryption where required; PII not logged.
-- **SSRF / outbound** — URL allowlist/validation; timeouts; no untrusted reflection.
-- **Misconfiguration** — safe defaults, debug off, CORS scoped, headers per project.
-- **Dependencies** — new/updated packages free of known-vuln versions.
-- **Deserialization** of untrusted data.
+Walk the **single-sourced OWASP-web checklist** — injection, access control / IDOR, auth /
+session / secrets, sensitive-data exposure, SSRF / outbound, misconfiguration, vulnerable
+dependencies, unsafe deserialization — in
+[`../skills/rite-review/reference/security-review.md`](../skills/rite-review/reference/security-review.md).
+Apply each against the diff adversarially; the checklist is the *what*, this agent is the
+independent *who*.
 
 ## AI / LLM surface (only when the feature calls a model / builds an agent / does RAG / exposes tool-use)
 Apply the OWASP LLM Top 10 (`.claude/rules/security.md` § AI / LLM features):

package/pack/.claude/rules/agents.md

@@ -90,8 +90,9 @@ The prefix mirrors visibility:
   names (`prototype`, `handoff`, `diagnose`, etc.) — peer skill packs may
   collide on the bare names internally even though these never appear in the
   user's slash menu. Parallel reviewer fan-out at `/rite-seal` is no longer
-  a skill — it lives as a reference file
-  (`.claude/skills/rite-seal/reference/parallel-dispatch.md`).
+  a skill — it lives as a shared reference file
+  (`.claude/skills/devrites-lib/reference/parallel-dispatch.md`), pointed at by both
+  `/rite-review` and `/rite-seal`.
 
 The `/rite` menu carries the routing previously held by `devrites-selector`, which
 has been removed. `user-invocable:` in each `SKILL.md` is the source of truth; the

package/pack/.claude/rules/core.md

@@ -1,7 +1,7 @@
 # DevRites core rules — always-on
 
 The minimal always-on subset of the DevRites engineering rules. DevRites
-`rite-*` skills Read `.claude/rules/core.md` as their first step; the other 20
+`rite-*` skills Read `.claude/rules/core.md` as their first step; the other 22
 rule files in this directory load on demand by the phase that needs them (see
 `README.md` for the index).
 

package/pack/.claude/rules/prose-style.md

@@ -31,7 +31,7 @@ means killing filler; in technical writing it means keeping the precise list.
 | False binary contrast — "It's not X, it's Y", "The question isn't X. It's Y", "not just X but Y" | State Y directly. Drop the negation. |
 | Fake profundity — "Let that sink in", "This is the deepest problem", "make no mistake" | Show the thing; trust the reader to weigh it. |
 | Vague declaratives — "The implications are significant", "the reasons are structural" | Name the specific implication or reason. |
-| Marketing adjectives on code/work — "robust", "scalable", "seamless", "production-ready", "comprehensive solution" | Say what it does and what proves it. |
+| Marketing adjectives *selling* the work — "a robust, scalable, seamless, production-ready solution" | Say what it does and what proves it. (Calibrated: "robust" / "scalable" / "comprehensive" are legitimate in a *precise technical claim* — "robust to a dropped connection, see `evidence.md`" — only slop when they sell. The canonical word-by-word tiering is `devrites-prose-craft/reference/banned-phrases.md` § AI vocabulary.) |
 | Hedging stacks — "it's important to note that, generally, in most cases" | Make the claim, or cut it. |
 | False agency — "the data tells us", "the complaint becomes a fix", "the decision emerges" | Name who did it. "The grader reads X and returns Y." |
 | Meta-narration — "In this section we'll…", "Let me walk you through…", "as we'll see" | Let the text move; delete the announcement. |

package/pack/.claude/skills/devrites-api-interface/SKILL.md

@@ -35,11 +35,10 @@ contract. Neither side blocks on the other.
 
 ## Doubt the contract
 Before standing the interface, run `devrites-doubt` — boundary decisions are exactly the
-non-trivial kind worth an adversarial check. Record the contract + rationale in
-`decisions.md`.
+non-trivial kind worth an adversarial check.
 
-## Gotchas
-- Be conservative — you can add to a contract later, but removing or changing a field breaks every consumer.
-- Validate at the boundary; never trust caller-supplied IDs, roles, or prices.
-- A breaking change to an existing consumer is a user decision (and a `drift.md` event if unplanned), not a silent edit.
-- Match the project's existing endpoint/module conventions; a competing convention is a tax, not a design.
+## Done when
+The contract is complete only when **every** field carries a type + optionality + unit,
+**every** success and error status code is enumerated with its error-body shape, the
+`devrites-doubt` verdict is accept, and the contract + rationale are recorded in
+`decisions.md`. A contract that pins only the happy-path shape is not done.

package/pack/.claude/skills/devrites-audit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-audit
-description: Read-only audit dispatch for the active feature on the requested axis — security (OWASP, trust boundary, secrets), perf (measure-first, N+1, CWV), or simplify (Chesterton's Fence, deletion test). Use when the user says "security review", "is this safe", "is this fast enough", "perf check", "N+1", "simplify this", "Chesterton's Fence". Not for write actions or whole-project audits.
+description: Audit the active feature read-only on one axis — security (OWASP, trust boundary, secrets), perf (measure-first, N+1, CWV), or simplify (Chesterton's Fence, deletion test). Use when the user says "security review", "perf check", or "simplify this". Not for write actions or whole-project audits.
 argument-hint: "<security | perf | simplify>"
 user-invocable: false
 ---
@@ -52,7 +52,7 @@ reconciles.
 
 Rules for the dispatch:
 
-- **One subagent per call.** This skill is not a fan-out; multi-axis fan-out is `/rite-seal`'s job (see `.claude/skills/rite-seal/reference/parallel-dispatch.md`).
+- **One subagent per call.** This skill is not a fan-out; multi-axis fan-out is `/rite-seal`'s job (see `.claude/skills/devrites-lib/reference/parallel-dispatch.md`).
 - **No author context.** Do not pass the caller's analysis or framing of the change to the subagent — fresh, adversarial read is the point.
 - **No cross-pollination.** If the caller wants more than one axis, dispatch each axis in its own `Task` call in a single message so the runtime parallelizes; each subagent gets only its own brief.
 

package/pack/.claude/skills/devrites-browser-proof/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-browser-proof
-description: Prove UI behavior via the browser-proof ladder — browser-harness → Chrome DevTools MCP → `/run`+`/verify` → project E2E → manual — recording routes, viewports, screenshots, console, network, interactions, design-reference match to `browser-evidence.md`. Use when the user says "check the UI in browser", "screenshot this", "prove it renders". Not for backend-only features.
+description: Prove UI behavior in a real browser, capturing screenshots, console, network, interactions, and Core Web Vitals to `browser-evidence.md`. Use when the user says "check the UI in browser", "screenshot this", "prove it renders", or a Core Web Vital / perf budget needs measuring. Not for backend-only features.
 user-invocable: false
 ---
 
@@ -46,7 +46,7 @@ reads it in Measured mode) and note the tool + route in `browser-evidence.md`. N
 a lab value as a field value or vice versa.
 
 ## Evidence schema → `browser-evidence.md`
-Tooling used · route(s) · viewports (375/768/1280) · screenshot paths **opened and
+Tooling used · route(s) · viewports (320/768/1024/1440 — the canonical responsive set; see [`devrites-frontend-craft/reference/quality-standards.md`](../devrites-frontend-craft/reference/quality-standards.md)) · screenshot paths **opened and
 described** · console errors/warnings · network failures · interaction path tested ·
 accessibility basics · responsive checks · **CWV capture** (tool + route + each
 source-labeled value, or `pending (manual)` + the command) · **Visual Verdict** (the
@@ -67,7 +67,7 @@ error / success / disabled / long-content), plus key **design-reference** diffs
 not the markup:
 
 ```markdown
-## Visual Verdict — <route / component>   (viewport: 375 / 1280)
+## Visual Verdict — <route / component>   (viewport: 320 / 1440)
 | Criterion (source) | Expected | Observed (screenshot) | Verdict | Severity |
 |---|---|---|---|---|
 | empty state (brief) | welcoming copy + primary action | renders, copy present | PASS | — |

package/pack/.claude/skills/devrites-debug-recovery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-debug-recovery
-description: Debug systematically when tests, builds, or runtime/browser checks fail — deterministic feedback loop, reproduce, 3-5 ranked hypotheses, instrument, fix root cause, regression-test. Use when the user says "debug this", "why is it failing", "it broke", "the build is red", "the tests fail". Not for code review or flaky tests (fix the flake first).
+description: Debug systematically when tests, builds, or runtime/browser checks fail — reproduce, rank hypotheses, fix the root cause, regression-test. Use when the user says "debug this", "the build is red", or "the tests fail". Not for code review or flaky tests (fix the flake first).
 user-invocable: false
 ---
 

package/pack/.claude/skills/devrites-doubt/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-doubt
-description: Stress-test a single non-trivial decision via CLAIM → EXTRACT → DOUBT → RECONCILE → STOP with `devrites-doubt-reviewer` for an independent take. Use when the user says "are we sure", "double-check this", "what could go wrong", or a boundary / data-model / auth / public-API / migration change is about to commit. Not for post-merge review or trivial choices.
+description: Stress-test a single non-trivial decision with an adversarial `devrites-doubt-reviewer` for an independent take. Use when the user says "are we sure", "double-check this", "what could go wrong", or a boundary / data-model / auth / public-API / migration change is about to commit. Not for post-merge review or trivial choices.
 user-invocable: false
 ---
 

package/pack/.claude/skills/devrites-frontend-craft/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-frontend-craft
-description: Implement frontend at senior designer-engineer quality — every state covered, anti-AI-slop, WCAG 2.2 AA. Use when the user says "build the UI", "ship-quality frontend", "design system", "a11y", or `/rite-build` detects UI. Not for polishing a built feature or design exploration.
+description: Implement frontend at senior designer-engineer quality — every state covered, anti-AI-slop, WCAG 2.2 AA. Use when the user says "build the UI", "design system", "a11y", or `/rite-build` detects UI. Not for polishing a built feature or design exploration.
 user-invocable: false
 ---
 

package/pack/.claude/skills/devrites-frontend-craft/reference/shape.md

@@ -25,7 +25,7 @@ brief inline.
    - success
    - disabled / read-only / no-permission
    - long content / overflow / many items
-5. **Responsive** — how it reflows from small (375) to large (1280). What collapses,
+5. **Responsive** — how it reflows from small (320) to large (1440). What collapses,
    stacks, hides, or scrolls.
 6. **Accessibility** — focus order, labels, contrast, keyboard operability, semantics.
 7. **Interaction model** — what's inline vs. navigated vs. (rarely) a modal; optimistic

package/pack/.claude/skills/devrites-interview/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-interview
-description: One-question-at-a-time interview to extract what the user wants — each question carries a best-guess + structured options; stop at ~95% confidence. Use when the user says "interview me", "grill me", "I'm not sure what I want", or `/rite-spec` / `/rite-define` flags the ask as underspecified. Not for casual clarification or ideation (use `rite-pressure-test`).
+description: Interview the user one question at a time to extract what they want. Use when the user says "interview me", "I'm not sure what I want", or `/rite-spec` / `/rite-define` flags the ask as underspecified. Not for casual clarification or ideation (use `/rite-pressure-test`).
 user-invocable: false
 ---
 

package/pack/.claude/skills/{rite-seal → devrites-lib}/reference/parallel-dispatch.md

@@ -1,17 +1,26 @@
 # Parallel review dispatch
 
-How `/rite-review` and `/rite-seal` fan out the fresh-context review subagents under `.claude/agents/`. Loaded on demand by the calling skill — not a skill itself.
+How `/rite-review` and `/rite-seal` fan out the fresh-context review subagents under
+`.claude/agents/`. The **single source** for the dispatch + reconciliation contract — loaded on
+demand by the calling skill (each points here); not a skill itself.
 
-DevRites ships ten fresh-context review subagents under `.claude/agents/` (plus the write-capable `devrites-slice-wright`, which is not a reviewer). Eight are post-build reviewers used at the seal / multi-axis review; the other two are gate-specific and *not* part of the seal fan-out — `devrites-strategy-reviewer` is **pre-plan** (it judges the spec for `/rite-temper`) and `devrites-plan-reviewer` is **pre-build** (it judges the plan for `/rite-vet`). The seal and the multi-axis review need most of the post-build reviewers running **at the same time**, on the same workspace + diff, so the verdicts don't contaminate each other.
+DevRites ships ten fresh-context review subagents under `.claude/agents/` (plus the
+write-capable `devrites-slice-wright`, which is not a reviewer). Eight are post-build reviewers
+used at the seal / multi-axis review; the other two are gate-specific and *not* part of this
+fan-out — `devrites-strategy-reviewer` is **pre-plan** (it judges the spec for `/rite-temper`)
+and `devrites-plan-reviewer` is **pre-build** (it judges the plan for `/rite-vet`). The seal and
+the multi-axis review need most of the post-build reviewers running **at the same time**, on the
+same workspace + diff, so the verdicts don't contaminate each other.
 
-Pattern: delegate to specialized agents with isolated context, brief each one precisely, run them concurrently, reconcile on return.
+Pattern: delegate to specialized agents with isolated context, brief each one precisely, run
+them concurrently, reconcile on return.
 
 ## When to use which subagent
 
 | Subagent | Always | Conditional |
 |---|---|---|
 | `devrites-spec-reviewer` | `/rite-review` Spec axis; `/rite-seal` | — |
-| `devrites-code-reviewer` | `/rite-review` Standards axis; `/rite-seal` | — |
+| `devrites-code-reviewer` | `/rite-review` Code-review axis; `/rite-seal` | — |
 | `devrites-test-analyst` | `/rite-seal` | — |
 | `devrites-frontend-reviewer` | — | UI files in the diff |
 | `devrites-security-auditor` | — | input / auth / data / external integrations / secrets in scope |
@@ -19,6 +28,9 @@ Pattern: delegate to specialized agents with isolated context, brief each one pr
 | `devrites-doubt-reviewer` | — | a non-trivial decision is being stood up (called from `devrites-doubt`) |
 | `devrites-simplifier-reviewer` | — | `/rite-polish` Phase 1 audit (called from `devrites-audit simplify`) |
 
+One entity, one name: the `devrites-code-reviewer`'s axis is the **Code-review axis** everywhere
+(at both `/rite-review` and `/rite-seal`) — don't rename it per caller.
+
 ## Dispatch shape
 
 For each chosen subagent, the caller uses the `Task` tool with this prompt shape:
@@ -58,12 +70,12 @@ Rules:
 
 When the subagents return:
 
-1. **Quote verbatim.** Place each subagent's findings under its own `## <axis>` heading in `review.md` / `seal.md`. Do not merge, re-rank, or summarize.
-2. **Surface contradictions explicitly.** "Spec axis says complete, Standards axis says untestable" is a finding, not noise. The caller decides at the gate.
+1. **Quote verbatim.** Place each subagent's findings under its own `## <axis>` heading in `review.md` / `seal.md`. Do not merge, re-rank, or summarize. `devrites-code-reviewer` runs its **full** documented discipline (tests-first, correctness, readability, architecture, maintainability, standards); the inline lead **reconciles** the returned reports — it does not re-run those same axes itself.
+2. **Surface contradictions explicitly.** "Spec axis says complete, Code-review axis says untestable" is a finding, not noise. The caller decides at the gate.
 3. **Severity is the gate, not a score.** Sum the labels (`Critical / Important / Suggestion / Nit / FYI`) and apply the caller's gate (`/rite-seal` blocks on `Critical == 0`; `/rite-review` reports counts).
 4. **One scale.** All subagents use the same five-label scale (Critical / Important / Suggestion / Nit / FYI). Reject any subagent output that invents its own. **Exception:** `devrites-simplifier-reviewer` deliberately emits only Suggestion / Nit / FYI (it is non-blocking by design) — that is a valid subset of the scale, not an invented one; do not reject it during reconciliation.
 5. **Consensus roll-up (after the verbatim per-axis record).** Keep every axis's findings verbatim under its `## <axis>` heading (above), then add one deduped roll-up the gate reads: where **≥2 axes flag the same `file:line`**, raise it to the top and mark it *consensus* — independent corroboration raises confidence. A lone low-confidence finding with no `file:line` or evidence anchor drops out of the roll-up (it stays in its per-axis section). The roll-up reduces noise without hiding any axis — the verbatim sections are the audit trail; the roll-up is the actionable summary the gate acts on.
 
 ## Fallback
 
-If the `Task` tool is unavailable in the current environment, the caller runs the relevant subagent discipline **inline** in its own context and flags the result as a fallback (not an independent review). The seal weighs the fallback differently — see [`./risk-and-rollback.md`](./risk-and-rollback.md).
+If the `Task` tool is unavailable in the current environment, the caller runs the relevant subagent discipline **inline** in its own context and flags the result as a fallback (not an independent review). The seal weighs the fallback differently — see [`../../rite-seal/reference/risk-and-rollback.md`](../../rite-seal/reference/risk-and-rollback.md).

package/pack/.claude/skills/devrites-lib/scripts/doubt-coverage.sh

@@ -1,25 +1,47 @@
 #!/usr/bin/env bash
 # doubt-coverage.sh — did the build doubt the decisions it stood?
-# Deterministic, zero-token. Reads the append-only footprint log the orchestrator writes at
-# /rite-build step 4 (one `doubt` line per devrites-doubt dispatch) and reports doubt coverage
-# against wright dispatches. It CANNOT prove a 1:1 verdict-per-decision match — `Decisions stood`
-# is not a structured ledger — so it proves the cheap, unambiguous half: a feature that ran the
-# wright but never once doubted a decision. The seal's prose gate (step 4a) + the reviewer fan-out
-# judge severity against decisions.md.
+# Deterministic, zero-token. Two checks, both sourced from records /rite-build writes:
+#   1. decisions.md `## Decisions stood` — each stood decision ends `— doubt: <verdict>`; a
+#      `doubt: MISSING` token means the decision was recorded but never doubted (the unambiguous
+#      skip — caught even when only some slices skipped doubt).
+#   2. footprint.log — `doubt` lines vs `wright` lines; zero doubt across any wright run is the
+#      coarse "no doubt ran at all" signal the seal then verifies against decisions.md.
+# It cannot prove a 1:1 verdict-per-decision match beyond what the build recorded — the seal's
+# prose gate (step 4a) + the reviewer fan-out judge the rest.
 #
 #   doubt-coverage.sh <slug>
 #
-# Exit: 0 = doubt dispatches present, or nothing to assess (no log / no wright) → pass.
-#       1 = wright dispatch(es) logged but ZERO doubt dispatches → coverage gap. The seal treats
-#           it as a finding (Important; NO-GO when decisions.md records an irreversible-risk
-#           decision — auth / public-API / migration — with no verdict).
+# Exit: 0 = doubt covered, or not assessable (no log / no wright / inline build) → pass.
+#       1 = footprint shows wright dispatch(es) but ZERO doubt → no doubt ran at all; a prompt to
+#           VERIFY against decisions.md (every-slice-trivial passes; a skipped decision is a finding).
 #       2 = usage.
+#       3 = decisions.md records a stood decision with `doubt: MISSING` → doubt was definitively
+#           skipped for a decision on record. The seal treats it as a finding.
 set -u
 
 slug="${1:-}"
 [ -n "$slug" ] || { echo "usage: doubt-coverage.sh <slug>" >&2; exit 2; }
 
-log=".devrites/work/$slug/footprint.log"
+dir=".devrites/work/$slug"
+log="$dir/footprint.log"
+dec="$dir/decisions.md"
+
+# A recorded stood decision that was never doubted is the unambiguous failure — check it first,
+# and on every path (it survives the inline-build case below, where the footprint heuristic can't).
+if [ -f "$dec" ] && grep -q 'doubt: MISSING' "$dec"; then
+  echo "doubt-coverage: SKIPPED — a '## Decisions stood' entry in decisions.md has doubt: MISSING."
+  echo "A decision was stood and recorded but never doubted. Re-dispatch doubt or escalate."
+  exit 3
+fi
+
+# Inline build (Task tool unavailable): the wright + doubt ran in-context, dispatching nothing,
+# so the footprint heuristic does not apply — the decisions.md check above is the assessment.
+if [ -f "$dir/.reconcile-inline" ]; then
+  echo "doubt-coverage: inline build (.reconcile-inline) — footprint heuristic n/a; no MISSING"
+  echo "verdict recorded. Verify by hand that each stood decision carries a devrites-doubt verdict."
+  exit 0
+fi
+
 if [ ! -f "$log" ]; then
   echo "doubt-coverage: no footprint log — nothing to assess (pass)"
   exit 0
@@ -27,13 +49,11 @@ fi
 
 w=$(awk '$2=="wright"{n++} END{print n+0}' "$log")
 d=$(awk '$2=="doubt"{n++}  END{print n+0}' "$log")
-
 echo "doubt-coverage: $w wright · $d doubt"
 
 if [ "$w" -gt 0 ] && [ "$d" -eq 0 ]; then
-  echo "doubt-coverage: GAP — $w wright dispatch(es), 0 doubt dispatches. Either every slice's"
-  echo "'Decisions stood' was genuinely empty, or step-4 doubt was skipped. Confirm against"
-  echo "decisions.md before GO."
+  echo "doubt-coverage: no doubt dispatched across $w wright run(s). Either every slice's"
+  echo "'Decisions stood' was genuinely empty, or doubt was skipped — verify against decisions.md."
   exit 1
 fi
 exit 0

package/pack/.claude/skills/devrites-lib/scripts/rites.sh

@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+# rites.sh — locate and run a devrites-lib helper by name, across install layouts.
+#
+# Usage: rites.sh <name> [args...]
+#   <name> = helper basename without extension (preamble, readiness, reconcile,
+#            stuck, footprint, test-integrity, progress, conventions, tick-afk, ...).
+#
+# Runs <this-dir>/<name>.sh — or <name>.py via python3 — propagating its exit code
+# unchanged, so callers that read `$?` (readiness/reconcile/test-integrity/tick-afk)
+# keep working. A missing helper, or a .py helper with no python3, prints a degraded
+# note to stderr and exits 0 (degraded-but-continue, the same standing as the inline
+# `|| echo "(... unavailable)"` fallback this replaces).
+#
+# This is the single home for the three-layout script-resolution dance; callers only
+# locate THIS script (one target) and name the helper they want.
+set -u
+
+dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" 2>/dev/null && pwd)" || dir="."
+name="${1:-}"
+if [ -z "$name" ]; then
+  echo "rites: usage: rites.sh <name> [args...]" >&2
+  exit 2
+fi
+shift
+
+sh="$dir/$name.sh"
+py="$dir/$name.py"
+
+if [ -f "$sh" ]; then
+  exec bash "$sh" "$@"
+fi
+if [ -f "$py" ]; then
+  if command -v python3 >/dev/null 2>&1; then
+    exec python3 "$py" "$@"
+  fi
+  echo "(devrites helper '$name' needs python3 — skipped)" >&2
+  exit 0
+fi
+
+echo "(devrites helper '$name' unavailable on this install)" >&2
+exit 0

package/pack/.claude/skills/devrites-prose-craft/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-prose-craft
-description: Write the artifacts and chat replies a senior engineer would — direct, specific, human voice — not the default LLM tells (filler openers, false contrasts, fake profundity, em-dash tics, hedging). Use when a DevRites phase writes prose (spec.md, plan.md, decisions.md, review.md, seal.md, commit/PR bodies) or composes a user-facing reply, and as the catch pass in /rite-polish. Calibrated for technical writing — keeps precise lists, exact terms, and spec structure. Not for code comments and naming (the build-time anti-slop charter covers those) or UI craft (use devrites-frontend-craft).
+description: Write the artifacts and chat replies a senior engineer would — direct, specific, human voice, with the default LLM tells stripped. Use when a DevRites phase writes prose (spec.md, plan.md, decisions.md, review.md, seal.md, commit/PR bodies) or a user-facing reply, and as the catch pass in /rite-polish. Not for code comments and naming (the build-time anti-slop charter covers those) or UI craft (use devrites-frontend-craft).
 user-invocable: false
 ---
 

package/pack/.claude/skills/devrites-refresh-indexes/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-refresh-indexes
-description: Keep the optional code-intelligence indexes — codebase-memory-mcp, codegraph, graphify — current after code changes so the next structural lookup reads live code, not a stale graph. Use when the index looks stale (a structural lookup disagrees with the live code), after a large change before a structural query, or the user says "reindex" / "the graph is stale" / "refresh the index". The Stop hook does this automatically; this skill is the manual force + the reference for it. Not for agentmemory (a separate, judgment-based store).
+description: Keep the optional code-intelligence indexes — codebase-memory-mcp, codegraph, graphify — current after code changes so the next structural lookup reads live code. Use when a structural lookup disagrees with the live code, after a large change before a structural query, or the user says "reindex". The Stop hook does this automatically; this skill is the manual force + the reference for it. Not for agentmemory (a separate, judgment-based store).
 user-invocable: false
 ---
 

package/pack/.claude/skills/devrites-source-driven/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-source-driven
-description: Verify uncertain framework or library behavior against official docs or installed source before relying on it, then record the source in `evidence.md` / `decisions.md`. Use when the user says "check the docs", "is this still the API", "don't guess", "cite the source", "verify this assumption", or build encounters an unfamiliar framework call. Not for project-internal code or trivial stdlib calls.
+description: Verify uncertain framework or library behavior against official docs or installed source before relying on it, then record the source in `evidence.md` / `decisions.md`. Use when the user says "check the docs", "verify this assumption", or build hits an unfamiliar framework call. Not for project-internal code or trivial stdlib calls.
 user-invocable: false
 ---
 

package/pack/.claude/skills/devrites-ux-shape/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: devrites-ux-shape
-description: Plan the UX/UI before any code — produce the feature-level `design-brief.md` (design direction, key states, interaction model, visual-direction probe) the build then targets. Use when `/rite-spec` detects UI, or the user says "shape the UX", "plan the UI before coding", "design direction", "what should this look like", or a UI feature needs its look & flow decided up front. Woven into spec/build, not a separate phase. Not for building (use `devrites-frontend-craft`), polishing a built UI (use `/rite-polish`), or throwaway exploration (use `/rite-prototype`).
+description: Plan the UX/UI before any code — produce the feature-level `design-brief.md` the build then targets. Use when `/rite-spec` detects UI, or the user says "shape the UX" or "plan the UI before coding". Not for building (use `devrites-frontend-craft`), polishing a built UI (use `/rite-polish`), or throwaway exploration (use `/rite-prototype`).
 user-invocable: false
 ---
 

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

@@ -40,6 +40,7 @@ F=.claude/skills/rite-$V/SKILL.md
 | `ship` | `/rite-ship` | type-GO + commit/push/tag, then archive the task |
 | `status [slug]` | `/rite-status` | active feature, next action, evidence |
 | `doctor` | `/rite-doctor` | health check — install integrity, stale ACTIVE, orphaned gates, hook wiring |
+| `learn [--mine \| "<lesson>"]` | `/rite-learn` | review the captured learning ledger → promote recurring lessons to project rules / principles |
 | `use <slug>` | (inline) | switch the active feature — re-point `.devrites/ACTIVE` |
 | `resolve <qid> "<answer>"` | `/rite-resolve` | answer a HITL gate |
 | `prototype [question]` | `/rite-prototype` | throwaway prototype |
@@ -62,8 +63,8 @@ Specialist triggers (model-invoked inside the above):
 `devrites-source-driven` (uncertain library) · `devrites-doubt` (non-trivial
 decision) · `devrites-api-interface` (cross-boundary) ·
 `devrites-audit <security|perf|simplify>` (single-axis review/polish pass) ·
-`devrites-debug-recovery` (failures). Parallel reviewer fan-out at seal lives
-inline in `/rite-seal` (see its `reference/parallel-dispatch.md`).
+`devrites-debug-recovery` (failures). Parallel reviewer fan-out at seal is a shared
+reference (see [`devrites-lib/reference/parallel-dispatch.md`](../devrites-lib/reference/parallel-dispatch.md)).
 
 ## What to output
 
@@ -96,6 +97,7 @@ SEAL          /rite seal               ≡    /rite-seal        final GO / NO-GO
 SHIP          /rite ship               ≡    /rite-ship        type-GO + commit/push/tag, then archive + clear ACTIVE
 STATUS        /rite status             ≡    /rite-status      active feature, next action, evidence, risks
 DOCTOR        /rite doctor             ≡    /rite-doctor      health check — install · stale ACTIVE · orphaned gates · hook wiring
+LEARN         /rite learn ...          ≡    /rite-learn       review captured lessons → promote to project rules / principles
 SWITCH        /rite use <slug>                                re-point .devrites/ACTIVE to another feature (inline)
 RESUME        /rite resolve ...        ≡    /rite-resolve     answer a HITL checkpoint
 AUTO          /rite autocomplete ...   ≡    /rite-autocomplete  run the whole lifecycle unattended (--ship to push)
@@ -110,26 +112,6 @@ UTILITY       /rite frame | prototype | handoff | zoom-out | pressure-test  (or
 
 ## Core operating rules (every DevRites skill enforces)
 
-The minimal version lives in `.claude/rules/core.md`; DevRites skills Read it as
-their first step, and the other rule files load on demand. The rule list:
-
-1. **Right step, right time** — smallest relevant workflow; don't load everything.
-2. **No silent assumptions** — surface material assumptions; ask when the
-   answer changes scope, architecture, data model, UX, security, migration
-   risk, or acceptance.
-3. **No guessing through confusion** — if requirements / code / tests / docs
-   conflict, stop, name the conflict, present options, wait for resolution
-   when the answer changes the product.
-4. **Spec is living, not sacred** — change spec/plan only through the
-   Spec Drift Guard; never code against a known-wrong plan.
-5. **One slice at a time** — `/rite-build` does one slice then stops.
-6. **Evidence over confidence** — tests, builds, runtime, screenshots beat
-   assertions; record commands and output.
-7. **Feature scope only** — review / simplify / polish / security stay within
-   the active feature and touched files.
-8. **Prefer existing conventions** — follow the project's architecture,
-   components, tokens, tests, and commands.
-9. **Verify uncertain facts at the source** — when framework / library
-   behaviour matters and isn't certain, check the docs or source and record it.
-
-Detail in [reference/menu.md](reference/menu.md) when needed.
+The operating rules live in `.claude/rules/core.md`; DevRites skills Read it as
+their first step, and the other rule files load on demand. See
+[`.claude/rules/README.md`](../../rules/README.md) for the full index.

package/pack/.claude/skills/rite/reference/menu.md

@@ -8,21 +8,28 @@ what each command does or how phases connect.
 | Phase | Command | Use when |
 |---|---|---|
 | Spec | `/rite-spec <feature>` | **Start here.** Investigate deeply → write spec.md. Asks you with options; gathers any design references you attach (optional). |
+| Adopt | `/rite-adopt` | Onboard an existing codebase instead of starting fresh — reverse-derive spec.md + seed the conventions ledger. |
 | Temper | `/rite-temper` | _Optional, before define._ Strategic review of the spec — scope mode (expand/selective/hold-rigor/reduce) + pre-mortem; hardens the spec. Best on big/risky features; mandatory in `/rite-autocomplete`. |
 | Plan | `/rite-define` | Turn the approved spec into plan + vertical task slices + state. |
+| Vet | `/rite-vet` | _Optional, before build._ Engineering review of the plan — scope · architecture · tests · perf; hardens the plan. Best on big/risky features; mandatory in `/rite-autocomplete`. |
 | Re-plan | `/rite-plan` | The active plan is too big, wrong, stale, ambiguous, or blocked. |
 | Build | `/rite-build` | Implement the next single vertical slice. Stops after one slice. |
 | Prove | `/rite-prove` | Prove the current scope: tests, build, runtime, browser evidence. |
 | Polish | `/rite-polish` | Code polish always; UI normalize + ship-quality polish if UI is in scope. Modes: `bolder/quieter/distill/harden/normalize-only`. |
 | Review | `/rite-review` | Feature-scoped review before sealing. |
-| Seal | `/rite-seal` | Final GO / NO-GO decision. |
+| Seal | `/rite-seal` | Final GO / NO-GO decision (no git). |
+| Ship | `/rite-ship` | Type-GO → commit/push/tag, then archive the task + clear ACTIVE. |
 | Status | `/rite-status` | See where the active feature stands. |
+| Doctor | `/rite-doctor` | Health check — install integrity, stale ACTIVE, orphaned gates, hook wiring. |
+| Learn | `/rite-learn` | Review the captured learning ledger → promote recurring lessons to project rules / principles. |
 
 ## Typical orderings
 
 - **Every feature**: `/rite-spec` (spec) → *(big feature? `/rite-temper` — strategic review)* →
-  `/rite-define` (plan) → `/rite-build` ×N (all slices) → `/rite-prove` (once all built) →
-  `/rite-polish` (always: code + UI if UI) → `/rite-review` → `/rite-seal`.
+  `/rite-define` (plan) → *(big feature? `/rite-vet` — engineering review)* →
+  `/rite-build` ×N (all slices) → `/rite-prove` (once all built) →
+  `/rite-polish` (always: code + UI if UI) → `/rite-review` → `/rite-seal` → `/rite-ship`.
+- **Existing codebase**: `/rite-adopt` (onboard → spec.md + conventions) → continue at `/rite-define`.
 - **Drift mid-build**: stop → drift question → `/rite-plan` (repair) → resume build.
 
 ## Rules this menu obeys

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

@@ -1,6 +1,6 @@
 ---
 name: rite-adopt
-description: Bring an EXISTING codebase under DevRites — reverse-derive a `spec.md` of current behavior, placement, and architecture, and seed the project conventions ledger from the idioms the code already follows, then hand off to the lifecycle. Use when the user says "adopt this project", "onboard this codebase", "we already have code", "bring this repo into DevRites", or "reverse-engineer a spec from the existing app". Not for a brand-new feature or idea (use `/rite-spec`), planning an approved spec (`/rite-define`), or just mapping unfamiliar code without onboarding it (`/rite-zoom-out`).
+description: Bring an EXISTING codebase under DevRites — reverse-derive a `spec.md` of current behavior, placement, and architecture, and seed the project conventions ledger from the idioms the code already follows, then hand off to the lifecycle. Use when the user says "adopt this project" or "reverse-engineer a spec from the existing app". Not for a brand-new feature or idea (use `/rite-spec`), planning an approved spec (`/rite-define`), or just mapping unfamiliar code without onboarding it (`/rite-zoom-out`).
 argument-hint: "[path or area to adopt] [+ what you want to build next]"
 user-invocable: true
 ---

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

@@ -1,6 +1,6 @@
 ---
 name: rite-autocomplete
-description: Run the entire DevRites lifecycle end-to-end with no per-phase human iteration — spec → temper → define → vet → build×N → prove → polish → review → seal → ship — picking the best option at each soft gate and recording why. A vague prompt triggers an up-front interview, then it runs unattended, pausing only on hard irreversible-risk / blocking / escalating gates or a NO-GO; `--ship` (alias `--yolo`) auto-confirms the final type-GO. Use when the user says "autocomplete", "do the whole thing", "run the full cycle", "one-shot this feature", or "ship it autonomously". Not for a single phase (use the specific `/rite-*` skill) or when the user wants to drive each step.
+description: Run the entire DevRites lifecycle end-to-end, unattended — no per-phase human iteration; `--ship` auto-confirms the final gate. Use when the user says "autocomplete", "one-shot this feature", or "ship it autonomously". Not for a single phase (use the specific `/rite-*` skill) or when the user wants to drive each step.
 argument-hint: "[idea] [--ship|--yolo] [--max-slices N]"
 user-invocable: true
 ---