@mohasinac/appkit 4.57.0 → 4.58.0

package/dist/features/admin/components/AdminBeysView.js

@@ -0,0 +1,178 @@
+"use client";
+import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-runtime";
+/**
+ * AdminBeysView — browse and correct the generated Beyblade database.
+ *
+ * ── 🛑 WHY THIS IS A CORRECTION SURFACE, NOT A CRUD SCREEN ────────────────
+ *
+ * `beys` is 1,988 rows built by committed generators from a crawled corpus. So
+ * there is no "Add Beyblade" button: a row authored here would have no source,
+ * would vanish on the next regeneration, and would make the claim "this dataset
+ * rebuilds from `appkit/src/seed/` alone" false. Adding one is a change to the
+ * generator.
+ *
+ * What this surface IS for is the thing the corpus demonstrably needs — fixing
+ * a wrong extraction. On mode data alone the source was wrong five times in one
+ * session: an inverted tip transition, a mechanism attributed to the wrong
+ * part, a part with no modes at all, and two misexpanded abbreviations. A
+ * correction made here survives the next reseed, field by field
+ * (`adminEditedFields`).
+ *
+ * @tag domain:beys
+ * @tag layer:feature
+ * @tag access:client
+ * @tag consumers:app/[locale]/admin/beys/page.tsx
+ */
+import React from "react";
+import { Heading, ListingLayout, Stack, Text } from "../../../ui/index.js";
+import { ADMIN_ENDPOINTS } from "../../../constants/api-endpoints.js";
+import { BEY_FIELDS } from "../../../constants/field-names.js";
+import { sortBy } from "../../../constants/sort.js";
+import { ROUTES } from "../../../next/routing/route-map.js";
+import { DataListingView } from "./DataListingView.js";
+/**
+ * 🛑 Rows are read from WHICHEVER envelope shape arrives.
+ *
+ * `apiClient.get()` unwraps `{success, data}` and returns `data` itself, so an
+ * endpoint that puts rows directly in `data` hands `mapRows` an ARRAY while one
+ * that nests them hands it an object. Reading `.data` off an array yields
+ * undefined — which is exactly how the categories listing rendered "No
+ * categories found" against a 200 carrying 58 rows. This route returns the
+ * object shape, and tolerating both is what keeps that from mattering.
+ */
+function extractRows(response) {
+    if (Array.isArray(response))
+        return response;
+    if (!response || typeof response !== "object")
+        return [];
+    const obj = response;
+    if (Array.isArray(obj.data))
+        return obj.data;
+    return Array.isArray(obj.items) ? obj.items : [];
+}
+function extractTotal(response) {
+    if (Array.isArray(response) || !response || typeof response !== "object")
+        return undefined;
+    const total = response.total;
+    return typeof total === "number" ? total : undefined;
+}
+/*
+ * audit-create-affordance-ok: this listing is deliberately inbound-only.
+ * The 1,988 rows are produced by committed generators from a crawled
+ * corpus, so there is no POST endpoint and no create route key to point a
+ * button at — a Beyblade authored by hand would have no source, would vanish
+ * on the next regeneration, and would make "this dataset rebuilds from
+ * appkit/src/seed/ alone" false. Adding one is a change to the generator.
+ * The surface exists to CORRECT a wrong extraction and to REMOVE a row that
+ * should not exist, which are the two operations the data actually needs.
+ */
+const COLUMNS = [
+    {
+        key: "primary",
+        header: "Beyblade",
+        sortable: true,
+        render: (row) => (_jsxs(Stack, { gap: "xs", children: [_jsx(Text, { weight: "semibold", color: "primary", children: row.primary }), _jsx(Text, { size: "xs", color: "muted", children: row.secondary })] })),
+    },
+    {
+        key: "weight",
+        header: "Mass",
+        className: "w-28",
+        render: (row) => (_jsx(Text, { size: "sm", color: "muted", children: row.weight })),
+    },
+    {
+        key: "edited",
+        header: "Corrected",
+        className: "w-28",
+        /*
+         * 🛑 Shown as a COLUMN, because a hand-corrected row behaves differently
+         * from its neighbours — the generator no longer owns the fields somebody
+         * fixed. Leaving that invisible is how a later maintainer concludes the
+         * generator is producing a value it is actually being prevented from
+         * writing. Text, not a colour-only dot (colour is never the only signal).
+         */
+        render: (row) => row.edited ? (_jsx(Text, { size: "xs", weight: "medium", children: "By hand" })) : (_jsx(Text, { size: "xs", color: "faint", children: "Generated" })),
+    },
+];
+const ADMIN_BEYS_CONFIG = {
+    portal: "admin",
+    title: "Beyblades",
+    subtitle: "The generated Beyblade database. Corrections made here are kept when the database is regenerated.",
+    searchPlaceholder: "Search Beyblades by name — Dranzer F, Variares…",
+    /*
+     * 🛑 `searchCommit: "enter"`, not debounce. The route's search is an indexed
+     * PREFIX range, so a partial word is a different query rather than a
+     * narrowing one — debouncing would fire a range query per pause and show
+     * confusing intermediate results. Enter also makes the prefix-only behaviour
+     * legible: you typed a prefix and asked for it.
+     */
+    searchCommit: "enter",
+    /*
+     * 🛑 DECLARED, so the placeholder can be CHECKED rather than trusted.
+     * The route matches exactly one field — an indexed prefix range on
+     * `name` — and the placeholder must not imply more. It is a prefix and
+     * it is case-sensitive; `mode` says so where a reader will see it.
+     */
+    search: {
+        placeholder: "Search Beyblades by name — a prefix, case-sensitive",
+        fields: ["name"],
+    },
+    emptyLabel: "No Beyblade matches that name",
+    filterKeys: [],
+    /*
+     * 🛑 Through `sortBy`, not a bare "name". The route currently ALWAYS
+     * orders by name and ignores the `sorts` param, so this is the only
+     * option — but writing it as a literal is what lets a field rename
+     * leave a sort string that silently sorts nothing.
+     */
+    defaultSort: sortBy(BEY_FIELDS.NAME, "ASC"),
+    pageSize: 25,
+    queryKey: ["admin", "beys"],
+    endpoint: ADMIN_ENDPOINTS.BEYS,
+    sortOptions: [{ value: sortBy(BEY_FIELDS.NAME, "ASC"), label: "Name A-Z" }],
+    columns: COLUMNS,
+    buildFilters: () => undefined,
+    getTotal: (response, rows) => extractTotal(response) ?? rows.length,
+    mapRows: (response) => extractRows(response).map((raw) => {
+        const r = raw;
+        /*
+         * 🛑 `≈` when the mass was SUMMED from the parts rather than stated by
+         * the source. 93% of beys have a mass but only 248 state it, and a
+         * derived figure shown as an exact one is the easiest way for this
+         * dataset to start lying — the same marking the detail page and the OG
+         * card use.
+         */
+        const summed = typeof r.weightGFromParts === "number" ? r.weightGFromParts : null;
+        const weight = typeof r.weightG === "number"
+            ? `${r.weightG} g`
+            : summed !== null
+                ? `≈ ${Math.round(summed * 10) / 10} g`
+                : "—";
+        return {
+            id: String(r.id ?? ""),
+            primary: String(r.name ?? r.id ?? "Unnamed Beyblade"),
+            /*
+             * System first: it is the one line a collector uses to place a bey in
+             * time, and it is present on 94% of them. The product code follows
+             * because two vendor releases of one model differ by little else.
+             */
+            secondary: [r.system, Array.isArray(r.productCodes) ? r.productCodes[0] : null]
+                .filter(Boolean)
+                .join(" · ") || "—",
+            weight,
+            edited: r.adminEdited === true,
+        };
+    }),
+    /*
+     * 🛑 `rowHrefTemplate`, not `rowHref`. Verified against the interface
+     * rather than guessed — there is no `rowHref` field, and an unknown key on
+     * an object literal typed by an interface is a compile error I could not
+     * have seen under this session's no-build cap.
+     */
+    rowHrefTemplate: (row) => String(ROUTES.ADMIN.BEYS_EDIT(row.id)),
+};
+export function AdminBeysView({ children, ...props }) {
+    if (React.Children.count(children) > 0) {
+        return (_jsxs(ListingLayout, { portal: "admin", ...props, children: [_jsx(Heading, { level: 1, className: "sr-only", children: "Beyblades" }), children] }));
+    }
+    return (_jsxs(_Fragment, { children: [_jsx(Heading, { level: 1, className: "sr-only", children: "Beyblades" }), _jsx(DataListingView, { config: ADMIN_BEYS_CONFIG })] }));
+}

