@mohasinac/appkit 4.14.0 → 4.16.0

package/dist/features/tester/seed-data/tester-checklist-seed-data.js

@@ -1116,6 +1116,236 @@ const rawTesterChecklistItems = [
                     label: "An accepted offer past its 48-hour checkout window can no longer be checked out, and is cleared from the cart with a notification to the buyer",
                     description: "Background/low-priority — requires waiting out the window or adjusting the fixture's checkoutDeadline.",
                 },
+                {
+                    key: "nav-item-invalid-href-inline",
+                    label: "A nav item with a bad destination is refused on the FIELD, not by a banner",
+                    description: "The routes always validated nav items; the form did not, so an invalid href came back as a 400 after a round-trip. Enter \"products\" (no leading slash) and confirm the error appears under the Destination field.",
+                    href: "/admin/navigation",
+                },
+                {
+                    key: "homepage-section-invalid-config-inline",
+                    label: "A homepage section with malformed config JSON, or a negative order, is refused inline",
+                    description: "Same shape: the route validated, the form did not. Paste broken JSON into Config, and separately set Order to -1 — each should report on its own field.",
+                    href: "/admin/sections",
+                },
+                {
+                    key: "classified-keeps-meetup-city",
+                    label: "A classified listing still has its meetup city after saving",
+                    description: "Regression test for CONFIRMED silent data loss found 2026-08-24: the product create schema stripped every key it did not name, and it named NONE of the classified / digital-code / live-item / prize-draw fields. A seller filled them in, pressed Publish, saw a success — and the fields were dropped before the write. Create a classified with a meetup city and contact method, save, then reopen it: both must still be there.",
+                    href: "/store/classified/new",
+                },
+                {
+                    key: "live-item-keeps-species-and-cites",
+                    label: "A live-item listing keeps its species, transport method, permitted jurisdictions and CITES reference",
+                    description: "Same bug. Jurisdiction is the one that matters most — shipping a live animal into a territory that forbids it is exactly what that field exists to prevent, and it was being discarded.",
+                    href: "/store/live/new",
+                },
+                {
+                    key: "digital-code-keeps-delivery-method",
+                    label: "A digital-code listing keeps its delivery method and pool size",
+                    href: "/store/digital-codes/new",
+                },
+                {
+                    key: "prize-draw-keeps-entry-price",
+                    label: "A prize draw keeps its price per entry and maximum entries",
+                    href: "/store/prize-draws/new",
+                },
+                {
+                    key: "per-type-fields-survive-EDIT-too",
+                    label: "Editing a classified's TITLE does not wipe its meetup city",
+                    description: "The fix had to cover the update path as well as create — a create-only fix would mean the listing saved correctly and then lost its per-type block the first time anyone edited anything else (Root Cause #39).",
+                    href: "/store/classified",
+                },
+                {
+                    key: "address-routes-normalised",
+                    label: "Adding and editing an address works, and the OLD urls still resolve",
+                    description: "/user/addresses/add and /user/addresses/edit/[id] were the only two non-standard route shapes in the app; every other entity uses /new and /[id]/edit. Both old paths are kept as redirects, so a bookmark still works. Check the buttons on the addresses page, then visit /user/addresses/add directly and confirm it lands on /user/addresses/new.",
+                    href: "/user/addresses",
+                },
+                {
+                    key: "custom-role-rejects-fake-permissions",
+                    label: "A custom role cannot be saved with a permission this system does not define",
+                    description: "Regression test for a real gap found 2026-08-24: both the create and update routes spread the raw request body into Firestore with NO validation, and neither page had a schema. Enter \"admin:widgets:frobnicate\" in the permissions box — it should be refused and NAMED. A permission outside the catalogue never matches anything, so the role would have read as configured and granted nothing.",
+                    href: "/admin/roles/new",
+                },
+                {
+                    key: "custom-role-edit-does-not-rewrite-creator",
+                    label: "Editing a role does not change who created it",
+                    description: "The edit page used to PATCH the whole loaded document — id, createdAt, createdBy and slug included — so any save re-attributed the privilege grant and could change the role's stable identifier. Edit a role, save, and confirm its creator and slug are unchanged.",
+                    href: "/admin/roles",
+                },
+                {
+                    key: "custom-role-rejects-empty",
+                    label: "A role with no name cannot be created",
+                    href: "/admin/roles/new",
+                },
+                {
+                    key: "bid-row-opens-in-all-three-portals",
+                    label: "A bid can be OPENED, not just seen — as a buyer, as a seller, and as an admin",
+                    description: "All three bid listings were dead ends: a row could be seen and never opened, so the amount, auction, timing and outcome existed only as a table row. Open one from /user/bids, /store/bids and /admin/bids and confirm each shows the auction, amount, when it was placed and its status.",
+                    href: "/user/bids",
+                },
+                {
+                    key: "bid-detail-hides-bidder-from-buyer",
+                    label: "A buyer's own bid detail does NOT show a bidder name; the seller and admin views DO",
+                    description: "One shared field builder serves all three portals, gated on the viewer's role — so a copy-paste cannot start showing one buyer another's identity.",
+                    href: "/user/bids",
+                },
+                {
+                    key: "admin-bid-view-before-cancel",
+                    label: "The admin bid row menu offers View before Cancel",
+                    description: "It previously offered ONLY Cancel — a destructive action on a record the admin had never been able to read. A menu of pure mutations is not a detail affordance (Root Cause #56).",
+                    href: "/admin/bids",
+                },
+                {
+                    key: "bid-row-keyboard-reachable",
+                    label: "A bid row can be opened with the keyboard, and public bid history rows still cannot",
+                    description: "Rows are only focusable when they are actually interactive. On an auction's PUBLIC bid history the same table renders with no row handler, so those rows must not be tab stops.",
+                    href: "/user/bids",
+                },
+                {
+                    key: "listing-template-edit-page-works",
+                    label: "Editing a listing template loads, saves and deletes — the page is not a 404",
+                    description: "Regression test for a real bug found 2026-08-24: /api/store/listing-templates/[id] did not exist, while the constant, the edit page's three calls (GET on load, PATCH on save, DELETE) and the list page's Edit button all did. Clicking Edit gave a page that 404'd on load, on save and on delete. Open a template from the list, change its name, save, reopen.",
+                    href: "/store/listing-templates",
+                },
+                {
+                    key: "listing-template-not-editable-across-stores",
+                    label: "One seller cannot open another seller's listing template by URL",
+                    description: "The new route checks the template's storeId against the caller's own store and returns \"not found\" (deliberately not \"forbidden\", which would confirm the id exists).",
+                    href: "/store/listing-templates",
+                },
+                {
+                    key: "payout-method-rejects-blank-bank-details",
+                    label: "A BANK payout method cannot be saved with a blank account number, IFSC or holder name",
+                    description: "This was validated at ZERO layers: the fields were bare inputs with no `required` and no pattern, the page's onSave checked nothing, and both the POST and PATCH routes wrote the raw request body straight into Firestore. An empty bank payout method saved cleanly and only failed at payout time. Select Bank account, leave the fields blank, save — each should be refused on the field itself.",
+                    href: "/store/payout-methods/new",
+                },
+                {
+                    key: "payout-method-rejects-bad-ifsc",
+                    label: "An IFSC code of the wrong shape is refused",
+                    description: "Enter \"ABC123\" as the IFSC. It should be refused inline with the expected format, matching the rule Payout Settings already enforces. Then check a UPI method rejects a VPA with no @.",
+                    href: "/store/payout-methods/new",
+                },
+                {
+                    key: "shipping-config-rejects-rateless-rule",
+                    label: "A \"flat\" shipping rule with no flat rate is refused, and a negative rate is refused",
+                    description: "Both the page and the route used to accept anything — the route spread the raw body into Firestore, so a rate of \"abc\" or a negative free-above threshold was persisted verbatim.",
+                    href: "/store/shipping-configs/new",
+                },
+                {
+                    key: "grouped-listing-count-not-caller-settable",
+                    label: "A grouped listing's member count always matches its member list",
+                    description: "activeMemberCount is derived from productIds.length by the route and is no longer accepted from the request body — it is what the public visibility check reads, so a caller-supplied count could have hidden or shown a group incorrectly.",
+                    href: "/store/grouped-listings",
+                },
+                {
+                    key: "store-feature-new-actually-creates",
+                    label: "Creating a store feature badge from /store/features/new actually creates it",
+                    description: "Regression test for a real bug found 2026-08-24: that page collected a single Label, validated it was non-empty, then navigated back to the list WITHOUT calling any API — the badge was silently discarded and the seller saw a normal success flow. It now renders the real editor, so all ten fields are present and the badge appears in the list afterwards.",
+                    href: "/store/features/new",
+                },
+                {
+                    key: "store-feature-edit-page-exists",
+                    label: "A store feature badge can be edited on its own page, not only in a drawer",
+                    description: "ROUTES.STORE.FEATURES_EDIT pointed at /store/features/[id]/edit with no page behind it and no caller anywhere — a dead route key. Open a badge's edit page directly by URL and confirm it loads with the badge's current values.",
+                    href: "/store/features",
+                },
+                {
+                    key: "feature-editor-validates",
+                    label: "The feature badge editor reports what is wrong instead of just disabling Save",
+                    description: "It had NO validation: ten fields, `required` on the inputs (an HTML attribute a programmatic submit bypasses), and nothing else — max lengths, display-order bounds and the product-types minimum were never checked. Submit with an over-long label, or a store-scoped badge with no store selected, and confirm the error appears on the field itself.",
+                    href: "/admin/features/new",
+                },
+                {
+                    key: "store-category-rejects-empty",
+                    label: "A storefront category with no label cannot be created",
+                    description: "Both the form AND the route used to accept anything — the page had raw inputs with no validation and the API spread the request body straight into Firestore, so a completely empty category could be saved. They now share one schema. Confirm an empty Label is refused inline, not by a generic \"Save failed\" toast.",
+                    href: "/store/categories/new",
+                },
+                {
+                    key: "blog-editor-sections-not-steps",
+                    label: "The blog editor shows every field at once in collapsible sections — not a 4-step wizard that blocks step 2",
+                    description: "Open any post. Content / Media / SEO & Tags / Publish should all be reachable immediately, with ONE Save button at the bottom. Previously a missing title blocked access to every later step, so a post could become uneditable because of a field on page 1.",
+                    href: "/admin/blog",
+                },
+                {
+                    key: "blog-existing-post-slug-is-valid",
+                    label: "Opening an EXISTING blog post shows no error on the Slug field",
+                    description: "Regression test for a real bug found 2026-08-24: the form required slugs to start with `blog-`, but all 20 stored posts hold the bare slug (the `blog-` prefix is on the document ID, not the slug field, and the public URL uses the bare form). Every existing post therefore opened with an invalid Slug, and correcting it to satisfy the rule would have changed the stored slug and 404'd the live URL.",
+                    href: "/admin/blog",
+                },
+                {
+                    key: "blog-new-post-url-matches-existing",
+                    label: "A newly created post's public URL has the same shape as an existing post's — no doubled `blog-` segment",
+                    description: "Create a post titled \"Test Slug Shape\", save, then open it publicly. The URL should read /blog/test-slug-shape, matching every seeded post.",
+                    href: "/admin/blog/new",
+                },
+                {
+                    key: "blog-readtime-updates-on-edit",
+                    label: "Editing a post's body updates its \"N min read\" estimate",
+                    description: "It used to be computed on create only, so the estimate froze at whatever the first draft was (Root Cause #39 — a CREATE transform with no UPDATE counterpart). Add several paragraphs to an existing post, save, and confirm the read time grows.",
+                    href: "/admin/blog",
+                },
+                {
+                    key: "blog-error-summary-jumps-to-section",
+                    label: "Clearing the title shows an error summary whose link OPENS the right section and focuses the field",
+                    description: "The jump was dead before this work — the section list was hardcoded empty in both context paths, so the summary's link resolved to nothing for every form in the app.",
+                    href: "/admin/blog",
+                },
+                {
+                    key: "blog-media-survives-collapse",
+                    label: "Collapsing the Media section mid-upload does NOT cancel the upload",
+                    description: "Collapsible panels unmount their children by default, which discards an in-flight transfer. The Media section is explicitly kept mounted.",
+                    href: "/admin/blog",
+                },
+                {
+                    key: "event-editor-sections-not-steps",
+                    label: "The event editor shows Details / Media / Settings / Raffle as sections, all reachable at once",
+                    description: "The old wizard gated Settings behind Details validating, so a missing end date made a poll's options unreachable. Also confirm the per-type rules still surface inline: an Offer event with no coupon, and a Poll with fewer than 2 options, should each show an error on the field itself rather than a step-blocking banner.",
+                    href: "/admin/events",
+                },
+                {
+                    key: "offer-history-timeline-renders",
+                    label: "An offer shows a timeline of every phase it went through, each stamped with who did it and when",
+                    description: "Open any offer on My Offers and expand its history. Offer made / countered / accepted / paid should each appear with a real timestamp and a Buyer or Store tag. Before this existed, an offer showed only its current status — the negotiation that produced it was not merely un-displayed, it was destroyed: each counter created a brand-new unlinked document.",
+                    href: "/user/offers",
+                },
+                {
+                    key: "offer-history-legacy-no-fabricated-date",
+                    label: "An offer with NO recorded history still renders a timeline, and its Expired step shows an em-dash rather than a made-up date",
+                    description: "Open the X Wizard Arrow expired offer — it is seeded deliberately without statusHistory, which is the exact shape of every offer written before this feature. Its timeline must still render, and the Expired step must show a dash, not a date. A date there would be fabricated: expireMany never wrote one, updatedAt means \"last write of any kind\", and expiresAt is a deadline rather than an event.",
+                    href: "/admin/offers",
+                },
+                {
+                    key: "offer-chain-walks-three-rounds",
+                    label: "A three-round negotiation reads as ONE story, oldest first, with rounds 1 and 2 labelled Superseded — never Withdrawn",
+                    description: "Open the Metal Storm Pegasus offer in the admin list. All three rounds should appear on one rail under Round 1 / Round 2 / Round 3 dividers, each with its own note. The first two rounds are stored as withdrawn but carry supersededByOfferId, and must read neutral: the buyer did not walk away, they countered. Contrast the Driger V offer, a genuine walk-away, which reads Withdrawn.",
+                    href: "/admin/offers",
+                },
+                {
+                    key: "offer-detail-opens-on-fresh-data",
+                    label: "Opening an offer row fetches that offer, rather than showing whatever the list last cached",
+                    description: "Open an offer, close it, have the seller respond in another session, then reopen the same row — the panel should show the new state without a full page reload, and the chain should be present.",
+                    href: "/admin/offers",
+                },
+                {
+                    key: "admin-offer-cancel-requires-reason",
+                    label: "Admin Cancel opens a form demanding a reason — a short one is rejected inline, and a valid one reaches the buyer, the audit log AND the offer's own timeline",
+                    description: "Cancel an offer as an admin. Type fewer than 10 characters: it must be refused before submitting. Then give a real reason and confirm four things: the offer is cancelled, the buyer's locked cart line is cleared (their whole cart is otherwise blocked by the offer lane), the buyer's notification quotes the reason, and the action appears in both /admin/audit-log and the offer's own timeline. Previously the route accepted a reason and never read it, so the buyer was told nothing.",
+                    href: "/admin/offers",
+                },
+                {
+                    key: "admin-cannot-accept-or-counter",
+                    label: "The admin row menu offers only View and Cancel — never Accept, Counter or Decline",
+                    description: "The store keeps sole authority over its own pricing; admin is a coordinator, and cancel is an escalation that is itself recorded. There should also be no bulk Cancel: one shared reason across a mixed selection is worse audit data than none.",
+                    href: "/admin/offers",
+                },
+                {
+                    key: "store-still-accepts",
+                    label: "The store can still Accept, Counter and Decline its own offers after the admin surface was added",
+                    href: "/store/offers",
+                },
             ],
         },
         {
@@ -1243,6 +1473,42 @@ const rawTesterChecklistItems = [
                 { key: "my-prize-draws", label: "\"My Prize Draw Entries\" shows accurate entries and outcomes", href: "/user/prize-draws" },
                 { key: "my-digital-codes", label: "\"My Digital Codes\" shows purchased codes correctly", href: "/user/digital-codes" },
                 { key: "my-offers", label: "\"My Offers\" list shows accurate offer history", href: "/user/offers" },
+                {
+                    key: "order-timeline-shows-real-events",
+                    label: "An order's timeline shows the transitions that actually happened, each stamped with who made it",
+                    description: "Open a delivered order. Placed / confirmed / shipped with its tracking number / delivered should each carry a real timestamp and a Buyer, Store, Admin or System tag. This used to be synthesised from four scalar date fields, so any transition without a dedicated date column — a payment review, a re-upload request — was invisible.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-partial-refund-in-timeline",
+                    label: "A PARTIAL refund appears on the order timeline with its amount and reason",
+                    description: "Open the X Knife Shinobi order. A partial refund changes no status field at all, so it can only reach the timeline as an explicit entry — if partial refunds are missing while full ones show, that is the bug.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-auction-won-vs-bought-out",
+                    label: "A won auction and a bought-out auction are visibly DIFFERENT on the order, not both just \"auction\"",
+                    description: "Compare the Diablo Nemesis order (won at ₹6,200 against a real ladder) with the Spriggan Requiem order (bought out at ₹4,999 while the standing bid was ₹3,100). Both are orderType \"auction\" — only the provenance record separates them. Crucially the buyout must NOT report zero bids: a buyout is itself a real bid, and Buy Now is no longer gated on the auction having no bids.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-offer-shows-what-was-saved",
+                    label: "An order placed from an accepted offer shows the offered amount against the asking price at the time",
+                    description: "The listing price can change afterwards, which is exactly why it is captured once at order time and never recomputed.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-history-no-money-churn",
+                    label: "The order timeline shows status, payment and refund events only — NOT every coupon or add-on the buyer tried",
+                    description: "Deliberate: the final coupon and add-on state already lives on the order. Replaying pricing churn would bury the handful of transitions anyone actually reads.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-history-carries-no-personal-data",
+                    label: "No timeline entry anywhere shows a buyer's name or email — only a role tag",
+                    description: "Security-relevant, not cosmetic. PII encryption does not descend into arrays, so a name written into an order or offer history would sit in the database in plain text and never be decrypted on the way out.",
+                    href: "/admin/orders",
+                },
                 {
                     key: "my-returns",
                     label: "Requesting and viewing a return works",
@@ -2787,6 +3053,90 @@ const rawTesterChecklistItems = [
                 { key: "support-tickets-triage-admin", label: "Admin can triage support tickets", href: "/admin/support-tickets" },
                 { key: "item-requests-admin", label: "Admin can manage item requests", href: "/admin/item-requests" },
                 { key: "reports-admin", label: "Admin reports queue works correctly", href: "/admin/reports" },
+                {
+                    key: "moderation-reject-requires-reason",
+                    label: "Rejecting media in the moderation queue REFUSES an empty reason, with the error shown on the Reason field itself",
+                    description: "Fixed 2026-08-24 — all four review surfaces (the queue page's inline Reject and the detail page's Reject, on both moderation and reports) submitted an empty note happily, so media could be blocked with no record of why. Press Reject with the box empty: it must refuse inline, not toast, and not save. Check BOTH /admin/moderation and a single item's detail page — they used to be two separate copies of the same modal.",
+                    href: "/admin/moderation",
+                },
+                {
+                    key: "moderation-reject-keeps-note-on-failure",
+                    label: "If a reject fails to save, the modal STAYS OPEN with the typed reason intact",
+                    description: "The modal closed on any outcome before. A decision that did not save must not look like one that did — expect an error toast and the reason still in the box, not a closed modal.",
+                    href: "/admin/moderation",
+                },
+                {
+                    key: "report-dismiss-asks-why",
+                    label: "Dismissing a report ASKS for a reason instead of silently recording the word \"Dismissed\"",
+                    description: "Fixed 2026-08-24 — Dismiss used to send a hardcoded resolution of \"Dismissed\", which is the status restated rather than a reason, so a dismissed report carried no explanation for the reporter or the next admin. It now opens the same required-note modal that Action does.",
+                    href: "/admin/reports",
+                },
+                {
+                    key: "report-close-stores-a-real-date",
+                    label: "Actioning or dismissing a report records a resolved date that renders as a DATE, not as raw text",
+                    description: "Fixed 2026-08-24 — both report surfaces sent `resolvedAt: new Date()`, which JSON turns into a string, and the route spread it straight into a field the document declares as a Date. Seeded reports held real timestamps, so the collection carried two shapes for one field. The server stamps it now and the client cannot send it. Close a report, then confirm via the admin detail page that the resolved date is present and well-formed.",
+                    href: "/admin/reports",
+                },
+                {
+                    key: "report-status-rejects-unknown-values",
+                    label: "A report or moderation item cannot be moved to a status outside its real set",
+                    description: "Both PATCH routes previously spread the raw request body into Firestore with no schema, so any key and any status string could be written. Confirm the normal Take / Action / Dismiss and Approve / Reject flows still all work — that is what the tightening must not have broken.",
+                    href: "/admin/reports",
+                },
+                {
+                    key: "admin-tables-render-badges-not-text",
+                    label: "Admin list tables show a coloured STATUS BADGE, a thumbnail and formatted money — not raw text",
+                    description: "Fixed 2026-08-25 — `column-renderers.tsx` was promised by its own sibling's docstring and never written (it could not be: a .ts and .tsx of the same name both emit the same .js). Every column without a hand-written renderer fell back to String(value), so a price read `1499` and a date read as a raw ISO string. Check a few different admin lists.",
+                    href: "/admin/products",
+                },
+                {
+                    key: "admin-table-readable-on-phone",
+                    label: "An admin list is readable at phone width — it switches to the card/list view instead of squeezing a table",
+                    description: "Fixed 2026-08-25 — no column-level responsive behaviour existed at all (`TableColumn.hidden` was documented but no DataTable ever read it). Below md the table view is now suppressed entirely; from md up, low-priority columns (created/updated dates, ids, view counts) drop out progressively. Resize from 320px to 1400px and confirm columns reappear rather than the row wrapping.",
+                    href: "/admin/orders",
+                },
+                {
+                    key: "action-buttons-have-icons",
+                    label: "Buttons driven by the action registry show an icon beside their label",
+                    description: "Fixed 2026-08-25 — `ActionDef.iconKey` existed on the type, was set on 2 of 220 actions, and was rendered by nothing. All 220 now carry one and `<Button action={…}>` renders it. Spot-check a row action menu and a bulk action bar.",
+                    href: "/admin/products",
+                },
+                {
+                    key: "sold-flag-badge-readable",
+                    label: "The \"Sold\" flag chip on an admin product card is legible in BOTH light and dark themes",
+                    description: "Fixed 2026-08-25 — the flag list gave `isSold` two backgrounds and two inks on one element, so the painted colour was decided by stylesheet order rather than by the list. The identical bug was found on the scammer status badge the day before. Also check \"Promoted\", which was raw dual-theme purple.",
+                    href: "/admin/products",
+                },
+                {
+                    key: "homepage-section-all-types-creatable",
+                    label: "EVERY section type in the New Section dropdown can actually be created — especially Featured Bundles, Prize Draws, Event Raffles and Collection Cards",
+                    description: "Fixed 2026-08-24 — the create route validated `type` against a hand-written list of 21 values while the union (and the dropdown) had 25. Those four types could be chosen, configured in full through their own builders, and then failed with a 400 on Save. Walk the dropdown and create one of each of the four named types.",
+                    href: "/admin/sections",
+                },
+                {
+                    key: "analytics-alert-threshold-is-numeric",
+                    label: "An analytics alert refuses a non-numeric threshold and a zero/blank time window",
+                    description: "Fixed 2026-08-24 — the create route spread the raw body into Firestore, so a threshold typed as text was stored as text and the rule then compared strings (\"9\" > \"10\"). The alert saved, listed, and looked configured while never firing correctly. Confirm a normal numeric alert still saves.",
+                    href: "/store/analytics/alerts",
+                },
+                {
+                    key: "item-request-requires-title-and-description",
+                    label: "An item request cannot be submitted with an empty title or description",
+                    description: "Fixed 2026-08-24 — this route spread the raw body into Firestore, and its list GET is PUBLIC (unauthenticated), so an unvalidated write here was an unvalidated publish. Confirm a normal request still submits and appears in the open list.",
+                    href: "/item-requests",
+                },
+                {
+                    key: "report-submit-requires-detail",
+                    label: "Reporting a listing or store refuses an empty description and still files a normal report correctly",
+                    description: "Fixed 2026-08-24 — the submit route accepted any body, so a report naming nothing and describing nothing could reach the moderation queue, and a caller could set reviewer-owned fields (`assignedTo`, `resolution`, `resolvedAt`) on their own report.",
+                    href: "/admin/reports",
+                },
+                {
+                    key: "scammer-removed-badge-readable",
+                    label: "A scammer profile with status \"Removed\" shows a readable grey badge in BOTH the list and the detail drawer, in light and dark themes",
+                    description: "Fixed 2026-08-24 — two separate copies of the status-colour map both gave `removed` two backgrounds and two inks on the same element. Tailwind emits all four and stylesheet order decides the winner, so the painted colour was not what either map said. Both copies now come from one module. Check the badge reads \"Removed\" (not \"removed\") and is legible in both themes.",
+                    href: "/admin/scammers",
+                },
                 { key: "payment-methods-clusters-admin", label: "Admin can manage payment methods and payment-method clusters", href: "/admin/payment-methods" },
                 { key: "catalogue-approvals-admin", label: "Admin can approve/reject personal catalogue submissions", href: "/admin/catalogue-approvals" },
                 {

package/dist/features/wishlist/hooks/useWishlistWithGuest.d.ts

@@ -29,7 +29,7 @@ export declare function useWishlistWithGuest(userId: string | null | undefined,
         productPrice: number;
         productSlug: string;
         addedAt: string | undefined;
-        type: "classified" | "category" | "auction" | "digital-code" | "live" | "store" | "product" | "preorder";
+        type: "category" | "store" | "classified" | "auction" | "digital-code" | "live" | "product" | "preorder";
     }[];
     total: number;
     wishlistedIds: Set<string>;

package/dist/index.d.ts

@@ -493,7 +493,7 @@ export type { ResolvedUser } from "./security/index";
 export type { RoleDefinition } from "./security/index";
 export type { UserRole } from "./security/index";
 export { AddressesRepository } from "./repositories/index";
-export { type PayoutMethodType, type PayoutMethodDocument, PAYOUT_METHODS_COLLECTION, PAYOUT_METHOD_INDEXED_FIELDS, DEFAULT_PAYOUT_METHOD_DATA, type ShippingMethod as ShippingConfigMethod, type ShippingConfigDocument, SHIPPING_CONFIGS_COLLECTION, SHIPPING_CONFIG_INDEXED_FIELDS, DEFAULT_SHIPPING_CONFIG_DATA, type AnalyticsScope, type AnalyticsCardType, type AnalyticsCardDocument, ANALYTICS_CARDS_COLLECTION, ANALYTICS_CARD_INDEXED_FIELDS, DEFAULT_ANALYTICS_CARD_DATA, type AlertOperator, type AnalyticsAlertDocument, ANALYTICS_ALERTS_COLLECTION, ANALYTICS_ALERT_INDEXED_FIELDS, DEFAULT_ANALYTICS_ALERT_DATA, type StoreCategoryDocument, STORE_CATEGORIES_COLLECTION, STORE_CATEGORY_INDEXED_FIELDS, DEFAULT_STORE_CATEGORY_DATA, type ListingTemplateType, type ListingTemplateDocument, LISTING_TEMPLATES_COLLECTION, LISTING_TEMPLATE_INDEXED_FIELDS, DEFAULT_LISTING_TEMPLATE_DATA, type ModerationStatus, type ModerationMediaType, type ModerationQueueDocument, MODERATION_QUEUE_COLLECTION, MODERATION_QUEUE_INDEXED_FIELDS, DEFAULT_MODERATION_QUEUE_DATA, type ReportEntityType, type ReportStatus, type ReportReason, type ReportDocument, REPORTS_COLLECTION, REPORT_INDEXED_FIELDS, DEFAULT_REPORT_DATA, type AdminNotificationCategory, type AdminNotificationDocument, ADMIN_NOTIFICATIONS_COLLECTION, ADMIN_NOTIFICATION_INDEXED_FIELDS, DEFAULT_ADMIN_NOTIFICATION_DATA, type ItemRequestStatus, type ItemRequestReply, type ItemRequestDocument, ITEM_REQUESTS_COLLECTION, ITEM_REQUEST_INDEXED_FIELDS, DEFAULT_ITEM_REQUEST_DATA, type StoreGoogleConfigDocument, STORE_GOOGLE_CONFIG_COLLECTION, STORE_GOOGLE_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_GOOGLE_CONFIG_DATA, type StoreWhatsAppConfigDocument, STORE_WHATSAPP_CONFIG_COLLECTION, STORE_WHATSAPP_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_WHATSAPP_CONFIG_DATA, type CustomRoleDocument, CUSTOM_ROLES_COLLECTION, CUSTOM_ROLE_INDEXED_FIELDS, DEFAULT_CUSTOM_ROLE_DATA, type RoleOverrideDocument, ROLE_OVERRIDES_COLLECTION, ROLE_OVERRIDE_INDEXED_FIELDS, DEFAULT_ROLE_OVERRIDE_DATA, PayoutMethodsRepository, ShippingConfigsRepository, AnalyticsCardsRepository, AnalyticsAlertsRepository, StoreCategoriesRepository, ListingTemplatesRepository, ModerationQueueRepository, ReportsRepository, AdminNotificationsRepository, ItemRequestsRepository, StoreGoogleConfigRepository, StoreWhatsAppConfigRepository, CustomRolesRepository, RoleOverridesRepository, payoutMethodsRepository, shippingConfigsRepository, analyticsCardsRepository, analyticsAlertsRepository, storeCategoriesRepository, listingTemplatesRepository, moderationQueueRepository, reportsRepository, adminNotificationsRepository, itemRequestsRepository, storeGoogleConfigRepository, storeWhatsAppConfigRepository, customRolesRepository, roleOverridesRepository, } from "./features/store-extensions/index";
+export { type PayoutMethodType, type PayoutMethodDocument, PAYOUT_METHODS_COLLECTION, PAYOUT_METHOD_INDEXED_FIELDS, DEFAULT_PAYOUT_METHOD_DATA, type ShippingMethod as ShippingConfigMethod, type ShippingConfigDocument, SHIPPING_CONFIGS_COLLECTION, SHIPPING_CONFIG_INDEXED_FIELDS, DEFAULT_SHIPPING_CONFIG_DATA, type AnalyticsScope, type AnalyticsCardType, type AnalyticsCardDocument, ANALYTICS_CARDS_COLLECTION, ANALYTICS_CARD_INDEXED_FIELDS, DEFAULT_ANALYTICS_CARD_DATA, type AlertOperator, type AnalyticsAlertDocument, ANALYTICS_ALERTS_COLLECTION, ANALYTICS_ALERT_INDEXED_FIELDS, DEFAULT_ANALYTICS_ALERT_DATA, type StoreCategoryDocument, storeCategoryFormSchema, storeCategoryCreateSchema, type StoreCategoryFormValues, listingTemplateFormSchema, listingTemplateCreateSchema, listingTemplateUpdateSchema, type ListingTemplateFormValues, LISTING_TEMPLATE_TYPES, payoutMethodFormSchema, payoutMethodCreateSchema, payoutMethodUpdateSchema, type PayoutMethodFormValues, shippingConfigFormSchema, shippingConfigCreateSchema, shippingConfigUpdateSchema, type ShippingConfigFormValues, customRoleFormSchema, customRoleCreateSchema, customRoleUpdateSchema, isKnownPermission, type CustomRoleFormValues, moderationReviewFormSchema, moderationReviewUpdateSchema, MODERATION_REVIEWER_STATUSES, type ModerationReviewFormValues, reportReviewFormSchema, reportReviewUpdateSchema, REPORT_REVIEWER_STATUSES, REPORT_TERMINAL_STATUSES, type ReportReviewFormValues, reportCreateSchema, type ReportCreateValues, itemRequestCreateSchema, type ItemRequestCreateValues, REPORT_ENTITY_TYPES, REPORT_REASONS, analyticsAlertCreateSchema, type AnalyticsAlertCreateValues, analyticsCardCreateSchema, type AnalyticsCardCreateValues, ANALYTICS_ALERT_OPERATORS, ANALYTICS_CARD_TYPES, storeGoogleConfigUpdateSchema, type StoreGoogleConfigFormValues, toSellerGoogleConfig, type SellerGoogleConfig, adminNotificationCreateSchema, type AdminNotificationCreateValues, ADMIN_NOTIFICATION_CATEGORIES, ADMIN_NOTIFICATION_SEVERITIES, STORE_CATEGORIES_COLLECTION, STORE_CATEGORY_INDEXED_FIELDS, DEFAULT_STORE_CATEGORY_DATA, type ListingTemplateType, type ListingTemplateDocument, LISTING_TEMPLATES_COLLECTION, LISTING_TEMPLATE_INDEXED_FIELDS, DEFAULT_LISTING_TEMPLATE_DATA, type ModerationStatus, type ModerationMediaType, type ModerationQueueDocument, MODERATION_QUEUE_COLLECTION, MODERATION_QUEUE_INDEXED_FIELDS, DEFAULT_MODERATION_QUEUE_DATA, type ReportEntityType, type ReportStatus, type ReportReason, type ReportDocument, REPORTS_COLLECTION, REPORT_INDEXED_FIELDS, DEFAULT_REPORT_DATA, type AdminNotificationCategory, type AdminNotificationDocument, ADMIN_NOTIFICATIONS_COLLECTION, ADMIN_NOTIFICATION_INDEXED_FIELDS, DEFAULT_ADMIN_NOTIFICATION_DATA, type ItemRequestStatus, type ItemRequestReply, type ItemRequestDocument, ITEM_REQUESTS_COLLECTION, ITEM_REQUEST_INDEXED_FIELDS, DEFAULT_ITEM_REQUEST_DATA, type StoreGoogleConfigDocument, STORE_GOOGLE_CONFIG_COLLECTION, STORE_GOOGLE_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_GOOGLE_CONFIG_DATA, type StoreWhatsAppConfigDocument, STORE_WHATSAPP_CONFIG_COLLECTION, STORE_WHATSAPP_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_WHATSAPP_CONFIG_DATA, type CustomRoleDocument, CUSTOM_ROLES_COLLECTION, CUSTOM_ROLE_INDEXED_FIELDS, DEFAULT_CUSTOM_ROLE_DATA, type RoleOverrideDocument, ROLE_OVERRIDES_COLLECTION, ROLE_OVERRIDE_INDEXED_FIELDS, DEFAULT_ROLE_OVERRIDE_DATA, PayoutMethodsRepository, ShippingConfigsRepository, AnalyticsCardsRepository, AnalyticsAlertsRepository, StoreCategoriesRepository, ListingTemplatesRepository, ModerationQueueRepository, ReportsRepository, AdminNotificationsRepository, ItemRequestsRepository, StoreGoogleConfigRepository, StoreWhatsAppConfigRepository, CustomRolesRepository, RoleOverridesRepository, payoutMethodsRepository, shippingConfigsRepository, analyticsCardsRepository, analyticsAlertsRepository, storeCategoriesRepository, listingTemplatesRepository, moderationQueueRepository, reportsRepository, adminNotificationsRepository, itemRequestsRepository, storeGoogleConfigRepository, storeWhatsAppConfigRepository, customRolesRepository, roleOverridesRepository, } from "./features/store-extensions/index";
 export { BaseRepository } from "./repositories/index";
 export { BlogRepository } from "./repositories/index";
 export { CartRepository } from "./repositories/index";
@@ -2240,6 +2240,10 @@ export type { OrderSiblingPaymentsProps } from "./features/orders/index";
 export { OrderPaymentSummary } from "./features/orders/index";
 export type { OrderPaymentSummaryProps } from "./features/orders/index";
 export { OrderStatusTimeline } from "./features/orders/index";
+export { StatusTimeline, stepsFromEntries } from "./features/status-history/index";
+export type { StatusTimelineProps, TimelineEntry, TimelineStep } from "./features/status-history/index";
+export { OfferPhaseTimeline } from "./features/seller/components/OfferPhaseTimeline";
+export type { OfferPhaseTimelineProps, OfferChainRound } from "./features/seller/components/OfferPhaseTimeline";
 export type { OrderStatusTimelineProps } from "./features/orders/index";
 export type { OrderPaymentRecord, OrderPaymentRecordMethod, OrderPaymentVerificationMethod, } from "./features/orders/index";
 export { RefundHistoryTable } from "./features/orders/index";
@@ -3030,6 +3034,10 @@ export { getWishlistForUser } from "./features/wishlist/server";
 export { removeFromWishlist } from "./features/wishlist/server";
 export type { EnrichedWishlistItem } from "./features/wishlist/server";
 export { BANNER_HEIGHTS } from "./features/homepage/schemas/index";
+export { homepageSectionTypeSchema } from "./features/homepage/schemas/index";
+export { homepageSectionCreateSchema } from "./features/homepage/schemas/index";
+export { resolveNextSectionOrder } from "./features/homepage/actions/homepage-section-actions";
+export type { HomepageSectionCreateValues } from "./features/homepage/schemas/index";
 export { CAROUSEL_SLIDES_COLLECTION } from "./features/homepage/schemas/index";
 export { CAROUSEL_SLIDES_INDEXED_FIELDS } from "./features/homepage/schemas/index";
 export { CAROUSEL_SLIDES_PUBLIC_FIELDS } from "./features/homepage/schemas/index";
@@ -3153,6 +3161,8 @@ export { BUNDLE_COPY, BUNDLE_STOCK_VARIANT, } from "./_internal/shared/features/
 export { REFUND_COPY } from "./_internal/shared/features/orders/refund-copy";
 export { bundleCreateSchema, bundleUpdateSchema, bundleQueryRuleSchema, bundleDisplaySchema, type BundleCreateBody, type BundleUpdateBody, } from "./_internal/shared/features/categories/bundle-schemas";
 export type { GroupedListingDocument, GroupTheme, GroupVisibility } from "./features/grouped/schemas/firestore";
+export { navItemFormSchema, navItemCreateSchema, navItemUpdateSchema, type NavItemFormValues, } from "./features/admin/schemas/nav-item-form";
+export { groupedListingFormSchema, groupedListingCreateSchema, groupedListingUpdateSchema, type GroupedListingFormValues, } from "./features/grouped/schemas/grouped-listing-form";
 export { scammersSeedData } from "./seed/index";
 export { productFeaturesSeedData } from "./seed/index";
 export { SCAMMER_COLLECTION, SCAMMER_ID_PREFIX, SCAMMER_MATCH_FIELDS, SCAMMER_INDEXED_FIELDS, SCAMMER_FIELDS, SCAMMER_INCIDENTS_SUBCOLLECTION, SCAMMER_COMMENTS_SUBCOLLECTION, SCAMMER_CONTESTS_SUBCOLLECTION, MAX_COMMENT_BODY_LENGTH, MAX_PENDING_SCAMMER_REPORTS_PER_USER, ScammerStatusValues, ScamPlatformValues, SocialPlatformValues, ContestTypeValues, ContestStatusValues, SCAM_PLATFORM_LABELS, SOCIAL_PLATFORM_LABELS, SCAMMER_STATUS_LABELS, CONTEST_TYPE_LABELS, CONTEST_STATUS_LABELS, DEFAULT_SCAMMER_DATA, DEFAULT_SCAMMER_INCIDENT_DATA, DEFAULT_SCAMMER_COMMENT_DATA, DEFAULT_SCAMMER_CONTEST_DATA, } from "./features/scams/schemas/firestore";
@@ -3267,7 +3277,7 @@ export { SellerDigitalCodesView } from "./features/seller/components/SellerDigit
 export type { SellerDigitalCodesViewProps } from "./features/seller/components/SellerDigitalCodesView";
 export { SellerLiveView } from "./features/seller/components/SellerLiveView";
 export type { SellerLiveViewProps } from "./features/seller/components/SellerLiveView";
-export { SCHEMAS, lookupApiSchema, lookupFirestoreSchema, } from "./schemas/index";
+export { SCHEMAS, lookupApiSchema, lookupFormSchema, lookupFirestoreSchema, } from "./schemas/index";
 export type { ApiRouteKey, ApiRouteSchema, FirestoreDocument, FirestoreValue, FormFieldValue, FormValues, HttpVerb, JsonArray, JsonObject, JsonObjectWithUndefined, JsonPrimitive, JsonValue, JsonValueWithUndefined, RegisteredApiRouteKey, RegisteredFirestoreCollection, RegisteredFormId, RegisteredRtdbChannel, RegisteredSieveCollection, RegisteredStorageOp, RegisteredWebhookProvider, RegistryEntry, SchemaRegistry, SchemasShape, WebhookSchemaBucket, } from "./schemas/index";
 export { safeFireAndForget } from "./utils/safe-fire-forget";
 export { withRetry } from "./http/retry";

package/dist/index.js

@@ -910,7 +910,7 @@ export { resolvePermissions } from "./security/index";
 // AddressesRepository - unified top-level addresses collection (SB-UNI-A 2026-05-13).
 export { AddressesRepository } from "./repositories/index";
 // S-STORE foundation — 14 schemas + 14 repositories + RBAC.
-export { PAYOUT_METHODS_COLLECTION, PAYOUT_METHOD_INDEXED_FIELDS, DEFAULT_PAYOUT_METHOD_DATA, SHIPPING_CONFIGS_COLLECTION, SHIPPING_CONFIG_INDEXED_FIELDS, DEFAULT_SHIPPING_CONFIG_DATA, ANALYTICS_CARDS_COLLECTION, ANALYTICS_CARD_INDEXED_FIELDS, DEFAULT_ANALYTICS_CARD_DATA, ANALYTICS_ALERTS_COLLECTION, ANALYTICS_ALERT_INDEXED_FIELDS, DEFAULT_ANALYTICS_ALERT_DATA, STORE_CATEGORIES_COLLECTION, STORE_CATEGORY_INDEXED_FIELDS, DEFAULT_STORE_CATEGORY_DATA, LISTING_TEMPLATES_COLLECTION, LISTING_TEMPLATE_INDEXED_FIELDS, DEFAULT_LISTING_TEMPLATE_DATA, MODERATION_QUEUE_COLLECTION, MODERATION_QUEUE_INDEXED_FIELDS, DEFAULT_MODERATION_QUEUE_DATA, REPORTS_COLLECTION, REPORT_INDEXED_FIELDS, DEFAULT_REPORT_DATA, ADMIN_NOTIFICATIONS_COLLECTION, ADMIN_NOTIFICATION_INDEXED_FIELDS, DEFAULT_ADMIN_NOTIFICATION_DATA, ITEM_REQUESTS_COLLECTION, ITEM_REQUEST_INDEXED_FIELDS, DEFAULT_ITEM_REQUEST_DATA, STORE_GOOGLE_CONFIG_COLLECTION, STORE_GOOGLE_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_GOOGLE_CONFIG_DATA, STORE_WHATSAPP_CONFIG_COLLECTION, STORE_WHATSAPP_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_WHATSAPP_CONFIG_DATA, CUSTOM_ROLES_COLLECTION, CUSTOM_ROLE_INDEXED_FIELDS, DEFAULT_CUSTOM_ROLE_DATA, ROLE_OVERRIDES_COLLECTION, ROLE_OVERRIDE_INDEXED_FIELDS, DEFAULT_ROLE_OVERRIDE_DATA, 
+export { PAYOUT_METHODS_COLLECTION, PAYOUT_METHOD_INDEXED_FIELDS, DEFAULT_PAYOUT_METHOD_DATA, SHIPPING_CONFIGS_COLLECTION, SHIPPING_CONFIG_INDEXED_FIELDS, DEFAULT_SHIPPING_CONFIG_DATA, ANALYTICS_CARDS_COLLECTION, ANALYTICS_CARD_INDEXED_FIELDS, DEFAULT_ANALYTICS_CARD_DATA, ANALYTICS_ALERTS_COLLECTION, ANALYTICS_ALERT_INDEXED_FIELDS, DEFAULT_ANALYTICS_ALERT_DATA, storeCategoryFormSchema, storeCategoryCreateSchema, listingTemplateFormSchema, listingTemplateCreateSchema, listingTemplateUpdateSchema, LISTING_TEMPLATE_TYPES, payoutMethodFormSchema, payoutMethodCreateSchema, payoutMethodUpdateSchema, shippingConfigFormSchema, shippingConfigCreateSchema, shippingConfigUpdateSchema, customRoleFormSchema, customRoleCreateSchema, customRoleUpdateSchema, isKnownPermission, moderationReviewFormSchema, moderationReviewUpdateSchema, MODERATION_REVIEWER_STATUSES, reportReviewFormSchema, reportReviewUpdateSchema, REPORT_REVIEWER_STATUSES, REPORT_TERMINAL_STATUSES, reportCreateSchema, itemRequestCreateSchema, REPORT_ENTITY_TYPES, REPORT_REASONS, analyticsAlertCreateSchema, analyticsCardCreateSchema, ANALYTICS_ALERT_OPERATORS, ANALYTICS_CARD_TYPES, storeGoogleConfigUpdateSchema, toSellerGoogleConfig, adminNotificationCreateSchema, ADMIN_NOTIFICATION_CATEGORIES, ADMIN_NOTIFICATION_SEVERITIES, STORE_CATEGORIES_COLLECTION, STORE_CATEGORY_INDEXED_FIELDS, DEFAULT_STORE_CATEGORY_DATA, LISTING_TEMPLATES_COLLECTION, LISTING_TEMPLATE_INDEXED_FIELDS, DEFAULT_LISTING_TEMPLATE_DATA, MODERATION_QUEUE_COLLECTION, MODERATION_QUEUE_INDEXED_FIELDS, DEFAULT_MODERATION_QUEUE_DATA, REPORTS_COLLECTION, REPORT_INDEXED_FIELDS, DEFAULT_REPORT_DATA, ADMIN_NOTIFICATIONS_COLLECTION, ADMIN_NOTIFICATION_INDEXED_FIELDS, DEFAULT_ADMIN_NOTIFICATION_DATA, ITEM_REQUESTS_COLLECTION, ITEM_REQUEST_INDEXED_FIELDS, DEFAULT_ITEM_REQUEST_DATA, STORE_GOOGLE_CONFIG_COLLECTION, STORE_GOOGLE_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_GOOGLE_CONFIG_DATA, STORE_WHATSAPP_CONFIG_COLLECTION, STORE_WHATSAPP_CONFIG_INDEXED_FIELDS, DEFAULT_STORE_WHATSAPP_CONFIG_DATA, CUSTOM_ROLES_COLLECTION, CUSTOM_ROLE_INDEXED_FIELDS, DEFAULT_CUSTOM_ROLE_DATA, ROLE_OVERRIDES_COLLECTION, ROLE_OVERRIDE_INDEXED_FIELDS, DEFAULT_ROLE_OVERRIDE_DATA, 
 // Repositories — classes
 PayoutMethodsRepository, ShippingConfigsRepository, AnalyticsCardsRepository, AnalyticsAlertsRepository, StoreCategoriesRepository, ListingTemplatesRepository, ModerationQueueRepository, ReportsRepository, AdminNotificationsRepository, ItemRequestsRepository, StoreGoogleConfigRepository, StoreWhatsAppConfigRepository, CustomRolesRepository, RoleOverridesRepository, 
 // Repositories — singletons
@@ -4104,6 +4104,11 @@ export { OrdersList } from "./features/orders/index";
 export { OrderSiblingPayments } from "./features/orders/index";
 export { OrderPaymentSummary } from "./features/orders/index";
 export { OrderStatusTimeline } from "./features/orders/index";
+// [CLIENT] StatusTimeline — the ONE rail both orders and offers render.
+// Each feature supplies only its phase vocabulary; the never-fabricate-a-
+// timestamp rule and the dot/connector rail live in one place.
+export { StatusTimeline, stepsFromEntries } from "./features/status-history/index";
+export { OfferPhaseTimeline } from "./features/seller/components/OfferPhaseTimeline";
 export { RefundHistoryTable } from "./features/orders/index";
 export { RefundRequestView } from "./features/orders/index";
 // [CLIENT-SSR]-Runs in both SSR and browser â€" React component or hook that does not depend on browser-only APIs.
@@ -5411,6 +5416,9 @@ export { removeFromWishlist } from "./features/wishlist/server";
 // [SCHEMA]-Schema / data-shape constant â€" Zod validator, default-value object, or Firestore collection/field name constant.
 // BANNER_HEIGHTS - Constant used across modules.
 export { BANNER_HEIGHTS } from "./features/homepage/schemas/index";
+export { homepageSectionTypeSchema } from "./features/homepage/schemas/index";
+export { homepageSectionCreateSchema } from "./features/homepage/schemas/index";
+export { resolveNextSectionOrder } from "./features/homepage/actions/homepage-section-actions";
 // [SCHEMA]-Schema / data-shape constant â€" Zod validator, default-value object, or Firestore collection/field name constant.
 // CAROUSEL_SLIDES_COLLECTION - Constant used across modules.
 export { CAROUSEL_SLIDES_COLLECTION } from "./features/homepage/schemas/index";
@@ -5560,6 +5568,8 @@ export { BUNDLE_COPY, BUNDLE_STOCK_VARIANT, } from "./_internal/shared/features/
 export { REFUND_COPY } from "./_internal/shared/features/orders/refund-copy";
 // S-SBUNI-4 follow-up â€" shared admin bundle zod schemas.
 export { bundleCreateSchema, bundleUpdateSchema, bundleQueryRuleSchema, bundleDisplaySchema, } from "./_internal/shared/features/categories/bundle-schemas";
+export { navItemFormSchema, navItemCreateSchema, navItemUpdateSchema, } from "./features/admin/schemas/nav-item-form";
+export { groupedListingFormSchema, groupedListingCreateSchema, groupedListingUpdateSchema, } from "./features/grouped/schemas/grouped-listing-form";
 // Scam registry â€" seed data
 export { scammersSeedData } from "./seed/index";
 // Product features â€" seed data (FI2)
@@ -5669,7 +5679,7 @@ export { SellerLiveView } from "./features/seller/components/SellerLiveView";
 // boundary (Firestore docs, API routes, forms, sieve, webhooks, RTDB, storage).
 // Per-feature `schemas/index.ts` files register into the relevant bucket.
 // Pure Zod, isomorphic — safe on both client and server.
-export { SCHEMAS, lookupApiSchema, lookupFirestoreSchema, } from "./schemas/index";
+export { SCHEMAS, lookupApiSchema, lookupFormSchema, lookupFirestoreSchema, } from "./schemas/index";
 // ── Fire-and-forget safety wrapper ─────────────────────────────────────────
 // Replaces .catch(console.error) for non-critical background operations.
 export { safeFireAndForget } from "./utils/safe-fire-forget";

package/dist/next/routing/route-map.d.ts

@@ -130,8 +130,15 @@ export declare const DEFAULT_ROUTE_MAP: {
         readonly WISHLIST: "/wishlist";
         readonly HISTORY: "/user/history";
         readonly ADDRESSES: "/user/addresses";
-        readonly ADDRESSES_ADD: "/user/addresses/add";
+        /**
+         * Canonical shapes. `/add` and `/edit/[id]` were the only two
+         * non-standard route shapes in the codebase — every other entity uses
+         * `/new` and `/[id]/edit`. Both old paths still resolve, as redirects.
+         */
+        readonly ADDRESSES_NEW: "/user/addresses/new";
         readonly ADDRESSES_EDIT: (id: string) => string;
+        /** @deprecated Use ADDRESSES_NEW. Kept so existing links keep resolving. */
+        readonly ADDRESSES_ADD: "/user/addresses/new";
         readonly ORDER_DETAIL: (id: string) => string;
         readonly ORDER_CANCEL: (id: string) => string;
         readonly ORDER_TRACK: (id: string) => string;
@@ -505,8 +512,15 @@ export declare const ROUTES: {
         readonly WISHLIST: "/wishlist";
         readonly HISTORY: "/user/history";
         readonly ADDRESSES: "/user/addresses";
-        readonly ADDRESSES_ADD: "/user/addresses/add";
+        /**
+         * Canonical shapes. `/add` and `/edit/[id]` were the only two
+         * non-standard route shapes in the codebase — every other entity uses
+         * `/new` and `/[id]/edit`. Both old paths still resolve, as redirects.
+         */
+        readonly ADDRESSES_NEW: "/user/addresses/new";
         readonly ADDRESSES_EDIT: (id: string) => string;
+        /** @deprecated Use ADDRESSES_NEW. Kept so existing links keep resolving. */
+        readonly ADDRESSES_ADD: "/user/addresses/new";
         readonly ORDER_DETAIL: (id: string) => string;
         readonly ORDER_CANCEL: (id: string) => string;
         readonly ORDER_TRACK: (id: string) => string;

package/dist/next/routing/route-map.js

@@ -134,8 +134,15 @@ export const DEFAULT_ROUTE_MAP = {
         WISHLIST: "/wishlist",
         HISTORY: "/user/history",
         ADDRESSES: "/user/addresses",
-        ADDRESSES_ADD: "/user/addresses/add",
-        ADDRESSES_EDIT: (id) => `/user/addresses/edit/${id}`,
+        /**
+         * Canonical shapes. `/add` and `/edit/[id]` were the only two
+         * non-standard route shapes in the codebase — every other entity uses
+         * `/new` and `/[id]/edit`. Both old paths still resolve, as redirects.
+         */
+        ADDRESSES_NEW: "/user/addresses/new",
+        ADDRESSES_EDIT: (id) => `/user/addresses/${id}/edit`,
+        /** @deprecated Use ADDRESSES_NEW. Kept so existing links keep resolving. */
+        ADDRESSES_ADD: "/user/addresses/new",
         ORDER_DETAIL: (id) => `/user/orders/view/${id}`,
         ORDER_CANCEL: (id) => `/user/orders/${id}/cancel`,
         ORDER_TRACK: (id) => `/user/orders/${id}/track`,

package/dist/schemas/firestore-value.d.ts

@@ -0,0 +1,8 @@
+import { z } from "zod";
+import type { FirestoreValue } from "./types";
+/**
+ * Recursive, so `z.lazy` — the array and record arms reference the schema
+ * being defined. The explicit `z.ZodType<FirestoreValue>` annotation is
+ * required: TypeScript cannot infer the type of a self-referential const.
+ */
+export declare const firestoreValueSchema: z.ZodType<FirestoreValue>;