verification-quality-gateslisted

# Verification Quality Gates ## Purpose Finish work with real evidence, not assumptions. Verification should match the change type and risk. ## Gate Selection - Run project-native tests, type checks, linters, format checks, and build checks that apply to touched code. - Use `rldyour-lsps` for language-server routing and diagnostics when language support matters. - Use `rldyour-browser` for frontend, UI-visible, browser behavior, responsive, visual, and business-flow changes. - Use `rldyour-security` for auth, authorization, input/output handling, secrets, file handling, dependency/config, payment, admin, or external integration changes. - Use `rldyour-design` for Figma, shadcn/ui, ReactBits, design tokens, FSD frontend placement, and design-system changes. - Use `rldyour-flow` `flow-post-task-sync` when changes should be committed, pushed, documented, or memory-synchronized. ## May 2026 Tooling Defaults **Python:** - Type-checker: **pyright** (default - best speed/spec-conformance ratio, 2-5x faster than mypy with 98% spec coverage). Optionally **ty** (Astral, 10-60x faster, 53% spec) for greenfield speed-first projects. Avoid mypy for new projects. - Lint: **ruff** (canonical - replaces flake8/isort/black/pylint). - Test: **pytest** (canonical, no change). **JavaScript/TypeScript:** - Lint: - **ESLint v9** with flat config - universal default for established codebases (largest plugin ecosystem). - **Biome** - recommended for greenfield projects (24x faster than