fix migration production

packages/database/prisma/migrations/20260817190000_remove_stripe_payment_provider/migration.sql

@@ -26,10 +26,13 @@ BEGIN
       AND column_name = 'paymentMethodsEnabled'
   ) THEN
     UPDATE "brand_settings"
-    SET "paymentMethodsEnabled" = ARRAY(
+    SET "paymentMethodsEnabled" = COALESCE(
+      ARRAY(
         SELECT x
         FROM unnest("paymentMethodsEnabled") AS x
         WHERE x::text <> 'STRIPE'
+      ),
+      ARRAY[]::"PaymentProvider"[]
     )
     WHERE EXISTS (
       SELECT 1
@@ -107,15 +110,13 @@ BEGIN
         AND table_name = 'brand_settings'
         AND column_name = 'paymentMethodsEnabled'
     ) THEN
+      -- PostgreSQL rejects subqueries in ALTER ... USING. STRIPE was already
+      -- filtered out above, so a text-array recast is enough.
       ALTER TABLE "brand_settings"
         ALTER COLUMN "paymentMethodsEnabled" TYPE "PaymentProvider_new"[]
         USING (
           COALESCE(
-            ARRAY(
+            "paymentMethodsEnabled"::text[]::"PaymentProvider_new"[],
-              SELECT x::text::"PaymentProvider_new"
-              FROM unnest("paymentMethodsEnabled") AS x
-              WHERE x::text <> 'STRIPE'
-            ),
             ARRAY[]::"PaymentProvider_new"[]
           )
         );

packages/database/scripts/db-deploy.cjs

@@ -155,8 +155,8 @@ async function main() {
       }
 
       // Prisma records a failed transactional migration even after the SQL rolls back.
-      // In local/dev Docker that leftover row blocks every subsequent startup.
+      // That leftover row blocks every subsequent Docker/startup deploy.
-      if (process.env.NODE_ENV === 'production') {
+      if (process.env.DB_DEPLOY_SKIP_FAILED_RETRY === 'true') {
         console.error('[db:deploy] Found failed migrations in a non-empty database. Resolve them manually before deploying again.')
         process.exit(1)
       }