rite-provelisted

# /rite-prove: prove the completed feature Record evidence for the **whole feature**. Read the active workspace first; if none, run `/rite-spec <feature>`. > **Scope:** built-in `/verify` proves one change and `/run` launches the app. > `/rite-prove` covers a feature. It walks `spec.md` acceptance > criteria one-by-one, runs the full relevant test suite + build/typecheck/lint, > ascends the browser-proof ladder (step 4), > and writes `evidence.md` + `browser-evidence.md` keyed to the active > `.devrites/work/<slug>/`. No DevRites workspace → use `/verify` or `/run` alone. ## Gate: all slices must be built first Read `tasks.md` + `state.md`. **If ANY slice is still pending/unbuilt, STOP** and tell the user to finish it with `/rite-build`: `/rite-prove` runs once, when the full task is complete, not after each slice. (Each slice already got its own targeted tests during `/rite-build`; this phase proves the assembled feature as a whole.) **Never report an unobserved pass.** If a command could not run, report that and give exact manual steps. **Scoped reruns are allowed.** `/rite-prove` runs once when the full feature is assembled. After `/rite-polish` or `/rite-review` edits code, the existing `evidence.md` no longer post-dates the change, so re-run `/rite-prove` over the affected criteria/routes to refresh proof before `/rite-seal`. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull these via `Read` when relevant: - `testing.m