package/dist/features/admin/components/AdminPartsView.d.ts

@@ -0,0 +1,27 @@
+/**
+ * AdminPartsView — browse and correct the generated part glossary.
+ *
+ * ── 🛑 WHY THIS IS A CORRECTION SURFACE, NOT A CRUD SCREEN ────────────────
+ *
+ * `partGlossary` is 2,488 rows built by committed generators from a crawled
+ * corpus. So there is no "Add part" button: a row authored here would have no
+ * source, would vanish on the next regeneration, and would make the claim
+ * "this dataset rebuilds from `appkit/src/seed/` alone" false. Adding a part is
+ * a change to the generator.
+ *
+ * What this surface IS for is the thing the corpus demonstrably needs — fixing
+ * a wrong extraction. On mode data alone the source was wrong five times in one
+ * session: an inverted tip transition, a mechanism attributed to the wrong
+ * part, a part with no modes at all, and two misexpanded abbreviations. A
+ * correction made here survives the next reseed, field by field
+ * (`adminEditedFields`).
+ *
+ * @tag domain:parts
+ * @tag layer:feature
+ * @tag access:client
+ * @tag consumers:app/[locale]/admin/parts/page.tsx
+ */
+import React from "react";
+import type { ListingLayoutProps } from "../../../ui";
+export type AdminPartsViewProps = ListingLayoutProps;
+export declare function AdminPartsView({ children, ...props }: AdminPartsViewProps): React.JSX.Element;

