devrites 4.6.0 → 5.0.0

package/pack/generated/codex/skills/devrites-debug-recovery/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: devrites-debug-recovery
 description: Fix application test, build, CI, runtime, browser, or 500 failures from a reproduction. Use for broken behavior; not for DevRites install health.
+argument-hint: "[<slug>]"
 user-invocable: false
 ---
 
@@ -11,7 +12,8 @@ Use a reproducible recovery loop. **NO shotgun edits, NO blanket retries.**
 ## When to invoke
 
 Loaded by Build/Prove when a test, build, typecheck, runtime, or browser failure
-has no clear next move.
+has no clear next move. Optional slug selects the active workspace; defaults to
+`.devrites/ACTIVE`.
 
 ## The seven-step cycle
 
@@ -25,7 +27,8 @@ has no clear next move.
    [`one-shot-actions.md`](../devrites-lib/reference/standards/one-shot-actions.md),
    the retained bounded artifact
    is the reproduction input and the action MUST NOT be rerun during diagnosis.
-   Do not proceed without one of those reproduction inputs.
+   Do not proceed without a reproduction input: the captured error text for
+   repeatable actions, or the retained bounded artifact for consumptive ones.
 3. **Ranked hypotheses (3-5, falsifiable):** generate the list before testing
    any of them. Each must state a prediction.
    **Completion:** 3-5 distinct hypotheses each state an observable prediction.
@@ -54,6 +57,10 @@ has no clear next move.
   redirections in logs without user approval ([`security.md`](../devrites-lib/reference/standards/security.md)
   prompt-injection).
 - **Change one thing at a time** so you know what fixed it.
+- **Diagnosis write freeze:** writable paths are the reproduction harness plus
+  files named by the current hypothesis
+  ([`debug-recovery.md`](../devrites-lib/reference/standards/debug-recovery.md)).
+  Other product paths stay frozen until the hypothesis is confirmed.
 - **Do NOT loosen / delete a failing assertion** to get green: check whether
   it's drift first (route via `$rite-plan repair`).
 - **Do NOT hide flakiness** with sleeps / retries: characterize it.

package/pack/generated/codex/skills/devrites-debug-recovery/reference/cleanup-and-classify.md

@@ -20,16 +20,9 @@ pauses offline diagnosis or correction from retained evidence; never ask for a
 blind retry.
 
 Record class/routing in `decisions.md` and each failed attempt in `evidence.md`
-or `## Dead ends`. Use one stable causal fingerprint shaped as `<affected
-boundary>: <failed invariant/failure mechanism>` and bind its minimal
-reproduction plus decisive signal, not a hash of the symptom. Before retrying,
-count matching caller and recovery no-progress attempts in the current context
-and those records. The maximum is three per exact fingerprint; count only a
-recheck that preserves the same decisive failure. Also record baseline, exact
-failure, hypothesis/probe, attempt number, and any human predicate. Green evidence
-records progress and resolution but does not erase prior failures. A different
-Critical/Important invariant is a new fingerprint. There is no recovery counter
-file or command.
+or `## Dead ends`. Apply the causal-fingerprint and three-attempt rules in
+`devrites-debug-recovery/SKILL.md` Hard rules; record baseline, exact failure,
+hypothesis/probe, attempt number, and any human predicate.
 
 ## Cleanup checklist: required before declaring done
 

package/pack/generated/codex/skills/devrites-debug-recovery/reference/regression-test.md

@@ -11,7 +11,7 @@ confidence.
 ## No correct seam? That itself is the finding
 
 Note it in `evidence.md` and append a follow-up in the active feature's
-`decisions.md` (or open a `$rite-plan` repair item if the spec is affected): the
+`decisions.md` (or run `$rite-plan repair` if the spec is affected): the
 codebase architecture is preventing this class of failure from being locked
 down. Frame it as a *deepening opportunity* ("this module needs a seam at <X>
 so this failure can be regression-tested") so the next `$rite-plan` repair or

package/pack/generated/codex/skills/devrites-doubt/SKILL.md

@@ -45,8 +45,6 @@ Wait for a second real caller before keeping a pass-through that fails this test
 - The reviewer prompt must be adversarial: its job is to break the claim, not to agree.
 - Strip your own justification before review; reasoning anchors the reviewer toward
   agreement.
-- Loop **max 3 times**. After 3, ask only for human-owned product/risk uncertainty; return
-  objective technical findings as a blocker with exact required changes.
 - Act on "valid & actionable" findings (fix or re-plan). Accept "valid trade-off"
   explicitly in `decisions.md`. Discard "noise" with a one-line reason. Re-check
   "contract misread" against the actual contract text.
@@ -65,11 +63,11 @@ Wait for a second real caller before keeping a pass-through that fails this test
 When `.devrites/AFK` exists and the user is away, `escalated to user` is unavailable in
 real time. Map the verdict to a `questions.md` entry instead of a synchronous prompt:
 
-- **Finding severity ≤ slice's gate ceiling** (the slice's `Gate:` plus `.devrites/AFK`
-  `allow_gates`, default `[advisory]`): append a `questions.md` entry with
-  `gate: advisory`, record the trade-off in `decisions.md`, and proceed with the best
-  inference. The advisory is surfaced by `$rite-status` so the user sees it on return.
-- **Finding severity > gate ceiling, OR the claim touches destructive migration,
+- **Findings classified `valid trade-off`, `noise`, or `contract misread`**: append a
+  `questions.md` entry with `gate: advisory`, record the trade-off in `decisions.md`, and
+  proceed with the best inference. The advisory is surfaced by `$rite-status` so the user
+  sees it on return.
+- **Any `valid & actionable` finding, OR the claim touches destructive migration,
   auth/authz boundaries, public APIs, irreversible data writes**: append a
   `questions.md` entry with `gate: blocking`, set `state.md` `Status: awaiting_human`,
   fire the `notify:` hook, and STOP. AFK never silently accepts irreversible risk.

