@mohasinac/appkit 4.56.0 → 4.58.0

package/dist/_internal/server/features/orders/actions.js

@@ -412,3 +412,106 @@ export async function raiseOrderDisputeAction(orderId, reason) {
         });
     });
 }
+/**
+ * A buyer submits payment for ONE of their own EMI instalments.
+ *
+ * 🛑 Why this exists at all: there was no buyer-side route. The only writer
+ * was the seller's `markEmiInstallmentPaid`, so a buyer on an EMI plan could
+ * not pay an instalment — they waited for the seller to record it. The
+ * schema had anticipated them all along (`EmiInstallment.transactionId` and
+ * `.proofUrl` are documented as "buyer-uploaded"), which is the tell that the
+ * surface, not the model, was missing.
+ *
+ * 🛑 **ANY unpaid instalment, at ANY time — deliberately unbounded.** There is
+ * no due-date check and none should be added. A buyer who wants to clear the
+ * plan early is reducing our exposure, not breaking a rule, and the dueDate is
+ * the date we will CHASE them on, never the first date they may pay. Paying
+ * ahead also keeps `emiComplete` honest: that flag is what
+ * `assertEmiShippable` reads, so early settlement should be able to release a
+ * shipment early rather than waiting out a calendar.
+ *
+ * It mirrors the manual-payment model rather than inventing a second one: the
+ * buyer supplies a UTR and a proof, the seller or an admin confirms. The
+ * status therefore moves to `pending` review here, NOT to `paid` — a buyer
+ * must never be able to mark their own money received. `markEmiInstallmentPaid`
+ * stays the only writer of `paid`, and so stays the only way `emiComplete`
+ * can flip.
+ */
+export async function submitEmiInstallmentPaymentAction(orderId, input) {
+    return wrapAction(async () => {
+        const user = await requireRoleUser(["user", "buyer", "seller", "admin"]);
+        const order = await orderRepository.findById(orderId);
+        if (!order)
+            throw new OrderNotFoundError(orderId);
+        if (!isAdminUser(user) && order.userId !== user.uid)
+            throw new OrderOwnershipError(orderId);
+        if (!order.emiEnabled)
+            throw new ValidationError("This order is not on an EMI plan");
+        const installments = order.emiInstallments ?? [];
+        const target = installments.find((i) => i.index === input.installmentIndex);
+        if (!target) {
+            throw new ValidationError(`Installment ${input.installmentIndex} not found on this order`);
+        }
+        if (target.status === "paid") {
+            throw new ValidationError("This installment is already paid");
+        }
+        // A second submission would overwrite the reference the reviewer is
+        // currently looking at, which reads to them as the buyer changing their
+        // story. Re-submitting needs the reviewer to reject the first one.
+        if (target.transactionId) {
+            throw new ValidationError("A payment reference is already under review for this installment");
+        }
+        /*
+         * 🛑 `status` is NOT written here, and writing it would be a lie dressed
+         * as a state change.
+         *
+         * A new instalment is created `status: "pending"` (see
+         * `createOrderForGroup`), so setting `"pending"` again changes nothing
+         * while reading like a transition — and it would leave "nobody has paid"
+         * and "the buyer has reported paying" indistinguishable, which is exactly
+         * the state a reviewer needs to tell apart.
+         *
+         * "Awaiting review" is DERIVED: `transactionId` set and `status !== "paid"`.
+         * Same rule as the manual-payment queue, which derives its four states
+         * from `paymentProofUrl` + `paymentReviewOutcome` rather than storing a
+         * mirror field that any write path could forget to update (Root Cause
+         * #42). Only `markEmiInstallmentPaid` writes `paid`, so a buyer can never
+         * mark their own money received, and `emiComplete` keeps its single writer.
+         */
+        const updatedInstallments = installments.map((i) => i.index === input.installmentIndex
+            ? { ...i, transactionId: input.transactionId, proofUrl: input.proofUrl }
+            : i);
+        await orderRepository.update(orderId, { emiInstallments: updatedInstallments });
+        /*
+         * Tell the seller there is something to confirm. Best-effort: a
+         * notification that fails must not lose the buyer's submitted reference,
+         * which is the only record that they paid.
+         */
+        const store = order.storeId ? await storeRepository.findById(order.storeId) : null;
+        if (store?.ownerId) {
+            await sendNotification({
+                userId: store.ownerId,
+                type: "payment_review",
+                /*
+                 * `high`, matching the other `payment_review` send in this file. The
+                 * two differ in urgency — that one has a 15-minute re-upload window
+                 * and this one has no deadline — but a single notification TYPE whose
+                 * priority disagrees between its call sites is the drift this codebase
+                 * keeps paying for, and unconfirmed money is a seller action item
+                 * either way.
+                 */
+                priority: "high",
+                title: "EMI instalment payment reported",
+                message: `A buyer has submitted payment for instalment ${input.installmentIndex} on order ${orderId}.`,
+                relatedId: orderId,
+                relatedType: "order",
+            }).catch((err) => {
+                void normalizeError(err);
+                serverLogger.error("Failed to notify seller of EMI instalment payment (non-fatal)", {
+                    orderId,
+                    installmentIndex: input.installmentIndex,
+                });
+            });
+        }
+    });
+}