package/dist/features/admin/components/AdminPartsView.js

@@ -0,0 +1,160 @@
+"use client";
+import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-runtime";
+/**
+ * AdminPartsView — browse and correct the generated part glossary.
+ *
+ * ── 🛑 WHY THIS IS A CORRECTION SURFACE, NOT A CRUD SCREEN ────────────────
+ *
+ * `partGlossary` is 2,488 rows built by committed generators from a crawled
+ * corpus. So there is no "Add part" button: a row authored here would have no
+ * source, would vanish on the next regeneration, and would make the claim
+ * "this dataset rebuilds from `appkit/src/seed/` alone" false. Adding a part is
+ * a change to the generator.
+ *
+ * What this surface IS for is the thing the corpus demonstrably needs — fixing
+ * a wrong extraction. On mode data alone the source was wrong five times in one
+ * session: an inverted tip transition, a mechanism attributed to the wrong
+ * part, a part with no modes at all, and two misexpanded abbreviations. A
+ * correction made here survives the next reseed, field by field
+ * (`adminEditedFields`).
+ *
+ * @tag domain:parts
+ * @tag layer:feature
+ * @tag access:client
+ * @tag consumers:app/[locale]/admin/parts/page.tsx
+ */
+import React from "react";
+import { Heading, ListingLayout, Stack, Text } from "../../../ui/index.js";
+import { ADMIN_ENDPOINTS } from "../../../constants/api-endpoints.js";
+import { PART_GLOSSARY_FIELDS } from "../../../constants/field-names.js";
+import { sortBy } from "../../../constants/sort.js";
+import { ROUTES } from "../../../next/routing/route-map.js";
+import { DataListingView } from "./DataListingView.js";
+/**
+ * 🛑 Rows are read from WHICHEVER envelope shape arrives.
+ *
+ * `apiClient.get()` unwraps `{success, data}` and returns `data` itself, so an
+ * endpoint that puts rows directly in `data` hands `mapRows` an ARRAY while one
+ * that nests them hands it an object. Reading `.data` off an array yields
+ * undefined — which is exactly how the categories listing rendered "No
+ * categories found" against a 200 carrying 58 rows. This route returns the
+ * object shape, and tolerating both is what keeps that from mattering.
+ */
+function extractRows(response) {
+    if (Array.isArray(response))
+        return response;
+    if (!response || typeof response !== "object")
+        return [];
+    const obj = response;
+    if (Array.isArray(obj.data))
+        return obj.data;
+    return Array.isArray(obj.items) ? obj.items : [];
+}
+function extractTotal(response) {
+    if (Array.isArray(response) || !response || typeof response !== "object")
+        return undefined;
+    const total = response.total;
+    return typeof total === "number" ? total : undefined;
+}
+/*
+ * audit-create-affordance-ok: this listing is deliberately inbound-only.
+ * The 2,488 rows are produced by committed generators from a crawled
+ * corpus, so there is no POST endpoint and no create route key to point a
+ * button at — a part authored by hand would have no source, would vanish
+ * on the next regeneration, and would make "this dataset rebuilds from
+ * appkit/src/seed/ alone" false. Adding one is a change to the generator.
+ * The surface exists to CORRECT a wrong extraction and to REMOVE a row that
+ * should not exist, which are the two operations the data actually needs.
+ */
+const COLUMNS = [
+    {
+        key: "primary",
+        header: "Part",
+        sortable: true,
+        render: (row) => (_jsxs(Stack, { gap: "xs", children: [_jsx(Text, { weight: "semibold", color: "primary", children: row.primary }), _jsx(Text, { size: "xs", color: "muted", children: row.secondary })] })),
+    },
+    {
+        key: "weight",
+        header: "Weight",
+        className: "w-24",
+        render: (row) => (_jsx(Text, { size: "sm", color: "muted", children: row.weight })),
+    },
+    {
+        key: "edited",
+        header: "Corrected",
+        className: "w-28",
+        /*
+         * 🛑 Shown as a COLUMN, because a hand-corrected row behaves differently
+         * from its neighbours — the generator no longer owns the fields somebody
+         * fixed. Leaving that invisible is how a later maintainer concludes the
+         * generator is producing a value it is actually being prevented from
+         * writing. Text, not a colour-only dot (colour is never the only signal).
+         */
+        render: (row) => row.edited ? (_jsx(Text, { size: "xs", weight: "medium", children: "By hand" })) : (_jsx(Text, { size: "xs", color: "faint", children: "Generated" })),
+    },
+];
+const ADMIN_PARTS_CONFIG = {
+    portal: "admin",
+    title: "Parts",
+    subtitle: "The generated part glossary. Corrections made here are kept when the database is regenerated.",
+    searchPlaceholder: "Search parts by name — Rubber Flat, Dranzer…",
+    /*
+     * 🛑 `searchCommit: "enter"`, not debounce. The route's search is an indexed
+     * PREFIX range, so a partial word is a different query rather than a
+     * narrowing one — debouncing would fire a range query per pause and show
+     * confusing intermediate results. Enter also makes the prefix-only behaviour
+     * legible: you typed a prefix and asked for it.
+     */
+    searchCommit: "enter",
+    /*
+     * 🛑 DECLARED, so the placeholder can be CHECKED rather than trusted.
+     * The route matches exactly one field — an indexed prefix range on
+     * `name` — and the placeholder must not imply more. It is a prefix and
+     * it is case-sensitive; `mode` says so where a reader will see it.
+     */
+    search: {
+        placeholder: "Search parts by name — a prefix, case-sensitive",
+        fields: ["name"],
+    },
+    emptyLabel: "No part matches that name",
+    filterKeys: [],
+    /*
+     * 🛑 Through `sortBy`, not a bare "name". The route currently ALWAYS
+     * orders by name and ignores the `sorts` param, so this is the only
+     * option — but writing it as a literal is what lets a field rename
+     * leave a sort string that silently sorts nothing.
+     */
+    defaultSort: sortBy(PART_GLOSSARY_FIELDS.NAME, "ASC"),
+    pageSize: 25,
+    queryKey: ["admin", "parts"],
+    endpoint: ADMIN_ENDPOINTS.PARTS,
+    sortOptions: [{ value: sortBy(PART_GLOSSARY_FIELDS.NAME, "ASC"), label: "Name A-Z" }],
+    columns: COLUMNS,
+    buildFilters: () => undefined,
+    getTotal: (response, rows) => extractTotal(response) ?? rows.length,
+    mapRows: (response) => extractRows(response).map((raw) => {
+        const r = raw;
+        const weight = typeof r.weightG === "number" ? `${r.weightG} g` : "—";
+        return {
+            id: String(r.id ?? ""),
+            primary: String(r.name ?? r.id ?? "Unnamed part"),
+            /* The classification is what disambiguates a bare code like "105". */
+            secondary: [r.classification, r.code].filter(Boolean).join(" · ") || "—",
+            weight,
+            edited: r.adminEdited === true,
+        };
+    }),
+    /*
+     * 🛑 `rowHrefTemplate`, not `rowHref`. Verified against the interface
+     * rather than guessed — there is no `rowHref` field, and an unknown key on
+     * an object literal typed by an interface is a compile error I could not
+     * have seen under this session's no-build cap.
+     */
+    rowHrefTemplate: (row) => String(ROUTES.ADMIN.PARTS_EDIT(row.id)),
+};
+export function AdminPartsView({ children, ...props }) {
+    if (React.Children.count(children) > 0) {
+        return (_jsxs(ListingLayout, { portal: "admin", ...props, children: [_jsx(Heading, { level: 1, className: "sr-only", children: "Parts" }), children] }));
+    }
+    return (_jsxs(_Fragment, { children: [_jsx(Heading, { level: 1, className: "sr-only", children: "Parts" }), _jsx(DataListingView, { config: ADMIN_PARTS_CONFIG })] }));
+}

