lovable-cloud-migration-sync

To sync duplicate Supabase migrations, you must detect unapplied original migration files, verify their equivalence against Lovable-created duplicates, run a local database reset, execute your verify command, and replace originals via PR only after tests pass.

Lovable Cloud leaves your database in a mismatched state because it only executes Supabase migrations it created, skipping original migrations authored by engineers or other bots, which causes logic and security drift without proper duplicate synchronization.

You verify Lovable duplicate migrations are safe by diffing each duplicate against its original to check for security-critical or logic-changing differences, ensuring only acceptable cosmetic or idempotency deltas exist before replacement.

No, you must not delete original Supabase migration files before running database reset and verify commands, because deletion is only permitted after a PASS result to prevent logic and security drift during the reconciliation pipeline.

The correct Lovable migration sync workflow requires dependency-ordered inspection of migration files, non-regenerated PR-comment usage, executing supabase db reset through the correct session path, running verify commands, and deleting originals only after PASS.

No, this migration sync workflow is specifically designed for projects using Supabase migrations where Lovable Cloud enforces safety during migrations, requiring dependency-ordered inspection and local database reset capabilities.