@mohasinac/appkit 4.52.1 → 4.52.3

package/dist/features/tester/seed-data/authored/content-discovery__category-brand-relations.js

@@ -44,14 +44,14 @@ export const authored = {
         startPage: "/categories",
         steps: [
             "Open /categories and read every top-level category shown.",
-            "Check both Spinning Tops and Living Collectibles are present.",
+            "Check all six roots are present: Spinning Tops, Trading Cards, Collectible Figures, Hot Wheels, Model Kits, Living Collectibles.",
             "Click Living Collectibles and read its children.",
             "Click down to a leaf under it.",
             "Check the leaf lists at least one live-item listing.",
         ],
         inputs: { rootA: "category-spinning-tops", rootB: "category-living-collectibles" },
-        expectedBehaviour: "Both roots are on the index. The tree had one root and two tiers before it was rebuilt, so the live-item listings carried no category at all and were unreachable from every category and brand page — a whole listing type invisible to browsing while its detail pages worked fine.",
-        expectedUiState: "Two roots on the index, and the Living Collectibles branch walks down to a leaf holding a live listing. One root, or a second root that leads nowhere, is the finding.",
+        expectedBehaviour: "All SIX roots are on the index. The tree had one root and two tiers before it was rebuilt, so the live-item listings carried no category at all and were unreachable from every category and brand page — a whole listing type invisible to browsing while its detail pages worked fine. Living Collectibles is the one to walk, because it is the root whose leaves hold the live-item listings.",
+        expectedUiState: "Six roots on the index, and the Living Collectibles branch walks down to a leaf holding a live listing. A missing root, or a root that leads nowhere, is the finding.",
         endResult: "Read-only.",
     },
     "checklist-content-discovery-category-brand-relations-root-page-shows-descendant-products": {

package/dist/features/tester/seed-data/authored/content-discovery__category-tabs-franchise-bundles.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/content-discovery__category-tabs-franchise-bundles.js

@@ -0,0 +1,152 @@
+/*
+ * WHY: Authored six-part procedures for the categories-index tabs, the
+ *      franchise unit and the bundle collage (2026-10-14).
+ * WHAT: 8 cases, keyed by full checklist id.
+ *
+ * 🛑 EVERY CASE IS BEFORE → AFTER, because every defect this work produced
+ * rendered a page that looked fine:
+ *
+ *   1. The index rendered all 1,185 rows flat — six roots buried under 752
+ *      part leaves. A case reading "the categories page loads" passes against
+ *      that.
+ *   2. The Parts tab first returned 772, catching the 20 classification NODES
+ *      as well as the leaves, because their own `parentIds` also pass through
+ *      a `*-parts` node. A list mixing "Attack Rings" with attack rings is not
+ *      visibly wrong.
+ *   3. Seven franchises have no stock. Active, each is a card opening an empty
+ *      shop; absent, seventeen `CharacterHotspot` links stay 404. Both look
+ *      correct from any single page — which is why two cases here check the
+ *      index and the detail page SEPARATELY.
+ *   4. Every bundle also carries a placeholder cover, so a collage tested
+ *      after the cover never renders — and one grey tile is not "broken".
+ *
+ * So each case counts an exact number or compares two surfaces. Several carry
+ * a nonsense control, because a filter that returns everything looks identical
+ * to a filter that works.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-content-discovery-category-tabs-franchise-bundles-index-shows-roots-only": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories.",
+            "Confirm the Categories tab is the one selected on arrival.",
+            "Count the cards. There must be exactly six.",
+            "Read the six names: Spinning Tops, Trading Cards, Collectible Figures, Hot Wheels, Model Kits, Living Collectibles.",
+            "Answer no if any deeper category appears here — 'Attack Rings', 'Beyblade Burst', '1B' or any single part name.",
+        ],
+        expectedBehaviour: "BEFORE: the index rendered the whole flat forest — 1,185 rows, of which 752 are part leaves and 220 are model leaves — so the six roots were buried and a visitor met a wall of names with no sense of where they were. AFTER: the Categories tab shows ONLY the tier-0 roots and you walk down from one.",
+        expectedUiState: "Exactly six cards, each a root. No tier-1-or-deeper row anywhere on this tab.",
+        expectedData: { rootCards: 6 },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-five-tabs-no-all": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories.",
+            "Read the tab bar.",
+            "Confirm there are exactly five tabs: Categories, Brands, Franchises, Parts, Bundles.",
+            "Answer no if a tab labelled 'All' is present.",
+        ],
+        expectedBehaviour: "BEFORE: the tabs were All / Categories / Brands, and 'All' was the DEFAULT — it is what rendered the 1,185 rows. AFTER: five tabs, no 'All'. Every tab answers a question ('which parts do you have?'); 'all' answered none of them, which is why it was removed rather than reordered.",
+        expectedUiState: "Five tabs, named exactly as above, with no 'All'.",
+        expectedData: { tabCount: 5, hasAllTab: false },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-parts-tab-is-leaves-only": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories and click the Parts tab.",
+            "Read the total the pager reports.",
+            "Confirm it reads 752 and not 772.",
+            "Scan the first page and confirm every card is an individual PART — '1B', 'Ten Heavy', 'Neo Right SG'.",
+            "Answer no if a classification GROUP appears as a card: 'Attack Rings', 'Weight Disks', 'Performance Tips', 'Bit Chips'.",
+        ],
+        expectedBehaviour: "BEFORE: the tab returned 772, because the predicate matched any row whose ancestry passes a `*-parts` node — which is true of the 20 classification NODES as well as the leaves beneath them. The list mixed groups with their own contents and was not visibly wrong. AFTER: leaves only, 752. A part is a leaf by itself; a classification is a branch you reach by drilling down.",
+        expectedUiState: "752 parts reported. Every card is a single part; no classification group appears.",
+        expectedData: { partsTotal: 752, classificationNodesShown: 0 },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-tabs-do-not-overlap": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories and note the total each of the five tabs reports: Categories, Brands, Franchises, Parts, Bundles.",
+            "Expect 6, 28, 8, 752, 5.",
+            "Pick one brand by name on the Brands tab — for example Takara-Tomy.",
+            "Open each of the other four tabs and search for that same name.",
+            "Answer no if it appears on any tab other than Brands.",
+            "Repeat once with a bundle name taken from the Bundles tab.",
+        ],
+        expectedBehaviour: "Brands, franchises and bundles are all tier-0 rows, so a predicate that tested the tier before the discriminator would list every one of them under Categories as well. The type check has to come first. A row on two tabs double-counts the catalogue and makes the totals unreadable.",
+        expectedUiState: "Tab totals read 6 / 28 / 8 / 752 / 5. The sampled brand and bundle each appear on exactly one tab.",
+        expectedData: { categories: 6, brands: 28, franchises: 8, parts: 752, bundles: 5 },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-franchise-index-hides-unstocked": {
+        roles: ["guest"],
+        startPage: "/franchise",
+        steps: [
+            "Open /franchise.",
+            "Count the cards. Exactly one must be present: Beyblade.",
+            "Answer no if Marvel, DC Comics, Dragon Ball, Naruto, Bleach, One Piece or One Punch Man appears here.",
+        ],
+        expectedBehaviour: "Eight franchises are seeded; seven have no stock. A row with no product is a dead facet — a card that opens an empty shop — so the index lists ACTIVE franchises only. The seven still exist and their pages still resolve; they are simply not advertised as somewhere to shop until they have something to sell.",
+        expectedUiState: "One card, Beyblade. None of the seven unstocked IPs.",
+        expectedData: { franchiseCards: 1 },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-unstocked-franchise-page-resolves": {
+        roles: ["guest"],
+        startPage: "/franchise/marvel",
+        steps: [
+            "Open /franchise/marvel directly.",
+            "Confirm a real page renders — a heading reading Marvel — and NOT a 404 or not-found view.",
+            "Confirm a message says plainly that this franchise is not stocked yet.",
+            "Answer no if the page 404s, or if it renders an empty product grid with no explanation.",
+        ],
+        expectedBehaviour: "BEFORE: `/franchise/*` was not a route at all, so seventeen links in CharacterHotspot 404ed. AFTER: the page resolves. An unstocked franchise is NOT a 404 — the row exists deliberately so those links land somewhere honest. An unexplained empty grid would be the other wrong answer: the visitor arrived from a real link and should be told it is coming, not left to assume something broke.",
+        expectedUiState: "The Marvel page renders with its name and an explicit 'not stocking this yet' message. No 404, no bare empty grid.",
+        expectedData: { httpOk: true, explanationShown: true },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-franchise-detail-lists-its-products": {
+        roles: ["guest"],
+        startPage: "/franchise/franchise-beyblade",
+        steps: [
+            "Open the Beyblade franchise page from /franchise.",
+            "Confirm it reports a listing count in the thousands, not zero and not a handful.",
+            "Confirm product cards render.",
+            "CONTROL: now open /franchise/zzznope by typing it.",
+            "Confirm that page 404s rather than showing the whole catalogue.",
+        ],
+        expectedBehaviour: "The products filter matches on `franchiseSlug`, so a clause that was silently dropped would return the ENTIRE catalogue on every franchise page — which looks like a working page full of products. The nonsense control is the only step that tells a working filter from an absent one.",
+        expectedUiState: "Beyblade lists ~1,304 listings. An unknown franchise slug 404s and never renders a populated grid.",
+        expectedData: { beybladeListings: 1304, nonsenseSlug404s: true },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-bundle-card-shows-a-collage": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories and click the Bundles tab.",
+            "Confirm five bundle cards render.",
+            "Look at each card's image area.",
+            "Confirm it shows a COLLAGE of several product photos, not one single image.",
+            "Answer no if any card shows a single flat colour tile or one lone photo.",
+        ],
+        expectedBehaviour: "BEFORE: a bundle card showed one generic placeholder tile — the least informative thing a bundle card can show, since a bundle IS its contents. AFTER: each card shows a collage built from its members' own photos, resolved at seed time so the card costs no extra query. All five bundles carry 3 or 4 member images, which clears the 3-image minimum the collage needs.",
+        expectedUiState: "Five bundle cards, each showing a multi-image collage rather than a single tile.",
+        expectedData: { bundleCards: 5, cardsWithCollage: 5 },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+};

package/dist/features/tester/seed-data/authored/design-ux__action-bar-placement.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/design-ux__action-bar-placement.js

@@ -0,0 +1,89 @@
+/*
+ * WHY: Authored six-part procedures for the design-ux/action-bar-placement page.
+ * WHAT: 6 case(s), keyed by full checklist id.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-design-ux-action-bar-placement-back-to-top-dismiss-visible": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Open /products and scroll down more than about 400 pixels.",
+            "Look at the floating controls in the bottom corner of the window.",
+            "Click the smaller of the two controls.",
+            "Navigate to /auctions and scroll past 400 pixels again.",
+        ],
+        expectedBehaviour: "The dismiss control is an icon button sized as a true square, so its glyph has room to render. Dismissal is in-memory and resets on route change, so it never hides the control for the rest of the session.",
+        expectedUiState: "TWO round controls are visible: a larger one showing an upward chevron, and a smaller one showing a clearly visible ✕. The prior symptom was the smaller control rendering as an EMPTY outlined pill — present and clickable, with no ✕ inside it, because its content box computed to zero width. After clicking the ✕, both controls disappear.",
+        endResult: "On /auctions both controls are back after scrolling. Nothing is persisted — a reload also brings them back.",
+    },
+    "checklist-design-ux-action-bar-placement-action-bar-top-on-desktop": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Maximise the browser window so it is wider than about 1024 pixels.",
+            "Open any product detail page from /products.",
+            "Look immediately below the site header.",
+            "Scroll the page down and watch the bar.",
+        ],
+        expectedBehaviour: "At `lg` and up the chrome tier is pinned under the header rather than to the bottom edge, and its shadow is cast downward onto the page.",
+        expectedUiState: "The full-width action bar sits directly beneath the header with no gap, and stays there while the page scrolls. Its drop shadow falls DOWNWARD. It must NOT be at the bottom of the window — that was the prior behaviour at every width.",
+        endResult: "Nothing persists; this is layout only. The bar stays under the header for the whole visit at this width.",
+    },
+    "checklist-design-ux-action-bar-placement-action-bar-bottom-on-mobile": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "On the same product detail page, narrow the browser window to phone width (under about 1024 pixels), or switch to device emulation.",
+            "Look at the bottom of the window.",
+            "Slowly widen the window back past the 1024-pixel line, then narrow it again.",
+        ],
+        expectedBehaviour: "One component serves both layouts, switching on a media query, so the bar must move between the two positions rather than being duplicated or dropped.",
+        expectedUiState: "At phone width the action bar is at the BOTTOM, stacked immediately above the bottom navigation bar, with its shadow falling UPWARD. While resizing across the breakpoint the bar moves cleanly from one end to the other — it is never visible in BOTH places at once, and never disappears entirely at any width.",
+        endResult: "No state is written. The bar's position always matches the current window width, including after a reload at either width.",
+    },
+    "checklist-design-ux-action-bar-placement-action-bar-no-content-overlap": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "At desktop width, open a product detail page that shows an action bar.",
+            "Read the very first line of page content under the header.",
+            "Now open a page with no action bar at all, such as /about.",
+            "Look at the space immediately under the header.",
+        ],
+        expectedBehaviour: "The bar is fixed, so it is out of flow and would cover content unless space is reserved. `<Main>` reserves exactly the published tier height, which is zero when no bar exists — so the reservation appears and disappears with the bar rather than being a constant allowance.",
+        expectedUiState: "With a bar present, the first heading and first row of content are fully visible and not clipped behind it. On /about, with no bar, there is NO empty band under the header — the content starts where it always did.",
+        endResult: "Nothing persists. Navigating between a page with a bar and one without must not leave a residual gap on the page that has none.",
+    },
+    "checklist-design-ux-action-bar-placement-action-bar-panels-open-into-screen": {
+        roles: ["admin"],
+        startPage: "/admin/products",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123! and open /admin/products at desktop width.",
+            "Tick the checkboxes on two rows to enter bulk mode.",
+            "Open the bulk action-type picker on the bar.",
+            "Narrow the window to phone width and open the same picker again.",
+        ],
+        expectedBehaviour: "The panel is positioned against the bar, so its open direction must follow whichever screen edge the bar is attached to. Opening away from the screen would put the panel partly or wholly out of view.",
+        expectedUiState: "At desktop width the picker expands DOWNWARD over the page content, below the bar. At phone width it expands UPWARD from the bar. In both cases the whole panel is on screen and scrollable, and no part of it is cut off by the window edge.",
+        endResult: "Closing the picker leaves the bulk selection intact. Clearing the selection removes the bar and the panel together.",
+    },
+    "checklist-design-ux-action-bar-placement-back-to-top-clears-the-bar": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "At phone width, open a product detail page with an action bar and scroll past 400 pixels.",
+            "Look at the vertical gap between the back-to-top control and the action bar.",
+            "Slowly widen the window past the desktop breakpoint, watching the control.",
+        ],
+        expectedBehaviour: "The back-to-top offset is expressed against the measured tier rather than against any individual bar, so it tracks the bar's height automatically — and when the tier moves to the top on desktop, the bottom measurement collapses to zero and the control settles lower.",
+        expectedUiState: "At phone width the control floats clear ABOVE the action bar, which itself sits above the bottom navigation — none of the three overlap. As the window widens past the breakpoint the control moves DOWN into the space the bar vacated. At no point during the resize do the control and any bar overlap.",
+        endResult: "Position is derived from layout alone and nothing is stored; reloading at either width reproduces the same spacing.",
+    },
+};

package/dist/features/tester/seed-data/authored/design-ux__feature-badge-picker.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/design-ux__feature-badge-picker.js

@@ -0,0 +1,82 @@
+/*
+ * WHY: Authored six-part procedures for the design-ux/feature-badge-picker page.
+ * WHAT: 5 case(s), keyed by full checklist id.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-design-ux-feature-badge-picker-features-are-searchable": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "Sign in as the seller who owns the store and open /store/products.",
+            "Open any product for editing.",
+            "Scroll to the 'Feature badges' section of the form.",
+            "Open the control and type a few letters of a badge name.",
+        ],
+        expectedBehaviour: "Anything over five options is a searchable picker in this codebase. The control loads the platform badges eligible for this listing type plus the store's own, and filters them client-side as you type.",
+        expectedUiState: "'Feature badges' is a SINGLE control that opens a searchable list with a text input — not a two-column grid of bordered checkbox tiles, which is what it was. Typing narrows the visible options, and selected badges appear as removable chips on the control.",
+        endResult: "Closing and reopening the picker preserves the current selection. Nothing is saved until the product form itself is saved.",
+    },
+    "checklist-design-ux-feature-badge-picker-features-search-matches-description": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "With the badge picker open, note a badge whose description contains a word that is NOT in its label — 'Sealed' is described as 'Factory wrap intact and never opened'.",
+            "Type that description-only word into the picker's search box, e.g. 'factory'.",
+        ],
+        inputs: { "picker search": "factory" },
+        expectedBehaviour: "Each option's description is folded into its label text specifically so it remains searchable after the conversion. In the old grid the description was visible on every tile, so it was findable by eye; in a filtered list it would be unreachable unless it is part of what is matched.",
+        expectedUiState: "The badge whose DESCRIPTION contains the typed word is listed, even though its name does not contain it. Searching a word in neither the label nor any description shows the no-results message instead.",
+        endResult: "Clearing the search box restores the full list. No selection has changed.",
+    },
+    "checklist-design-ux-feature-badge-picker-features-scope-is-visible": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "Open the badge picker on a product belonging to a store that has at least one custom badge of its own.",
+            "Read the full text of several options in the list.",
+            "Select one platform badge and one store badge, then close the picker and read the two chips.",
+        ],
+        expectedBehaviour: "The grid separated the two scopes under 'Platform features' and 'Store custom features' headings. A flat searchable list has no headings, so the scope is carried in each option's own text — which also means it survives into the selected chip, where the grid's headings never reached.",
+        expectedUiState: "Every option ends with '(platform)' or '(your store)'. The two selected chips each still show which scope they came from. An option with no scope marker at all is a regression.",
+        endResult: "The distinction persists after saving and reopening the product — it is derived from the badge's own scope, not from selection order.",
+    },
+    "checklist-design-ux-feature-badge-picker-features-respects-the-cap": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "Open the badge picker and read the 'Selected: N of 24' line above it.",
+            "Select badges one at a time until N reaches the stated maximum.",
+            "Try to select one more badge.",
+        ],
+        expectedBehaviour: "The ceiling is applied to the incoming selection rather than by disabling unticked rows, because a multi-select has no per-row disabled state. Selections beyond the cap are refused, keeping the earliest ones — so the badge that fails is the one just clicked, which is what a user expects.",
+        expectedUiState: "The counter stops at the maximum and does not go above it. Attempting to add one more does not increase the count and does not silently replace an existing selection. The counter line always matches the number of chips shown.",
+        expectedData: { "selected badge count": "never exceeds the stated maximum" },
+        endResult: "Saving the product stores at most the maximum number of badges. Reopening the product shows the same set.",
+    },
+    "checklist-design-ux-feature-badge-picker-features-inline-create": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "Open the badge picker on one of your own products.",
+            "Choose 'Create a badge for my store'.",
+            "Enter a label such as 'QA inline badge' and leave the icon as its default.",
+            "Submit the create form.",
+            "Close the picker, reload the page, and reopen the picker.",
+        ],
+        inputs: { "Badge label": "QA inline badge", Icon: "star" },
+        expectedBehaviour: "Creating posts to the store-scope features route, which sets the owning store server-side rather than trusting the request body, and scopes the new badge to the listing type being edited. The picker's option list is refetched afterwards so the badge becomes a real option rather than a chip with nothing behind it.",
+        expectedUiState: "The create drawer closes on success and the new badge appears immediately as a SELECTED chip. Reopening the picker lists it among the options, marked '(your store)'. After a full page reload it is still listed and still selected on the product.",
+        expectedData: {
+            "new badge scope": "store",
+            "new badge owner": "the signed-in seller's store",
+        },
+        endResult: "The badge persists as a store-scope feature and is available on that store's other products too. Remove it from the store's feature settings afterwards so it does not accumulate.",
+    },
+};

package/dist/features/tester/seed-data/authored/design-ux__rich-text-readability.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/design-ux__rich-text-readability.js

@@ -0,0 +1,84 @@
+/*
+ * WHY: Authored six-part procedures for the design-ux/rich-text-readability page.
+ * WHAT: 5 case(s), keyed by full checklist id.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-design-ux-rich-text-readability-prose-body-readable-dark": {
+        roles: ["guest"],
+        startPage: "/categories/category-spinning-tops",
+        steps: [
+            "Set the site to DARK mode using the theme toggle in the header.",
+            "Open /categories/category-spinning-tops.",
+            "Scroll to the multi-paragraph write-up directly below the hero banner (it begins 'Four generations of Beyblade').",
+            "Read the full write-up at normal viewing distance without leaning in or changing zoom.",
+        ],
+        expectedBehaviour: "The rich-text block takes its body colour from the active theme's own text token rather than from the Tailwind typography plugin's light-theme default. No element in the block should be rendering a colour that was chosen for a white page.",
+        expectedUiState: "Every sentence of the write-up is comfortably readable against the dark page. The body copy is a light grey, clearly brighter than the page background. It is NOT the dim, low-contrast grey that appears to recede into the background — the specific prior symptom was body text at gray-700 on a dark surface.",
+        endResult: "Nothing is written and nothing persists. Reloading the page in dark mode shows the same readable text; this is a pure rendering check.",
+    },
+    "checklist-design-ux-rich-text-readability-prose-links-visible-dark": {
+        roles: ["guest"],
+        startPage: "/categories/category-spinning-tops",
+        steps: [
+            "Stay in DARK mode on /categories/category-spinning-tops.",
+            "Without moving the mouse over them, locate the five inline links in the write-up: 'Beyblade Original', 'Metal Fight', 'Burst', 'Beyblade X' and 'Accessories'.",
+            "Compare each link's text colour against the paragraph text immediately surrounding it.",
+        ],
+        expectedBehaviour: "Link colour resolves to the theme's secondary accent in dark mode, not to the typography plugin's default link colour. Identifying a link must not require hovering, because hover is unavailable on touch devices.",
+        expectedUiState: "All five links are a visibly different colour from the body copy around them and are obviously clickable at a glance. The prior symptom was links rendering at gray-900 — near-black on a dark page, effectively invisible, findable only by sweeping the cursor and watching for the pointer to change. An underline alone does NOT satisfy this case: the text colour itself must differ.",
+        endResult: "No state changes. Clicking any of the five navigates to that category, which also confirms they were real links and not styled text.",
+    },
+    "checklist-design-ux-rich-text-readability-prose-readable-light-regression": {
+        roles: ["guest"],
+        startPage: "/categories/category-spinning-tops",
+        steps: [
+            "On /categories/category-spinning-tops, switch the theme toggle to LIGHT mode.",
+            "Read the same write-up and locate the same five inline links.",
+            "Toggle between light and dark three times, pausing on each to re-read one paragraph and one link.",
+        ],
+        expectedBehaviour: "Both themes resolve their colours from the same rebound token set, so a regression in one is a plausible consequence of a change to the other. Headings, body copy and links must each stay distinct from one another in both themes.",
+        expectedUiState: "In LIGHT mode the body copy is dark on the white surface and the links are the primary brand colour. Headings remain visibly darker/stronger than body copy. Nothing is washed out, and no text becomes near-invisible at either end of the toggle.",
+        endResult: "The theme choice persists across a reload (it is stored client-side), and the write-up renders correctly in whichever mode was last selected.",
+    },
+    "checklist-design-ux-rich-text-readability-prose-readable-across-surfaces": {
+        roles: ["guest"],
+        startPage: "/blog",
+        steps: [
+            "Set the site to DARK mode.",
+            "Open any published post from /blog and read its body copy and any inline links.",
+            "Open /terms (or /privacy) and read the policy body copy.",
+            "Open /faqs and expand any answer.",
+            "Open any product from /products and read its Description tab.",
+        ],
+        expectedBehaviour: "All four surfaces render through the same shared rich-text renderer, so one shared fix must reach all of them. A surface that is still unreadable means the fix did not apply there and the renderer is being bypassed.",
+        expectedUiState: "On each of the four pages the body copy is readable light-grey-on-dark and any inline links are a visibly distinct colour. No page shows the dim gray-700 body or the near-black links described in the dark-mode cases above.",
+        endResult: "Nothing persists. If any ONE of the four fails while the others pass, record which one — that narrows the cause to that surface's own markup rather than the shared renderer.",
+    },
+    "checklist-design-ux-rich-text-readability-prose-follows-custom-theme": {
+        roles: ["admin"],
+        startPage: "/admin/site",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Open /admin/site and go to the Themes tab.",
+            "Note which theme is currently the default, then set a visibly different one as the active default (for example Cobalt Night, or Sunset).",
+            "Open /categories/category-spinning-tops in a new tab and read the write-up's body copy and links.",
+            "Return to /admin/site → Themes and restore the original default theme.",
+        ],
+        inputs: {
+            "Themes tab — active default": "a theme other than the current default",
+        },
+        expectedBehaviour: "Rich-text colours are bound to `--appkit-color-*` theme tokens, so switching the active theme must restyle admin-authored prose along with the rest of the site. This is only possible since the 2026-10-15 fix: the typography plugin's palette is hardcoded Tailwind greys that no theme record could ever reach.",
+        expectedUiState: "After the theme change, the write-up's paragraph colour and link colour both shift to match the new theme — they do not stay the same grey the previous theme used. Body copy remains readable against whatever surface the new theme sets.",
+        expectedData: {
+            "siteSettings.theme.defaultDarkThemeId": "restored to its original value at the end",
+        },
+        endResult: "The original default theme is restored, so no other tester inherits a changed site theme. Reloading the category page shows prose in the original theme's colours again.",
+    },
+};

package/dist/features/tester/seed-data/authored/index.js

@@ -78,6 +78,7 @@ import { authored as a_content_discovery__coupons } from "./content-discovery__c
 import { authored as a_content_discovery__events } from "./content-discovery__events.js";
 import { authored as a_content_discovery__faq_help } from "./content-discovery__faq-help.js";
 import { authored as a_content_discovery__parts_database } from "./content-discovery__parts-database.js";
+import { authored as a_content_discovery__category_tabs_franchise_bundles } from "./content-discovery__category-tabs-franchise-bundles.js";
 import { authored as a_content_discovery__notifications } from "./content-discovery__notifications.js";
 import { authored as a_content_discovery__search } from "./content-discovery__search.js";
 import { authored as a_cta_layout__checkout_bottom_bar } from "./cta-layout__checkout-bottom-bar.js";
@@ -85,6 +86,9 @@ import { authored as a_cta_layout__dialog_footers } from "./cta-layout__dialog-f
 import { authored as a_cta_layout__editor_action_bar } from "./cta-layout__editor-action-bar.js";
 import { authored as a_cta_layout__product_bottom_bar } from "./cta-layout__product-bottom-bar.js";
 import { authored as a_design_ux__back_to_top_button } from "./design-ux__back-to-top-button.js";
+import { authored as a_design_ux__rich_text_readability } from "./design-ux__rich-text-readability.js";
+import { authored as a_design_ux__action_bar_placement } from "./design-ux__action-bar-placement.js";
+import { authored as a_design_ux__feature_badge_picker } from "./design-ux__feature-badge-picker.js";
 import { authored as a_design_ux__dashboard_layout } from "./design-ux__dashboard-layout.js";
 import { authored as a_design_ux__footer_theme } from "./design-ux__footer-theme.js";
 import { authored as a_design_ux__form_validation_errors } from "./design-ux__form-validation-errors.js";
@@ -199,6 +203,7 @@ export const AUTHORED_CASES = {
     ...a_content_discovery__events,
     ...a_content_discovery__faq_help,
     ...a_content_discovery__parts_database,
+    ...a_content_discovery__category_tabs_franchise_bundles,
     ...a_content_discovery__notifications,
     ...a_content_discovery__search,
     ...a_cta_layout__checkout_bottom_bar,
@@ -206,6 +211,9 @@ export const AUTHORED_CASES = {
     ...a_cta_layout__editor_action_bar,
     ...a_cta_layout__product_bottom_bar,
     ...a_design_ux__back_to_top_button,
+    ...a_design_ux__rich_text_readability,
+    ...a_design_ux__action_bar_placement,
+    ...a_design_ux__feature_badge_picker,
     ...a_design_ux__dashboard_layout,
     ...a_design_ux__footer_theme,
     ...a_design_ux__form_validation_errors,

package/dist/features/tester/seed-data/authored/public-pages__core-listing-pages.js

@@ -180,8 +180,8 @@ export const authored = {
             "Click into one root category and read its page.",
             "Go back and click a tier-3 category and read its page.",
         ],
-        expectedBehaviour: "The index renders the category forest — two roots across four tiers — and every card links to a page that resolves. Products carry their full ancestor chain, so a category page matches on its own id alone and needs no descendant expansion.",
-        expectedUiState: "Both roots, Spinning Tops and Living Collectibles, are present. Every card shows a name and a count rather than a bare name. Both the root and the tier-3 page render with products rather than an empty grid.",
+        expectedBehaviour: "The index renders the SIX roots of the category forest — Spinning Tops, Trading Cards, Collectible Figures, Hot Wheels, Model Kits, Living Collectibles — and every card links to a page that resolves. It shows roots ONLY: the forest is 1,185 rows across five tiers (0-4) and the index used to render every one of them flat. Products carry their full ancestor chain, so a category page matches on its own id alone and needs no descendant expansion.",
+        expectedUiState: "All six roots are present, and NO tier-1-or-deeper category appears on the Categories tab. Every card shows a name and a count rather than a bare name. Both the root and the tier-3 page render with products rather than an empty grid.",
         expectedData: { rootCategoryCount: 2 },
         endResult: "Read-only; nothing persists. A root category page rendering blank with no error is the specific failure worth watching for — the query that produces it is wrapped in a catch that returns nothing.",
     },