package/dist/features/admin/components/OwnerQuickActions.d.ts

@@ -1,5 +1,5 @@
 /** Which registry bucket supplies the labels and the confirm copy. */
-export type OwnerQuickActionsResource = "PRODUCT" | "CATEGORY" | "BRAND" | "FRANCHISE" | "BUNDLE" | "GROUP" | "SUBLISTING" | "EVENT" | "BLOG" | "REVIEW" | "STORE" | "USER" | "CAROUSEL" | "SECTION";
+export type OwnerQuickActionsResource = "PRODUCT" | "CATEGORY" | "BRAND" | "FRANCHISE" | "PART" | "BEY" | "BUNDLE" | "GROUP" | "SUBLISTING" | "EVENT" | "BLOG" | "REVIEW" | "STORE" | "USER" | "CAROUSEL" | "SECTION";
 export interface OwnerQuickActionsProps {
     resource: OwnerQuickActionsResource;
     /** Where the pencil goes — that record's dashboard editor. */
@@ -24,6 +24,23 @@ export interface OwnerQuickActionsProps {
      * `detail` sits in a header row beside the title.
      */
     placement?: "card" | "detail";
+    /**
+     * 🛑 Set this whenever `placement="detail"` sits on a DARK cover hero.
+     *
+     * `detail` otherwise renders the `ghost` variant, which is
+     * `color: var(--appkit-color-zinc-600)` — a dark grey that is correct on a
+     * page-surface header row and invisible on a cover photo. Every detail view
+     * that has a hero already computes a `hasCover` flag and flips each of its
+     * siblings to `color="inverse"`; this toolbar was the one element in that
+     * block that did not, so the pencil rendered near-black on near-black and
+     * read as "admins get no edit button" (Root Cause #67 — a theme-relative ink
+     * on a theme-invariant dark surface).
+     *
+     * Pass the SAME flag the rest of the hero branches on, not a literal `true`:
+     * a coverless hero falls back to the page surface, where the scrim's white
+     * ink would be invisible in the mirror-image way.
+     */
+    onMedia?: boolean;
     className?: string;
 }
-export declare function OwnerQuickActions({ resource, editHref, onDelete, onClone, ownerId, storeId, recordLabel, placement, className, }: OwnerQuickActionsProps): import("react").JSX.Element | null;
+export declare function OwnerQuickActions({ resource, editHref, onDelete, onClone, ownerId, storeId, recordLabel, placement, onMedia, className, }: OwnerQuickActionsProps): import("react").JSX.Element | null;

package/dist/features/admin/components/OwnerQuickActions.js

@@ -57,6 +57,15 @@ import { toUserMessage } from "../../../errors/error-display-map.js";
 const RESOURCE_LEAVES = {
     PRODUCT: { bucket: "PRODUCT", edit: "edit", remove: "delete", duplicate: "duplicate" },
     CATEGORY: { bucket: "CATEGORY", edit: "edit", remove: "delete" },
+    /*
+     * Both get a bin. Unlike the three pencil-only resources below, the blast
+     * radius of removing one reference row is SMALL and bounded: a bey keeps
+     * its parts list (`partName` sits beside `partId` for exactly this), a
+     * boxed set keeps its contents, and a category page keeps its listings.
+     * Nothing cascades, and the committed seed can put the row back.
+     */
+    PART: { bucket: "PART", edit: "edit", remove: "delete" },
+    BEY: { bucket: "BEY", edit: "edit", remove: "delete" },
     BRAND: { bucket: "BRAND", edit: "edit", remove: "delete" },
     BUNDLE: { bucket: "BUNDLE", edit: "edit", remove: "delete" },
     GROUP: { bucket: "GROUP", edit: "edit", remove: "delete" },
@@ -93,7 +102,7 @@ const RESOURCE_LEAVES = {
     USER: { bucket: "ADMIN", edit: "manage-user" },
     SECTION: { bucket: "ADMIN", edit: "edit-section" },
 };
-export function OwnerQuickActions({ resource, editHref, onDelete, onClone, ownerId, storeId, recordLabel, placement = "card", className = "", }) {
+export function OwnerQuickActions({ resource, editHref, onDelete, onClone, ownerId, storeId, recordLabel, placement = "card", onMedia = false, className = "", }) {
     const session = useOptionalSession();
     const isOwnerOrAdmin = useIsOwner(ownerId);
     const isAdmin = useIsAdmin();
@@ -164,6 +173,25 @@ export function OwnerQuickActions({ resource, editHref, onDelete, onClone, owner
      * resource, not to each of its call sites, or the next call site re-opens it.
      */
     const showDelete = Boolean(onDelete) && Boolean(leaves.remove);
+    /*
+     * 🛑 The scrim is for ANY dark backdrop, not only a card.
+     *
+     * `detail` used to hard-map to `ghost` (`color: var(--appkit-color-zinc-600)`),
+     * which is right on a page-surface header row and invisible on a cover photo
+     * — and every detail view with a hero puts this toolbar inside that hero,
+     * beside siblings it has already flipped to `color="inverse"`. The pencil
+     * therefore rendered near-black on near-black and read as "admins get no
+     * edit button at all". See `onMedia` above and Root Cause #67.
+     */
+    const onDark = placement === "card" || onMedia;
+    const neutralVariant = onDark ? "scrim" : "ghost";
+    /*
+     * Danger ink is dropped on a dark backdrop for the same reason: `danger`
+     * resolves to a theme-relative red that disappears against the hero. The bin
+     * keeps its confirm dialog, which is where the destructive intent is
+     * actually communicated — colour was never the safeguard.
+     */
+    const dangerVariant = onDark ? "scrim" : "danger";
     return (_jsxs(_Fragment, { children: [_jsxs(Row, { gap: "xs", align: "center", className: className, 
                 /*
                  * Stops the click reaching an ancestor `<Link>` or the card's own
@@ -172,7 +200,7 @@ export function OwnerQuickActions({ resource, editHref, onDelete, onClone, owner
                  */
                 onClick: (e) => {
                     e.stopPropagation();
-                }, children: [_jsx(IconButton, { "aria-label": editDef?.ariaLabel ?? editDef?.label ?? "Edit", size: "touch", variant: placement === "card" ? "scrim" : "ghost", icon: _jsx(Icon, { name: "edit" }), onClick: () => {
+                }, children: [_jsx(IconButton, { "aria-label": editDef?.ariaLabel ?? editDef?.label ?? "Edit", size: "touch", variant: neutralVariant, icon: _jsx(Icon, { name: "edit" }), onClick: () => {
                             /*
                              * `window.location`, not `next/link`. This component is rendered
                              * inside cards whose whole body is already an anchor, and nesting
@@ -183,7 +211,7 @@ export function OwnerQuickActions({ resource, editHref, onDelete, onClone, owner
                             if (typeof window !== "undefined")
                                 window.location.assign(editHref);
                         } }), showClone && (_jsx(IconButton, { "aria-label": (leaves.duplicate ? bucket[leaves.duplicate]?.ariaLabel ?? bucket[leaves.duplicate]?.label : undefined) ||
-                            "Duplicate", size: "touch", variant: placement === "card" ? "scrim" : "ghost", icon: _jsx(Icon, { name: "duplicate" }), onClick: () => void onClone?.() })), showDelete && (_jsx(IconButton, { "aria-label": deleteDef?.ariaLabel ?? deleteDef?.label ?? "Delete", size: "touch", variant: placement === "card" ? "scrim" : "danger", icon: _jsx(Icon, { name: "delete" }), onClick: () => setConfirmOpen(true) }))] }), showDelete && (_jsx(ConfirmDeleteModal, { isOpen: confirmOpen, onClose: () => setConfirmOpen(false), onConfirm: handleConfirmedDelete, isDeleting: deleting, title: confirmation?.title ?? "Delete this record?", message: recordLabel && confirmation
+                            "Duplicate", size: "touch", variant: neutralVariant, icon: _jsx(Icon, { name: "duplicate" }), onClick: () => void onClone?.() })), showDelete && (_jsx(IconButton, { "aria-label": deleteDef?.ariaLabel ?? deleteDef?.label ?? "Delete", size: "touch", variant: dangerVariant, icon: _jsx(Icon, { name: "delete" }), onClick: () => setConfirmOpen(true) }))] }), showDelete && (_jsx(ConfirmDeleteModal, { isOpen: confirmOpen, onClose: () => setConfirmOpen(false), onConfirm: handleConfirmedDelete, isDeleting: deleting, title: confirmation?.title ?? "Delete this record?", message: recordLabel && confirmation
                     ? `${confirmation.body}\n\nDeleting: ${recordLabel}`
                     : confirmation?.body, confirmText: confirmation?.confirmLabel ?? deleteDef?.label ?? "Delete", variant: "danger" }))] }));
 }

package/dist/features/admin/components/RecordOwnerQuickActions.d.ts

@@ -0,0 +1,31 @@
+/**
+ * The admin-owned resources this wrapper can delete.
+ *
+ * 🛑 Deliberately NOT every `OwnerQuickActionsResource`. `STORE`, `USER` and
+ * `SECTION` omit a `remove` leaf in `RESOURCE_LEAVES` because their blast
+ * radius is far wider than the page a bin would sit on, and `REVIEW` has no
+ * admin edit route to send the pencil to. Adding one here without adding its
+ * leaf there still renders no bin — the resource owns that decision, which is
+ * the point of gating it in two places.
+ */
+export type RecordQuickActionResource = "CATEGORY" | "BRAND" | "BUNDLE" | "GROUP" | "EVENT" | "BLOG" | "FRANCHISE" | "SUBLISTING" | "PART" | "BEY";
+export interface RecordOwnerQuickActionsProps {
+    resource: RecordQuickActionResource;
+    /** The record's document id — what the endpoint and the editor are keyed on. */
+    recordId: string;
+    /** Names the record in the delete confirmation. */
+    recordLabel?: string;
+    /**
+     * Forwarded to `OwnerQuickActions` so a store-owned record (a grouped
+     * listing, a store-authored bundle) stays visible to the seller who owns it
+     * and not only to an admin. `SessionUser.storeId` holds the store SLUG, not
+     * the Auth UID — two different id spaces, hence two props.
+     */
+    ownerId?: string;
+    storeId?: string;
+    placement?: "card" | "detail";
+    /** Pass the hero's own `hasCover` flag. See `OwnerQuickActions.onMedia`. */
+    onMedia?: boolean;
+    className?: string;
+}
+export declare function RecordOwnerQuickActions({ resource, recordId, recordLabel, ownerId, storeId, placement, onMedia, className, }: RecordOwnerQuickActionsProps): import("react").JSX.Element;

package/dist/features/admin/components/RecordOwnerQuickActions.js

@@ -0,0 +1,128 @@
+"use client";
+import { jsx as _jsx } from "react/jsx-runtime";
+/**
+ * The client half of `OwnerQuickActions` for every admin-owned collection.
+ *
+ * ## 🛑 Why a wrapper is REQUIRED, not a convenience
+ *
+ * `OwnerQuickActions` takes `onDelete` / `onClone` as FUNCTIONS, and every
+ * detail view that renders it (`CategoryDetailPageView`, `BrandDetailPageView`,
+ * `BundleDetailView`, …) is a Server Component. A closure cannot cross that
+ * boundary — React throws
+ *
+ *     Event handlers cannot be passed to Client Component props.
+ *
+ * at render. `ProductOwnerQuickActions` records that this exact mistake took
+ * down every `/products/[slug]` page in production, with an opaque digest per
+ * handler.
+ *
+ * That is why ten detail views were passing `editHref` and nothing else: the
+ * bin and the clone are rendered behind `{showDelete && …}` / `{showClone && …}`,
+ * so with no handler they silently do not exist. It read as "admins get no
+ * delete button", and the cause was a serialization boundary, not a permission.
+ *
+ * ## 🛑 Why ONE wrapper and not one per resource
+ *
+ * `ProductOwnerQuickActions` is resource-specific because products are the one
+ * collection a SELLER can also own, so its endpoints live under
+ * `SELLER_ENDPOINTS` and its clone has a bespoke redirect to the copy's editor.
+ * Everything here is admin-owned and differs only by three strings, so eight
+ * near-identical files would trip the Duplication Framework's Rule of Three
+ * immediately. One table, one component.
+ *
+ * ## Why the redirect lands on the ADMIN list
+ *
+ * You deleted the record from its own public page, so that page is now a 404 —
+ * staying is not an option and the public index tells you nothing about whether
+ * the delete worked. The admin list is where the absence is verifiable.
+ * `ProductOwnerQuickActions` differs deliberately: a seller may delete a
+ * product and has no admin list to land on.
+ *
+ * @tag domain:admin
+ * @tag layer:components
+ * @tag access:client
+ */
+import { useCallback } from "react";
+import { OwnerQuickActions } from "./OwnerQuickActions.js";
+import { ADMIN_ENDPOINTS } from "../../../constants/api-endpoints.js";
+import { ROUTES } from "../../../next/routing/route-map.js";
+const WIRING = {
+    CATEGORY: {
+        endpoint: ADMIN_ENDPOINTS.CATEGORY_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.CATEGORIES_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.CATEGORIES),
+    },
+    PART: {
+        endpoint: ADMIN_ENDPOINTS.PART_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.PARTS_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.PARTS),
+    },
+    BEY: {
+        endpoint: ADMIN_ENDPOINTS.BEY_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.BEYS_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.BEYS),
+    },
+    BRAND: {
+        endpoint: ADMIN_ENDPOINTS.BRAND_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.BRANDS_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.BRANDS),
+    },
+    BUNDLE: {
+        endpoint: ADMIN_ENDPOINTS.BUNDLE_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.BUNDLES_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.BUNDLES),
+    },
+    GROUP: {
+        endpoint: ADMIN_ENDPOINTS.GROUPED_LISTING_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.GROUPED_LISTINGS_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.GROUPED_LISTINGS),
+    },
+    EVENT: {
+        endpoint: ADMIN_ENDPOINTS.EVENT_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.EVENTS_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.EVENTS),
+    },
+    BLOG: {
+        endpoint: ADMIN_ENDPOINTS.BLOG_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.BLOG_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.BLOG),
+    },
+    /*
+     * A franchise row IS a category (`categoryType: "franchise"`), so it shares
+     * the category endpoint and editor — the same reasoning `RESOURCE_LEAVES`
+     * uses to give it the category copy. Only the landing page differs.
+     */
+    FRANCHISE: {
+        endpoint: ADMIN_ENDPOINTS.CATEGORY_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.CATEGORIES_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.CATEGORIES),
+    },
+    SUBLISTING: {
+        endpoint: ADMIN_ENDPOINTS.SUBLISTING_CATEGORY_BY_ID,
+        editHref: (id) => String(ROUTES.ADMIN.SUBLISTING_CATEGORIES_EDIT(id)),
+        afterDelete: String(ROUTES.ADMIN.SUBLISTING_CATEGORIES),
+    },
+};
+export function RecordOwnerQuickActions({ resource, recordId, recordLabel, ownerId, storeId, placement = "detail", onMedia, className, }) {
+    const wiring = WIRING[resource];
+    /*
+     * 🛑 THROWS on a failed DELETE rather than returning quietly.
+     *
+     * `OwnerQuickActions.handleConfirmedDelete` catches and toasts, and success
+     * navigates away — so a swallowed failure is indistinguishable from "it
+     * worked but the page did not move", and the obvious user response is to
+     * press the button again. Returning early on `!res.ok` is the bug
+     * `ProductOwnerQuickActions` documents having had.
+     */
+    const handleDelete = useCallback(async () => {
+        const res = await fetch(wiring.endpoint(recordId), { method: "DELETE" });
+        if (!res.ok) {
+            const body = (await res.json().catch(() => null));
+            throw Object.assign(new Error("Delete failed"), { code: body?.code });
+        }
+        if (typeof window !== "undefined") {
+            window.location.assign(wiring.afterDelete);
+        }
+    }, [wiring, recordId]);
+    return (_jsx(OwnerQuickActions, { resource: resource, placement: placement, onMedia: onMedia, className: className, recordLabel: recordLabel, ownerId: ownerId, storeId: storeId, editHref: wiring.editHref(recordId), onDelete: handleDelete }));
+}