@mohasinac/appkit 4.71.0 → 4.72.0

package/dist/features/events/schemas/index.js

@@ -1,4 +1,5 @@
 export * from "./firestore.js";
+export * from "./entry-votes.js";
 import { z } from "zod";
 import { mediaUrlSchema } from "../../../validation/schemas.js";
 import { mediaFieldSchema } from "../../media/types/index.js";
@@ -12,16 +13,53 @@ const eventCoverImageSchema = z
     .optional()
     .transform((value) => value ?? null);
 // --- Sub-schemas --------------------------------------------------------------
-export const eventTypeSchema = z.enum([
+/**
+ * 🛑 WRITE enum — the current spellings only. The three chance-based types
+ * were renamed 2026-10-31 (`raffle` -> `giveaway`, `spin_wheel` ->
+ * `bonus-spin`, `giveaway` -> `random-draw`).
+ *
+ * Deliberately does NOT accept the legacy spellings: a form or API caller
+ * sending `raffle` today is using a stale client, and a 400 says so. Stored
+ * documents that still hold them are handled on the READ side by
+ * `normalizeEventType`, and rewritten by
+ * `appkit/scripts/migrate-collector-drop-rename.mjs`.
+ */
+/**
+ * 🛑 OPEN, not a closed enum. Owner, 2026-11-08: *"all event types are also
+ * configs … they should not be fixed, nothing in the code should be fixed"*
+ * and *"the types we have now are the DEFAULT TEMPLATES"*.
+ *
+ * The eight below are the shipped templates, kept as a named list so the
+ * common ones are discoverable and so a typo in one of THEM is still caught.
+ * Anything else is accepted as a slug and resolved against the event-type
+ * config (`seed/event-types-seed-data.ts`).
+ *
+ * The rejected shape was the previous one: a closed `z.enum` that 400s an
+ * unknown value. It made a new kind of event — a photo contest judged by votes,
+ * say — an enum edit, a schema change and a deploy, which is precisely the
+ * coupling the rework removes. The same change is owed to coupons, listings
+ * and reviews, which are all still closed today.
+ *
+ * The slug shape is still enforced, because an unvalidated string here becomes
+ * a URL segment and a Firestore query value: lowercase, digits and hyphens,
+ * 2-40 characters.
+ */
+export const DEFAULT_EVENT_TYPE_TEMPLATES = [
     "sale",
     "offer",
     "poll",
     "survey",
     "feedback",
-    "raffle",
-    "spin_wheel",
-    "lottery",
-]);
+    "giveaway",
+    "bonus-spin",
+    "random-draw",
+];
+export const eventTypeSchema = z
+    .string()
+    .trim()
+    .min(2)
+    .max(40)
+    .regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/, "Use a lowercase slug, e.g. photo-contest");
 export const eventStatusSchema = z.enum(["draft", "active", "paused", "ended", "cancelled"]);
 export const saleConfigSchema = z.object({
     discountPercent: z.number(),
@@ -76,17 +114,17 @@ export const spinPrizeSchema = z.object({
     weight: z.number(),
     isActive: z.boolean(),
 });
-/** Lottery slot schema — client-safe shape (no price/weight sent to clients). */
-export const lotterySlotClientSchema = z.object({
+/** Giveaway slot schema — client-safe shape (no price/weight sent to clients). */
+export const giveawaySlotClientSchema = z.object({
     slotNumber: z.number().int().min(1),
     name: z.string(),
     isBooked: z.boolean(),
-    bookedByUserLotteryNumber: z.number().optional(),
+    bookedByUserGiveawayNumber: z.number().optional(),
     bookedByDisplayName: z.string().optional(),
 });
-/** Client-safe lottery config schema — price/weight fields stripped server-side. */
-export const lotteryConfigClientSchema = z.object({
-    slots: z.array(lotterySlotClientSchema),
+/** Client-safe giveaway config schema — price/weight fields stripped server-side. */
+export const giveawayConfigClientSchema = z.object({
+    slots: z.array(giveawaySlotClientSchema),
     totalSlots: z.number().int().min(1).max(200),
     pricingMode: z.enum(["uniform", "variable"]),
     drawWindowDurationMinutes: z.number(),
@@ -130,6 +168,8 @@ export const eventItemSchema = z.object({
     couponIds: attachedCouponIdsSchema,
     // Raffle fields
     hasRaffle: z.boolean().optional(),
+    // 🛑 `RaffleType`, NOT `EventType`. Its `spin_wheel` is the draw MECHANISM
+    // and was deliberately left alone when the EventType became `bonus-spin`.
     raffleType: z.enum(["top_n_scorers", "top_n_participants", "open_raffle", "spin_wheel"]).optional(),
     raffleTopN: z.number().optional(),
     rafflePrize: z.string().optional(),
@@ -147,8 +187,8 @@ export const eventItemSchema = z.object({
     spinMaxPerUser: z.number().optional(),
     spinWindowStart: z.string().optional(),
     spinWindowEnd: z.string().optional(),
-    // Lottery config (new) — client-safe shape (price/weight stripped by adapter)
-    lotteryConfig: lotteryConfigClientSchema.optional(),
+    // Giveaway config (new) — client-safe shape (price/weight stripped by adapter)
+    giveawayConfig: giveawayConfigClientSchema.optional(),
     stats: z.object({
         totalEntries: z.number(),
         approvedEntries: z.number(),

package/dist/features/events/types/index.d.ts

@@ -1,7 +1,14 @@
 import type { MediaField } from "../../media/types/index";
-import type { JsonValue } from "@mohasinac/appkit";
-import type { ClientLotteryConfig } from "../../lottery/types";
-export type EventType = "sale" | "offer" | "poll" | "survey" | "feedback" | "raffle" | "spin_wheel" | "lottery";
+import type { JsonValue } from "../../../schemas/types";
+import type { ClientGiveawayConfig } from "../../giveaway/types";
+export type EventType = "sale" | "offer" | "poll" | "survey" | "feedback" | "giveaway" | "bonus-spin" | "random-draw";
+/**
+ * Map a stored or inbound `type` onto the current union, tolerating the three
+ * legacy spellings. Returns `undefined` for anything it does not recognise —
+ * never a plausible default, because mislabelling a giveaway as an offer is
+ * worse than admitting we do not know (same rule as `eventTypeMeta`).
+ */
+export declare function normalizeEventType(type: string | undefined | null): EventType | undefined;
 export declare const ALL_EVENT_TYPES: EventType[];
 /**
  * Display labels for the admin/seller dashboards, which are not i18n-wrapped.
@@ -10,6 +17,15 @@ export declare const ALL_EVENT_TYPES: EventType[];
  * `Record<EventType, string>` so a new union member is a compile error here too.
  */
 export declare const EVENT_TYPE_LABELS: Record<EventType, string>;
+/**
+ * The DRAW MECHANISM a giveaway event uses — a different axis from
+ * `EventType`, and deliberately NOT renamed alongside it on 2026-10-31.
+ *
+ * 🛑 Its `"spin_wheel"` member is NOT the `EventType` member that became
+ * `"bonus-spin"`. They sat three lines apart and used the same word, so every
+ * `spin_wheel` match has to be classified before it is touched. The field
+ * `raffleType` is persisted and also stays.
+ */
 export type RaffleType = "top_n_scorers" | "top_n_participants" | "open_raffle" | "spin_wheel";
 /**
  * A spin prize as STORED on the event document. `weight` IS the odds and
@@ -28,7 +44,7 @@ export interface SpinPrize {
 /**
  * A spin prize as a VIEW may see it: what it is, not what it is worth.
  *
- * 🛑 This exists because `SpinWheelView.prizes` was typed `SpinPrize[]`, which
+ * 🛑 This exists because `BonusSpinView.prizes` was typed `SpinPrize[]`, which
  * made `weight` and `couponId` REQUIRED of every caller — so handing the public
  * wheel the full stored prize, odds included, was the only way to satisfy the
  * compiler. The participate page duly cast the stored array straight into a
@@ -142,8 +158,17 @@ export interface EventItem {
     spinWindowEnd?: string;
     /** Per-event admin toggle — unauthenticated visitors may participate when true. */
     allowGuestParticipation?: boolean;
-    /** Lottery config — slots have price/weight stripped for client consumption. */
-    lotteryConfig?: ClientLotteryConfig;
+    /**
+     * Slot config for a `random-draw` event — slots have price/weight stripped
+     * for client consumption.
+     *
+     * 🛑 The FIELD stays `giveawayConfig` even though the event type is now
+     * `random-draw`: it is persisted, it is shared with the product-level
+     * `prizeDrawMode: "giveaway"` axis, and `giveawayConfigWriteSchema` /
+     * `mergeGiveawayConfig` are its only legal writers (CLAUDE.md § "Giveaway
+     * Config Writes").
+     */
+    giveawayConfig?: ClientGiveawayConfig;
     stats: {
         totalEntries: number;
         approvedEntries: number;
@@ -200,7 +225,7 @@ export interface PollResultEntry {
     percent: number;
 }
 /**
- * One row of the public "Last 10 Spin Results" feed for a spin_wheel event.
+ * One row of the public "Last 10 Spin Results" feed for a `bonus-spin` event.
  * `userDisplayName` is undefined for guest spins (`isGuest: true`) — callers
  * should render a generic "Guest" label in that case, never a raw hash.
  */

package/dist/features/events/types/index.js

@@ -1,3 +1,36 @@
+/**
+ * Pre-2026-10-31 spellings of the three chance-based types, kept as READ
+ * aliases only. Nothing may write them.
+ *
+ * `raffle` -> `giveaway`, `spin_wheel` -> `bonus-spin`, `giveaway` ->
+ * `random-draw`. Renamed for payment-aggregator merchant-screening optics;
+ * `raffle` in particular is free-to-enter and never touches a payment
+ * provider, so its rename is pure terminology.
+ *
+ * 🛑 `appkit/scripts/migrate-collector-drop-rename.mjs` rewrites the stored
+ * `events.type` values. Until it has been RUN against a project, documents
+ * still hold the old spelling — so `normalizeEventType` is what every read
+ * path must go through, and these entries must not be deleted on the
+ * assumption the migration happened.
+ */
+const LEGACY_EVENT_TYPE_ALIASES = {
+    raffle: "giveaway",
+    spin_wheel: "bonus-spin",
+    giveaway: "random-draw",
+};
+/**
+ * Map a stored or inbound `type` onto the current union, tolerating the three
+ * legacy spellings. Returns `undefined` for anything it does not recognise —
+ * never a plausible default, because mislabelling a giveaway as an offer is
+ * worse than admitting we do not know (same rule as `eventTypeMeta`).
+ */
+export function normalizeEventType(type) {
+    if (!type)
+        return undefined;
+    if (type in ALL_EVENT_TYPES_MAP)
+        return type;
+    return LEGACY_EVENT_TYPE_ALIASES[type];
+}
 /**
  * Every event type, in canonical iteration order — the single array every
  * filter chip group, tab bar and dropdown derives from.
@@ -8,8 +41,12 @@
  * enumerations of this union and all three had drifted — the admin chips
  * offered `contest`/`giveaway`/`flash-sale` (values `EventType` never had, so
  * they matched zero rows) while omitting five real types, the public filter
- * omitted `lottery`, and `EVENT_FIELDS.TYPE_VALUES` omitted it too. Same shape
- * as `ALL_LISTING_TYPES_MAP`; same reason (Root Cause #61).
+ * omitted the random-draw type, and `EVENT_FIELDS.TYPE_VALUES` omitted it too.
+ * Same shape as `ALL_LISTING_TYPES_MAP`; same reason (Root Cause #61).
+ *
+ * 🛑 Note the historical account above: `giveaway` was once an INVENTED chip
+ * value matching zero rows. It is a real member of the union now. Do not read
+ * that paragraph as evidence the value is still fictional.
  */
 const ALL_EVENT_TYPES_MAP = {
     sale: true,
@@ -17,9 +54,9 @@ const ALL_EVENT_TYPES_MAP = {
     poll: true,
     survey: true,
     feedback: true,
-    raffle: true,
-    spin_wheel: true,
-    lottery: true,
+    giveaway: true,
+    "bonus-spin": true,
+    "random-draw": true,
 };
 export const ALL_EVENT_TYPES = Object.keys(ALL_EVENT_TYPES_MAP);
 /**
@@ -34,9 +71,9 @@ export const EVENT_TYPE_LABELS = {
     poll: "Poll",
     survey: "Survey",
     feedback: "Feedback",
-    raffle: "Raffle",
-    spin_wheel: "Spin the Wheel",
-    lottery: "Lottery",
+    giveaway: "Giveaway",
+    "bonus-spin": "Bonus Spin",
+    "random-draw": "Random Draw",
 };
 /** Every event status, in lifecycle order. Compile-checked like `ALL_EVENT_TYPES`. */
 const ALL_EVENT_STATUSES_MAP = {

package/dist/features/events/utils/carousel-slide.d.ts

@@ -9,11 +9,18 @@
  * Three Months", and neither edit knew about the other.
  *
  * So the event owns its promo, and this is the only function that renders that
- * intent into a slide. The seed derives `carouselSlidesSeedData` through it;
- * `scripts/push-editorial-content.mjs` pushes what the seed produced. Neither
- * hand-writes a slide, so there is no second copy to drift from.
+ * intent into a slide.
+ *
+ * 🛑 NOTHING PERSISTS THE RESULT (2026-10-31). A first attempt materialized
+ * this output into a standalone `carouselSlides` Firestore document at
+ * seed/push time — the owner reverted that entirely on 2026-10-27 after it
+ * shipped a 6-card slide linking into a closed `/events` section. The
+ * `carouselSlides` collection, its schema and its admin authoring UI are gone;
+ * `getHeroCarouselSlides()` (`_internal/server/features/events/data.ts`) is
+ * the one caller, and it calls this live on every homepage request instead of
+ * writing the output anywhere.
  */
-import type { CarouselSlideDocument } from "../../homepage/schemas/firestore";
+import type { CarouselSlide } from "../../homepage/types/index";
 import type { EventDocument } from "../schemas/firestore";
 export interface BuildSlideOptions {
     /** The event's public detail path, e.g. `/events/festive-cashback-10`. */
@@ -21,13 +28,4 @@ export interface BuildSlideOptions {
     /** Who the generated document records as its author. */
     createdBy: string;
 }
-export declare function buildSlideFromEvent(event: EventDocument, opts: BuildSlideOptions): Partial<CarouselSlideDocument> | null;
-/**
- * Build every event-owned slide, newest-ordered, and refuse an over-full rail.
- *
- * 🛑 `MAX_ACTIVE_SLIDES` is a real ceiling, not advice — `HeroCarousel` renders
- * the first five and a sixth active slide is authored, stored, and never seen
- * by anyone. Failing here is what makes that visible at seed time rather than
- * as a silently missing promotion.
- */
-export declare function buildSlidesFromEvents(events: readonly EventDocument[], resolveHref: (event: EventDocument) => string, createdBy: string): Partial<CarouselSlideDocument>[];
+export declare function buildSlideFromEvent(event: EventDocument, opts: BuildSlideOptions): CarouselSlide | null;

package/dist/features/events/utils/carousel-slide.js

@@ -9,11 +9,17 @@
  * Three Months", and neither edit knew about the other.
  *
  * So the event owns its promo, and this is the only function that renders that
- * intent into a slide. The seed derives `carouselSlidesSeedData` through it;
- * `scripts/push-editorial-content.mjs` pushes what the seed produced. Neither
- * hand-writes a slide, so there is no second copy to drift from.
+ * intent into a slide.
+ *
+ * 🛑 NOTHING PERSISTS THE RESULT (2026-10-31). A first attempt materialized
+ * this output into a standalone `carouselSlides` Firestore document at
+ * seed/push time — the owner reverted that entirely on 2026-10-27 after it
+ * shipped a 6-card slide linking into a closed `/events` section. The
+ * `carouselSlides` collection, its schema and its admin authoring UI are gone;
+ * `getHeroCarouselSlides()` (`_internal/server/features/events/data.ts`) is
+ * the one caller, and it calls this live on every homepage request instead of
+ * writing the output anywhere.
  */
-import { MAX_ACTIVE_SLIDES } from "../../homepage/schemas/firestore.js";
 /** Matches the seeded slides; a slower rail is unreadable, a faster one is a blur. */
 const DEFAULT_AUTOPLAY_MS = 6000;
 const DEFAULT_DIM = 0.55;
@@ -122,8 +128,10 @@ export function buildSlideFromEvent(event, opts) {
         return null;
     const dim = cfg.dimOpacity ?? DEFAULT_DIM;
     const bg = background(resolveBackgroundSlug(event), dim);
+    // Nothing persists this slide, so there is no competing document-id
+    // namespace to disambiguate — the slide's id IS the event's id.
     const base = {
-        id: `slide-${event.id}`,
+        id: event.id,
         title: event.title,
         order: cfg.order ?? 99,
         /*
@@ -178,7 +186,7 @@ export function buildSlideFromEvent(event, opts) {
             description: cfg.description,
             button: cfg.buttonText
                 ? {
-                    id: `slide-${event.id}-cta`,
+                    id: `${event.id}-cta`,
                     text: cfg.buttonText,
                     link: opts.eventHref,
                     variant: "primary",
@@ -188,24 +196,13 @@ export function buildSlideFromEvent(event, opts) {
         },
     };
 }
-/**
- * Build every event-owned slide, newest-ordered, and refuse an over-full rail.
- *
- * 🛑 `MAX_ACTIVE_SLIDES` is a real ceiling, not advice — `HeroCarousel` renders
- * the first five and a sixth active slide is authored, stored, and never seen
- * by anyone. Failing here is what makes that visible at seed time rather than
- * as a silently missing promotion.
+/*
+ * There is deliberately no batch "build every event-owned slide" helper here
+ * any more. The one that used to live here THREW past `MAX_ACTIVE_SLIDES` —
+ * correct for a seed-time build guard, wrong for a live request path: an
+ * admin toggling a 6th event's `showOnCarousel` on would 500 the homepage for
+ * every visitor until someone noticed and toggled it back off.
+ * `getHeroCarouselSlides()` (`_internal/server/features/events/data.ts`) maps
+ * each event through `buildSlideFromEvent` individually and caps the result
+ * with a plain `.slice(0, MAX_ACTIVE_SLIDES)` — no throw.
  */
-export function buildSlidesFromEvents(events, resolveHref, createdBy) {
-    const slides = events
-        .map((e) => buildSlideFromEvent(e, { eventHref: resolveHref(e), createdBy }))
-        .filter((s) => s !== null)
-        .sort((a, b) => (a.order ?? 99) - (b.order ?? 99));
-    const activeCount = slides.filter((s) => s.active).length;
-    if (activeCount > MAX_ACTIVE_SLIDES) {
-        throw new Error(`${activeCount} active event slides but MAX_ACTIVE_SLIDES is ${MAX_ACTIVE_SLIDES}. ` +
-            `The extras would never render. Deactivate one, or fold several deals into ` +
-            `a single cards slide — that is what the 6 zones are for.`);
-    }
-    return slides;
-}

package/dist/features/faq/actions/faq-actions.d.ts

@@ -1,6 +1,49 @@
 import { z } from "zod";
 import type { FAQDocument } from "../schemas";
 import type { FirebaseSieveResult } from "../../../providers/db-firebase";
+/**
+ * Mirrors `ContentFragment` (`_internal/shared/content/fragments.ts`) — for
+ * an answer that MENTIONS several governed things rather than being solely
+ * about one (document-level `contentTags` already covers that case). Each
+ * fragment's own `governs` is optional (omitted = always-shown clause, e.g.
+ * the answer's opening sentence).
+ *
+ * Exported (added Item 7, 2026-11-04) so the `/api/admin/faqs*` routes — a
+ * SEPARATE write path from this file's own `createFaq`/`updateFaq`, with
+ * their own local Zod schemas — can accept the same field with one
+ * definition instead of a third hand-copy. Those routes are what the admin
+ * FAQ editor UI actually calls; `answerFragments` existing only here, with
+ * no reader on the path the UI uses, would mean an editor that appears to
+ * save but silently drops the field on every write.
+ */
+export declare const answerFragmentsSchema: z.ZodOptional<z.ZodArray<z.ZodObject<{
+    governs: z.ZodOptional<z.ZodObject<{
+        governs: z.ZodEnum<["listingType", "categoryType", "browsePage"]>;
+        value: z.ZodString;
+    }, "strip", z.ZodTypeAny, {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }, {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }>>;
+    text: z.ZodString;
+    whenHidden: z.ZodOptional<z.ZodString>;
+}, "strip", z.ZodTypeAny, {
+    text: string;
+    governs?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    } | undefined;
+    whenHidden?: string | undefined;
+}, {
+    text: string;
+    governs?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    } | undefined;
+    whenHidden?: string | undefined;
+}>, "many">>;
 export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
     question: z.ZodString;
     answer: z.ZodObject<{
@@ -21,6 +64,44 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
     isPinned: z.ZodDefault<z.ZodBoolean>;
     order: z.ZodDefault<z.ZodNumber>;
     tags: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
+    contentTags: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        governs: z.ZodEnum<["listingType", "categoryType", "browsePage"]>;
+        value: z.ZodString;
+    }, "strip", z.ZodTypeAny, {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }, {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }>, "many">>;
+    answerFragments: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        governs: z.ZodOptional<z.ZodObject<{
+            governs: z.ZodEnum<["listingType", "categoryType", "browsePage"]>;
+            value: z.ZodString;
+        }, "strip", z.ZodTypeAny, {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        }, {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        }>>;
+        text: z.ZodString;
+        whenHidden: z.ZodOptional<z.ZodString>;
+    }, "strip", z.ZodTypeAny, {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }, {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }>, "many">>;
     relatedFAQs: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
     useSiteSettings: z.ZodDefault<z.ZodBoolean>;
     variables: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
@@ -39,10 +120,22 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
     showInFooter: boolean;
     isPinned: boolean;
     useSiteSettings: boolean;
+    template?: string | undefined;
     tags?: string[] | undefined;
     relatedFAQs?: string[] | undefined;
     variables?: Record<string, string> | undefined;
-    template?: string | undefined;
+    contentTags?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }[] | undefined;
+    answerFragments?: {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }[] | undefined;
 }, {
     category: string;
     question: string;
@@ -50,6 +143,7 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
         text: string;
         format?: "html" | "plain" | "markdown" | undefined;
     };
+    template?: string | undefined;
     tags?: string[] | undefined;
     isActive?: boolean | undefined;
     order?: number | undefined;
@@ -60,7 +154,18 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
     relatedFAQs?: string[] | undefined;
     useSiteSettings?: boolean | undefined;
     variables?: Record<string, string> | undefined;
-    template?: string | undefined;
+    contentTags?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }[] | undefined;
+    answerFragments?: {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }[] | undefined;
 }>, {
     category: string;
     isActive: boolean;
@@ -75,10 +180,22 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
     showInFooter: boolean;
     isPinned: boolean;
     useSiteSettings: boolean;
+    template?: string | undefined;
     tags?: string[] | undefined;
     relatedFAQs?: string[] | undefined;
     variables?: Record<string, string> | undefined;
-    template?: string | undefined;
+    contentTags?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }[] | undefined;
+    answerFragments?: {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }[] | undefined;
 }, {
     category: string;
     question: string;
@@ -86,6 +203,7 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
         text: string;
         format?: "html" | "plain" | "markdown" | undefined;
     };
+    template?: string | undefined;
     tags?: string[] | undefined;
     isActive?: boolean | undefined;
     order?: number | undefined;
@@ -96,7 +214,18 @@ export declare const faqCreateSchema: z.ZodEffects<z.ZodObject<{
     relatedFAQs?: string[] | undefined;
     useSiteSettings?: boolean | undefined;
     variables?: Record<string, string> | undefined;
-    template?: string | undefined;
+    contentTags?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }[] | undefined;
+    answerFragments?: {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }[] | undefined;
 }>;
 export declare const faqUpdateSchema: z.ZodObject<{
     question: z.ZodOptional<z.ZodString>;
@@ -118,11 +247,50 @@ export declare const faqUpdateSchema: z.ZodObject<{
     isPinned: z.ZodOptional<z.ZodDefault<z.ZodBoolean>>;
     order: z.ZodOptional<z.ZodDefault<z.ZodNumber>>;
     tags: z.ZodOptional<z.ZodOptional<z.ZodArray<z.ZodString, "many">>>;
+    contentTags: z.ZodOptional<z.ZodOptional<z.ZodArray<z.ZodObject<{
+        governs: z.ZodEnum<["listingType", "categoryType", "browsePage"]>;
+        value: z.ZodString;
+    }, "strip", z.ZodTypeAny, {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }, {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }>, "many">>>;
+    answerFragments: z.ZodOptional<z.ZodOptional<z.ZodArray<z.ZodObject<{
+        governs: z.ZodOptional<z.ZodObject<{
+            governs: z.ZodEnum<["listingType", "categoryType", "browsePage"]>;
+            value: z.ZodString;
+        }, "strip", z.ZodTypeAny, {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        }, {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        }>>;
+        text: z.ZodString;
+        whenHidden: z.ZodOptional<z.ZodString>;
+    }, "strip", z.ZodTypeAny, {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }, {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }>, "many">>>;
     relatedFAQs: z.ZodOptional<z.ZodOptional<z.ZodArray<z.ZodString, "many">>>;
     useSiteSettings: z.ZodOptional<z.ZodDefault<z.ZodBoolean>>;
     variables: z.ZodOptional<z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>>;
     template: z.ZodOptional<z.ZodOptional<z.ZodString>>;
 }, "strip", z.ZodTypeAny, {
+    template?: string | undefined;
     category?: string | undefined;
     tags?: string[] | undefined;
     isActive?: boolean | undefined;
@@ -139,8 +307,20 @@ export declare const faqUpdateSchema: z.ZodObject<{
     relatedFAQs?: string[] | undefined;
     useSiteSettings?: boolean | undefined;
     variables?: Record<string, string> | undefined;
-    template?: string | undefined;
+    contentTags?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }[] | undefined;
+    answerFragments?: {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }[] | undefined;
 }, {
+    template?: string | undefined;
     category?: string | undefined;
     tags?: string[] | undefined;
     isActive?: boolean | undefined;
@@ -157,7 +337,18 @@ export declare const faqUpdateSchema: z.ZodObject<{
     relatedFAQs?: string[] | undefined;
     useSiteSettings?: boolean | undefined;
     variables?: Record<string, string> | undefined;
-    template?: string | undefined;
+    contentTags?: {
+        value: string;
+        governs: "listingType" | "categoryType" | "browsePage";
+    }[] | undefined;
+    answerFragments?: {
+        text: string;
+        governs?: {
+            value: string;
+            governs: "listingType" | "categoryType" | "browsePage";
+        } | undefined;
+        whenHidden?: string | undefined;
+    }[] | undefined;
 }>;
 export type FaqCreateInput = z.infer<typeof faqCreateSchema>;
 export type FaqUpdateInput = z.infer<typeof faqUpdateSchema>;