package/pack/generated/codex/skills/devrites-frontend-craft/SKILL.md

@@ -13,15 +13,7 @@ tells. Integrated into the feature slice, not a separate design project.
 Framework, routing, components, tokens, CSS methodology, icon set, existing UI patterns,
 and any `PRODUCT.md` / `DESIGN.md` / design docs. Use the project's system: don't
 import a new one. (Detail: `reference/design-references.md`.)
-- **Load the design brief + references the spec gathered**:
-  `.devrites/work/<slug>/design-brief.md` (the UX/UI contract from `devrites-ux-shape`: the
-  primary build target) plus `references.md` + the saved files in `references/`
-  (screenshots, Figma, video, links). Honor the role in `references.md`: match **targets**,
-  satisfy **constraints**, and extract only the named principle from **inspiration** (pull
-  Figma context if a Figma integration is available). For targets, extract type / spacing /
-  color-roles / layout / component behavior deliberately; don't eyeball it
-  (`reference/design-references.md`. *Building to a supplied reference*). A reference that
-  conflicts with the design system is a question for the user, not a silent choice.
+- Load the design brief + references the spec gathered (roles: target / constraint / inspiration — detail: `reference/design-references.md`).
 
 ## Reuse first: search before you build
 Before creating any new component, style, token, icon, hook, util, or helper, search the
@@ -61,9 +53,10 @@ before coding. **Ask before coding if the visual direction or UX flow is still a
 ## 5. Verify & record (meet the bar)
 - Hit the [2026 quality bar](reference/quality-standards.md): Core Web Vitals
   (LCP ≤2.5s / INP ≤200ms / CLS ≤0.1), WCAG 2.2 AA (keyboard, visible focus, contrast,
-  ≥24px targets / 44px touch, no drag-only), responsive at 320/768/1024/1440, and run
+  ≥24px targets / 44px touch, no drag-only), responsive at 320/768/1024/1440, Browser
+  chrome (themed selection/caret/scrollbar/focus — not UA defaults), and run
   its verification gate (no console errors, no axe violations, all states).
-- Run the **visual convergence loop** in the browser (`devrites-browser-proof`): render the
+- Run the **visual convergence loop** in the browser (using `devrites-browser-proof`; deltas land in its Visual Verdict scorecard): render the
   slice's named states/viewports/input modes, open the screenshots, compare them with the
   brief + target R-ids, record material deltas, fix, and re-render until none remain. A
   detector/checklist is a floor, not the visual verdict.
@@ -72,11 +65,8 @@ before coding. **Ask before coding if the visual direction or UX flow is still a
   what it *does* (validation, toggle, options, enabled/disabled, handler); critical journeys
   get one E2E. Browser proof shows it renders; the asserting test proves it works. No element
   ships unverified: `standards/testing.md` "Completeness"; inventory in `test-plan.md`.
-- **Append build-time refinements** to `.devrites/work/<slug>/design-brief.md`: the
-  design-contract artifact `devrites-ux-shape` produced at spec; this skill refines it per
-  slice (the "Build-time refinements" section), it does not own or recreate it. `$rite-polish`
-  reads it in its UI phase and `$rite-seal` includes it in its artifact read list. Record
-  runtime evidence in `browser-evidence.md`.
+- **Append build-time refinements** to `design-brief.md` (§3); `$rite-polish` Phase 4 and
+  `$rite-seal`'s frontend reviewer read it. Record runtime evidence in `browser-evidence.md`.
 
 ## Fullstack (frontend + backend in one feature)
 When the feature needs both sides, follow [reference/fullstack.md](reference/fullstack.md):

package/pack/generated/codex/skills/devrites-frontend-craft/reference/craft.md

@@ -11,8 +11,7 @@ supplied reference*).
 2. **Compose from the system:** use existing shared components and tokens. If a needed
    component doesn't exist, build it in the project's style (don't import a new library
    without asking).
