Prevent schema drift and enable safe non-destructive migrations for Supabase/Postgres

Executive Summary

Developers using Prisma and Supabase frequently hit destructive resets and extension drift. Provide a migration safety layer that detects drift, suggests non-destructive fixes, and enforces a history-consistent CI flow. Managed Postgres and serverless DBs like Supabase have rapidly increased adoption while teams push schema changes more frequently, raising the incidence of drift. The source issue demonstrates weekly recurrence and team adoption signals, showing this is an active daily pain for developer teams. Prisma has become a de facto ORM and migration system for many JS/TS teams, so a focused safety and drift-detection layer that plugs into Prisma and CI can immediately reduce labor costs and deployment risk. Integrate with Prisma migration history and Supabase/Postgres metadata to detect drift before applying migrations, synthesize minimal non-destructive migration steps, and enforce a migration-safe CI gate. The GitHub issue shows recurring resets and extension drift across Supabase projects, indicating a focused product can save repeated manual triage for teams using this exact stack. By capturing team's migration history, diffs, and environment policies, the product creates a workflow layer that prevents destructive operations and automates extension handling specific to managed Postgres variants.