devrites 5.13.1 → 5.14.1

package/pack/generated/pi/skills/rite-fast/reference/artifacts.md

@@ -0,0 +1,107 @@
+# /rite-fast artifacts
+
+Three files under `.devrites/work/<slug>/`. The root writes them; agents never do.
+Keep each short: a reader should finish `spec.md` in two minutes.
+
+## spec.md
+
+```markdown
+# <Feature title>
+
+Lane: fast · Risk: <none | list of risk flags>
+
+## Intent
+<2-4 sentences: the problem, who it serves, what "done" looks like.>
+Frozen after plan approval; change only with the user's answer.
+
+## Acceptance criteria
+- AC-001: <observable behavior at a named surface; one test can show it>
+- AC-002: ...
+
+<!-- Risky criteria use the full grammar instead of a flat bullet: -->
+### Requirement: <name> (AC-003)
+The system SHALL <behavior>.
+#### Scenario: <name>
+- WHEN <condition>
+- THEN <observable outcome>
+
+## Out of scope
+- <what this run will not touch>
+
+## Clarifications
+- Q: <question> → A: <answer> (user | recommended default accepted)
+
+## Assumptions
+- <gap the user was not asked about, with the chosen default and why it is safe>
+```
+
+Criteria rules (from [`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md)):
+- Describe behavior, not implementation. Anchor each AC to a surface: a command, an
+  endpoint, a screen, a function contract.
+- Buildable test: one slice can make it true and one test can show it. A goal that
+  no single test shows is a success metric; list it in Intent, not as an AC.
+- Two engineers reading an AC must build the same thing.
+
+## plan.md
+
+```markdown
+# Plan: <slug>
+
+Lane: fast · Baseline: <git status --short output, or "clean"> · Commands: <detected>
+
+## Approach
+<3-6 lines: where the change lives, which existing seams it reuses, what it adds.>
+
+## Slices
+- [ ] S1 [AC-001, AC-002] files: src/a.ts, test/a.test.ts · demo: <one sentence>
+- [ ] S2 [AC-003] after: S1 · files: src/b.ts, test/b.test.ts · demo: <one sentence>
+
+## Ledger
+- S1 done: <files returned> · <one-line note>
+
+## Decisions
+- <decision made during build, and why>
+
+## Review
+- accepted: <finding id> <file:line> <one line>
+- dropped: <finding id> <reason>
+
+## Deferred
+- <item> — <why deferred, who agreed>
+```
+
+Slice rules:
+- At most 10. Each is vertical: it delivers behavior an AC names, with its tests.
+- Split only where one slice could fail while its neighbor passes. A slice with no
+  demo sentence is horizontal; merge it into the slice it serves.
+- Every AC appears in at least one slice. Every slice names at least one AC.
+- `files:` lists exact project-relative paths, tests included. The builder may touch
+  only these. A new file is listed like any other.
+- `after:` names a real dependency. Slices with no `after:` link and no shared file
+  may build in parallel.
+
+## evidence.md
+
+```markdown
+# Evidence: <slug>
+
+## Check run
+- `<command>` → exit <n> · <decisive output line>
+
+## Proof
+- `<command>` → exit <n> · <decisive output line>
+
+## Acceptance
+| AC | Test | Result |
+| --- | --- | --- |
+| AC-001 | test/a.test.ts: "rejects empty name" | pass |
+
+## Unproven
+- <what could not run, and why>
+```
+
+## Marker sweep
+
+Before approval and before the report, search `spec.md` and `plan.md` for `[NEEDS`,
+`TBD`, `TODO`, `???`, and unfilled `<...>` placeholders. Each hit is a defect: fix it,
+move it to Assumptions with a default, or ask the user.

package/pack/generated/pi/skills/rite-fast/reference/check-and-triage.md

@@ -0,0 +1,51 @@
+# /rite-fast check and triage
+
+The lane has no gate between slices, so this is where misses are caught. It runs
+once after the last slice, and again only after fixes (at most 2 rounds).
+
+## Check run
+
+Run, on the full tree and in this order, the detected typecheck or build command and
+then the test suite. Record each command, exit code, and first decisive failure line
+in `evidence.md` `## Check run`. Do not fix anything yourself; failures become gaps.
+
+## Gap kinds (what `fast-checker` looks for)
+
+| Kind | Means |
+| --- | --- |
+| `missing-ac` | An AC has no code that makes it true. |
+| `untested-ac` | An AC has code but no test that would fail without it. |
+| `unfinished-slice` | A ledger slice is unticked, or its files lack the promised change. |
+| `out-of-scope` | A changed path or behavior no slice or AC asked for. |
+| `failing-command` | The check run is red. |
+| `marker` | A `TODO`, `TBD`, placeholder, stub, or `not implemented` left in changed code. |
+| `broken-contract` | A caller, type, or interface the diff changed is now inconsistent. |
+
+Gaps only. Style, naming, and simplification belong to `fast-critic` in REFINE.
+
+## Admission
+
+A gap is a claim. Before routing it:
+1. Open the cited `file:line` and confirm it. A citation that does not hold is
+   dropped and noted as `false`.
+2. Merge gaps with one root cause into one item.
+3. Never admit a "fix" that edits `spec.md` or `plan.md` to match the code.
+
+## Routes
+
+| Route | When | Action |
+| --- | --- | --- |
+| `patch` | The fix stays inside the approved intent and adds no public surface. | Dispatch `fast-builder` in `fix` mode with the gap, its AC, and exact paths. |
+| `intent_gap` | The fix needs a decision the spec does not make, or the plan was wrong. | Ask the user one question with a recommended answer; record `Q → A` in `spec.md`; then `patch`. |
+| `defer` | Real but outside this run. | Record in `plan.md` `## Deferred`. Deferring an AC needs the user's consent. |
+
+`out-of-scope` changes default to `patch` as a revert of that change, unless the
+user accepts them as a new AC.
+
+## Round limits
+
+- At most 2 check-and-fix rounds, and at most 2 proof-and-fix rounds in PROVE.
+- A gap with the same cause twice is no progress; stop with `Stopped:` naming it.
+- Proof rules that never bend: a skipped, filtered, or `.only` test counts as
+  missing; a test expectation is never edited to match the code; a deleted or
+  weakened assertion is a Critical finding.

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

@@ -28,7 +28,11 @@ cannot hold; the engine supplies what the workspace already knows.
 ## Where to write
 
 - **Active feature exists** → `.devrites/work/<slug>/handoff.md` (overwrites the previous
-  handoff; the workspace is the canonical home for this slug).
+  handoff; the workspace is the canonical home for this slug). Before overwriting, read the
+  previous file: its "External references" and "Live assumptions" exist nowhere else. Carry
+  each still-valid entry into the new file or list it under "Retired from the previous
+  handoff" with a reason; an entry in neither place is a silent drop — fix the draft before
+  writing.
 - **No active feature** → OS temp dir (`$TMPDIR` / `/tmp` / `%TEMP%`) as
   `rite-handoff-<ISO-timestamp>.md`. Print the absolute path after writing.
 
@@ -64,7 +68,15 @@ themselves. The workspace is the canonical store; the handoff is the chat-only d
 4. **Live assumptions the agent is acting on** that the workspace doesn't reflect yet
    (after the sync above, this section should be near-empty: flag anything that
    remains).
-5. **How to resume:** fixed boilerplate (see template below).
+5. **Tree record.** `HEAD <sha>` (`git rev-parse HEAD`) and the `git status --short` path
+   count at write time, so the next session can see edits made after the handoff.
+6. **In-flight work.** Every dispatch wave opened or sealed without a return (`devrites-engine
+   dispatch <slug> status`), running writer handle, held claim id plus paths (`devrites-engine
+   claim list --all`), and consumptive action started, each `terminal: yes|unknown` (`yes` only with
+   an admitted return, release, or proof of stop). The live handle exists only in chat. Any
+   `unknown` row makes item 1 a reconcile step (`dispatch <slug> status`, `parallel status`,
+   `claim list --all`), never a writer command: otherwise the next session dispatches a second writer.
+7. **How to resume:** fixed boilerplate (see template below).
 
 ## What NOT to include
 

package/pack/generated/pi/skills/rite-handoff/reference/handoff-template.md

@@ -10,6 +10,8 @@ Loaded on demand by `/rite-handoff`. Write the filled-in template to
 Current objective: <one sentence>
 Last completed slice: <SLICE-### | none>
 Blockers: <none | q-YYYY-MM-DD-NNN / released Q-### / DRIFT-###>
+Tree at write: HEAD <sha | no git>; dirty paths <n>
+In flight: <none | wave <id> role <r> handle <h> | wright SLICE-### handle <h> | claim <id> <paths> | action <name>>; each `terminal: yes|unknown`
 
 ## Read next
 1. `.devrites/work/<slug>/README.md` — workspace map.
@@ -18,17 +20,22 @@ Blockers: <none | q-YYYY-MM-DD-NNN / released Q-### / DRIFT-###>
 4. <phase-specific source artifact; link, do not duplicate>.
 
 ## Next action
-<one command or action, no option set>
+<one command or action, no option set; any `terminal: unknown` row makes it reconcile:
+`devrites-engine dispatch <slug> status`, `devrites-engine parallel status --root <repo> --slug <slug>`,
+`devrites-engine claim list --all` — never a writer command>
 
 ## What changed this turn
 - <short event; link to source artifact instead of copying full content>
 
 ## External references (chat-only)
-- <URL / Figma / screenshot path / video timestamp>
+- <URL / Figma / screenshot path / video timestamp>   (carried forward if still valid)
 
 ## Live assumptions (not yet in assumptions.md)
 - ...   (this section should be near-empty after the sync step)
 
+## Retired from the previous handoff
+- <none | reference or assumption — why it no longer holds>
+
 ## Synced this turn
 - decisions.md: <N entries appended>
 - questions.md: <N appended>
@@ -39,6 +46,11 @@ Blockers: <none | q-YYYY-MM-DD-NNN / released Q-### / DRIFT-###>
 ## How to resume
 1. Read this file.
 2. Read `.devrites/work/<slug>/state.md` for the workspace cursor.
-3. Run `/rite-status` for the current phase / next action / open drift.
-4. Continue with the `Next action` above.
+3. Tree check: compare `git rev-parse HEAD` and `git status --short` with `Tree at write`
+   and `touched-files.md`. Other HEAD, other dirty count, or a path missing from
+   `touched-files.md` → record it in `drift.md` or `questions.md` before any writer command.
+4. Any `In flight` row `terminal: unknown` → run the reconcile commands first; never dispatch
+   a second writer onto its paths.
+5. Run `/rite-status` for the current phase / next action / open drift.
+6. Continue with the `Next action` above.
 ```

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

@@ -20,10 +20,20 @@ of one authority; it cannot promote a rule alone.
 
 ## Workflow
 
-1. Read [durable promotion](../devrites-lib/reference/standards/documentation.md#promote-durable-guidance);
-   bound the archive; inspect applicable `AGENTS.md`/`CLAUDE.md`, accepted ADRs, and relevant `.devrites/archive/*/{decisions,drift,review,seal}.md`.
+1. Read [durable promotion](../devrites-lib/reference/standards/documentation.md#promote-durable-guidance).
+   Before bounding, fixed-string search all of `.devrites/archive/` and active
+   `decisions.md` for `rite-learn: accepted` and `rite-learn: declined`; read every hit
+   whole. Then bound the archive; inspect applicable `AGENTS.md`/`CLAUDE.md`, accepted ADRs, and relevant `.devrites/archive/*/{decisions,drift,review,seal}.md`.
+   **Failing case:** a declined proposal returns because its feature fell outside the bound.
 2. Broad mode dispatches exact fresh/read-only `devrites-retrospector`; reconcile its claims against cited files.
+   A missing, failed, timed-out, or malformed result reports `Candidate: NOT-RUN
+   (unavailable: <reason>)` as a gap, never `Candidate: none`; an unavailable role stops
+   for HITL per [`agents.md`](../devrites-lib/reference/standards/agents.md) (trigger `agents`).
 3. Keep corrections repeated in two features, a judgement call made twice, or a defect class seen twice; drop one-off preferences, task-specific detail, generic advice.
+   Broad mode also proposes **retirements**: a rule found via a `rite-learn: accepted`
+   marker whose cited failing case or owner no longer exists in live source, whose
+   review-by date passed unverified, or that is a model-default no-op. Zero is valid but
+   names the searched scope; a rule still guarding a live failing case is never retired.
 4. Verify claims against live authoritative sources; state currentness signal, applies/does-not-apply scope, `unknown` where unverifiable.
    **Research promotion requires:** each external claim carries a dated citation per
    [[`tooling.md`](../devrites-lib/reference/standards/tooling.md) § Research provenance](../devrites-lib/reference/standards/tooling.md#research-provenance-staleness-and-cost).
@@ -44,6 +54,20 @@ of one authority; it cannot promote a rule alone.
   conversation or on an unmerged branch is lost and will be re-litigated.
   **Failing case:** the same rejected proposal returns next round because no tracked
   entry exists.
+- Every disposition entry carries the fixed marker `rite-learn: accepted` or
+  `rite-learn: declined`, its evidence refs, and (accepted) owner path plus a review-by
+  date. A later round reuses a matching declined record instead of re-proposing.
+- A lesson needs an **external signal** (user correction, failing test/gate, review
+  finding) with its source; self-critique or model reflection alone never changes guidance.
+- Promotion path is fixed: lesson → artifact type (retrospector class) → one canonical
+  owner → human approval of the exact edit. A skipped stage is no promotion.
+- **Recurrence ⇒ mechanism.** When `Authority: existing <path>` already holds the violated
+  rule, the candidate is a check, gate, template slot, or default at that owner
+  ([`skill-authoring.md`](../devrites-lib/reference/standards/skill-authoring.md#match-form-to-failure) § Match form to failure),
+  never a reworded, bolder, or relocated copy; otherwise record `no mechanical form
+  possible: <reason>` and narrow the proposal. An unwired or broken existing check is
+  itself the candidate. **Failing case:** a round accepts a bolder copy of an `AGENTS.md`
+  rule that two archived features already violated.
 - A lesson proposing a new recurring check names its **controls**: the real past
   instance it would have caught (positive) and a near-miss class it must not fire on
   (negative). **Failing case:** a trigger patterned on an imagined command that never
@@ -52,17 +76,23 @@ of one authority; it cannot promote a rule alone.
 - A proposal names the **retrospective failing case**: the concrete past feature/artifact the
   rule would have caught. None → generic advice — drop.
 - ≤3 accepted lessons per round; proposals extend/narrow but never lower an existing bar (revisions show old text beside new); duplicates consolidate into one canonical edit — simplification (deletions/merges) counts toward the cap.
+  Net growth cap: a round adds at most 3 net rules across all owners (additions minus
+  retirements). A round whose approved edits add net bytes to an owner states the
+  retirement search it ran.
 - An accepted lesson ships with a **follow-through owner and deadline**: the exact edit
   lands in the named canonical file in the same round; a lesson unapplied at round end
   returns to candidates with its blocker recorded. **Failing case:** an accepted lesson
   with no applied edit and no recorded blocker — promotion failed; re-raise it.
+  Still unapplied at a second round end, it becomes an apply-or-decline decision; a
+  decline takes the `rite-learn: declined` record, so no lesson is carried a third time.
 
 ## Output
 
 ```text
 Done: reviewed <scope>.
 Changed: none (proposal only)
-Candidate: <specific proposal or none>
+Candidate: <specific proposal | none | NOT-RUN (unavailable: <reason>)>
+Retirements: <candidates | none — searched <scope>>
 Currentness: <live source + signal | unknown>
 Scope: applies <trigger>; does not apply <boundary>
 Authority: existing <path|none>; canonical <path>; consumers/discovery <route>
@@ -70,5 +100,5 @@ Disposition: <no conflict | update/narrow/replace/retire path + reason>
 Evidence: <feature/file references>
 Awaiting: <approval for exact edits | none>
 Next: <single action>
-Record: <nearest owning decisions file | chat-only>
+Record: <nearest owning decisions file | chat-only only when the round made no accepted/declined disposition>
 ```

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

@@ -63,7 +63,8 @@ Before classifying any Reslice, read `.pi/skills/devrites-lib/reference/standard
    dependency's current API surface, consult context7 if available.
 2. **Pick the mode** (`$ARGUMENTS` or infer): Apply the marked action before writes and
    retain its decision/coverage evidence.
-   - **decompose:** first/again break the feature into vertical slices.
+   - **decompose:** break an already-sliced feature into vertical slices again. With no
+     `SLICE-###` in `tasks.md`, stop and route to `/rite-define`; first-pass decomposition is its.
    - **reslice:** a slice is too large; split into thinner end-to-end slices.
    - **repair:** a Spec Drift Guard event; fold the resolution into plan + tasks.
    - **reorder:** fix the dependency order.

package/pack/generated/pi/skills/rite-plan/reference/task-breakdown.md

@@ -38,6 +38,12 @@ This reference owns decomposition; the shared schema owns field names and meanin
   called `clearLayers()` in slice 3 and `clearFullLayers()` in slice 7 is a planning bug:
   name shared symbols once, here.
 - Don't pre-write code in the task: describe the outcome, not the implementation.
+- **Read the fields, not the title.** A slice fails Vet (`kind: contract`, Important, field
+  quoted) when its `Goal` or `Done condition` names an activity instead of an observable end
+  state ("implement backend", "add tests", "handle errors", "wire up UI"); when a no-op or
+  wrong diff could meet the `Done condition` ("tests pass", "works correctly"); or when
+  `Tests/proof` names no specific test or assertion ("run the suite"). **Failing case:**
+  `Goal: Implement export backend · Done condition: tests pass · Tests/proof: go test ./...`.
 - Don't bundle "while we're here" work into a slice. That's scope creep; log it as a
   follow-up instead.
 - Don't slice to a target number: the count comes from the capabilities + the sizing

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

@@ -63,12 +63,18 @@ Incomplete comparison is **not** agreement. Record axis deltas in `polish-report
    Then read the explicit or active workspace's `state.md` directly.
 1. **Read** `state.md`, `touched-files.md`, the current candidate digest, and the
    `git diff` for the active workspace (or `$ARGUMENTS` if a target was given).
-2. **Detect UI scope:** UI is touched if the diff or `touched-files.md`
-   contains any of: `.tsx`, `.jsx`, `.vue`, `.svelte`, `.html`, `.css`,
+2. **Detect UI scope:** UI is touched when the diff changes rendered output:
+   markup, template, style, design token, client component, or a visible string
+   (including an API error message shown in the UI). These paths are leads to
+   inspect, not the predicate: `.tsx`, `.jsx`, `.vue`, `.svelte`, `.html`, `.css`,
    `.scss`, `.sass`, `.less`, `.styl`, component dirs (`components/`,
    `pages/`, `routes/`, `app/`, `views/`, `screens/`), Storybook stories,
-   or design-token files. When in doubt, look for visual changes that need
-   verification.
+   or design-token files; when in doubt whether output changes, treat it as UI
+   scope. A diff with no rendered-output change records
+   `UI scope: none (no rendered output)` and skips Phases 3–4; non-visual client
+   code still gets frontend engineering review (`devrites-code-reviewer` frontend lane).
+   **Failing case:** an `app/services/billing.rb` diff opens Phase 4 and demands
+   captures.
 3. **Always** read [`reference/code.md`](reference/code.md) and assess **Phase 1
    (code polish)**; if backend was touched, assess **Phase 2 (backend polish)** from
    the same file. Reconcile the findings, then send accepted corrections as one bounded

package/pack/generated/pi/skills/rite-polish/reference/anti-ai-slop.md

@@ -10,50 +10,72 @@ Tells of generic LLM-generated work — in **UI** and in **code**. Applies at tw
 Avoid these unless the project's existing system explicitly uses them. When in doubt,
 match the neighbors.
 
+## UI admission rule (tells are leads, not findings)
+Build avoids every UI entry; review and polish admit a hit only by this rule. Classes:
+**ENG** (engineering/realism), **A11Y** (WCAG 2.2 SC or platform requirement), **DS**
+(binding only where project tokens, components or `design-brief.md` declare it), **AES**
+(optional aesthetic). A hit is a finding only with cited mismatch evidence: it contradicts
+a declared token, brief line or nearest neighbour (cite both locations), or it has a
+measured user consequence (contrast ratio, overflow, CLS, lost or hidden focus). Otherwise
+it is an AES proposal under "Proposals (non-blocking)": never a Visual Verdict FAIL, never
+scored, capped at Suggestion/Minor, never blocking unless `design-brief.md` adopts it (then
+DS). Act on clusters per [`prose-style.md`](../../devrites-lib/reference/standards/prose-style.md).
+A broken task, data loss or misleading state is reported and fixed before any AES item.
+**Failing case:** `tokens.css` declares Inter and a 20 px card radius, yet review files
+"reflex font" and "balloon radius" as Important; or three eyebrows on six sections become
+a FAIL row with no brief conflict.
+
+**UI-copy boundary.** Craft owns functional copy: action-named controls, errors with cause
+and recovery, next-step empty states, product vocabulary, fit under expansion, and an
+accessible name containing the visible label (SC 2.5.3, A11Y). Long-form product text
+routes to `devrites-prose-craft`; translation catalogs stay untouched without their owner.
+
 ## UI anti-slop (banned defaults)
-- Default **purple/blue gradients** as the brand look. Special case: any
+- [AES] Default **purple/blue gradients** as the brand look. Special case: any
   hero hex in the `#6366f1 → #a855f7 → #ec4899` family applied as a default.
-- **Gradient text** (`background-clip: text`) used decoratively on headings.
-- **Glassmorphism** (`backdrop-filter: blur(...)` on translucent panels) as
+- [AES] **Gradient text** (`background-clip: text`) used decoratively on headings.
+- [AES] **Glassmorphism** (`backdrop-filter: blur(...)` on translucent panels) as
   a default surface.
-- **Side-stripe colored borders** on cards/sections — the
+- [AES] **Side-stripe colored borders** on cards/sections — the
   "tiny-bar-of-meaningful-accent-color-on-the-left" pattern. Distinctive
   templating tell.
-- **Pure `#000` / `#fff`** as raw text or background — too clinical; use
+- [AES] **Pure `#000` / `#fff`** as raw text or background — too clinical; use
   near-black/near-white tokens (`oklch(0.18 0 0)` / `oklch(0.98 0 0)` or
   the project's surface tokens).
-- **All-CAPS body text** for paragraphs/labels. Reserve uppercase for short
+- [AES] **All-CAPS body text** for paragraphs/labels. Reserve uppercase for short
   micro-copy (badges, eyebrows); never for sentences.
-- **Em-dashes in UI copy — zero.** Soft limits ("use sparingly") get ignored; the rule
-  is binary and greppable: no `—` in any visible string. Use a comma, period, or colon.
-- **Cards inside cards** — nested bordered/elevated containers.
-- **Identical card grids** for everything, regardless of content.
-- A **generic rounded-square icon tile** above every heading/section.
-- **Gray text on colored backgrounds** (fails contrast, looks templated).
-- The **hero-metric cliché** — three big numbers in a row with no real meaning.
-- **Decorative bounce / elastic easing** on everything; motion without purpose.
-- **Reflex fonts** picked because they're the default in a tutorial:
+- [AES] **Em dashes in UI copy** are a lead, not a ban: DS only where the project's
+  style guide bans them; otherwise no rule applies to product copy, because
+  [`prose-style.md`](../../devrites-lib/reference/standards/prose-style.md) governs DevRites
+  prose, not product UI.
+- [AES] **Cards inside cards** — nested bordered/elevated containers.
+- [AES] **Identical card grids** for everything, regardless of content.
+- [AES] A **generic rounded-square icon tile** above every heading/section.
+- [A11Y] **Gray text on colored backgrounds** — a finding with the measured ratio (SC 1.4.3).
+- [AES] The **hero-metric cliché** — three big numbers in a row with no real meaning.
+- [AES] **Decorative bounce / elastic easing** on everything; motion without purpose.
+- [AES] **Reflex fonts** picked because they're the default in a tutorial:
   - Inter for every product when the project has its own choice.
   - **DM Sans**, **Plus Jakarta Sans**, **Fraunces**, **Newsreader** when
     they're not the project's actual type system.
   Match the project; don't reach for the "tasteful default" of 2024.
-- **Modal-first thinking** — reaching for a modal as the answer to every interaction.
-- **Ghost-card** — a `1px` border *and* a soft (blur ≥16px) shadow on the same element.
+- [AES] **Modal-first thinking** — reaching for a modal as the answer to every interaction.
+- [AES] **Ghost-card** — a `1px` border *and* a soft (blur ≥16px) shadow on the same element.
   Borders separate; shadows lift — pick one
   ([`quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md) — Materiality).
-- **Balloon radius** — `border-radius` above ~16px on cards, inputs, panels. Cards top
+- [AES] **Balloon radius** — `border-radius` above ~16px on cards, inputs, panels. Cards top
   out around 12–16px; full pills are for tags and buttons only.
-- **Uppercase tracked eyebrow above every section** — one named kicker is voice; one per
+- [AES] **Uppercase tracked eyebrow above every section** — one named kicker is voice; one per
   section is template grammar (countable cap below).
-- **Numbered-section scaffolding** (`01 / 02 / 03`) when the sections aren't a sequence.
-- **Fake UI-in-a-div** — a "product screenshot" assembled from nested divs, or hand-drawn/
+- [AES] **Numbered-section scaffolding** (`01 / 02 / 03`) when the sections aren't a sequence.
+- [ENG] **Fake UI-in-a-div** — a "product screenshot" assembled from nested divs, or hand-drawn/
   sketchy SVG scenery. Ship a real capture/asset or nothing (quality-standards — Materiality).
-- **Hero prop badges** — version labels (`V0.6`, `BETA`) and decorative pulsing status
+- [AES] **Hero prop badges** — version labels (`V0.6`, `BETA`) and decorative pulsing status
   dots as set dressing.
-- **Unstyled UA chrome** — shipping the browser's default blue selection, caret,
-  scrollbar, or focus outline as the look (quality-standards § Browser chrome).
-- **Invented metrics** — precise-looking numbers with no source (`+247% faster`,
-  `99.99% uptime`). **Off-token color** — a hex used inline that the token set doesn't
+- [AES] **UA chrome** — default selection, caret or scrollbar; the UA focus ring is a
+  finding only when SC 2.4.7/1.4.11 fails (quality-standards § Browser chrome).
+- [ENG] **Invented metrics** — precise-looking numbers with no source (`+247% faster`,
+  `99.99% uptime`). [DS] **Off-token color** — a hex used inline that the token set doesn't
   define. Both are realism failures, not styling choices.
 
 ### Required remediations (fix the hit, don't just flag it)
@@ -65,11 +87,11 @@ an incomplete finding.
 | Default purple/blue gradient; gradient text; glassmorphism default | Re-derive from the scene sentence and colour commitment, then re-run both category-reflex tests |
 | Invented metric | Replace with the state lattice's missing-data placeholder (quality-standards § Focus & states) plus a "metric to confirm" question, or delete the proof slot |
 | Off-token color | Lift into the token set as a named color; replace every inline use |
-| Wrapping CTA / nav overflow | Shorter label, `white-space: nowrap`, or a collapsed nav — never a shrunken tap target |
-| Horizontal scroll in 320–1920 | `minmax(0, 1fr)` on content tracks + `overflow-x: clip` on `html`/`body` (quality-standards § Responsive) |
+| Wrapping CTA / nav overflow | Shorter label or a collapsed nav, verified at 200% text zoom — never `white-space: nowrap` or a shrunken tap target |
+| Horizontal scroll in 320–1920 | Fix intrinsic sizing (`minmax(0, 1fr)`, wrapping, media constraints) with the bounded exception of quality-standards § Responsive — never `overflow-x: clip` on `html`/`body` |
 | Fake UI-in-a-div screenshot | Ship a real capture/asset or remove the block |
 | Sticky sub-nav hidden by a banner | Offset by the banner's token height; split z-index roles instead of one raised value |
-| Unstyled UA selection / focus ring / caret / scrollbar | Theme from tokens per quality-standards § Browser chrome, or decline in `design-brief.md` |
+| UA focus ring failing SC 2.4.7/1.4.11 | Apply the DS focus-ring token per quality-standards § Browser chrome |
 
 ### Copy & data realism
 Placeholder content is a tell even when the layout is clean: fake-perfect numbers
@@ -101,14 +123,15 @@ second one catches what the first one misses.
 Both pass = the surface looks like *this product*, not "an app in this category".
 
 ### Mechanical pre-flight (countable — run, don't vibe)
-Each is pass/fail by counting or grep, not judgment:
-- **Em-dashes** in visible UI strings: exactly **0**.
-- **Eyebrows** (uppercase-tracked kickers): ≤ `ceil(sections / 3)`.
-- **Layout families** (hero, image+text split, card grid, bento, table…): no family more
+Each is counted or grepped, not judged. ENG and DS rows pass or fail; an AES count past
+its cap is a lead for the admission rule, not a failure:
+- [AES] **Em dashes** in visible UI strings: counted; DS only where the style guide bans them.
+- [AES] **Eyebrows** (uppercase-tracked kickers): ≤ `ceil(sections / 3)`.
+- [AES] **Layout families** (hero, image+text split, card grid, bento, table…): no family more
   than twice per page; never 3 consecutive image+text zigzags.
-- **Icons**: 0 emoji-as-icon; exactly one icon set imported.
-- **State presence in code**: default+hover+focus-visible+active+disabled for every interactive element; loading/error/empty where data delays or fails — an unreachable state's screenshot proves nothing.
-- **Form inputs**: no border-width shifts between states; focus ring from outline/ring (not border swap); consistent control height; reserved helper slot; disabled beyond opacity alone.
+- [DS] **Icons**: 0 emoji-as-icon; exactly one icon set imported.
+- [ENG] **State presence in code**: every state the role lattice requires (quality-standards § Focus & states) — an unreachable state's screenshot proves nothing.
+- [ENG] **Form inputs**: no border-width shifts between states; focus ring from outline/ring (not border swap); consistent control height; reserved helper slot; disabled beyond opacity alone.
 
 ## Code anti-slop (UI **and** backend)
 - **Over-defensive checks** — `if (x && x.length > 0)` repeated, layered null guards,

package/pack/generated/pi/skills/rite-polish/reference/harden-checklist.md

@@ -55,7 +55,8 @@ might miss.
 - **Screen reader:** every control has a name; live regions for async
   feedback; reading order matches visual order.
 - **Reduced motion:** `prefers-reduced-motion` removes non-essential motion
-  (no auto-carousel, no spring entrances).
+  (no auto-carousel, no spring entrances); auto-moving content over 5 s pauses under any
+  preference ([`quality-standards.md`](../../devrites-frontend-craft/reference/quality-standards.md) § Motion).
 - **High zoom:** 200% text zoom; layout doesn't break, nothing overflows.
 
 ## 4. Localisation / i18n

package/pack/generated/pi/skills/rite-polish/reference/ui.md

@@ -50,6 +50,13 @@ Goal: this feature looks and behaves like it belongs in *this* product.
    components, align flow shape with neighbors, consolidate duplication, remove
    obsolete styles created by this feature. Ask the user when a design-system
    principle is genuinely ambiguous: don't guess the system's intent.
+4. **Protected contracts:** normalization never changes URL slugs or anchors, form
+   field `name`/`autocomplete`/order, analytics or test IDs, or legal/consent copy
+   unless `spec.md` or `decisions.md` names the change. The wright contract lists
+   these identifiers, the returned diff is checked against them, and visible-label
+   renames are recorded in `polish-report.md`. **Failing case:** polish renames
+   `name="email"` to `emailAddress`; autofill and analytics break while role-query
+   tests pass.
 
 ## Phase 4: UI polish
 
@@ -74,7 +81,7 @@ path isn't polish.
 - [ ] **Alignment** perfect at every breakpoint
 - [ ] **Typography** hierarchy consistent; line length sane (65-75ch prose)
 - [ ] **Color & contrast**: semantic roles; text ≥ 4.5:1 (≥ 3:1 large/UI), WCAG 2.2 AA
-- [ ] **All interaction states**: hover, active, focus, disabled, selected
+- [ ] **All states** the role lattice requires (quality-standards § Focus & states)
 - [ ] **Focus states visible** and **keyboard navigation** works
 - [ ] **Loading** states clear; **empty** states welcoming with a next action
 - [ ] **Error** states helpful (what happened + how to recover); **success** states clear
@@ -82,7 +89,7 @@ path isn't polish.
 - [ ] **Copy & terminology** consistent with the product's vocabulary
 - [ ] **Icons** consistent set, properly sized and aligned
 - [ ] **Responsive** behavior correct across target viewports
-- [ ] **Target size** ≥ 24×24px (WCAG 2.2 AA); ≥ 44×44px for primary touch; **no drag-only** actions
+- [ ] **Target size** ≥ 24×24px (WCAG 2.2 AA); 44×44px for primary touch is a DS preference; **no drag-only** actions
 - [ ] **Motion** smooth (~60fps), purposeful; **reduced-motion** respected
 - [ ] **Performance basics:** no obvious jank, oversized images, or blocking work
 - [ ] **No console errors or warnings**
@@ -105,7 +112,9 @@ Cite the evidence in `browser-evidence.md`.
 ### Triage
 
 If it ships in 30 minutes, fix what users will notice (hierarchy,
-states, broken layout, bad copy) before micro-spacing. Don't introduce bugs
+states, broken layout, bad copy) before micro-spacing. A broken task, data loss or
+misleading state outranks every AES proposal
+([anti-ai-slop.md](anti-ai-slop.md) admission rule); AES work waits while one is open. Don't introduce bugs
 while polishing: re-prove after changes.
 
 ### Refinement modes (optional dials within Phase 4)

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

@@ -4,7 +4,7 @@ description: Project-grounded verdict for adopting, switching, rejecting, or rev
 argument-hint: "[candidate/link/question]"
 user-invocable: true
 ---
-<!-- loads: {"always":["devrites-lib/reference/standards/core.md"],"workspace":["decisions.md"]} -->
+<!-- loads: {"always":["devrites-lib/reference/standards/core.md","devrites-lib/reference/standards/tooling.md"],"workspace":["decisions.md"]} -->
 > Read-set manifest: `devrites-engine context [slug] --skill rite-pov` bundles every file named below into one deduplicated read.
 
 # /rite-pov: project-grounded external verdict
@@ -22,7 +22,12 @@ named outside candidate.
    incumbent dependency/call site, integration seam, relevant ADR/decision, or
    confirmed absence. No profile cache.
 3. Verify the external claim from current primary documentation, source,
-   advisory, or release notes.
+   advisory, or release notes, cited with URL, version or advisory id, and
+   retrieval date ([`tooling.md`](../devrites-lib/reference/standards/tooling.md) citation contract). A CVE verdict also needs the
+   installed version from the lockfile (`path:line`) checked against the
+   advisory's affected range, and a call-site search for the affected API
+   (`reachable` / `unreachable` / `unknown`). Known exploitation (a KEV listing)
+   raises priority, never severity.
 4. Compare fit, existing alternatives, migration cost, reversibility, project
    principles, security, licensing, and deprecation risk.
 5. Return exactly one verdict: `Adopt`, `Trial`, `Hold`, `Reject`, or
@@ -37,7 +42,8 @@ named outside candidate.
 Verdict: <grade> — <one sentence>
 Tier: <two-way | bounded-one-way | high-stakes>
 Project evidence: <file:line or local doc>
-External evidence: <primary source>
+External evidence: <URL — version/advisory id — retrieved YYYY-MM-DD>
+CVE applicability: <n/a | range in/out (lockfile path:line); reachability reachable/unreachable/unknown>
 Why: <three bullets max>
 Next: <one action | done>
 Record: <path | not written>
@@ -57,4 +63,9 @@ before any `Adopt`/`Trial`.
 - Missing project evidence or missing live primary source → `Hold`. **Failing
   case:** "Adopt Redis" with no incumbent call site and no opened docs URL.
 - High-stakes / irreversible without a named rollback → cannot be `Adopt`.
+- A citation missing version or retrieval date, or a CVE verdict missing range
+  evidence → `Hold`. `Not-our-problem` for a CVE needs out-of-range or
+  `unreachable` evidence. **Failing case:** "Not-our-problem: we don't call that
+  function" with no call-site search, or "Adopt upgrade" while the lockfile already
+  pins a fixed version.
 - Persist only when asked; a chat-only verdict is not a decision record.

package/pack/generated/pi/skills/rite-pr-feedback/SKILL.md

@@ -22,7 +22,11 @@ Step 0: Read [`core.md`](../devrites-lib/reference/standards/core.md), plus [`gi
 - Never resolve a thread without a reply that names what happened.
 
 ## Workflow
-1. **Locate PR/thread.** Argument URL = targeted thread; PR number = all unresolved threads on that PR; blank = current branch PR via `gh pr view`. Stop if `gh` is unavailable.
+1. **Locate PR/thread.** Argument URL = targeted thread; PR number = all unresolved threads on that PR; blank = current branch PR via `gh pr view`. Stop if `gh` is unavailable. Each stop below quotes the failing command's output and names one recovery command; never substitute another branch's or the most recent PR:
+   - `gh auth status` fails → unauthenticated; recovery `gh auth login`.
+   - `git symbolic-ref -q HEAD` fails → detached HEAD (step 5 cannot push); recovery `gh pr checkout <number>` or `git switch <branch>`.
+   - blank argument and `gh pr view` finds no PR for the branch → recovery `/rite-pr-feedback <number>` for an existing PR, or `gh pr create`.
+   **Completion:** exactly one PR (and thread, for a URL) located, or one named stop reported.
 2. **Fetch.** Use GitHub GraphQL/CLI to collect unresolved review threads with file, line, author, body, and thread id. Completion: every unresolved thread is represented once, or the fetch error is reported.
 3. **Legitimacy gate.** For each item, read the surrounding code and classify: `fix`, `not-addressing`, `declined`, `reply-only`, or `needs-human`. Deduplicate overlapping items.
 4. **Fix approved items.** Apply contained fixes, add/update tests when behavior changes, and run targeted checks. Larger product/API/security calls become `needs-human`.