04-core-verify-interactive-web-elements-before-claiming-completelisted

# Verify Interactive Web Elements Before Claiming Complete **TERMINATION RULE**: Nothing is complete until every interactive element on every affected page/feature has been clicked and verified. Page loads are NOT verification. If a step is blocked by missing ARIA semantics, fix the page first, then resume. 1. **WEB PAGES**: For every page use the **chrome-devtools MCP** (Chrome) - call the snapshot tool after every load/click/form/modal/nav/error and prove a visible diff. See reference/verification-protocol.md. Verify tool names against the live server at execution time (see `04-core-use-chrome-devtools-mcp-for-browser-automation`). 2. **CRUD**: For every entity run the full create-read-update-delete cycle, each verified against a `SELECT` and a snapshot. See reference/verification-protocol.md. 3. **API ENDPOINTS**: For every endpoint send valid, missing-field, wrong-type, unauthenticated, empty, oversized, SQL-injection, and HTML/script payloads. See reference/verification-protocol.md. 4. **BUILDS / LINTS / TYPECHECKS**: Run the command, print the exit code, fix every error, never proceed on non-zero. See reference/verification-protocol.md. 5. **CROSS-CUTTING (every page)**: Zero console errors, toasts, validation, loading states, responsive, dark mode, tab title. See reference/verification-protocol.md. 6. **DETERMINISTIC FINAL PASS (AGENTS.md rule 14)**: For anything visual or visually-inspectable, the LAST step before declaring done OR deploying is driving EVERY affecte