@mohasinac/appkit 4.41.14 → 4.41.16

package/dist/features/events/actions/event-actions.d.ts

@@ -64,6 +64,32 @@ export declare function listPublicEvents(params?: string | {
     page?: number;
     pageSize?: number;
 }): Promise<FirebaseSieveResult<EventDocument>>;
+/**
+ * 🛑 ONLY `draft` IS HIDDEN. Every other status is public history.
+ *
+ * This read `status !== "active"`, which collapsed four distinct states into
+ * "this event does not exist":
+ *
+ *   ended     a finished raffle — the thing people come back to read, and the
+ *             only place `raffleWinnerDisplayName` is ever shown. The seeded
+ *             `event-won-original-set-raffle` has a real recorded winner and
+ *             its page answered 404.
+ *   cancelled should say it was cancelled. Vanishing tells a visitor holding
+ *             the link that they misremembered it, not that it was called off.
+ *   paused    temporarily not accepting entries, which is not the same as gone.
+ *   draft     genuinely not published yet — the one case 404 is right for.
+ *
+ * The rendering layer was ALREADY built for this: `events/[id]/layout.tsx`
+ * computes `eventStatus`, derives `isActive`, and gates `showParticipateTab`
+ * on it. Participation is refused by that gate, not by hiding the page — so
+ * this filter was the only thing standing between a visitor and content the
+ * UI knew how to show.
+ *
+ * The API (`GET /api/events/[id]`) already returned cancelled and ended events
+ * with 200 while the page 404'd them, so the two layers disagreed about what
+ * exists. Measured live before the fix:
+ *   active 200/renders · cancelled 200/404 · ended 200/404 · paused 404/404
+ */
 export declare function getPublicEventById(id: string): Promise<EventDocument | null>;
 export declare function getEventLeaderboard(eventId: string): Promise<import("../types").LeaderboardEntry[]>;
 /**

package/dist/features/events/actions/event-actions.js

@@ -140,9 +140,35 @@ export async function listPublicEvents(params) {
     // PUBLIC by name — it backs the homepage strip and /events.
     return { ...result, items: hidePublicTestData(result.items) };
 }
+/**
+ * 🛑 ONLY `draft` IS HIDDEN. Every other status is public history.
+ *
+ * This read `status !== "active"`, which collapsed four distinct states into
+ * "this event does not exist":
+ *
+ *   ended     a finished raffle — the thing people come back to read, and the
+ *             only place `raffleWinnerDisplayName` is ever shown. The seeded
+ *             `event-won-original-set-raffle` has a real recorded winner and
+ *             its page answered 404.
+ *   cancelled should say it was cancelled. Vanishing tells a visitor holding
+ *             the link that they misremembered it, not that it was called off.
+ *   paused    temporarily not accepting entries, which is not the same as gone.
+ *   draft     genuinely not published yet — the one case 404 is right for.
+ *
+ * The rendering layer was ALREADY built for this: `events/[id]/layout.tsx`
+ * computes `eventStatus`, derives `isActive`, and gates `showParticipateTab`
+ * on it. Participation is refused by that gate, not by hiding the page — so
+ * this filter was the only thing standing between a visitor and content the
+ * UI knew how to show.
+ *
+ * The API (`GET /api/events/[id]`) already returned cancelled and ended events
+ * with 200 while the page 404'd them, so the two layers disagreed about what
+ * exists. Measured live before the fix:
+ *   active 200/renders · cancelled 200/404 · ended 200/404 · paused 404/404
+ */
 export async function getPublicEventById(id) {
     const event = await eventRepository.findByIdOrSlug(id);
-    if (!event || event.status !== "active")
+    if (!event || event.status === "draft")
         return null;
     return event;
 }

package/dist/features/faq/components/FAQPageContent.d.ts

