rite-provelisted

# /rite-prove: prove the completed feature Prove the **whole feature**. Read the active workspace; if absent, run `/rite-spec <feature>`. > **Scope:** `/verify` proves one change; `/run` launches the app. `/rite-prove` > walks feature acceptance, relevant suite/build/typecheck/lint, and browser > proof, writing evidence under the active workspace. Without one, use > `/verify` or `/run`. ## Gate: all slices must be built first Read `tasks.md` + `state.md`. If any slice is pending, stop for `/rite-build`. This phase proves the assembled feature once, after per-slice tests. **Never report an unobserved pass.** If a command could not run, report that and give exact manual steps. After polish/review edits, rerun affected criteria/routes so evidence binds the changed candidate digest before Seal. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull these via `Read` when relevant: - `testing.md`: pyramid, determinism, no-flake discipline. - `test-proof-checklist.md`: compact proof-quality gate for tests and recorded evidence. - `browser-proof-checklist.md`: required UI states and Visual Verdict evidence. - `spec-grammar.md`: when the spec uses structured `### Requirement:` / `#### Scenario:` blocks, each scenario (WHEN/THEN) is one observable behavior to walk and prove. - `performance.md`: measure first when perf is in scope. - `observability.md`: runtime telemetry must be observed to emit. - `developer-experience.md`: when the cha