feat(v3.4.13): partner column, version release cascade, client UX fixes

- HQ stores: partner column uses companyName/name/phone via partnerOptionLabel

- Dev plan: version RELEASED auto-marks tasks RELEASED and tickets PUBLISHED with releasedVersionNo

- mini-user/h5-shop/h5-partner v3.4.13 UX fixes (store UI, iOS scan OAuth, partner login guard)

- Docs: v3.4.13 dev doc + status audit updates

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

server/dukang-api/prisma/schema.prisma

@@ -107,6 +107,7 @@ enum SupportTicketStatus {
   DEVELOPING
   TESTING
   PASSED
+  PUBLISHED
 }
 
 enum SupportTicketPriority {
@@ -671,6 +672,8 @@ model CommonSupportTicket {
   reviewedAt   DateTime?            @map("reviewed_at") @db.DateTime(3)
   remark       String?              @db.VarChar(512)
   attachmentUrls Json?              @map("attachment_urls")
+  releasedVersionNo String?         @map("released_version_no") @db.VarChar(32)
+  publishedAt  DateTime?            @map("published_at") @db.DateTime(3)
   createdAt    DateTime             @default(now()) @map("created_at") @db.DateTime(3)
   updatedAt    DateTime             @updatedAt @map("updated_at") @db.DateTime(3)
   completedAt  DateTime?            @map("completed_at") @db.DateTime(3)
@@ -678,6 +681,7 @@ model CommonSupportTicket {
   @@index([status, createdAt])
   @@index([ticketType, status])
   @@index([creatorId])
+  @@index([releasedVersionNo])
   @@map("common_support_ticket")
 
   devPlanTasks DevPlanTask[]