package/dist/_internal/server/features/orders/adapters.js

@@ -170,6 +170,13 @@ export function orderDocumentToOrder(doc) {
         // the packer needs giftWrapMessage in hand. An
         // adapter that drops them makes every downstream surface render its
         // "not applicable" fallback instead (Root Cause #57).
+        // EMI, so the buyer can see and pay their own schedule. Mapped with the
+        // add-ons above for the same reason recorded there: an adapter that drops
+        // a field makes every downstream surface render its not-applicable
+        // fallback (Root Cause #57).
+        emiEnabled: doc.emiEnabled,
+        emiInstallments: doc.emiInstallments,
+        emiRemainingBalance: doc.emiRemainingBalance,
         giftWrapAddon: doc.giftWrapAddon,
         giftWrapFee: doc.giftWrapFee,
         giftWrapMessage: doc.giftWrapMessage,

package/dist/_internal/server/features/parts/data.js

@@ -11,6 +11,7 @@ import { PART_GLOSSARY_COLLECTION, MODEL_COMPOSITION_COLLECTION, partGlossaryId,
 import { getAdminDb } from "../../../../providers/db-firebase/index.js";
 import { serverLogger } from "../../../../monitoring/server-logger.js";
 import { normalizeError } from "../../../../errors/normalize.js";
+import { MODEL_COMPOSITION_FIELDS, PART_GLOSSARY_FIELDS, } from "../../../../constants/field-names.js";
 /** The bucket cap. 87 is the largest real classification, so this clears it. */
 export const PART_SLOT_PAGE_SIZE = 120;
 /** One part, by `(slot, code|name)` — the only key this collection has. */
@@ -125,7 +126,7 @@ export const getCompositionsForCategory = cache(async (categoryId) => {
     try {
         const snap = await getAdminDb()
             .collection(MODEL_COMPOSITION_COLLECTION)
-            .where("categoryId", "==", categoryId)
+            .where(MODEL_COMPOSITION_FIELDS.CATEGORY_ID, "==", categoryId)
             .limit(8)
             .get();
         return snap.docs.map((d) => ({ id: d.id, ...d.data() }));
@@ -154,7 +155,7 @@ export const listPartsBySlot = cache(async (slot) => {
     try {
         const snap = await getAdminDb()
             .collection(PART_GLOSSARY_COLLECTION)
-            .where("slot", "==", slot)
+            .where(PART_GLOSSARY_FIELDS.SLOT, "==", slot)
             .limit(PART_SLOT_PAGE_SIZE)
             .get();
         const parts = snap.docs

package/dist/_internal/shared/actions/action-registry.d.ts

@@ -29,7 +29,7 @@ import type { IconKey } from "../../../ui/icons/icon-registry";
 /** What KIND of action — drives default UI affordance (link vs button vs danger). */
 export type ActionKind = "primary" | "secondary" | "danger" | "ghost" | "link" | "chip";
 /** Resource bucket — keyed top-level in the ACTIONS tree. */
-export type ActionResource = "PRODUCT" | "AUCTION" | "PRE_ORDER" | "PRIZE_DRAW" | "DIGITAL_CODE" | "BUNDLE" | "GROUP" | "CATEGORY" | "BRAND" | "SUBLISTING" | "STORE" | "BLOG" | "EVENT" | "REVIEW" | "SHIPMENT" | "CATALOGUE" | "USER" | "SELLER" | "ADMIN" | "CART" | "CHECKOUT" | "NAV" | "MEDIA" | "SUPPORT" | "LOTTERY" | "TESTER";
+export type ActionResource = "PRODUCT" | "AUCTION" | "PRE_ORDER" | "PRIZE_DRAW" | "DIGITAL_CODE" | "BUNDLE" | "GROUP" | "CATEGORY" | "BRAND" | "PART" | "BEY" | "SUBLISTING" | "STORE" | "BLOG" | "EVENT" | "REVIEW" | "SHIPMENT" | "CATALOGUE" | "USER" | "SELLER" | "ADMIN" | "CART" | "CHECKOUT" | "NAV" | "MEDIA" | "SUPPORT" | "LOTTERY" | "TESTER";
 /** Confirmation modal config — when set, <Button action={...}> opens
  *  a confirm dialog before firing the actual handler. */
 export interface ActionConfirmation {

package/dist/_internal/shared/actions/action-registry.js

@@ -432,6 +432,92 @@ export const ACTIONS = {
             },
         },
     },
+    /*
+     * ── 🛑 THE TWO GENERATED REFERENCE DATABASES ─────────────────────────────
+     *
+     * `partGlossary` (2,488) and `beys` (1,988) are built by committed
+     * generators from a crawled corpus. That shapes every leaf below:
+     *
+     *   · NO `create`. A row authored by hand has no source, vanishes on the
+     *     next regeneration, and makes "this dataset rebuilds from the repo"
+     *     false. Adding a part is a change to the generator, not a button.
+     *   · `edit` is CORRECT-A-WRONG-EXTRACTION, and says so, because that is
+     *     what it is for — the corpus was measurably wrong five times in one
+     *     session on mode data alone.
+     *   · `delete`'s confirmation does NOT say "cannot be undone", because that
+     *     would be a lie: the row is in a committed seed file and the next
+     *     reseed restores it. It says what actually happens.
+     */
+    PART: {
+        view: {
+            iconKey: "view",
+            id: "part.view",
+            label: "View",
+            ariaLabel: "View part",
+            description: "Open the part reference page.",
+            kind: "secondary",
+        },
+        edit: {
+            iconKey: "edit",
+            id: "part.edit",
+            label: "Edit",
+            ariaLabel: "Edit part",
+            description: "Correct this part's recorded details. The correction is kept when the database is regenerated.",
+            kind: "secondary",
+            permissions: ["admin"],
+        },
+        delete: {
+            iconKey: "delete",
+            id: "part.delete",
+            label: "Delete",
+            ariaLabel: "Delete part",
+            description: "Remove this part from the live database.",
+            kind: "danger",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Remove this part from the live database?",
+                body: "Beyblades built from it keep their parts list and will show its name without a link. " +
+                    "This part is also in the committed seed data, so regenerating the database will bring it " +
+                    "back — to remove it for good, take it out of the generator.",
+                confirmLabel: "Remove",
+            },
+        },
+    },
+    BEY: {
+        view: {
+            iconKey: "view",
+            id: "bey.view",
+            label: "View",
+            ariaLabel: "View Beyblade",
+            description: "Open the Beyblade reference page.",
+            kind: "secondary",
+        },
+        edit: {
+            iconKey: "edit",
+            id: "bey.edit",
+            label: "Edit",
+            ariaLabel: "Edit Beyblade",
+            description: "Correct this Beyblade's recorded details. The correction is kept when the database is regenerated.",
+            kind: "secondary",
+            permissions: ["admin"],
+        },
+        delete: {
+            iconKey: "delete",
+            id: "bey.delete",
+            label: "Delete",
+            ariaLabel: "Delete Beyblade",
+            description: "Remove this Beyblade from the live database.",
+            kind: "danger",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Remove this Beyblade from the live database?",
+                body: "Its category page and any listings under it are not touched, and boxed sets that include " +
+                    "it keep their contents list. It is also in the committed seed data, so regenerating the " +
+                    "database will bring it back — to remove it for good, take it out of the generator.",
+                confirmLabel: "Remove",
+            },
+        },
+    },
     CATEGORY: {
         view: {
             iconKey: "view",
@@ -1039,6 +1125,21 @@ export const ACTIONS = {
         },
     },
     BLOG: {
+        /*
+         * Clone, admin-only, backed by POST /api/admin/blog/[id]/duplicate. A
+         * templated post is the real use case: same structure and category, new
+         * subject. The copy starts as a DRAFT with a freshly derived slug — blog is
+         * a pure-slug resource, so reusing the source slug would overwrite it.
+         */
+        "duplicate-post": {
+            iconKey: "duplicate",
+            id: "blog.duplicate-post",
+            label: "Duplicate",
+            ariaLabel: "Duplicate this post as a draft",
+            description: "Copy this post into a new draft, without its views or featured flag.",
+            kind: "secondary",
+            permissions: ["admin"],
+        },
         "create-post": {
             iconKey: "create",
             id: "blog.create-post",
@@ -1113,6 +1214,23 @@ export const ACTIONS = {
         },
     },
     EVENT: {
+        /*
+         * Clone, admin-only, backed by POST /api/admin/events/[id]/duplicate. A
+         * recurring sale is the real use case: same copy, same prizes, new dates.
+         *
+         * 🛑 The endpoint rebuilds every lottery slot from its prize definition and
+         * resets the booking half — a spread would attribute a real buyer’s
+         * purchased slot to a brand-new event.
+         */
+        duplicate: {
+            iconKey: "duplicate",
+            id: "event.duplicate",
+            label: "Duplicate",
+            ariaLabel: "Duplicate this event as a draft",
+            description: "Copy this event into a new draft, without its entries, winner or slot bookings.",
+            kind: "secondary",
+            permissions: ["admin"],
+        },
         /*
          * This bucket had only register / cancel-registration / draw-raffle-winner
          * — no edit, no delete — so the owner affordance on an event card or detail
@@ -2208,6 +2326,27 @@ export const ACTIONS = {
             kind: "ghost",
             permissions: ["admin"],
         },
+        /*
+         * Homepage sections have no bucket of their own, so their edit leaf lives
+         * here beside the carousel pair for the same reason — both are homepage
+         * chrome an admin edits from a list rather than from a detail page.
+         *
+         * 🛑 There is deliberately NO `delete-section` counterpart. Section `order`
+         * is POSITIONAL, so removing one silently renumbers its neighbours — not
+         * something to offer from the public homepage, where the only confirmation
+         * a person gets is a dialog. `OwnerQuickActions` enforces the absence by
+         * omitting `remove` from the SECTION mapping, so no call site can pass a
+         * delete handler and have it render.
+         */
+        "edit-section": {
+            iconKey: "edit",
+            id: "admin.edit-section",
+            label: "Edit Section",
+            ariaLabel: "Edit this homepage section",
+            description: "Open the homepage sections list, which owns this section's config.",
+            kind: "ghost",
+            permissions: ["admin"],
+        },
         "delete-carousel": {
             iconKey: "delete",
             id: "admin.delete-carousel",

package/dist/_internal/shared/shipping/quote.js

@@ -78,7 +78,7 @@ export function roundShippingUp(rawRate) {
 export function reconcileShipping(quote, actual) {
     const charged = Number.isFinite(quote.chargedRate) ? Math.max(0, quote.chargedRate) : 0;
     const spent = Number.isFinite(actual.actualRate) ? Math.max(0, actual.actualRate) : 0;
-    const delta = roundPaise(charged - spent);
+    const delta = roundMoney(charged - spent);
     return {
         sellerAbsorbs: delta < 0 ? Math.abs(delta) : 0,
         buyerPoints: delta > 0 ? delta : 0,
@@ -88,12 +88,11 @@ export function reconcileShipping(quote, actual) {
 /**
  * Two decimal places.
  *
- * Money here is decimal rupees (the paise→rupees migration, Root Cause #31), so
- * a subtraction can leave a float artefact — `100 - 47.1` is `52.900000000000006`,
- * and that would become a points credit with eleven decimal places on a user's
- * balance.
+ * Money is stored as decimal rupees (Root Cause #31), so a subtraction can
+ * leave a float artefact — `100 - 47.1` is `52.900000000000006`, and that would
+ * become a points credit with eleven decimal places on a user's balance.
  */
-function roundPaise(value) {
+function roundMoney(value) {
     return Math.round(value * 100) / 100;
 }
 /**

package/dist/client.d.ts

@@ -387,6 +387,8 @@ export type { UserAccountHubViewProps, UserAccountHubViewLabels, UserOrdersViewP
 export { useOrders, useOrder, OrdersList } from "./features/orders/index";
 export { OrderStatusTimeline } from "./features/orders/components/OrderStatusTimeline";
 export type { OrderStatusTimelineProps } from "./features/orders/components/OrderStatusTimeline";
+export { EmiInstallmentsPanel } from "./features/orders/components/EmiInstallmentsPanel";
+export type { EmiInstallmentsPanelProps } from "./features/orders/components/EmiInstallmentsPanel";
 export { CountdownDisplay } from "./ui/components/CountdownDisplay";
 export type { CountdownDisplayProps } from "./ui/components/CountdownDisplay";
 export { OrderAddonBadges } from "./features/orders/components/OrderAddonBadges";
@@ -435,6 +437,8 @@ export type { ListingTypeCapability } from "./_internal/shared/listing-types/cap
 export { LISTING_TYPE_REGISTRY, pluginFor, detectListingTypeFromSlug } from "./_internal/shared/listing-types/_registry";
 export { useStoreListingEntitlements } from "./features/seller/hooks/useStoreListingEntitlements";
 export { OwnerQuickActions } from "./features/admin/components/OwnerQuickActions";
+export { RecordOwnerQuickActions } from "./features/admin/components/RecordOwnerQuickActions";
+export type { RecordOwnerQuickActionsProps, RecordQuickActionResource } from "./features/admin/components/RecordOwnerQuickActions";
 export { YourPurchaseStrip } from "./features/orders/components/YourPurchaseStrip";
 export { ReviewFormDrawer, reviewFormSchema } from "./features/reviews/components/ReviewFormDrawer";
 export type { ReviewFormDrawerProps, ReviewFormValues } from "./features/reviews/components/ReviewFormDrawer";
@@ -584,3 +588,22 @@ export { PriceIndexToolView } from "./features/price-index/components/PriceIndex
 export type { PriceIndexToolViewProps, PriceIndexToolResponse, PriceIndexResultRow, PriceIndexBandRow, PriceIndexConditionRow, } from "./features/price-index/components/PriceIndexToolView";
 export { COURIER_RATING_MIN_CONFIDENT_SAMPLES, courierRatingDisplay, isValidCourierVote, courierVoteId, rollUpCourierVotes, } from "./_internal/shared/features/shipping/courier-rating";
 export type { CourierRatingPair, CourierRatingDisplay, CourierRatingVote, CourierStats, } from "./_internal/shared/features/shipping/courier-rating";
+/**
+ * The `/api/checkout/pricing-preview` RESPONSE CONTRACT.
+ *
+ * 🛑 `export type`, from a `_internal/server` module, deliberately. A type-only
+ * re-export is fully erased at compile time — `audit-client-server-only-leak`
+ * states that explicitly — so this pulls no server chain into the client
+ * bundle. It is the one exception worth making for this module.
+ *
+ * The consumer had been keeping a HAND-WRITTEN copy of both shapes in
+ * `src/lib/api/payment-client.ts`, under a comment reading "mirrors
+ * `CheckoutPricingPreviewStore` on the server". It drifted exactly as Root
+ * Cause #42 predicts: the server gained `emiSurcharge`, the mirror did not, and
+ * the preview the cart rendered could not be assigned to the breakdown
+ * component that displays it. Four `tsc` errors across the cart and checkout
+ * clients, all from one missing field in a second definition of one shape.
+ *
+ * A response contract has exactly one owner — the handler that produces it.
+ */
+export type { CheckoutPricingPreview, CheckoutPricingPreviewStore, } from "./_internal/server/features/checkout/actions";

package/dist/client.js

@@ -405,6 +405,8 @@ export { couponDraftToPayload } from "./features/seller/schemas/coupon-form.js";
 export { UserAccountHubView, UserOrdersView, UserBidsView, OrderDetailView, UserReturnsView, useNotifications } from "./features/account/index.js";
 export { useOrders, useOrder, OrdersList } from "./features/orders/index.js";
 export { OrderStatusTimeline } from "./features/orders/components/OrderStatusTimeline.js";
+// Buyer-facing EMI schedule with a pay-any-instalment action.
+export { EmiInstallmentsPanel } from "./features/orders/components/EmiInstallmentsPanel.js";
 export { CountdownDisplay } from "./ui/components/CountdownDisplay.js";
 export { OrderAddonBadges } from "./features/orders/components/OrderAddonBadges.js";
 // Manual-payment (cash / UPI / EMI) shared constants — pure data + predicates,
@@ -458,6 +460,7 @@ export { LISTING_TYPE_REGISTRY, pluginFor, detectListingTypeFromSlug } from "./_
 export { useStoreListingEntitlements } from "./features/seller/hooks/useStoreListingEntitlements.js";
 // Pencil / clone / bin for whoever owns the record, on a PUBLIC surface.
 export { OwnerQuickActions } from "./features/admin/components/OwnerQuickActions.js";
+export { RecordOwnerQuickActions } from "./features/admin/components/RecordOwnerQuickActions.js";
 // "You ordered this - track it" / "your review - edit it", on a product page.
 export { YourPurchaseStrip } from "./features/orders/components/YourPurchaseStrip.js";
 // The first review form this app has had - see the component's header.

package/dist/constants/api-endpoints.d.ts

@@ -126,6 +126,10 @@ export declare const ADMIN_ENDPOINTS: {
     readonly BUNDLE_REBUILD: (id: string) => string;
     readonly CATEGORIES: "/api/admin/categories";
     readonly CATEGORY_BY_ID: (id: string) => string;
+    readonly PARTS: "/api/admin/parts";
+    readonly PART_BY_ID: (id: string) => string;
+    readonly BEYS: "/api/admin/beys";
+    readonly BEY_BY_ID: (id: string) => string;
     readonly BRANDS: "/api/admin/brands";
     readonly BRAND_BY_ID: (id: string) => string;
     readonly FAQS: "/api/admin/faqs";
@@ -690,6 +694,10 @@ export declare const API_ENDPOINTS: {
         readonly BUNDLE_REBUILD: (id: string) => string;
         readonly CATEGORIES: "/api/admin/categories";
         readonly CATEGORY_BY_ID: (id: string) => string;
+        readonly PARTS: "/api/admin/parts";
+        readonly PART_BY_ID: (id: string) => string;
+        readonly BEYS: "/api/admin/beys";
+        readonly BEY_BY_ID: (id: string) => string;
         readonly BRANDS: "/api/admin/brands";
         readonly BRAND_BY_ID: (id: string) => string;
         readonly FAQS: "/api/admin/faqs";
@@ -1219,6 +1227,10 @@ export declare const API_ROUTES: {
         readonly BUNDLE_REBUILD: (id: string) => string;
         readonly CATEGORIES: "/api/admin/categories";
         readonly CATEGORY_BY_ID: (id: string) => string;
+        readonly PARTS: "/api/admin/parts";
+        readonly PART_BY_ID: (id: string) => string;
+        readonly BEYS: "/api/admin/beys";
+        readonly BEY_BY_ID: (id: string) => string;
         readonly BRANDS: "/api/admin/brands";
         readonly BRAND_BY_ID: (id: string) => string;
         readonly FAQS: "/api/admin/faqs";

package/dist/constants/api-endpoints.js

@@ -157,6 +157,16 @@ export const ADMIN_ENDPOINTS = {
     BUNDLE_REBUILD: (id) => `/api/admin/bundles/${id}/rebuild`,
     CATEGORIES: "/api/admin/categories",
     CATEGORY_BY_ID: (id) => `/api/admin/categories/${id}`,
+    /*
+     * The generated reference databases. PATCH corrects a wrong extraction;
+     * DELETE removes a row that should not exist. No POST — see the note on
+     * `ROUTES.ADMIN.PARTS` for why creating one by hand is not a supported
+     * operation on generated data.
+     */
+    PARTS: "/api/admin/parts",
+    PART_BY_ID: (id) => `/api/admin/parts/${id}`,
+    BEYS: "/api/admin/beys",
+    BEY_BY_ID: (id) => `/api/admin/beys/${id}`,
     BRANDS: "/api/admin/brands",
     BRAND_BY_ID: (id) => `/api/admin/brands/${id}`,
     FAQS: "/api/admin/faqs",

package/dist/constants/field-names.d.ts

@@ -509,6 +509,52 @@ export declare const STORE_FIELDS: {
         readonly TOTAL_PRODUCTS: "stats.totalProducts";
     };
 };
+/**
+ * The two GENERATED reference databases.
+ *
+ * 🛑 NOT reused from `CATEGORY_FIELDS`. `audit-route-nav-field-constants`
+ * suggested `CATEGORY_FIELDS.NAME` for a query against `partGlossary`, and the
+ * string would have been identical — which is exactly why that would be the
+ * wrong fix. A constant's job is to say WHICH collection's field is meant, so
+ * that renaming one collection's field cannot silently retarget another's
+ * query. Same bytes, different claim.
+ */
+/**
+ * `modelComposition` — which parts a model is built from.
+ *
+ * 🛑 ITS OWN `CATEGORY_ID`, not `BEY_FIELDS.CATEGORY_ID`. The audit suggested
+ * the bey constant for a query against THIS collection, and the string is
+ * identical — which is precisely the substitution the comment on
+ * `PART_GLOSSARY_FIELDS` warns about. A composition row's `categoryId` points
+ * at the model leaf it describes; a bey's points at its own paired leaf. Same
+ * bytes, two different facts, and only one of them moves if either is renamed.
+ */
+export declare const MODEL_COMPOSITION_FIELDS: {
+    readonly ID: "id";
+    readonly CATEGORY_ID: "categoryId";
+    readonly SLOT: "slot";
+};
+export declare const PART_GLOSSARY_FIELDS: {
+    readonly ID: "id";
+    readonly NAME: "name";
+    readonly SLOT: "slot";
+    readonly CLASSIFICATION: "classification";
+    readonly CODE: "code";
+    readonly WEIGHT_G: "weightG";
+    /** Set by `applyAdminEdit`; the seed loader queries on it. */
+    readonly ADMIN_EDITED: "adminEdited";
+    readonly ADMIN_EDITED_FIELDS: "adminEditedFields";
+};
+export declare const BEY_FIELDS: {
+    readonly ID: "id";
+    readonly SLUG: "slug";
+    readonly NAME: "name";
+    readonly TYPE: "type";
+    readonly SYSTEM: "system";
+    readonly CATEGORY_ID: "categoryId";
+    readonly ADMIN_EDITED: "adminEdited";
+    readonly ADMIN_EDITED_FIELDS: "adminEditedFields";
+};
 export declare const CATEGORY_FIELDS: {
     readonly ID: "id";
     readonly NAME: "name";

package/dist/constants/field-names.js

@@ -613,6 +613,52 @@ export const STORE_FIELDS = {
 // ============================================================================
 // CATEGORY FIELDS
 // ============================================================================
+/**
+ * The two GENERATED reference databases.
+ *
+ * 🛑 NOT reused from `CATEGORY_FIELDS`. `audit-route-nav-field-constants`
+ * suggested `CATEGORY_FIELDS.NAME` for a query against `partGlossary`, and the
+ * string would have been identical — which is exactly why that would be the
+ * wrong fix. A constant's job is to say WHICH collection's field is meant, so
+ * that renaming one collection's field cannot silently retarget another's
+ * query. Same bytes, different claim.
+ */
+/**
+ * `modelComposition` — which parts a model is built from.
+ *
+ * 🛑 ITS OWN `CATEGORY_ID`, not `BEY_FIELDS.CATEGORY_ID`. The audit suggested
+ * the bey constant for a query against THIS collection, and the string is
+ * identical — which is precisely the substitution the comment on
+ * `PART_GLOSSARY_FIELDS` warns about. A composition row's `categoryId` points
+ * at the model leaf it describes; a bey's points at its own paired leaf. Same
+ * bytes, two different facts, and only one of them moves if either is renamed.
+ */
+export const MODEL_COMPOSITION_FIELDS = {
+    ID: "id",
+    CATEGORY_ID: "categoryId",
+    SLOT: "slot",
+};
+export const PART_GLOSSARY_FIELDS = {
+    ID: "id",
+    NAME: "name",
+    SLOT: "slot",
+    CLASSIFICATION: "classification",
+    CODE: "code",
+    WEIGHT_G: "weightG",
+    /** Set by `applyAdminEdit`; the seed loader queries on it. */
+    ADMIN_EDITED: "adminEdited",
+    ADMIN_EDITED_FIELDS: "adminEditedFields",
+};
+export const BEY_FIELDS = {
+    ID: "id",
+    SLUG: "slug",
+    NAME: "name",
+    TYPE: "type",
+    SYSTEM: "system",
+    CATEGORY_ID: "categoryId",
+    ADMIN_EDITED: "adminEdited",
+    ADMIN_EDITED_FIELDS: "adminEditedFields",
+};
 export const CATEGORY_FIELDS = {
     ID: "id",
     NAME: "name",

package/dist/features/about/components/PublicProfileView.js

@@ -16,6 +16,7 @@ import { pluginFor } from "../../../_internal/shared/listing-types/_registry.js"
 import { normalizeListingType } from "../../products/utils/listing-type.js";
 import { isAdminUser, isSellerUser } from "../../auth/role-predicates.js";
 import { User, Star, ShoppingBag, Package, Trophy, Globe, MapPin, ExternalLink } from "lucide-react";
+import { OwnerQuickActions } from "../../admin/components/OwnerQuickActions.js";
 const __P = {
     p4: "p-[var(--appkit-space-4)]",
     p6: "p-[var(--appkit-space-6)]",
@@ -120,7 +121,7 @@ export async function PublicProfileView({ userId, tab, }) {
     const profileHeroCtx = { displayName, photoURL, memberSince, isSeller, storeSlug, flex, page };
     const statItems = buildProfileStatItems(t, { listingCount, reviewCount, itemsSold, auctionsWon, totalOrders, isSeller });
     const activeTab = tab === "catalogue" ? "catalogue" : "overview";
-    return (_jsxs(Div, { className: "-mx-4 md:-mx-6 lg:-mx-8 -mt-6 sm:-mt-8 lg:-mt-10", children: [renderProfileHero(t, profileHeroCtx), _jsxs(Stack, { gap: "2xl", className: `${page.container.md}`, paddingY: "y-3xl", children: [_jsxs(Row, { gap: "md", padding: "t-xs", border: "bottom", children: [_jsx(TextLink, { href: `/profile/${userId}/overview`, variant: activeTab === "overview" ? "default" : "muted", weight: activeTab === "overview" ? "semibold" : "normal", children: "Overview" }), _jsx(TextLink, { href: `/profile/${userId}/catalogue`, variant: activeTab === "catalogue" ? "default" : "muted", weight: activeTab === "catalogue" ? "semibold" : "normal", children: "Catalogue" })] }), activeTab === "catalogue" ? (_jsx(PublicCatalogueView, { ownerSlug: userId })) : (_jsxs(_Fragment, { children: [renderProfileStatsRow(flex, statItems), renderProfileBioSection(pub), renderStoreDescriptionSection(isSeller, storeSlug ?? null, storeDescription ?? null, storeName, t), renderProfileListingsSection(t, products, storeSlug ?? null), renderAuthoredReviewsSection(t, reviewsAuthored, displayName), reviewsReceivedAsBuyer.length > 0 && renderBuyerReceivedReviewsSection(t, reviewsReceivedAsBuyer)] })), _jsx(Row, { justify: "center", padding: "t-xs", children: _jsxs(Link, { href: String(ROUTES.HOME), className: "text-[length:var(--appkit-text-sm)] text-[var(--appkit-color-text-faint)] hover:text-[var(--appkit-color-text-muted)]", children: ["\u2190 ", t("backHome")] }) })] })] }));
+    return (_jsxs(Div, { className: "-mx-4 md:-mx-6 lg:-mx-8 -mt-6 sm:-mt-8 lg:-mt-10", children: [renderProfileHero(t, profileHeroCtx), _jsxs(Stack, { gap: "2xl", className: `${page.container.md}`, paddingY: "y-3xl", children: [_jsx(Row, { justify: "end", children: _jsx(OwnerQuickActions, { resource: "USER", placement: "detail", recordLabel: displayName, editHref: String(ROUTES.ADMIN.USER_EDIT(userId)) }) }), _jsxs(Row, { gap: "md", padding: "t-xs", border: "bottom", children: [_jsx(TextLink, { href: `/profile/${userId}/overview`, variant: activeTab === "overview" ? "default" : "muted", weight: activeTab === "overview" ? "semibold" : "normal", children: "Overview" }), _jsx(TextLink, { href: `/profile/${userId}/catalogue`, variant: activeTab === "catalogue" ? "default" : "muted", weight: activeTab === "catalogue" ? "semibold" : "normal", children: "Catalogue" })] }), activeTab === "catalogue" ? (_jsx(PublicCatalogueView, { ownerSlug: userId })) : (_jsxs(_Fragment, { children: [renderProfileStatsRow(flex, statItems), renderProfileBioSection(pub), renderStoreDescriptionSection(isSeller, storeSlug ?? null, storeDescription ?? null, storeName, t), renderProfileListingsSection(t, products, storeSlug ?? null), renderAuthoredReviewsSection(t, reviewsAuthored, displayName), reviewsReceivedAsBuyer.length > 0 && renderBuyerReceivedReviewsSection(t, reviewsReceivedAsBuyer)] })), _jsx(Row, { justify: "center", padding: "t-xs", children: _jsxs(Link, { href: String(ROUTES.HOME), className: "text-[length:var(--appkit-text-sm)] text-[var(--appkit-color-text-faint)] hover:text-[var(--appkit-color-text-muted)]", children: ["\u2190 ", t("backHome")] }) })] })] }));
 }
 function buildProfileStatItems(t, ctx) {
     const { listingCount, reviewCount, itemsSold, auctionsWon, totalOrders, isSeller } = ctx;