Full-Stack Web Developer (Bug Fixes, Architecture Cleanup + Repo Organization)

I'm the solo founder of CareVoy, a non-emergency medical transportation (NEMT) coordination platform. The product is built and has a working end-to-end loop, but it's grown through rapid iteration and now needs an experienced full-stack developer to standardize the architecture, fix known bugs, and clean up the repository before launch. Stack: Frontend: static HTML/CSS/vanilla JavaScript (four portals: patient, coordinator, driver, admin) Backend: Supabase (Postgres, Auth, Row Level Security) API: Vercel serverless functions (Node.js) using Supabase service-role key for privileged writes Integrations: Stripe, Resend (email), Google Maps/Places/Distance Matrix, Twilio Hosted on Vercel, code in a GitHub repo, developed in GitHub Codespaces Note: the repo also contains a deprecated React Native/Expo mobile app and various working folders/scripts from the build process that need cleanup What I need (in priority order): Repository cleanup and organization. The GitHub repo has accumulated leftover folders, one-off scripts, a deprecated mobile app build, and duplicate/experimental assets from rapid iteration. I need it cleaned into a clear, maintainable structure with only what's actually in use, properly organized, and documented (a clean README explaining the structure). Standardize authentication across all four web portals. Each portal currently authenticates differently (mix of sessionStorage, localStorage, Supabase session tokens, and publishable key). This inconsistency causes login flashes and users getting logged out on refresh. Most other bugs trace back to this — it's a top priority. Fix session token expiry. Portals authenticate database reads with the user's Supabase token, which expires after ~1 hour, breaking queries and bouncing users. Implement proper token refresh or move user-specific lookups to the service-role API pattern already in use. Audit the RLS vs. service-role write pattern for consistency and security across all API endpoints. Fix a documented list of specific bugs: fare calculation pipeline (booking → completion → display), remove hardcoded placeholder values (this is meant to be the live version), coordinator existing-patient picker, coordinator ride-detail view, driver "booked ride not showing," completed-ride fare breakdown, Apple Pay on iOS, and status-timestamp display. Full end-to-end regression test with fresh data across both self-pay and facility-covered flows. I have a detailed written bug list, roadmap, and architecture reference I'll share with the selected candidate. Ideal candidate: Strong with Supabase (Postgres, RLS, Auth) and serverless APIs Comfortable debugging live web apps with browser DevTools Vanilla JavaScript proficiency (no framework — these are plain HTML/JS files) Experience with Stripe and third-party API integrations Good judgment on repo hygiene and project structure Clear communicator who documents their work To apply: Briefly describe your experience with Supabase RLS and authentication architecture, and share one example of a similar debugging or cleanup project. Please start your response with the word "CareVoy" so I know you read this. Include your hourly rate and availability. This is a focused engagement with strong potential for ongoing work as the platform scales.