-- 20260319090000_backfill_active_profiles_to_approved.up.sql UPDATEs
-- customer_profiles.status, but that column isn't ADDed until
-- 20260721020000_customer_profiles_status -- four months later in this
-- chain. Any environment bootstrapping fresh via `sqlx migrate run` hits
-- "column status does not exist" at 20260319090000, regardless of whether
-- it's ever seeded by anything else first.
--
-- This runs one migration before that backfill and adds the column early
-- (IF NOT EXISTS, matching 20260721020000's own guard exactly), so that
-- migration and everything after it can proceed. 20260721020000 then
-- becomes a safe no-op when it's reached later in the same run.
ALTER TABLE customer_profiles
    ADD COLUMN IF NOT EXISTS status VARCHAR(50) NOT NULL DEFAULT 'DRAFT';
