fix: rename the henza brand to montzar

اپ: اصلاح نام برند به منتزر

Co-authored-by: Cursor <cursoragent@cursor.com>

apps/api/prisma/schema.prisma

@@ -473,14 +473,14 @@ model Customer {
   ///
   /// Legacy recorded NO reason: none of its 49 `customers` columns is a
   /// reason/note field, and on rejection it only sent a fixed SMS. So the 14
-  /// rows migrated from henza carry the sentinel
+  /// rows migrated from the legacy system carry the sentinel
   /// «رد شده در سیستم قدیم — فاقد شرح علت ثبت‌شده» instead of NULL, so support
   /// knows why it is blank (owner ruling 2026-10-07). The migration tool
   /// writes it only WHERE this IS NULL, so a re-run cannot overwrite a real
   /// reason entered in the new system.
   verificationRejectionReason String?
 
-  /// NULL for rows migrated from henza — legacy recorded no rejection time.
+  /// NULL for rows migrated from the legacy system — it recorded no rejection time.
   verificationRejectedAt DateTime?
 
   /// Legacy customers.birth_date, populated on 917 of 1,595 rows. Kept for the

apps/api/prisma/seed.ts

@@ -385,10 +385,12 @@ async function main() {
     prisma.category.upsert({ where: { id: 'cat-coins' }, update: {}, create: { id: 'cat-coins', title: 'سکه و شمش' } }),
   ]);
 
+  // Databases seeded before the rename hold the old id; Product/Promotion FKs cascade on update.
+  await prisma.brand.updateMany({ where: { id: 'brand-henza' }, data: { id: 'brand-montzar' } });
   const brandMontzar = await prisma.brand.upsert({
-    where: { id: 'brand-henza' },
+    where: { id: 'brand-montzar' },
     update: { title: 'منتزر طلا' },
-    create: { id: 'brand-henza', title: 'منتزر طلا' },
+    create: { id: 'brand-montzar', title: 'منتزر طلا' },
   });
   const brandArtisan = await prisma.brand.upsert({
     where: { id: 'brand-artisan' },