Excellent writeup. I particularly liked the createApiRouteHandler pattern for keeping Next.js routes thin. How do you usually handle the 'fail-open' scenario for rate limiting and idempotency in production? If Redis is down, do you prioritize system availability over preventing duplicates, or do you have a fallback mechanism to prevent a potential 'retry storm'?