Urgent: Fix Next.js EHR Lock Issue

Summary We need an urgent production bug fix in a Next.js app (Vercel + AWS Cognito + Supabase). Login succeeds, but clicking Open EHR shows “Production EHR access locked” (and some EHR paths may 404). Need an experienced developer to trace and fix route guard/middleware/page-lock logic and restore authorized owner access to the EHR route for non-PHI demo testing. Scope / Tasks Reproduce bug in production. Identify exact lock enforcement point (middleware, route guard, or page conditional). Fix lock condition so authorized owner can access /ehr (non-PHI demo mode only). Verify production env var behavior (including NEXT_PUBLIC_RLTH_EHR_DEMO_ENABLED). Fix Open EHR button/link target to valid route (no 404). Deploy and validate with owner login. Provide handoff note: changed files, required env vars, rollback steps. Acceptance Criteria Owner can log in and open EHR dashboard (no lock screen). No EHR route 404 from the primary Open EHR flow. No PHI used in testing. Clear documentation of fix + rollback. Budget/Timeline Fixed price: $100 (consider up to $150 for same-day completion). Start immediately; complete today if possible. Required Experience Next.js production debugging on Vercel AWS Cognito token/session/claims integration Supabase + auth/role-aware gating patterns Screening Questions Share one similar Next.js middleware/route-guard bug you fixed on Vercel. How would you isolate whether this is env, auth claims, or routing in first 60 minutes? Can you complete fixed-price at $100 today Confirm you will provide changed-files list and rollback steps.