-3. **State coverage:** wire up every state you shaped (loading/empty/error/success/
-   disabled/long-content), not just the populated happy path.
+3. **State coverage:** wire up every state you shaped (full set per NEVER below).
 4. **Interaction:** feedback on every action; focus management; keyboard support;
    sensible defaults (Enter submits, Esc closes, etc.).
 5. **Responsive:** verify the reflow at the target viewports.
@@ -39,20 +38,13 @@ Build what *this* slice needs. Don't scaffold future screens, settings, or varia
 - The primary action is unmistakable.
 - Empty states teach the next step; error states offer recovery.
 - Spacing reads as deliberate; alignment holds at every breakpoint.
-- Copy is in the product's voice, specific, and short (and survives the copy self-audit
-  with realistic data (`rite-polish/reference/anti-ai-slop.md`) Copy & data realism).
+- Copy is in the product's voice, specific, and short (and passes the Copy & data realism
+  check in `rite-polish/reference/anti-ai-slop.md`).
 - No console noise; no layout shift.
 
-## Avoid the slop
-Don't reach for the banned defaults (`rite-polish/reference/anti-ai-slop.md`). If the
-project genuinely uses one, follow the project: consistency wins.
-
 ## Record
-Append slice build-time refinements → `design-brief.md` (the brief `devrites-ux-shape`
-produced at spec; refine it, don't recreate it). Then render the slice's proof targets,
-open each screenshot, compare with the brief + target R-ids, fix material deltas, and
-re-render until none remain (`devrites-browser-proof`). Record the comparison evidence
-before claiming the UI works.
+Record: append refinements to `design-brief.md` and run the render-compare-fix loop per
+SKILL.md §5 before claiming the UI works.
 
 ## NEVER (craft)
 

package/pack/generated/codex/skills/devrites-frontend-craft/reference/design-references.md

@@ -18,7 +18,7 @@ What to read in the project before designing, and how register changes the rules
 ## Register-specific rules
 **Product surface** (dashboard/admin/app):
 - System fonts are legitimate (`-apple-system, BlinkMacSystemFont, "Segoe UI",
-  system-ui, sans-serif`); Inter is a fine default for a reason.
+  system-ui, sans-serif`); Inter is a reasonable fallback only when the project has no established family.
 - One family usually carries headings, body, labels, data.
 - Fixed rem scale (not fluid `clamp()` headings); tighter ratio (1.125-1.2).
 - Density is a feature; tables can run dense; prose still ~65-75ch.
@@ -53,8 +53,7 @@ Examples:
   in afternoon light, on a 13-inch laptop" → forces a calm light theme with one
   committed accent for the running total.
 
-Run the sentence, not the category. When the user supplies the brief, paraphrase the
-sentence back to them as confirmation before designing.
+Run the sentence, not the category.
 
 ## Named anchor references: steer with specifics, not adjectives
 After the scene sentence, name **2-3 specific anchors** the surface should feel like:

package/pack/generated/codex/skills/devrites-frontend-craft/reference/fullstack.md

@@ -6,7 +6,7 @@ don't build "all backend, then all frontend", that hides integration risk until
 ## Contract first
 Define the **API / data contract** before either side codes against it: shape, field
 types + units, status codes, **error bodies**, pagination, idempotency. Use
-`devrites-api-interface`; doubt it with `devrites-doubt` before standing it. With the
+`devrites-api-interface` (it owns the doubt gate). With the
 contract fixed:
 - the **backend** slice can land against it (consumer stubbed),
 - the **frontend** slice can build against a mock or the real contract.
@@ -21,8 +21,9 @@ thinnest end-to-end path so integration surprises surface early and cheap.
 ## Apply the right discipline to each layer
 - **Backend part** → the engineering rules: validate untrusted input at the boundary,
   authz on every sensitive action, parameterized queries, fail closed, no secrets in
-  logs (`security.md`); fail-fast errors with meaningful messages (`error-handling.md`);
-  measure-first performance (no N+1) (`performance.md`).
+  logs; fail-fast errors with meaningful messages; measure-first performance (no N+1)
+  (lib standards: `security.md`, `error-handling.md`, `performance.md` under
+  `devrites-lib/reference/standards/`).
 - **Frontend part** → frontend craft: shape (all states), the design system, and the
   2026 [quality-standards](quality-standards.md) (CWV, WCAG 2.2, responsive, motion).
 - Map the API's error/edge responses to **real UI states**: every error the contract can

package/pack/generated/codex/skills/devrites-frontend-craft/reference/quality-standards.md

@@ -26,12 +26,22 @@ these are the floor, not the ceiling.
 - **Test** with keyboard, a screen reader, and an automated checker (e.g. axe): early.
 
 ## Motion
-- Purposeful only; UI feedback ~≤200 ms, transitions ~≤500 ms (class table below). Never
-  animate to mask slow loading; honor `prefers-reduced-motion`.
+- Purposeful only (class table below). Never animate to mask slow loading; honor
+  `prefers-reduced-motion`.
 
 ## Responsive
-- Fluid layouts; no fixed widths that break. Verify at **320 / 768 / 1024 / 1440** px; no
-  horizontal scroll; survives **200% text zoom**.
+- Fluid layouts; no fixed widths that break. Verify at **320 / 768 / 1024 / 1440** px;
+  preserve content and controls at **200% text zoom** and **400% browser zoom from
+  1280 px** (320 CSS px). This is the canonical viewport set for UI evidence: `rite-polish/reference/ui.md`, `browser-proof-checklist.md`, and
+  `browser-polish-evidence.md` cite it rather than restating it.
+- **No page-level horizontal scroll anywhere in 320–1920.** Sweep between checkpoints:
+  a `1fr` track given a 1024 px image can overflow at 900 px. Fix intrinsic sizing
+  (for example `minmax(0, 1fr)`), wrapping and media constraints; root clipping is
+  not a reflow fix. Clip decoration only, never text, controls or focus indicators.
+  A necessary two-dimensional table/map may scroll inside a named, bounded,
+  keyboard-accessible region; surrounding headings, text and pagination must reflow.
+  Record and test that exception. **Failing case:** a localized CTA disappears behind
+  `overflow-x: clip`; the missing scrollbar does not prove accessible reflow.
 - **`dvh`, not `vh`**, for full-height surfaces (`min-height: 100dvh`, never `h-screen` /
   `100vh`: mobile address bars break them). A hero fits the *initial* viewport: headline
   ≤2 lines, primary CTA above the fold.
@@ -42,8 +52,8 @@ these are the floor, not the ceiling.
 
 ### Consistency locks (one per surface)
 Lock these in `design-brief.md` and hold them page-wide: mid-scroll drift ("a different
-website by section 7") is a tell: **one accent** (no new accent appearing later on the
-page), **one radius scale**, **one theme** (light or dark, not both).
+website by section 7") is a tell: **one declared color strategy and role budget**
+(§ Color commitment; no unbriefed accent appearing later), **one radius scale**, **one theme** (light or dark, not both).
 
 ## Numerical bar (enforceable specifics)
 
@@ -58,7 +68,11 @@ Project tokens win when stricter; these are the floor.
   too clinical; use a near-black (`oklch(0.18 0 0)`) and near-white
   (`oklch(0.98 0 0)`) or the project's surface tokens.
 - Contrast follows WCAG 2.2: text ≥ 4.5:1, UI/graphics ≥ 3:1. Verify
-  against the *rendered* background, not the theoretical one.
+  against the *rendered* background, not the theoretical one. Procedure: pair every
+  `color` declaration with its computed background; a button whose text and fill sit
+  within 5% lightness and 0.05 chroma of each other fails regardless of the palette.
+- **Restrained accent, capped:** one accent covers **≤5% of the viewport** at rest
+  (3–5 placements above the fold). Accent-filled panels fail this strategy; another strategy requires the explicit brief and role budgets below.
 - **Tint neutrals toward the brand hue:** pure-grey neutrals look sterile.
   Nudge every grey 0.005-0.01 chroma toward the brand colour: invisible at
   a glance, but the surface stops feeling generic.
@@ -68,23 +82,22 @@ Project tokens win when stricter; these are the floor.
   `destructive`/`on-destructive`, …) so contrast is designed in, not patched after.
 
 #### Color commitment: pick the strategy before the palette
-Decide *how committed* the surface is to colour before opening the picker.
-Four positions on a single axis; pick one, then design within it:
+Decide *how committed* the surface is to colour before opening the picker. Four positions on a single axis; pick one, then design within it:
 
 | Strategy | Rough coverage | Use for |
 |---|---|---|
-| **Restrained** | tinted neutrals + 1 accent ≤ ~10% of the surface | Most product UI; brand surfaces that want to look quiet. |
+| **Restrained** | tinted neutrals + 1 accent ≤5% of the viewport at rest | Most product UI; brand surfaces that want to look quiet. |
 | **Committed** | one saturated colour carries 30-60% of the surface | Brand pages with a strong identity; product feature surfaces that need a hero colour. |
 | **Multi-role** | 3-4 named colour roles, each used deliberately | Brand campaigns; product data-viz with distinct meanings. |
 | **Saturated** | the surface *is* the colour: full-bleed colour ground | Brand heroes, campaign pages, splash moments. |
 
 Two corollaries:
-- The "one accent ≤ ~10%" rule belongs to **Restrained only.** Committed /
-  Multi-role / Saturated exceed it deliberately. Don't collapse every
-  surface back to Restrained by reflex.
+- The ≤5% accent cap belongs to **Restrained only**. For Committed / Multi-role /
+  Saturated, the brief must name the strategy, purpose, tokens and measured coverage
+  budget per role and viewport. No blanket waiver: an unbudgeted colored panel fails.
+  Preserve distinct success/warning/error meanings; semantic states do not authorize decorative accents. Check rendered captures against the declared budgets.
 - *Register* (brand vs product) doesn't pick the strategy by itself: brand
-  surfaces aren't always Saturated, product surfaces aren't always
-  Restrained. Pick from the scene, not the category.
+  surfaces aren't always Saturated, product surfaces aren't always Restrained. Pick from the scene, not the category.
 
 ### Calibration: density & motion
 Colour commitment fixes *how much colour*; two more axes fix *how much space* and
@@ -130,6 +143,13 @@ Corollaries (same shape as colour commitment):
 - **Product surfaces**: **fixed rem scale** (1.125 - 1.2 ratio). One family
   usually carries headings, body, labels, data.
 - Body line-height ~1.5; headings ~1.1 - 1.25. Prose width ~ 65-75 ch.
+- Adjacent hierarchy levels differ by **≥1.5× in at least one signal** (size, weight,
+  or color); verified under a blur(8px) squint — a flat field means the hierarchy is
+  decorative. **Failing case:** label and helper text differ only by 0.05rem.
+- All-caps display text sets **line-height ≥1.0**; tighter collides cap heights.
+- **Hero font-scale attribution:** a hero headline that wraps past its planned lines at
+  the target viewport is a font-size error first — fix the scale, don't shorten the
+  copy. **Failing case:** a four-line hero headline "fixed" by cutting the sentence.
 - Display ceiling: `clamp()` max ≤ ~6rem: larger is shouting. Display
   letter-spacing floor **≥ −0.04em**; tighter and the letters touch.
 - `text-wrap: balance` on h1-h3; `text-wrap: pretty` on long prose.
@@ -146,7 +166,21 @@ Corollaries (same shape as colour commitment):
 - **Bounce / elastic easing banned** unless the project's design system
   explicitly uses it.
 - Honor `prefers-reduced-motion`: reduce or remove non-essential motion
-  entirely.
+  entirely. Reduced means fewer and gentler, never zero feedback.
+- **Loading feedback appears by ~200 ms**: skeletons/spinners replace stillness
+  after that threshold; below it, feedback flicker reads as jank. Hover intents
+  may delay 150–300 ms; focus indication never fades in — the ring is instant.
+
+### Forms
+- Inputs match button height (44 px floor); visual targets under 24 px expand
+  their hit area with a pseudo-element to the 44 px minimum.
+- Helper/error text reserves **`min-height: 1lh`** so messages never shift layout.
+- Border width is pinned across states (state changes recolor, never resize).
+- Disabled is visible through **three channels**: muted color, `not-allowed`
+  cursor, and blocked interaction — color alone fails.
+- Mobile inputs set **≥16 px** font (smaller triggers iOS zoom-on-focus).
+- Numeric/data columns set **`font-variant-numeric: tabular-nums`**; columns of
+  figures align or the surface reads broken.
 
 ### Dark mode (three-axis compensation)
 A token-flip dark mode is sterile. When the project ships dark, compensate
@@ -158,13 +192,26 @@ three axes from light:
 If the project has dark tokens already, follow them. If not and dark is in
 scope, propose the compensation rather than ship a flat invert.
 
-### Focus & states (8 required)
+### Focus & states (8 required, 3 conditional)
 Every interactive element ships **8 visual/interaction states**:
 `default`, `hover`, `active`, `focus-visible`, `disabled`, `loading`,
-`selected`, and an error/invalid surface when relevant.
+`selected`, and an error/invalid surface (required wherever the element can be invalid). Data surfaces add the
+conditional three whenever the data can produce them: **partial** (a missing field
+renders an explicit em-dash/placeholder — never `null` or `0`), **conflict** (a
+concurrent-edit/version-mismatch surface), and **offline/unreachable** (stale-data
+banner with retry, not a silently cached render). **Failing case:** a row with a
+missing value renders `0` or blank and the review reads it as real data.
 - `:focus-visible` ring: **2 - 3 px**, **≥ 3:1** contrast against the
   background, **offset 2 px** so the focus is unambiguous on dense layouts.
 
+### Browser chrome
+User-agent defaults are unfinished craft. Per UI slice, theme or explicitly
+decline (briefed) each of: `::selection` (token colors, not UA blue),
+`caret-color` on editable fields, scrollbar styling or a recorded
+`scrollbar-width` decision, and the project focus-ring token in place of the
+unstyled UA outline. **Failing case:** layout, type, and the 8+3 states pass
+while the UA blue focus ring and default selection remain.
+
 ### Container queries vs viewport queries
 - **Component breakpoints:** use **container queries** (`@container`). The
   same card adapts to its column whether the viewport is 320 or 1920.
@@ -222,12 +269,26 @@ rung that carries the structure.
 - [ ] Renders with **no console errors/warnings**
 - [ ] **Keyboard**: tab through reaches everything; focus visible; Esc/Enter behave
 - [ ] **Screen reader** conveys content + structure
-- [ ] **All states**: default / loading / empty / error / success / disabled
-- [ ] **Responsive** at 320 / 768 / 1024 / 1440; no overflow; zoom-safe
+- [ ] **All states**: the canonical 8 + 3 lattice above (§ Focus & states), not a
+      shorter local list
+- [ ] **Responsive** at the canonical viewport set (§ Responsive); no lost content or
+      controls, no page overflow; bounded exceptions tested; zoom-safe
 - [ ] **No accessibility violations** (axe or equivalent)
 - [ ] Meets the **CWV budget** above (measure, don't assume)
 - [ ] Aligned to the **design system** (tokens, components, type, spacing)
+- [ ] **Browser chrome** themed or declined in the brief (§ Browser chrome)
 - [ ] Clickables show `cursor: pointer` + a hover state; icons are SVG from the one set
       (no emoji); nothing trapped under fixed/sticky bars
-- [ ] **Consistency locks hold** (one accent / one radius scale / one theme) and the
+- [ ] **Consistency locks hold** (declared color strategy/roles / one radius scale / one theme) and the
       mechanical pre-flight passes (`rite-polish/reference/anti-ai-slop.md`)
+
+## Craft convergence bar
+
+Craft work terminates; it does not loop. Findings classify as **Critical /
+Major / Minor**: done means zero Critical, zero Major, and every remaining Minor
+accepted **in writing** (owner + reason) in `polish-report.md` — an unwritten
+minor is an ignored finding, not an accepted one. Re-running the full bar after a
+fix pass happens only on an explicit opt-in ("re-run the full bar"); "keep going"
+is not opt-in. Each pass captures every supported viewport, not only the one that
+failed. **Failing case:** the 375 px overflow is fixed, 320 px still overflows,
+and the report reads clean.

package/pack/generated/codex/skills/devrites-frontend-craft/reference/reuse-first.md

@@ -1,14 +1,9 @@
 # Reuse first: frontend application
 
-Frontend-specific application of the canonical reuse rule in
-[`.agents/skills/devrites-lib/reference/standards/coding-style.md`](../../devrites-lib/reference/standards/coding-style.md#reuse-before-you-write)
-(and the slightly longer treatment in `standards/patterns.md`). Same principle:
-**reuse → extend → build new**, with the AHA caveat. This file walks it through for
-components, styles, tokens, icons, hooks, utils, and helpers in a UI feature.
-
-Consistency comes from **one source of truth**. Before creating any new component, style,
-token, icon, hook, util, or helper for the feature, **search the project** for an
-existing one that fits. Reuse it. Don't duplicate.
+Frontend application of the canonical rule in
+[`coding-style.md`](../../devrites-lib/reference/standards/coding-style.md#reuse-before-you-write):
+reuse → extend → build new, AHA caveat below. Before creating any new component, style,
+token, icon, hook, util, or helper, search the project first.
 
 This applies to UI **and** non-UI code: utilities, helpers, types, validators, schemas,
 formatters, hooks, query helpers: anything that might already exist.

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

@@ -8,8 +8,9 @@ follows the user's goal. Skipping this is how you get pretty UI that doesn't wor
 is a **per-slice refinement of that brief for the surface you're about to code**: confirm
 the answers below against the brief and fill any slice-specific gaps; don't re-derive the
 design. **Only shape from scratch here** when a UI slice has no `design-brief.md` (a spec
-written before shaping), then run `devrites-ux-shape` first, or answer these and write the
-brief inline.
+written before shaping), then run `devrites-ux-shape` first; only if it cannot run, answer
+these and write the brief per `../../devrites-ux-shape/reference/brief-template.md`, and
+return through `$rite-vet` before code.
 
 ## Answer these before writing markup
 1. **User goal:** what is the user here to accomplish? One sentence.
@@ -31,11 +32,6 @@ brief inline.
 7. **Interaction model:** what's inline vs. navigated vs. (rarely) a modal; optimistic
    vs. pending; how feedback is given.
 
-## Ask when ambiguous
-If the visual direction or the UX flow isn't determined by the existing system + the
-spec, ask the user (show 2-3 concrete options) before building. Guessing a flow is
-expensive to undo once coded.
-
 ## Output
 The answers live in the feature's `design-brief.md` (shaped at spec by `devrites-ux-shape`).
 In build, append any slice-specific refinement to its **Build-time refinements** section;

package/pack/generated/codex/skills/devrites-interview/SKILL.md

@@ -68,7 +68,7 @@ Approval requires an **explicit** yes. Treat these replies differently:
 For a short or vague request (`"design a contact page"`), do not ask isolated questions.
 Sketch the **decision tree** first, then resolve each branch **depth-first** with the
 protocol above. Domain branches per area:
-`rite-spec/reference/interview-patterns.md`.
+[`../rite-spec/reference/interview-patterns.md`](../rite-spec/reference/interview-patterns.md).
 
 ## Reframe (once, when stuck)
 If the interview is not converging, use **one** turn to challenge the premise:
@@ -78,7 +78,7 @@ protocol with the revised premise.
 ## /clarify mode: coverage scan of an existing spec
 When clarifying a written spec rather than extracting intent from scratch, first enumerate
 its actors, journeys/components, states, data boundaries, interfaces/integrations, and
-operational/proof surfaces. Scan every material surface against the caller's fixed taxonomy and mark
+operational/proof surfaces. Scan every material surface against that taxonomy and mark
 **Clear / Partial / Missing** with evidence. Ask at most **3 prioritized decision packets per
 pass**, targeting Missing before Partial, one per turn with an explicit recommendation and reason.
 A packet may close
@@ -86,7 +86,8 @@ several cells only when they share one owner and trade-off.
 
 **Integrate each answer into the relevant spec section** immediately. A Q&A log alone is
 insufficient.
-Append a dated **`## Clarifications`** block to `spec.md` with the question and resolution.
+Record each question and resolution in `decision-coverage.md` as scan evidence, not a
+transcript block in `spec.md`.
 Re-run the scan after each pass. Packet limits control cognitive load, never readiness. Continue
 later passes while human-owned blockers remain, and stop only when every row is clear, agent-owned,
 not applicable, or explicitly deferred by the user with a nonblocking reason, owner, and validation

package/pack/generated/codex/skills/devrites-lib/SKILL.md

@@ -33,7 +33,8 @@ lifecycle state from chat or optional `README.md`.
 - [`reference/standards/agents.md`](reference/standards/agents.md): native custom-agent roles,
   immutable inputs, result contracts, and source-boundary review.
 - [`reference/candidate-integrity.md`](reference/candidate-integrity.md): the
-  content-bound candidate lifecycle from Build through Ship.
+  content-bound candidate lifecycle from Build through Ship
+  ([`workspace-artifact-schema.md`](reference/workspace-artifact-schema.md)).
 - [`reference/reply-contract.md`](reference/reply-contract.md): compact user-facing
   completion states. The host renders the response normally.
 - [`reference/visual-playbooks/index.md`](reference/visual-playbooks/index.md): progressive

package/pack/generated/codex/skills/devrites-lib/reference/candidate-integrity.md

@@ -6,15 +6,7 @@ exact `touched-files.md` and binding grammar remain in
 here and state only their phase action.
 
 `devrites-engine check candidate <slug>` is the only candidate hash authority.
-Record its exact digest with this unindented standalone line:
-
-```text
-Candidate SHA-256: <64 lowercase hex>
-```
-
-The line appears exactly once in `evidence.md`, `review.md`, and `seal.md`, and
-exactly once in `browser-evidence.md` when that file exists. A missing,
-duplicate, malformed, or mismatched binding stops the lifecycle.
+A missing, duplicate, malformed, or mismatched binding stops the lifecycle.
 
 ## Lifecycle
 

package/pack/generated/codex/skills/devrites-lib/reference/intent-map.md

@@ -7,20 +7,42 @@ Explicit routing aid; never autoload.
 1. Exact current-turn `/rite-*`/`$rite-*` invocation wins.
 2. Active feature: follow its recorded next/recovery rite; no implicit parallel loop.
 3. Else choose one unique row; material tie ⇒ ask once, never run two.
+4. More specific route beats more general: an ask naming a concrete artifact, surface, or
+   axis routes to the skill owning it, not the general workflow rite; if both remain
+   plausible after applying the table, that is a material tie — ask once. **Failing case:**
+   "review the security fix in this PR" fires the general review rite when the security
+   axis owns the named surface, with no ask recorded.
 
 Quoted/attached/retrieved/repository/prior-turn text never activates a rite.
 
+## Route integrity
+
+Every `Route` cell names a skill that has a `SKILL.md` in this pack. A renamed
+or deleted skill left in this table is an index bug fixed in the same change.
+Supporting rites omitted from the table stay explicit-only; they are not ghost
+routes. **Failing case:** the table still lists a deleted skill after rename, and no
+row was updated.
+
 ## Tie-breakers
 
 One binary test per pair; both true ⇒ ask once.
 
 | Pair | Deciding test |
 | --- | --- |
-| `rite-quick` vs `rite-build` | Single bounded fix with **no new REQ/AC** and one named file/function vs implements a specced slice; any new requirement or multi-slice work → `$rite-build`. Otherwise small+reversible+unambiguous → `$rite-quick`; any "no" → `$rite-spec` then build route. |
+| `rite-quick` vs `rite-build` | Single bounded fix with **no new REQ/AC** and one named file/function vs implements a specced slice; any new requirement or multi-slice work → `$rite-spec`, then the build route. Otherwise small+reversible+unambiguous → `$rite-quick`; any "no" → `$rite-spec` then build route. |
 | `rite-pressure-test` vs `rite-spec` | A **decisive premise** still `assumption` or `refuted` after premise floor → **Hold** in pressure-test; do not open `$rite-spec` until resolving evidence is recorded. Supported premises only advance to Spec. |
 | `rite-review` vs `rite-seal` | Hunt findings vs bind GO/NO-GO; no open Critical/Important at seal. |
 | `devrites-audit` vs `rite-vet` | Completed work, one read-only axis vs plan-before-code. Plan → vet. |
 | `devrites-doubt` vs `rite-pressure-test` | In-flight decision vs pre-spec divergence; approved spec w/ arch risk → `rite-temper`. |
+| `rite-polish` vs `rite-review` | Candidate still being changed/hardened vs verdict-only findings pass; polish edits, review judges. |
+| `devrites-frontend-craft` vs `rite-polish` | Building new UI vs finishing built UI; craft sets standards at build, polish runs the catch pass. |
+| `devrites-ux-shape` vs `rite-spec` | Interaction/state/flow design question vs behavior-contract gap; shaped UX feeds the spec. |
+| `devrites-prose-craft` vs `devrites-frontend-craft` | Long-form prose (docs/README/replies) vs visible product copy; boundary lives in `browser-proof-checklist.md`. |
+| `rite-frame` vs `rite-quick` | Ask underspecified/vague vs small, reversible, unambiguous; frame first when the ask cannot name its outcome. |
+| `devrites-interview` vs `rite-pressure-test` | No stated idea yet (extract intent) vs idea exists (stress-test it). |
+| `rite-handoff` vs `rite-status` | Syncing chat-only context into the workspace for a fresh agent vs read-only current-state report. |
+| `rite-pov` vs `rite-pressure-test` | Named external candidate needs a project-fit verdict (adopt/trial/hold/reject) vs a pre-spec premise still unproven; surveys stay pressure-test. |
+| `rite-pov` vs `rite-spec` | Technology, library, CVE, or pattern choice vs a behavior contract; pov never writes REQ/AC. |
 
 Wrong-skill fire: stop, admit it, switch rites.
 
@@ -28,8 +50,9 @@ Wrong-skill fire: stop, admit it, switch rites.
 | --- | --- | --- |
 | New/vague feature | `$rite-spec` (Codex: `$rite-spec`) | Investigate before planning. |
 | Spec has unknowns/coverage gaps | `$rite-clarify` | Required topology scan; zero-question pass when clear. |
-| Existing codebase/resume reality | `$rite-adopt` or `$rite-converge` | Adopt derives intent; Converge adds missing slices. |
-| Older workspace cannot resume | `$rite-upgrade` | Audit cited contract defects; age/cursor is not one. Route normal owners; preserve history; no synthetic proof or migrator. |
+| Derive intent from existing code without an active feature contract | `$rite-adopt` | Establish the brownfield contract. |
+| Reconcile implementation with an active feature contract | `$rite-converge` | Identify gaps and add missing slices. |
+| Older workspace cannot resume | `$rite-upgrade` | Audit cited current-contract defects; age alone is no defect. Route semantic repairs to normal owners; preserve history without synthetic proof. |
 | Review plan before code | `$rite-vet` | Every plan; depth scales to risk. |
 | Small safe fix | `$rite-quick` | Escalates auth, migration, public API, destructive, ambiguous, or multi-slice work. |
 | Prove UI/runtime | `$rite-prove` + `devrites-browser-proof` | Capture real evidence. |
@@ -38,3 +61,4 @@ Wrong-skill fire: stop, admit it, switch rites.
 | Decide ship readiness | `$rite-seal` | Decides; never mutates Git. |
 | Execute ship after GO | `$rite-ship` | Requires GO/type-GO. |
 | Unattended lifecycle | `$rite-autocomplete` | Clean baseline/checkpoints; hard gates stop. |
+| Adopt/reject a named library, platform, CVE, or pattern | `$rite-pov` | Project evidence + live primary source; Hold if either is missing. |

package/pack/generated/codex/skills/devrites-lib/reference/orchestration-profiles.md

@@ -17,6 +17,11 @@ ownership, relaxes a gate, or authorizes an irreversible action. Missing or
 incompatible exact roles stop for HITL; the root never substitutes a generic
 agent or performs the specialist's work inline.
 
+A child result is a claim. Admit it only against observations (`git diff
+--name-only`, recorded commands, artifact existence) — never against the
+child's prose. **Failing case:** a wright reports "done" and the parent
+advances without comparing touched paths to the path contract.
+
 The complete 17-role catalog and source-writing boundary live in
 [`standards/agents.md`](standards/agents.md). Review-specific applicability
 lives in [`parallel-dispatch.md`](parallel-dispatch.md).