feat build

apps/api/release/migrations/20260916141751_add_retail_customer_kind/migration.sql

@@ -0,0 +1,8 @@
+-- Placeholder: the original migration.sql for this migration was lost from
+-- disk (directory existed but was empty) while the database's
+-- _prisma_migrations ledger already recorded it as applied and finished.
+-- Recreated as an empty no-op file, then registered via
+-- `prisma migrate resolve --applied`, so Prisma tooling stops blocking on
+-- P3015 without re-running or guessing at SQL that already ran against this
+-- database. The actual schema effect (CustomerKind.RETAIL) is present in
+-- schema.prisma and already exists in the live database.

apps/api/release/migrations/20260917120000_customer_name_parts_and_percent/migration.sql

@@ -0,0 +1,12 @@
+-- Placeholder: this migration is recorded as applied in the database's
+-- _prisma_migrations ledger, but no migration.sql for it ever existed on
+-- disk in this checkout (added Customer.firstName/lastName/productPercent
+-- directly against the live DB, schema.prisma was never regenerated from it
+-- as a tracked migration). Recreated as an empty no-op file purely so Prisma
+-- CLI tooling (migrate status/dev) stops blocking on a missing-migration
+-- error. Does not re-run or alter anything — the columns already exist live.
+--
+-- NOT reconciled with schema.prisma: Customer.firstName, Customer.lastName,
+-- Customer.productPercent exist in the database but have no field in
+-- prisma/schema.prisma's Customer model. This is a pre-existing drift,
+-- separate from this change, and should be looked at on its own.

apps/api/release/migrations/20260918090000_customer_parent_agent_self_relation/migration.sql

@@ -0,0 +1,12 @@
+-- Placeholder: this migration is recorded as applied in the database's
+-- _prisma_migrations ledger, but no migration.sql for it ever existed on
+-- disk in this checkout (added Customer.parentAgentId + Customer.birthDate
+-- directly against the live DB; schema.prisma was never regenerated from it
+-- as a tracked migration). Recreated as an empty no-op file purely so Prisma
+-- CLI tooling (migrate status/dev) stops blocking on a missing-migration
+-- error. Does not re-run or alter anything — the columns already exist live.
+--
+-- NOT reconciled with schema.prisma: Customer.parentAgentId,
+-- Customer.birthDate exist in the database but have no field in
+-- prisma/schema.prisma's Customer model. This is a pre-existing drift,
+-- separate from this change, and should be looked at on its own.

apps/api/release/migrations/20260918120000_add_product_image_role/migration.sql

@@ -0,0 +1,5 @@
+-- CreateEnum
+CREATE TYPE "ProductImageRole" AS ENUM ('FEATURED', 'FEATURED_MOBILE', 'GALLERY', 'GALLERY_MOBILE');
+
+-- AlterTable
+ALTER TABLE "ProductImage" ADD COLUMN "role" "ProductImageRole" NOT NULL DEFAULT 'GALLERY';