What problem does it solve? Backend contributors risk silently breaking routes, leaking memory, or misconfiguring environments when working on the PalFish GMV FastAPI backend without knowing its architectural contract — most notably the 2026-06-19 indentation incident that silently dropped 10 routes. ## Core Features & Use Cases - Route Registration Contract: Documents the exact register_*_routes(app, _supabase) pattern, module-scope helper rules, and post-merge route count verification commands to catch silent 404s. - Operational Runbooks: Covers local dev startup on Windows, health checks, PostgREST schema cache fixes, Supabase client singleton usage, audit logging, sequential ID generation via RPC helpers, and Render deploys via scripts/deploy.sh. - Incident & Gotcha Knowledge: Records the singleton Supabase client memory leak fix, disabled legacy JWT keys, CORS regex requirements, RBAC role resolution order, and sandbox DingTalk isolation. - Use Case: After merging a PR touching activation_routes.py, run the Tier 1 route-count verification to confirm all 17 activation routes are still registered before deploying. ## Quick Start Ask the assistant to verify that all backend routes are correctly registered after your latest merge to main.py.