-- Safety migration to ensure cached profile columns stay removed.
-- Some environments created an empty migration folder, so deploys failed
-- because Prisma could not find migration.sql. This keeps the history intact
-- while acting as a no-op when the columns already dropped earlier.

ALTER TABLE "public"."users"
  DROP COLUMN IF EXISTS "first_name",
  DROP COLUMN IF EXISTS "last_name",
  DROP COLUMN IF EXISTS "company",
  DROP COLUMN IF EXISTS "phone";

COMMENT ON TABLE "public"."users"
  IS 'Portal authentication only. Profile data fetched from WHMCS via IdMapping.';

