Revert "PHP Rebuild"

This reverts commit 2ef3654841.

prisma/migrations/20260804202231_phase10_loyalty_card_and_permission_fixes/migration.sql

@@ -0,0 +1,19 @@
+-- AlterTable
+ALTER TABLE `LoyaltyProgramme` ADD COLUMN `cardBorderColor` VARCHAR(191) NULL,
+    ADD COLUMN `cardFont` ENUM('SANS', 'SERIF', 'MONO') NOT NULL DEFAULT 'SANS',
+    ADD COLUMN `cardMemberNumberColor` VARCHAR(191) NULL,
+    ADD COLUMN `cardTopRightText` VARCHAR(191) NULL,
+    ADD COLUMN `cardTopRightTextColor` VARCHAR(191) NULL,
+    ADD COLUMN `cardTopRightTextSize` ENUM('SM', 'MD', 'LG') NOT NULL DEFAULT 'MD',
+    ADD COLUMN `rewardPosition` ENUM('AFTER_ALL_STAMPS', 'FINAL_SLOT_IS_REWARD') NOT NULL DEFAULT 'AFTER_ALL_STAMPS';
+
+-- Stamp-limit enforcement (Phase 10 follow-up brief: "Valid range: 1–10").
+-- Confirmed via a direct read of the live database before writing this
+-- migration that no existing LoyaltyProgramme row has stampsRequired > 10
+-- and no LoyaltyAccount has currentStamps > 10 — safe to add directly,
+-- no data migration needed. Defense-in-depth alongside the identical
+-- 1-10 check in validateProgrammeConfig() and the owner form's client
+-- validation; MySQL 8.0.16+ enforces CHECK constraints (this app's
+-- documented target, see schema.prisma's own header).
+ALTER TABLE `LoyaltyProgramme` ADD CONSTRAINT `LoyaltyProgramme_stampsRequired_range`
+    CHECK (`stampsRequired` BETWEEN 1 AND 10);