@mohasinac/appkit 4.42.2 → 4.42.4

package/dist/client.d.ts

@@ -229,6 +229,15 @@ export { PERMISSION_GROUPS, PERMISSION_DOMAINS, getPermissionsForDomain, formatP
 export { Details, Summary } from "./ui/components/Details";
 export { ADMIN_ENDPOINTS } from "./constants/index";
 export { SELLER_ENDPOINTS } from "./constants/index";
+/**
+ * The buyer-portal endpoint map. Its admin and seller siblings were already
+ * here; this one was reachable only from `index.ts`, so a Client Component
+ * needing a /api/user/* URL had to either hardcode the path (blocked by
+ * audit-hardcoded-api-routes) or import the bare entry (the firebase-admin
+ * client-bundle leak audit-client-server-only-leak blocks). Added for
+ * BidDetailPageClient — checklist-page-wiring-detail-pages-detail-page-matches-list-modal.
+ */
+export { ACCOUNT_ENDPOINTS } from "./constants/index";
 export { TourProvider, useTour } from "./_internal/client/features/tour/TourProvider";
 export type { TourContextValue, TourRole } from "./_internal/client/features/tour/TourProvider";
 export { apiClient, ApiClientError } from "./http/index";

package/dist/client.js

@@ -280,6 +280,15 @@ export { PERMISSION_GROUPS, PERMISSION_DOMAINS, getPermissionsForDomain, formatP
 export { Details, Summary } from "./ui/components/Details";
 export { ADMIN_ENDPOINTS } from "./constants/index";
 export { SELLER_ENDPOINTS } from "./constants/index";
+/**
+ * The buyer-portal endpoint map. Its admin and seller siblings were already
+ * here; this one was reachable only from `index.ts`, so a Client Component
+ * needing a /api/user/* URL had to either hardcode the path (blocked by
+ * audit-hardcoded-api-routes) or import the bare entry (the firebase-admin
+ * client-bundle leak audit-client-server-only-leak blocks). Added for
+ * BidDetailPageClient — checklist-page-wiring-detail-pages-detail-page-matches-list-modal.
+ */
+export { ACCOUNT_ENDPOINTS } from "./constants/index";
 // P-16 — Tour system (driver.js-backed onboarding walkthrough).
 export { TourProvider, useTour } from "./_internal/client/features/tour/TourProvider";
 export { apiClient, ApiClientError } from "./http/index";

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

@@ -79,7 +79,33 @@ export function AdminSupportTicketsView({ children, ...props }) {
             { value: sortBy("updatedAt", "DESC"), label: "Recently updated" },
         ],
         columns: TICKET_COLUMNS,
-        mapRows: (response) => toRecordArray(response.tickets).map((item, index) => ({
+        /*
+         * 🛑 The item array is `items`. This read `response.tickets`, a key the
+         * route does not emit, so EVERY admin saw "No support tickets found".
+         *
+         * `GET /api/admin/support-tickets` ends in `successResponse(result)` where
+         * `result` is `supportRepository.listAll(model)` — a PagedResult, i.e.
+         * `{ items, total, page, pageSize, totalPages, hasMore }`. Measured against
+         * production: the API returns **total 10** while this list rendered its
+         * empty state, so nobody on staff could see a single support ticket.
+         *
+         * 🛑 I NEARLY MISSED THIS, and the reason is worth recording. The same
+         * defect was fixed on the BUYER side (`/user/support`) minutes earlier, and
+         * the sweep I ran afterwards searched for the `ok`-vs-`success` envelope
+         * flag — not for item-array key misreads — so it reported "no further
+         * copies" while this one sat one route away. A sweep narrower than the rule
+         * it is checking finds what it was shaped to find (Root Cause #84).
+         *
+         * A grep of the route then said it emitted `tickets`; the live API said
+         * `items`. The grep had matched the word elsewhere in the file. The
+         * MEASUREMENT is what settled it, which is the same lesson again.
+         *
+         * `tickets` is kept in the chain rather than deleted, for the same reason as
+         * the buyer-side fix: both spellings demonstrably exist in this codebase,
+         * and reading one key too many costs nothing while reading the wrong one
+         * cost the entire staff-facing queue.
+         */
+        mapRows: (response) => toRecordArray(response.items ?? response.tickets).map((item, index) => ({
             id: toStringValue(item.id, `ticket-${index}`),
             primary: toStringValue(item.subject, "No subject"),
             secondary: [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mohasinac/appkit",
-  "version": "4.42.2",
+  "version": "4.42.4",
   "license": "MIT",
   "publishConfig": {
     "access": "public"