@mohasinac/appkit 4.53.0 → 4.53.1

package/dist/features/tester/seed-data/authored/tools__sticker-promote-to-listings.d.ts

@@ -0,0 +1,2 @@
+import type { AuthoredCase } from "./_types";
+export declare const authored: Record<string, AuthoredCase>;

package/dist/features/tester/seed-data/authored/tools__sticker-promote-to-listings.js

@@ -0,0 +1,58 @@
+/*
+ * WHY: Authored six-part procedures for promoting a traced sticker sheet into
+ *      real marketplace listings — distinct from the tracer's own "promote"
+ *      (run -> sheet). This is sheet -> marketplace.
+ * WHAT: 3 case(s), keyed by full checklist id.
+ *
+ * 🛑 These depend on the sticker-tracer's own happy path having already
+ * produced an accepted, full-resolution-rendered run on a sheet — they are
+ * not reachable standing alone. Run the tracer's own cases (checklist-tools-
+ * sticker-tracer-*) up through "Accept & render" first.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+const ADMIN_SIGNIN = "Sign in as admin@letitrip.in / TempPass123!.";
+export const authored = {
+    "checklist-tools-sticker-promote-to-listings-promote-creates-one-group": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Open a sheet whose active run has already been accepted and rendered to full resolution, with at least one part marked a duplicate of another.",
+            "Click \"Promote to listings\". Pick \"Beyblade Arena\" as the store, enter 499 for the sheet price and 99 for the flat part price, then confirm.",
+            "Open the newly created parent listing's product page and view its group/\"Pick what you want\" section.",
+        ],
+        expectedBehaviour: "The promoter creates one parent (the whole sheet) plus one child per UNIQUE part only — a part marked `duplicateOf` another must NOT get its own listing. All children are linked into ONE group via `linkChildrenToGroup`, a single batch call rather than N separate `linkChildToGroup` calls in a loop.",
+        expectedUiState: "The group picker on the parent's page shows every UNIQUE child — if the sheet had, say, 8 parts with 3 confirmed duplicates, the picker shows 5 members, not 1 and not 8. This is exactly the `linkChildToGroup` stale-append bug this phase fixed first: looping that call used to leave only the LAST child linked, so the picker showed just one member no matter how many parts existed.",
+        endResult: "BEFORE the fix, promoting an 8-part sheet silently produced a group whose parent claimed only 1 child, even though all 8 children individually had the correct `groupId` set. AFTER: the group's member list and the children's own `groupId`s agree.",
+    },
+    "checklist-tools-sticker-promote-to-listings-promoted-part-image-watermarked": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "After promoting a sheet, open one of the new CHILD listings' public product page and inspect its main image.",
+            "Separately, from the tracer's own sheet-review UI, download that same part's original full-resolution file (via the signed URL, not the public page).",
+        ],
+        expectedBehaviour: "The marketplace copy is served through `/media/{shortId}`, which the proxy watermarks on read because the `mediaAssets` row for it was written with `watermarkedAt` deliberately absent. The admin's own download goes through a signed GCS URL pointing at the SAME `assetPath` — the clean original — with zero bytes duplicated between the two.",
+        expectedUiState: "The public listing's image carries a visible watermark. The admin's direct download of the same part is clean — no watermark at all. Both are visibly the same artwork at the same crop.",
+        endResult: "BEFORE this phase, there was no public listing for a traced part at all. AFTER: the same pixels serve two audiences two different ways from one stored object — if the public copy is clean, or the admin's download is watermarked, the `watermarkedAt` wiring has inverted.",
+    },
+    "checklist-tools-sticker-promote-to-listings-promote-refuses-before-full-res-render": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Open a sheet that has been traced but whose run has NOT had \"Accept & render\" run on it (a fresh trace, or one accepted but not yet rendered to full resolution).",
+            "Attempt to promote it to listings.",
+        ],
+        expectedBehaviour: "`promoteStickerSheetToListings` checks every precondition UP FRONT — an active run, at least one unique part, and every unique part actually carrying an `assetPath` — and refuses the WHOLE action if any is missing, rather than creating a handful of listings and silently skipping the rest.",
+        expectedUiState: "The action is refused with a message naming the missing step (e.g. \"accept and render the run before promoting it to listings\"). NO parent or child listing is created — checking the store's product list afterward shows nothing new.",
+        endResult: "BEFORE this check existed, promoting too early would have been the exact 'wrong data, no error' failure this whole phase exists to avoid: some parts listed, others silently missing, with nothing anywhere saying so. AFTER: the refusal happens before any write, so a half-promoted sheet cannot exist.",
+    },
+};

package/dist/features/tester/seed-data/authored/tools__sticker-tracer.js

@@ -248,8 +248,8 @@ export const authored = {
             "Open the Tools entry in the main navigation and read its children.",
             "Visit /tools and read the cards.",
         ],
-        expectedBehaviour: "The guard is the layout's server-side session read, so a non-admin is redirected before any HTML is produced. The nav child is filtered out client-side, which is presentation only — the redirect is the real boundary.",
-        expectedUiState: "The tracer URL does not render; the browser lands elsewhere. The Tools dropdown does not list 'Sticker sheet tracer'. /tools itself renders normally with its other cards.",
+        expectedBehaviour: "A non-admin is refused. MEASURED on production 2026-10-19: the response is a 200 carrying an Unauthorized state, NOT a 307 — but no tracer UI is served, which is the property that matters. The nav child is filtered client-side, which is presentation only.",
+        expectedUiState: "An unauthorized / sign-in state, not the tracer. The phrase 'Choose a scan' appears nowhere on the page. The Tools dropdown does not list 'Sticker sheet tracer'. /tools itself renders normally with its other cards.",
         endResult: "BEFORE/AFTER is unchanged for a buyer — this case exists to prove the gate holds. Nothing is created or persisted.",
     },
     "checklist-tools-sticker-tracer-guest-redirected": {
@@ -260,9 +260,10 @@ export const authored = {
             "Navigate directly to /tools/sticker-tracer.",
             "Then visit /tools.",
             "View source on /tools/sticker-tracer's response and search for 'Choose a scan'.",
+            "In the same source, confirm a <meta name=\"robots\" content=\"noindex, nofollow\"> tag is present.",
         ],
-        expectedBehaviour: "A signed-out visitor is redirected to login. No part of the tracer UI is sent to the browser, because the layout redirects before rendering rather than hiding controls after.",
-        expectedUiState: "The login page, with a redirect back to the tracer. /tools renders normally and is unaffected. The phrase 'Choose a scan' appears nowhere in the response body.",
+        expectedBehaviour: "A signed-out visitor gets no tracer UI. 🛑 MEASURED on production: a 200 with a sign-in state and `<title>Sticker sheet tracer</title>`, NOT a redirect — so the plan's premise that 'a crawler gets a redirect and there is no indexable content at that URL' is FALSE. What actually keeps it out of the index is the `noindex, nofollow` meta plus the robots.txt Disallow, both verified live. That is exactly why all three protections were specified as non-redundant.",
+        expectedUiState: "A sign-in state rather than the tracer. `Choose a scan` appears NOWHERE in the response body — that absence is the real assertion. /tools renders normally and is unaffected.",
         endResult: "BEFORE/AFTER unchanged for a guest — this proves the gate is server-side rather than a hidden control. Nothing is persisted.",
     },
     "checklist-tools-sticker-tracer-storage-meter-honest": {

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

@@ -218,6 +218,49 @@ const rawTesterChecklistItems = [
         },
     ]),
     ...group("buying", "Buying", [
+        {
+            /*
+             * Part Two B/C/D/E — spares, made-to-order, promoted sticker parts and
+             * the group discount, all together on the one page a buyer actually
+             * uses. Each case is an explicit BEFORE -> AFTER: a spare page returning
+             * 200 with plausible cards is not evidence any of this works.
+             */
+            pageKey: "spares-and-groups",
+            pageLabel: "Spares browse, made-to-order, and group selections",
+            href: "/spares",
+            cases: [
+                {
+                    key: "spares-not-in-general-catalogue",
+                    label: "A spare does NOT appear on /products, but does appear on /spares",
+                    description: "BEFORE: there was no tenth listing type. AFTER: open /products and search for a known spare's title (e.g. \"Cross Dranzer\") — it must NOT appear, because `spares` sets `inGeneralCatalogue: false`. The same title DOES appear on /spares. If it appears on both, the exclusion broke; if it appears on neither, the nav/page wiring broke.",
+                },
+                {
+                    key: "spares-nav-entry-present",
+                    label: "The main nav's Products dropdown has a \"Spares\" child linking to /spares",
+                },
+                {
+                    key: "made-to-order-buyable-at-zero-stock",
+                    label: "A made-to-order listing at zero stock is buyable and says \"Made to order\", never \"Out of Stock\"",
+                    description: "Open the seeded \"Custom Beyblade Sticker Sheet — Print on Demand\" (stockQuantity 0, madeToOrder true). It must show \"Made to order — printed when you order\" rather than an Out of Stock badge, Add to Cart must work, and checkout must complete. This is the exact case C exists for: stock must gate nothing on this listing.",
+                    href: "/products/sticker-beyblade-custom-print-on-demand",
+                },
+                {
+                    key: "group-picker-shows-rules-before-choosing",
+                    label: "A group with selection rules states them BEFORE the buyer picks anything",
+                    description: "Open the seeded \"Burst & X Attackers You Might Like\" group (via one of its member products' Group section). The picker must show its rules (min 2, max 3, max 2 of any one, 10% off) as text near the top — not only as a refusal after submitting.",
+                },
+                {
+                    key: "group-picker-blocks-and-explains-invalid-selection",
+                    label: "Picking an invalid combination (e.g. only 1 item, or 3 of one item) shows the reason and disables Add",
+                    description: "On the same group, select only 1 item: the Add button must be disabled and a message naming the rule must appear (\"Pick at least 2…\"). Select 3 of one item: a different message naming the per-item cap must appear. Fixing the selection must re-enable Add without a page reload.",
+                },
+                {
+                    key: "group-discount-applied-and-shown",
+                    label: "The group discount is shown on the picker AND the cart line is actually discounted by that percentage",
+                    description: "Select a valid combination (e.g. 2 different items) on the 10%-off group and note the total shown in the picker. Add to cart, then open the cart and the checkout review: the line total must be 10% below the sum of the two items' individual prices, to the paisa, in all three places (picker, cart, checkout).",
+                },
+            ],
+        },
         {
             /*
              * The post-purchase money surface. `/user/orders/[id]/` has five
@@ -2212,6 +2255,39 @@ const rawTesterChecklistItems = [
         },
     ]),
     ...group("selling", "Selling", [
+        {
+            /*
+             * Part Two B/E — the seller side of spares, and the shared group-stock
+             * editor. "Stock is independent per listing" is the whole premise, so
+             * the editor-save-and-reload round trip is what actually proves that —
+             * a shared pool bug would show up exactly here, as one listing's stock
+             * silently changing another's.
+             */
+            pageKey: "spares-seller-and-group-editing",
+            pageLabel: "Seller spares dashboard and group stock/rules editing",
+            href: "/store/spares",
+            cases: [
+                {
+                    key: "seller-can-list-a-spare",
+                    label: "A seller can create, publish and see a spare on their own /store/spares list",
+                },
+                {
+                    key: "group-stock-edit-is-independent",
+                    label: "Editing one group member's stock does NOT change any other member's stock",
+                    description: "Open a group parent's editor, note two children's stock figures, change ONLY one of them in the shared stock editor, save, reload. The edited child shows the new figure; the other child is UNCHANGED. This is the premise the whole feature rests on — a shared pool would fail exactly this check.",
+                },
+                {
+                    key: "group-rules-save-and-reload",
+                    label: "Saved group rules (min/max/per-item cap/discount) survive a reload and reach the public picker",
+                    description: "In the group parent's editor, set min/max/per-item/discount to new values, save, reload the editor — the same values must still be there. Then open the group's public picker (as a buyer) and confirm the NEW rule text is what shows, not the old one.",
+                },
+                {
+                    key: "group-stock-partial-failure-reported",
+                    label: "Saving group stock for a member no longer in the group reports it, without losing the other saved rows",
+                    description: "Unlink a child from a group in one tab, then (without reloading) try to save that same child's stock from a second tab holding the stale member list. The response must name that row as rejected while the OTHER rows in the same save still succeed — not a blanket failure.",
+                },
+            ],
+        },
         {
             /*
              * The UPDATE path. The create path has 57 cases on /store/products/new
@@ -3160,28 +3236,123 @@ const rawTesterChecklistItems = [
              * romanisation and a licensed Indian importer's name.
              */
             pageKey: "authenticity-checker",
-            pageLabel: "Authenticity checker — box codes, per-generation checks and the sign-in gate",
+            pageLabel: "Authenticity checker — box codes, per-generation checks and the regional code tables",
             href: "/tools/authenticity",
             cases: [
-                { key: "guest-sees-reference-not-a-wall", label: "Signed out, the generation table and universal checks still render — only the lookup is gated" },
-                { key: "no-signin-flash-when-authenticated", label: "A signed-in user never sees 'Sign in to run a lookup' during a hard reload" },
+                /* ── Guards for the near-miss work (2026-10-19) ──────────────────
+                 * All three protect behaviour that is ALREADY CORRECT. They exist
+                 * because a "did you mean" feature is precisely the change that
+                 * could turn an absent code into an accusation, and this tool's
+                 * third rule is that a false counterfeit accusation against a real
+                 * seller is worse than a missed one.
+                 */
+                {
+                    key: "authenticity-unknown-code-is-not-fake",
+                    label: "An invented but well-formed box code returns NEUTRAL + inconclusive — never a counterfeit verdict",
+                    description: "Type a code that is well-formed (one letter, four digits) but not in any table — try Z9999. The verdict must be \"Inconclusive\", the signal must read neutral, and the text must say the code is NOT RECORDED rather than fake. Any wording that implies the item is counterfeit is the failure, and so is any verdict more severe than inconclusive. New genuine codes appear regularly, and counterfeiters use real codes anyway, so an absent code proves nothing in either direction.",
+                    href: "/tools/authenticity",
+                },
+                {
+                    key: "authenticity-near-miss-suggests",
+                    label: "A one-character-off code offers \"did you mean …?\" as a SUGGESTION, with no change to the verdict",
+                    description: "BEFORE: a transposed code said only \"not in either table\". AFTER: enter A0831 when A0813 is a known code — you get a neutral \"did you mean A0813?\" line. It must sit OUTSIDE the \"What I checked\" list, must not appear as a signal, must not fire any evasion or counterfeit warning, and the verdict must stay exactly what it was without the suggestion. A near-miss is ambiguous between a typo and a batch mimicking a real code; it is input correction, never evidence.",
+                    href: "/tools/authenticity",
+                },
+                {
+                    key: "authenticity-inconclusive-asks-for-more",
+                    label: "Code-only input prompts for the model name and offers the ask-the-seller next step",
+                    description: "Enter a code and a generation but NO model name. The inconclusive result must now say that supplying the name lets it cross-check name against code, and must offer asking the seller for a photo of the box bottom and the screws. BEFORE: you got the physical checklist and no indication that a second field would unlock a real check.",
+                    href: "/tools/authenticity",
+                },
+                {
+                    key: "authenticity-evasion-warning-survives",
+                    label: "Typing \"Pegasis\" still reaches the tool's own verdict with the evasion warning intact",
+                    description: "SECURITY-SHAPED, and it exists because of a specific hazard. The site search matcher deliberately treats \"Pegasis\" as a match for \"Storm Pegasus\" — its alias table is built FROM a counterfeit seller's spellings. This tool treats that same spelling as EVIDENCE of trademark evasion. Type Pegasis here: the fuzzy/evasion signal must still fire. If a name typeahead is offered and you pick a canonical name from it, the tool must STILL analyse what you typed — a case asserting only \"the typeahead found it\" would pass against exactly the bug this guards.",
+                    href: "/tools/authenticity",
+                },
+                {
+                    key: "authenticity-name-typeahead",
+                    label: "Typing a partial model name offers canonical releases, and picking one does NOT change what gets checked",
+                    description: "BEFORE: you had to already know the exact release name. AFTER: type a partial name (e.g. \"Drago\") and canonical releases appear beneath the field as suggestions. Click one — a confirmation line appears (\"We have a record close to this: …\"), but the TEXT YOU TYPED in the field must stay exactly as you typed it. Submit the check and confirm the result is consistent with what you typed, not with the suggestion you clicked.",
+                    href: "/tools/authenticity",
+                },
+                {
+                    key: "authenticity-box-code-still-instant",
+                    label: "A box date code (e.g. A0813) resolves instantly with no network request — it is NOT in the search index",
+                    description: "GUARD CASE. Open DevTools -> Network, clear it, and submit a known box date code. No fetch to the search artifact or any search endpoint should appear — the date-code table is bundled locally and always was. This case exists because the site-wide index work added a name typeahead to this same page, and the two must stay on separate code paths.",
+                    href: "/tools/authenticity",
+                },
+                { key: "guest-sees-reference-not-a-wall", label: "Signed out, the LOOKUP ITSELF runs — no sign-in card anywhere on the page" },
+                { key: "no-signin-flash-when-authenticated", label: "No session placeholder and no sign-in card during a hard reload, signed in or out" },
                 { key: "midfake-code-reads-as-batch-not-accusation", label: "A matched midfake code reports a batch, never a counterfeit accusation against the seller" },
                 { key: "date-code-shows-both-readings", label: "A box date code shows BOTH circulating readings and says neither is official" },
                 { key: "real-product-code-is-not-evidence", label: "A well-formed product code is marked neutral and states that real codes appear on fakes" },
-                { key: "name-code-mismatch-asks-rather-than-accuses", label: "A name/code mismatch is a question, and ticking Random Booster re-reads it as expected" },
+                { key: "name-code-mismatch-asks-rather-than-accuses", label: "A name/code mismatch is a question, and answering 'How it was sold' re-reads it as expected" },
                 { key: "ambiguous-name-asks-which-model", label: "An ambiguous name asks which release instead of confidently naming one" },
                 { key: "takara-spelling-is-not-flagged", label: "'Storm Pegasis' (the Takara Tomy spelling) is not flagged, while 'Scythee' is" },
                 { key: "funskool-is-not-a-fake-signal", label: "Funskool reads as a licensed importer; Rapidity reads as an unlicensed producer" },
                 { key: "unknown-code-is-not-called-fake", label: "An unrecorded code says 'not recorded' and explicitly not 'fake'" },
                 { key: "asks-generation-when-nothing-inferable", label: "With no generation inferable the tool asks instead of returning a verdict" },
-                { key: "api-refuses-signed-out", label: "POST /api/tools/authenticity returns 401/403 signed out and leaks no assessment" },
-                { key: "json-ld-declares-the-gate", label: "The WebApplication JSON-LD declares the gated region, and its cssSelector matches a real element" },
+                { key: "api-refuses-signed-out", label: "POST /api/tools/authenticity answers a signed-out caller, and still 400s an undeclared key" },
+                { key: "json-ld-declares-no-false-gate", label: "The WebApplication JSON-LD declares NO paywalled region, now that there is none" },
+                { key: "defaults-to-metal-fight", label: "Generation opens on Metal Fight, and a Burst code against it raises a mismatch signal rather than passing silently" },
+                { key: "contested-code-reports-the-disagreement", label: "A code two sources disagree about reports the disagreement instead of picking a side" },
+                { key: "font-midfake-does-not-accuse", label: "A midfake row whose own source calls the code authentic does NOT reach 'likely reproduction'" },
+                { key: "regional-code-reads-as-regional", label: "A Korean or Middle-East code names its region instead of coming back unrecorded" },
+                { key: "series-window-names-the-production-run", label: "A derivable date names its Metal-series production window, or names none outside all four" },
+                { key: "temporal-context-for-an-unmatched-code", label: "An unmatched code reports what else the tables record from the same month, framed as context not a match" },
+            ],
+        },
+        {
+            pageKey: "price-index-tool",
+            pageLabel: "What it sold for — realised prices",
+            href: "/tools/price-index",
+            cases: [
+                {
+                    key: "price-index-resolves-locally",
+                    label: "Candidate names appear with no network delay while typing; only the bands themselves come from the server",
+                    description: "BEFORE: resolving a free-text query to a category leaf was a Firestore searchTxt query on every lookup. AFTER: open /tools/price-index, open DevTools -> Network, clear the log, and search a real model name. The suggestion/candidate step must feel instant and correspond to the local search artifact (a .json fetched once, not per search); only ONE further request — to the bands endpoint — should fire, carrying just the resolved id(s), and it must return real min/median/mean/max figures for a model with recorded sales.",
+                    href: "/tools/price-index",
+                },
+                {
+                    key: "price-index-falls-back-when-index-off",
+                    label: "Price lookup still works end-to-end if the search index is unavailable",
+                    description: "GUARD CASE for the fallback path. If the admin search-index kill switch is off (or the artifact fails to load), the price lookup must still return real results via the original query-based endpoint — the feature must not go blank just because the faster path is unavailable.",
+                    href: "/tools/price-index",
+                    needsReview: true,
+                    reviewNote: "Needs the kill switch flipped off to observe, which an ordinary run does not do — flagged for a human or admin-tooling pass.",
+                },
+            ],
+        },
+        {
+            pageKey: "compare-overlay-add-item",
+            pageLabel: "Compare overlay — add another item",
+            href: "/products",
+            cases: [
+                {
+                    key: "compare-add-another-via-typeahead",
+                    label: "The compare overlay's \"Add another\" typeahead adds a real item without leaving the page",
+                    description: "BEFORE: the compare overlay only ever showed items selected via listing-page checkboxes before opening it — there was no way to add a further item once the overlay was open. AFTER: open the compare overlay with at least one item selected, find the 'Add another to compare' box, type a product name, and pick a suggestion. The picked item's full column (image, price, specs) appears in the overlay without closing it or returning to the listing grid.",
+                    href: "/products",
+                },
+                {
+                    key: "compare-add-hidden-at-column-limit",
+                    label: "The \"Add another\" box disappears once the compare overlay is full",
+                    description: "Add items via checkboxes (or the typeahead) until the overlay holds its maximum number of columns. The 'Add another' box must then be absent entirely — not merely disabled — since a picker that cannot add anything is worse than none.",
+                    href: "/products",
+                },
             ],
         },
         {
             /*
-             * D12 — the parts database, the composition panel, and the part line in a
-             * seller's auto-filled description.
+             * D12 — the Beyblade parts gallery, the composition panel, and the part
+             * line in a seller's auto-filled description.
+             *
+             * 🛑 `pageKey` stays `parts-database` even though the surface is now
+             * called the Beyblade parts gallery. It keys all nine case ids, every
+             * `testerChecklistResponses` row already recorded against them, and
+             * `audit-tester-checklist-hrefs`. A label is a label; a key is an
+             * identifier.
              *
              * 🛑 Four defects this feature has already produced, every one of them a
              * 200 with plausible content: a read against a field the collection does
@@ -3192,7 +3363,7 @@ const rawTesterChecklistItems = [
              * ABSENT panel — indistinguishable from a model we have no data for.
              */
             pageKey: "parts-database",
-            pageLabel: "Parts database, composition panel and the part line in a description",
+            pageLabel: "Beyblade parts gallery, composition panel and the part line in a description",
             href: "/parts",
             cases: [
                 { key: "index-lists-every-classification", label: "The parts index lists all 20 classifications, labelled as names and not as URL slugs" },
@@ -3217,30 +3388,33 @@ const rawTesterChecklistItems = [
              *
              *   1. The index rendered all 1,185 rows flat. Nothing errored; it just
              *      buried the six roots under 752 part leaves.
-             *   2. The Parts tab first matched 772 rows — it also caught the 20
-             *      classification NODES, whose own parentIds pass through a
-             *      `*-parts` node. A tab mixing "Attack Rings" with the attack rings
-             *      inside it looks entirely reasonable.
-             *   3. Seven franchises have NO stock. Seeded active they would each be
+             *   2. Seven franchises have NO stock. Seeded active they would each be
              *      a card opening an empty shop; omitted entirely, seventeen
              *      CharacterHotspot links stay 404. Both failure modes look fine
              *      from one page.
-             *   4. Every bundle carries a placeholder cover image, so a collage
+             *   3. Every bundle carries a placeholder cover image, so a collage
              *      checked AFTER the cover would never render — and a card showing
              *      one grey tile is not visibly broken.
+             *
+             * 🛑 There was a fifth tab, Parts, removed 2026-10-20 — parts belong to
+             * `/parts` and the spares listing type, not to a flat tab over 752
+             * leaves. Its own case went with it. The product-detail Parts
+             * COMPOSITION tab is a different surface and still has cases, on the
+             * `parts-database` page above.
              */
             pageKey: "category-tabs-franchise-bundles",
             pageLabel: "Categories index tabs, the franchise unit and the bundle collage",
             href: "/categories",
             cases: [
                 { key: "index-shows-roots-only", label: "The Categories tab lists the six roots and NO deeper category" },
-                { key: "five-tabs-no-all", label: "There are exactly five tabs and none of them is 'All'" },
-                { key: "parts-tab-is-leaves-only", label: "The Parts tab lists part leaves and NOT the 20 classification nodes" },
+                { key: "four-tabs-no-all-no-parts", label: "There are exactly four tabs — no 'All', and no 'Parts'" },
                 { key: "tabs-do-not-overlap", label: "No single row appears on two tabs" },
                 { key: "franchise-index-hides-unstocked", label: "The franchise index shows only stocked franchises, not all eight" },
                 { key: "unstocked-franchise-page-resolves", label: "An unstocked franchise page loads and says so, rather than 404ing or showing an empty grid" },
                 { key: "franchise-detail-lists-its-products", label: "The Beyblade franchise page lists its listings, with a nonsense slug as the control" },
                 { key: "bundle-card-shows-a-collage", label: "A bundle card shows a collage of its members, not its placeholder cover" },
+                { key: "tabs-collapse-on-narrow-viewport", label: "On a phone-width viewport the four tabs collapse into a searchable dropdown, not a row running off-screen" },
+                { key: "tabs-hover-changes-ink", label: "On desktop, hovering an inactive tab visibly changes its text colour" },
             ],
         },
         {
@@ -3450,7 +3624,7 @@ const rawTesterChecklistItems = [
                 {
                     key: "search-typeahead-differs",
                     label: "Typing \"dranzer\" and then \"dragoon\" in the header search gives DIFFERENT suggestions",
-                    description: "WAS: the same 5 newest rows appeared for every keystroke, because no search term reached the query at all. If both terms give an identical list, the term is still being ignored.",
+                    description: "WAS: the same 5 newest rows appeared for every keystroke, because no search term reached the query at all. If both terms give an identical list, the term is still being ignored. UPDATED 2026-10-19: suggestions now come from the local index and span all 21 content types rather than the four the old endpoint could produce — so expect categories, parts and FAQs among the rows, not only products. ALSO CHECK, in DevTools -> Network: after the first index download there must be NO request per keystroke.",
                 },
                 {
                     key: "search-typeahead-no-drafts",
@@ -3565,6 +3739,138 @@ const rawTesterChecklistItems = [
                     description: "Write this one carefully. Every other case here passes on freshly seeded data while real production documents stay invisible, because search tokens are only written when a record is saved. Pick a listing that has NOT been edited recently and confirm it is findable; if it is not, the backfill did not cover it.",
                     href: "/products",
                 },
+                /* ── The site-wide index (2026-10-19) ─────────────────────────────
+                 * Every case below is written as an explicit BEFORE -> AFTER,
+                 * because almost all of them describe behaviour that previously
+                 * returned HTTP 200 with plausible rows. A case reading "check
+                 * search works" passes AGAINST the bug it is meant to catch.
+                 */
+                {
+                    key: "search-finds-every-type",
+                    label: "Searching \"dranzer\" from the header lands on /search and returns hits in SEVERAL sections",
+                    description: "BEFORE: the header sent you to /products?q=dranzer — one browse page — so you never learned there is also a category, a part, a blog post and an FAQ about it. AFTER: you land on /search and see grouped results across several sections. CONTROL, and it is the only assertion here that cannot pass by accident: search \"zzzznope\" and the page must say nothing matched, with ZERO result rows.",
+                    href: "/search",
+                },
+                {
+                    key: "search-finds-a-part",
+                    label: "Searching \"Rubber Flat\" and then \"RF\" both find the part",
+                    description: "BEFORE: zero results for either — all 752 parts had no search tokens at all, so they were reachable only by drilling /parts -> classification -> code. AFTER: both queries return the part, and the row shows its classification underneath the name.",
+                    href: "/search",
+                },
+                {
+                    key: "search-ambiguous-part-code",
+                    label: "Searching \"105\" returns SEVERAL parts, each showing a DIFFERENT classification",
+                    description: "BEFORE: there was no way to search parts at all. AFTER: \"105\" is deliberately ambiguous — it is a Metal Fight spin-track height, while a bare number in Burst is a disc — so the right answer is several rows, each naming its own classification and each linking to a different two-segment /parts/<classification>/<code> page. ONE row is the failure: it means something picked a winner.",
+                    href: "/search",
+                },
+                {
+                    key: "search-midword",
+                    label: "Searching \"ariza\" finds Charizard",
+                    description: "BEFORE: impossible. Firestore token search is word-PREFIX only, so a mid-word fragment matched nothing. AFTER: it matches, because the browser scans the whole index. CONTROL: \"zzzz\" must still return nothing — a matcher that returns everything for any fragment would also pass the first half.",
+                    href: "/search",
+                },
+                {
+                    key: "search-typo",
+                    label: "Searching \"dragon g\" finds Dragoon G, and \"Pegasis\" finds Storm Pegasus",
+                    description: "Misspellings are expanded at index time from a crawl of a counterfeit seller's real titles, on the basis that an evasion spelling is the same string a buyer mistypes. BEFORE: neither matched. AFTER: both do.",
+                    href: "/search",
+                },
+                {
+                    key: "search-normalised-away",
+                    label: "Searching \"!!!\" shows the \"no searchable words\" state — NOT every listing",
+                    description: "BEFORE (the inverse bug, on /api/products): a punctuation-only query produced no filter clause, so it returned the ENTIRE published catalogue as search results. AFTER: the page says the query had no searchable words in it. Note this is a different message from \"nothing matched\" and both must be distinguishable.",
+                    href: "/search",
+                },
+                {
+                    key: "search-zero-reads",
+                    label: "After the first search, typing produces NO further network requests",
+                    description: "Open DevTools -> Network, signed out. Type a query: you should see ONE fetch of the index artifact (a .json from firebasestorage, a few hundred KB) and nothing per keystroke thereafter. BEFORE: every keystroke hit /api/search/suggestions. A request per character is the failure even though the results look identical.",
+                    href: "/search",
+                },
+                {
+                    key: "search-no-prices",
+                    label: "No rupee amount appears anywhere in the header suggestions or /search results, signed out",
+                    description: "BEFORE: the header dropdown printed the product price as the suggestion subtitle, from a route cached PUBLIC for 60s — a live guest-price leak on every page. AFTER: suggestions show the brand and category instead, and no ₹ appears anywhere for a signed-out visitor.",
+                    href: "/search",
+                },
+                {
+                    key: "search-no-sandbox",
+                    label: "No tester-sandbox row appears in search results for a signed-out visitor",
+                    description: "The index is ONE shared file every browser downloads, with no per-viewer filter anywhere after it is built — so a sandbox row in it is published to the world for that version's lifetime. Search \"sandbox\" and \"tester\" signed out; nothing seeded as test data may appear.",
+                    href: "/search",
+                },
+                {
+                    key: "search-freshness",
+                    label: "A newly published listing becomes findable within ~15 minutes, and unpublishing removes it",
+                    description: "Publish a listing, note the time, and search its exact title. It should appear within about 15 minutes. Then unpublish it and search again — it must disappear within the same window. BEFORE: there was no index to go stale. A row that never appears, or never leaves, both mean the rebuild stopped.",
+                    href: "/search",
+                },
+                {
+                    key: "search-facet-counts",
+                    label: "Facet chips on /search show counts that match the rows actually displayed, and ticking one narrows BOTH",
+                    description: "Search a broad term. The rail shows chips like Type/Brand/Condition with a number on each. Tick one: the results narrow AND the other chips' numbers drop to match. A chip whose count does not change the result set, or a count that disagrees with the rows you can see, is the failure.",
+                    href: "/search",
+                },
+                {
+                    key: "search-guest-no-private",
+                    label: "Signed out, /search shows no account sections and makes ZERO authenticated requests",
+                    description: "SECURITY. In a private window with no session, search a broad term and watch DevTools -> Network. There must be no request to /api/search/scoped at all — not a 401, not an empty 200. An authenticated request firing for a guest means a session the page did not expect.",
+                    href: "/search",
+                },
+                {
+                    key: "search-buyer-isolation",
+                    label: "Buyer A cannot find Buyer B's order — by the UI AND by calling the API directly",
+                    description: "SECURITY, and the API half is the half that matters. Signed in as one buyer, search a term from another buyer's order. Then call /api/search/scoped?q=<term> directly in the same session and read the JSON. Neither may contain the other buyer's row. A UI that hides it while the API returns it is the failure this case exists for.",
+                    href: "/search",
+                },
+                {
+                    key: "search-seller-own-store",
+                    label: "A seller finds their own DRAFT listing; another seller's draft is absent",
+                    description: "Signed in as a seller, search a draft listing's title. It appears under \"Your listings (incl. drafts)\" — that section exists precisely because published listings are deduped away into the public results, so what is left is your drafts. Then confirm a different store's draft title returns nothing.",
+                    href: "/search",
+                },
+                {
+                    key: "search-listing-boxes-still-filter",
+                    label: "The per-collection search boxes still filter — one public, one seller, one admin",
+                    description: "REGRESSION GUARD. The box on /stores, the one on /store/orders and the one on /admin/users are a DIFFERENT system from site-wide search and must be untouched. For each: a real term narrows the list, a nonsense term returns zero, pagination still works, and the filter-drawer badge still counts correctly.",
+                    href: "/stores",
+                },
+                {
+                    key: "search-support-ticket-two-words",
+                    label: "A TWO-WORD support-ticket search narrows to tickets matching BOTH words",
+                    description: "BEFORE: the second word was discarded entirely, so the search returned everything matching the longer word and looked like it was working. AFTER: search two words you know appear in one ticket's subject but not together in others — only the matching ticket should remain.",
+                    href: "/admin/support-tickets",
+                },
+                {
+                    key: "search-parts-page-has-a-box",
+                    label: "/parts has a search box that finds a part by name or by code",
+                    description: "BEFORE: /parts was browse-only — 752 parts reachable only by clicking a classification then a code. AFTER: there is a search input above the classification grid. Type \"RF\" and the part appears with its classification; type \"zzzznope\" and it says nothing matches. The classification grid must still be there below it.",
+                    href: "/parts",
+                },
+                {
+                    key: "search-facet-carries-through",
+                    label: "\"See all →\" on a group with a facet ticked lands on the browse page WITH that facet still applied",
+                    description: "Search a broad term and tick a facet chip (e.g. a brand). Click the group's own \"See all →\" link. BEFORE: the link always went to the plain, unfiltered browse page, so refining on /search and then following through threw the refinement away. AFTER: the destination URL carries the same filter (e.g. ?f=brand==Takara-Tomy) and the browse page opens already narrowed.",
+                    href: "/search",
+                },
+                {
+                    key: "search-admin-person-exact",
+                    label: "Admin can find a user by typing just their FIRST name — but a prefix of it finds nothing",
+                    description: "Signed in as admin, open /admin/users and type a real user's first name only (not their full \"First Last\"). BEFORE: the search was an exact match on the WHOLE displayName string, so typing only the first name found nobody. AFTER: it is a whole-WORD match and finds them. Then type only the first 3-4 letters of that name (a prefix, not the whole word) — this must find NOTHING. That second half is the design, not a bug: the index is whole-word only so it cannot be unpicked by counting partial-match frequencies.",
+                    href: "/admin/users",
+                },
+                {
+                    key: "search-no-plaintext-pii",
+                    label: "The stored search-index values are HMAC digests, never a readable name",
+                    description: "For an admin or engineer with Firestore console access: open a `users` document and find `nameTokensIndex`. Every entry must be an opaque hex digest (prefixed `hmac:`), never the person's actual name or email in any form. Also confirm no such field exists on, or is reachable from, the public search artifact (the .json file fetched by a signed-out visitor) — a deterministic per-person identifier published to every browser is a disclosure even though it cannot be reversed.",
+                    href: "/admin/users",
+                },
+                {
+                    key: "faq-punctuation-search",
+                    label: "Searching \"!!!\" in the FAQ box shows the normalised-away state, not every FAQ",
+                    description: "GUARD CASE — this behaviour is already correct and this case exists to pin it so it cannot regress while the site-wide index work is in motion elsewhere. Open /faqs and search \"!!!\". It must say the search had no searchable words, and show zero FAQs — not the entire FAQ list.",
+                    href: "/faqs",
+                },
             ],
         },
         {
@@ -6756,6 +7062,24 @@ const rawTesterChecklistItems = [
             pageLabel: "Header search",
             href: "/",
             cases: [
+                {
+                    key: "header-search-submit-lands-on-search",
+                    label: "Submitting the header search lands on /search with GROUPED results — not on one browse page",
+                    description: "BEFORE: submitting sent you to the browse route for whichever type was selected in the dropdown — /products?q=dranzer — so a cross-resource search was unreachable and the /search page it should have used had no users at all. AFTER: you land on /search?q=dranzer and see results grouped by type, each group with its own \"See all … →\" link pointing at that browse page. The per-type destinations are not lost; they moved to where they belong.",
+                    href: "/",
+                },
+                {
+                    key: "header-search-type-is-a-filter",
+                    label: "The type dropdown NARROWS the results — it no longer decides where you land",
+                    description: "BEFORE: choosing \"Stores\" meant submitting took you to /stores. AFTER: choosing \"Stores\" narrows what you see, and the Stores group's own \"See all stores →\" link is what takes you to /stores. Also confirm an EMPTY query does nothing at all on submit — landing on a bare browse page you did not ask for is worse than staying put.",
+                    href: "/",
+                },
+                {
+                    key: "header-search-no-price-for-guest",
+                    label: "Signed out, no suggestion row shows a price",
+                    description: "BEFORE: the suggestion subtitle was the product's price, served from a route cached PUBLIC for 60 seconds — so every signed-out visitor saw prices in the header on every page. AFTER: the subtitle is the brand and category. Any ₹ in the dropdown while signed out is a FAIL.",
+                    href: "/",
+                },
                 {
                     key: "search-finds-maintenance-toggle",
                     label: "Searching 'maintenance' reaches the maintenance TOGGLE, not just Site Settings",
@@ -6880,6 +7204,36 @@ const rawTesterChecklistItems = [
                 { key: "storage-meter-honest", label: "The storage meter reports object COUNT beside bytes, and says when it truncated" },
             ],
         },
+        {
+            /*
+             * Part Two D — promoting a traced, accepted, promoted-to-full-res
+             * sheet into real marketplace listings. Distinct from the tracer's
+             * own "promote" (run -> sheet, full-res pixels); this is sheet ->
+             * marketplace (real products). Needs a real traced sheet to reach, so
+             * these cases follow the tracer's own happy path rather than
+             * standing alone.
+             */
+            pageKey: "sticker-promote-to-listings",
+            pageLabel: "Promoting a sheet to real listings",
+            href: "/tools/sticker-tracer",
+            cases: [
+                {
+                    key: "promote-creates-one-group",
+                    label: "Promoting a sheet creates one parent listing plus one child per UNIQUE part, all in one group",
+                    description: "On a sheet with at least one part marked a duplicate of another, promote it to listings. The group must contain the parent plus exactly the UNIQUE parts — a duplicate part must NOT get its own listing — and the picker on the parent's product page must show every member, not just one (this is exactly the `linkChildToGroup` stale-append bug: linking N children in a loop used to leave only one).",
+                },
+                {
+                    key: "promoted-part-image-watermarked",
+                    label: "A promoted part's marketplace image is watermarked; the admin's original download is NOT",
+                    description: "Open the promoted CHILD listing's public page and note its image carries a visible watermark. Then, from the tracer's own UI, download that same part's original — it must be clean, with no watermark. Same pixels, same object, two different responses: that is the point.",
+                },
+                {
+                    key: "promote-refuses-before-full-res-render",
+                    label: "Promoting a sheet that has not been accepted-and-rendered is refused, naming the fix",
+                    description: "Attempt to promote a sheet whose active run has not had \"Accept & render\" run on it (or try on a fresh trace with no promoted run). The action must refuse with a message naming the required step (accept/render the run first) — not create partial listings.",
+                },
+            ],
+        },
     ], { adminOnly: true }),
 ];
 const defaultPhases = assignDefaultPhases(rawTesterChecklistItems);