Persistent staging/prod project parity — schema + edge functions + auth sync without ephemeral branching

Problem When running a production app on Supabase, the standard recommendation is to use two separate projects (e.g. my-app-staging and my-app-prod) to maintain isolated environments. This works, but Supabase currently provides no native tooling to keep them in sync. Every schema migration, edge function deploy, auth config change, or RLS policy update has to be manually applied to both projects. The existing Branching feature doesn't solve this because: - Branches are ephemeral — designed for PR previews, not persistent staging environments - Branching is a paid add-on, making it disproportionately expensive for small teams who just need a stable staging environment alongside prod - Branching doesn't cover edge functions or auth configuration parity Database replication also doesn't fit. We don't want data to flow between environments, only schema and configuration. Requested Feature A lightweight "p…