rule-verificationlisted

# Verification Rules A task is not done because the code was written. It is done when the check for its type has passed. > **The checks below catch crashes. They do not catch the common case.** Across > 3,127 fix commits in three production repos, runtime crashes were a small > minority; the bulk was code that ran fine and was wrong — a handler nested > where it never fires, four surfaces disagreeing about one number, a cache key > missing the account dimension, a locale holding a translation of the previous > sentence. Work `rule-ramifications` before claiming any of these passed. > Evidence: [`docs/failure-evidence.md`](../../../../docs/failure-evidence.md). ## Scope boundary - **audit** owns: security, a11y, performance, type safety, `console.log`, hardcoded colors, missing states, test gaps. - **brainstorm** owns: new features, dead code removal, file splitting, unused deps, competitor research, UX flow ideas. No overlap. If brainstorm turns up a bug, note it and suggest `audit`. ## Verification by task type | Task | Required before done | |------|----------------------| | Edge Function / API | curl with real params, verify 200 + response shape | | UI (public) | Browser check: page reads correctly and the console is clean | | UI (admin) | typecheck + build only | | Refactor | typecheck + build + existing tests pass | | Bulk change | grep for the old pattern to confirm full elimination | | Auth / Billing / RLS | tests + manual verification of deny-by-default beh