Replace the prisma migrate deploy subprocess with a custom applyMissingMigrations() that reads each migration SQL file and runs it via prisma.$executeRawUnsafe. This avoids the Prisma CLI aborting when the restored _prisma_migrations table contains orphaned entries (migration names that no longer have a corresponding file in the migrations folder). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>