@@ -26,6 +26,8 @@ interface FAQPageContentProps {
         resultCount: (count: number) => string;
         inCategory: (categoryLabel: string) => string;
         loading: string;
+        emptyTitle?: string;
+        emptyDescription?: string;
         contactTitle: string;
         contactDescription: string;
         contactEmailUs: string;

package/dist/features/faq/components/FAQPageContent.js

@@ -1,6 +1,6 @@
 "use client";
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-import { Alert, Div, Heading, Input, SlottedListingView, Text } from "../../../ui";
+import { Alert, Div, EmptyState, Heading, Input, SlottedListingView, Text } from "../../../ui";
 import { sortBy } from "../../../constants/sort";
 import { FAQCategorySidebar } from "./FAQCategorySidebar";
 import { FAQSortDropdown } from "./FAQSortDropdown";
@@ -69,7 +69,24 @@ export function FAQPageContent({ initialCategory = "all", categories, routeHelpe
                                  * Saying so costs nothing and makes the next index gap
                                  * self-reporting rather than a phantom empty state.
                                  */
-                                _jsx(Alert, { variant: "error", title: "Couldn't load questions", children: "Something went wrong fetching these FAQs. Try a different sort or reload the page." })) : renderAccordion ? (renderAccordion(faqs)) : (_jsx(FAQAccordion, { faqs: faqs })), renderPagination: () => renderPagination?.(total) ?? null, total: total, isLoading: isLoading }), faqs.length > 0 ? (_jsx(Div, { className: "mt-12", children: _jsx(ContactCTA, { email: contact.email, phone: contact.phone, contactHref: routeHelpers.contactHref, labels: {
+                                _jsx(Alert, { variant: "error", title: "Couldn't load questions", children: "Something went wrong fetching these FAQs. Try a different sort or reload the page." })) : faqs.length === 0 ? (
+                                /*
+                                 * 🛑 AN EXPLICIT EMPTY BRANCH — without it the page rendered a
+                                 * BARE WHITE AREA.
+                                 *
+                                 * The chain fell through to <FAQAccordion faqs={[]} />, which
+                                 * renders nothing at all. Measured on /faqs?q=zzzznope: the
+                                 * page showed "0 questions", the search box, a divider, and
+                                 * then blank space — no message anywhere in the DOM.
+                                 *
+                                 * A blank region is the worst possible answer here because it
+                                 * is indistinguishable from a page that failed to load, which
+                                 * is exactly the confusion the isError branch above exists to
+                                 * prevent. Three states, three distinct renderings: loading,
+                                 * failed, and genuinely nothing found.
+                                 */
+                                _jsx(EmptyState, { title: labels.emptyTitle ?? "No questions found", description: labels.emptyDescription ??
+                                        "Try a different search term, or pick another category from the list." })) : renderAccordion ? (renderAccordion(faqs)) : (_jsx(FAQAccordion, { faqs: faqs })), renderPagination: () => renderPagination?.(total) ?? null, total: total, isLoading: isLoading }), faqs.length > 0 ? (_jsx(Div, { className: "mt-12", children: _jsx(ContactCTA, { email: contact.email, phone: contact.phone, contactHref: routeHelpers.contactHref, labels: {
                                         title: labels.contactTitle,
                                         description: labels.contactDescription,
                                         emailUs: labels.contactEmailUs,

package/dist/features/homepage/components/AnnouncementBar.js

@@ -55,8 +55,32 @@ export function AnnouncementBar({ message, link, className = "", onDismiss, over
     }, [message, userAlreadyDismissed]);
     if (dismissed)
         return null;
+    /*
+     * 🛑 THE OVERLAY IS md AND UP ONLY — IT PAINTED OVER THE HERO HEADING ON
+     * EVERY PHONE WIDTH.
+     *
+     * `absolute` reserves no space, which is the whole point of the overlay: the
+     * hero's own top padding is sized to sit a ONE-LINE banner over it. A real
+     * announcement wraps on a narrow screen, grows downward, and there is
+     * nothing to stop it.
+     *
+     * Measured on production against the live announcement, against the <h1>:
+     *
+     *   320px → 30px overlap      768px → 10px clear
+     *   390px → 10px overlap     1280px → 10px clear
+     *   430px → 10px overlap
+     *
+     * So it was every phone width and no tablet or desktop width — which is why
+     * it survived: the breakpoints people check it at are the ones where the
+     * message still fits on one line.
+     *
+     * Below `md` it is an ordinary in-flow bar that pushes the hero down, with a
+     * SOLID background (the translucent + blur treatment only reads as
+     * deliberate when there is artwork behind it). From `md` up, the designed
+     * overlay is unchanged.
+     */
     const positionCls = overlay
-        ? "absolute inset-x-0 top-0 z-20 bg-primary-700/85 backdrop-blur-sm"
+        ? "relative md:absolute inset-x-0 top-0 z-20 bg-primary-700 md:bg-primary-700/85 md:backdrop-blur-sm"
         : "relative left-1/2 right-1/2 w-screen -translate-x-1/2 bg-primary-700";
     return (_jsx(Div, { className: `${positionCls} transition-opacity duration-200 ${mounted ? "opacity-100" : "opacity-0"} ${className}`, role: "banner", children: _jsx(Div, { paddingX: "x-page", className: "container mx-auto max-w-[1920px]", children: _jsxs(Row, { textWeight: "medium", textSize: "sm", className: "relative text-left text-white", padding: "y-xs", align: "center", justify: "start", children: [link ? (_jsx(TextLink, { href: link, className: "text-white underline", children: message })) : (_jsx(Span, { children: message })), _jsx(IconButton, { type: "button", onClick: () => {
                             saveLocalDismissal(message);

package/dist/features/seller/components/SellerProductsView.js

@@ -252,11 +252,27 @@ export function SellerProductsView({ onDeleteProduct, onCreateClick, }) {
                         .filter(Boolean)
                         .join(" · ")
                     : "";
+                /*
+                 * 🛑 THE STATUS GOES IN THE VISIBLE LINE, NOT ONLY IN `status`.
+                 *
+                 * `status` is mapped correctly and the API does emit it (measured:
+                 * "published" on every row) — but this view's right-hand slot holds
+                 * Edit / Duplicate / Delete, so unlike the admin table there is no
+                 * status chip and the value was never rendered anywhere. A seller
+                 * could not tell which of their listings were live without opening
+                 * each one, and a checklist case that begins "find a listing whose
+                 * status reads Published" had nothing to read.
+                 *
+                 * Same family as Root Cause #52: the data was already on the row and
+                 * the UI simply never presented it.
+                 */
+                const statusLabel = toStringValue(item.status, "draft");
+                const secondaryBase = auctionSecondary || toStringValue(item.condition, "");
                 return {
                     id: toStringValue(item.id, `product-${index}`),
                     primary: toStringValue(item.title ?? item.name, "Untitled product"),
-                    secondary: auctionSecondary || toStringValue(item.condition, ""),
-                    status: toStringValue(item.status, "draft"),
+                    secondary: [secondaryBase, statusLabel].filter(Boolean).join(" · "),
+                    status: statusLabel,
                     updatedAt: toRelativeDate(item.updatedAt ?? item.createdAt),
                     imageUrl: toStringValue(item.mainImage ?? item.images?.[0], undefined),
                     image: toStringValue(item.mainImage ?? item.images?.[0], undefined),