fix customer_status trigger passing OLD.status blocks flag toggles

The customers trigger was passing OLD.status='live' to customer_status(),
causing the once-live-stay-live guard to fire on deliberate flag changes
(revoking has_payment_method, confirmed_details_at, allow_onboard_transition).
Pass NULL so the trigger always does a full recompute.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: chatch

sqitch/deploy/0021_corporate_body_customer_status.sql

@@ -119,4 +119,19 @@ END;
 $function$
 ;
 
+-- The customers trigger was passing OLD.status which caused the 'once live, stay live'
+-- guard to fire on deliberate flag toggles (e.g. revoking has_payment_method). Pass NULL
+-- so the trigger always does a full status recompute.
+CREATE OR REPLACE FUNCTION myenergy.customer_status_update_on_trigger() RETURNS trigger
+    LANGUAGE plpgsql SECURITY DEFINER
+    AS $$
+DECLARE
+     new_status myenergy.customer_status_enum;
+BEGIN
+    SELECT myenergy.customer_status(NEW, NULL, NULL) INTO new_status;
+    NEW.status = new_status;
+    RETURN NEW;
+END;
+$$;
+
 COMMIT;

sqitch/revert/0021_corporate_body_customer_status.sql

@@ -110,4 +110,16 @@ END;
 $function$
 ;
 
+CREATE OR REPLACE FUNCTION myenergy.customer_status_update_on_trigger() RETURNS trigger
+    LANGUAGE plpgsql SECURITY DEFINER
+    AS $$
+DECLARE
+     new_status myenergy.customer_status_enum;
+BEGIN
+    SELECT myenergy.customer_status(NEW, OLD.status, NULL) INTO new_status;
+    NEW.status = new_status;
+    RETURN NEW;
+END;
+$$;
+
 COMMIT;