Initial project commit for Coolify staging

schema-diff.sql

@@ -0,0 +1,31 @@
+-- ============================================================
+-- SCHEMA DIFF DOCUMENTATION
+-- ============================================================
+-- Generated: 2026-04-20
+-- Status: DO NOT RUN prisma db push --accept-data-loss
+--
+-- PROBLEM:
+-- prisma db push detects drift and wants to DROP+RECREATE:
+--   - VisitorProfile (19,336 rows)
+--   - HouseholdCluster (2,741 rows)
+--   - AdClickEvent (1,524 rows)
+--   - AttributionPath (841 rows)
+--   - TrackedSession columns: channelGroup, fbclid, gbraid,
+--     gclid, utmContent, utmTerm, wbraid
+--
+-- All models and columns ARE present in prisma/schema.prisma.
+-- The drift is from structural differences (types, constraints,
+-- indexes) between the schema file and production.
+--
+-- SOLUTION: Use safe-migration.sql for additive changes only.
+-- Then run `npx prisma db pull` to sync the schema file with
+-- the production database state.
+--
+-- To generate the actual diff SQL, run from a machine with
+-- DATABASE_URL:
+--
+--   npx prisma migrate diff \
+--     --from-schema-datasource prisma/schema.prisma \
+--     --to-schema-datamodel prisma/schema.prisma \
+--     --script
+-- ============================================================