Backend migration Lovable Cloud → Supabase + full decoupling (short mission)

My web app (frontend: Vite/React/TS/Tailwind/shadcn) currently runs its backend on Lovable Cloud. I want it migrated to my own Supabase project and the whole stack made fully self-contained from my GitHub repo, with no dependency on Lovable whatsoever. One thing that's easy: no real users to migrate (just my admin account, which I'll recreate) → no password migration, no OAuth re-linking. Scope: replay the schema (existing migrations) on my Supabase, RLS, edge functions, storage (low/none), repoint the frontend (.env + TS types), recreate the admin account. This is a like-for-like migration, no new features. Two non-negotiables: Zero regression: functional parity with the current app. Zero data leaks: RLS tested (deny by default, each account sees only its own data), nothing exposed via the anon key, service_role and secrets never on the frontend or in the repo, .env untracked. Short verification report on delivery. Done when: I clone the repo + connect my Supabase → the app runs end-to-end without Lovable, and the database is reproducible via supabase db push. Profile: solid Supabase (Auth, RLS, Edge Functions, Storage, CLI) + strong security practices. Hands-on Lovable Cloud experience is a big plus (cite a specific case). In your proposal: a similar project you've done + your price and timeline + how you guarantee zero regression and zero leaks.