@mohasinac/appkit 4.42.1 → 4.42.2

package/dist/features/tester/seed-data/authored/admin__media-watermark.js

@@ -15,6 +15,29 @@
  * within the platform's compute budget, so the mark is a client overlay and its
  * settings have to reach a second consumer.
  *
+ * 🛑 …AND THAT SECOND CONSUMER IS NOT ON THE PRODUCT PAGE (found 2026-09-29).
+ * `<MediaVideo>`, which owns the overlay, is mounted in exactly three places:
+ * `HeroCarousel` and the two admin upload previews. A product video plays in
+ * `ImageLightbox`, which renders a bare `<video controls>` — no overlay layer at
+ * all. So the poster frame is watermarked (it is a still, proxied like any
+ * image) and the playing video is not. The parity case now expects that and
+ * names the homepage hero as the surface where the overlay does apply.
+ *
+ * The watermark tab is on /admin/site → 'Watermark'. Its real controls:
+ * a 'Watermark type' select (Text | Image), 'Watermark text' or a
+ * 'Watermark image' upload, a `Size — N% of image width` slider (5-100 step 5),
+ * an `Opacity — N%` slider (5-100 step 5), a 'Position' select, and a
+ * 'Use a custom X/Y offset instead' toggle revealing two labelled offset
+ * inputs measured in percent FROM CENTER (+right/+down).
+ *
+ * 🛑 THEME RECOLOUR READS `defaultLightThemeId` AND NOTHING ELSE.
+ * `resolveThemeGradientStops` looks up the theme record named by
+ * `theme.defaultLightThemeId` (falling back to "default-light") and takes its
+ * `--appkit-gradient-logo` stops. Changing the DARK default, or a viewer's own
+ * mode, does not move the composited mark's colour — so the case must change
+ * the default LIGHT theme or it will report a failure that is really a
+ * mis-aimed step.
+ *
  * @tag domain:tester
  * @tag layer:seed
  * @tag pattern:none
@@ -28,14 +51,20 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/site and go to the watermark settings, noting the current size and opacity.",
-            "Open a product image in a private window and note how the mark looks.",
-            "Change the size to its largest offered value and the opacity to its most opaque, then save.",
-            "Reload the product image in the private window and compare.",
-            "Restore both settings to their original values and reload the image again.",
+            "Open /admin/site, go to its 'Watermark' tab, and write down the current values of the `Size — N% of image width` and `Opacity — N%` sliders.",
+            "Sign out and open /products/product-beyblade-burst-valkyrie, then open its main image and note how the mark looks.",
+            "Sign back in and set Size to 100 and Opacity to 100, then save.",
+            "Sign out, reload that product image with a HARD reload, and compare.",
+            "Sign back in, restore both sliders to the values written down in step 2, save, and reload the image again.",
         ],
+        inputs: {
+            product: "product-beyblade-burst-valkyrie",
+            sizeAfter: 100,
+            opacityAfter: 100,
+            sliderStep: 5,
+        },
         expectedBehaviour: "Size and opacity reach the served image. The mark is composited server-side as the image is proxied, so a setting that saves without changing the output means the render path is not reading it — and because images are cached aggressively, a hard reload may be needed before concluding either way.",
-        expectedUiState: "The mark is visibly larger and more opaque after the change, and back to its original appearance after the restore. A settings page that saves with no visible effect on the served image is the failure.",
+        expectedUiState: "The mark is visibly larger and more opaque after the change, and back to its original appearance after the restore. Both sliders move in steps of 5 between 5 and 100, so a value typed outside that range is not reachable and is not a finding. A settings page that saves with no visible effect on the served image IS the failure.",
         endResult: "Both settings are restored. Note whether a hard reload was required — that is cache behaviour rather than a defect, but it changes how the next tester reads this page.",
     },
     "checklist-admin-media-watermark-watermark-position-presets": {
@@ -43,12 +72,13 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the watermark settings and read every position preset offered.",
-            "Select each preset in turn, saving after each.",
-            "After each save, open a product image in a private window and note where the mark sits.",
-            "Check the mark stays fully inside the image at every preset.",
-            "Restore the original preset.",
+            "Open /admin/site → 'Watermark' and read every option in the 'Position' select, writing down which is currently set.",
+            "Select each preset in turn — the four corners and center — saving after each. Leave 'custom' to the offset case.",
+            "After each save, sign out and open /products/product-beyblade-burst-valkyrie's main image, noting where the mark sits.",
+            "Repeat one corner preset against a portrait image and a landscape one.",
+            "Restore the preset written down in step 2.",
         ],
+        inputs: { product: "product-beyblade-burst-valkyrie" },
         expectedBehaviour: "Every preset places the mark somewhere different and every one keeps it inside the frame. A corner preset that pushes part of the mark off the edge is the likely failure, since the offset is computed from the image's dimensions and a portrait image behaves differently from a landscape one.",
         expectedUiState: "Each preset moves the mark to its named position and the whole mark remains visible within the image at all of them. Test at least one portrait and one landscape image — a preset correct on one aspect and clipped on the other is the finding.",
         endResult: "The original preset is restored.",
@@ -58,14 +88,20 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the watermark settings and find the custom offset controls.",
-            "Set a modest offset, save, and read a product image in a private window.",
-            "Set an extreme offset — larger than the image itself would allow — save, and read the image again.",
-            "Read whether the mark is clipped, hidden entirely, or clamped to stay visible.",
-            "Restore the original offset.",
+            "Open /admin/site → 'Watermark' and write down the current Position and any offsets.",
+            "Turn on 'Use a custom X/Y offset instead' and read the two inputs it reveals — 'X offset (%) — + right / − left of center' and 'Y offset (%) — + down / − up from center'.",
+            "Set X to 10 and Y to 10, save, sign out, and read /products/product-beyblade-burst-valkyrie's main image.",
+            "Sign back in, set X to 100 and Y to 100 — far enough to push the mark past the edge — save, sign out, and read the image again.",
+            "Read whether the mark is clipped, gone entirely, or clamped so it stays fully inside the frame.",
+            "Sign back in and restore the Position and offsets written down in step 2.",
         ],
+        inputs: {
+            product: "product-beyblade-burst-valkyrie",
+            modestOffset: 10,
+            extremeOffset: 100,
+        },
         expectedBehaviour: "A custom offset moves the mark, and an offset that would push it out of frame is clamped rather than obeyed. Obeying it produces images with no visible watermark at all — which is indistinguishable from the proxy being bypassed and would mask a much larger problem.",
-        expectedUiState: "The modest offset moves the mark by the amount set. The extreme offset leaves the mark still visible, clamped to the frame, rather than pushing it off the image. A silently unwatermarked image is the failure.",
+        expectedUiState: "The modest offset moves the mark by the amount set. The extreme offset leaves the mark still visible, clamped flush to the frame, rather than pushing it off the image. A silently unwatermarked image is the failure. This is expected to PASS — the offset is clamped twice, once when the setting is read and again when the overlay is placed — so a clipped mark here would mean one of those clamps stopped running.",
         endResult: "The original offset is restored.",
     },
     "checklist-admin-media-watermark-watermark-theme-recolor": {
@@ -73,15 +109,17 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the watermark settings and confirm no custom image override is set.",
-            "Open a product image in a private window and note the mark's colour.",
-            "Open the Themes tab, switch the active theme to one with different brand colours, and save.",
-            "Reload the product image and compare the mark's colour.",
-            "Read a dark product photo and a light one and check the mark is visible on both.",
-            "Restore the original theme.",
+            "Open /admin/site → 'Watermark' and confirm 'Watermark type' has no uploaded 'Watermark image' override — with none set the mark falls through to the bundled brand glyph, which is the only tier the theme can recolour.",
+            "Sign out, open /products/product-beyblade-burst-valkyrie's main image, and note the mark's colour.",
+            "Sign back in, open the 'Themes' tab, and write down which theme is set as the DEFAULT LIGHT theme.",
+            "Change the default LIGHT theme to one with different brand colours and save. Changing the dark default will not move the mark — the resolver reads the light one only.",
+            "Sign out, hard-reload the product image, and compare the mark's colour.",
+            "Compare a dark product photo and a light one and check the mark is legible on both.",
+            "Sign back in and restore the default light theme written down in step 4.",
         ],
+        inputs: { product: "product-beyblade-burst-valkyrie", themeSetting: "defaultLightThemeId" },
         expectedBehaviour: "With no image override the mark falls through to the bundled brand glyph, whose gradient stops come from theme colour tokens — so changing the theme recolours it without a second asset. It must stay legible over both dark and light photographs, which is the part a colour change can quietly break.",
-        expectedUiState: "The mark's colour follows the theme. It remains visible on both a dark and a light product photo after the change. A mark that vanishes into one of the two is the finding.",
+        expectedUiState: "The mark's colour follows the DEFAULT LIGHT theme's logo gradient. It remains legible on both a dark and a light product photo after the change. A mark that vanishes into one of the two is the finding. A mark that does not change at all is only a finding if the default LIGHT theme was the one changed — say which you changed.",
         endResult: "The original theme is restored.",
     },
     "checklist-admin-media-watermark-watermark-video-overlay-parity": {
@@ -89,16 +127,22 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the watermark settings and note the size, opacity and position.",
-            "Open /products/product-beyblade-burst-spryzen-video-demo in a private window.",
-            "Look at the video's POSTER frame in the gallery strip and note the mark.",
-            "Play the video and look for the mark while it is playing.",
-            "Compare the mark on the video against the mark on a still image on the same page.",
-            "Change the watermark position, save, and check both the still and the video follow.",
+            "Open /admin/site → 'Watermark' and write down the size, opacity and position.",
+            "Sign out and open /products/product-beyblade-burst-spryzen-video-demo.",
+            "Look at the video's POSTER frame in the gallery strip and note whether it carries the mark.",
+            "Click it to open the lightbox, play the video, and look for the mark while it is playing.",
+            "Compare that against a still image on the same page.",
+            "Now open / and find the 'Live auctions' hero slide, whose background is a video, and look for the mark on it while it plays.",
+            "Sign back in, change the watermark position, save, sign out, and check which of the three — the poster, the product video, the hero video — followed.",
             "Restore the position.",
         ],
-        expectedBehaviour: "The poster frame is a still image and goes through the proxy, so it is composited like any other. The video itself cannot be composited server-side within the platform's compute budget, so its mark is a client overlay reading the same settings from the public settings response — two consumers, one configuration, and they must agree.",
-        expectedUiState: "The poster frame carries the mark. The playing video carries a matching overlay in the same position at a comparable size. After the position change both the still and the video move. A video with no mark, or one whose mark ignores the setting, is the failure.",
-        endResult: "The position is restored. Parity between the two paths is the case — either alone proves nothing.",
+        inputs: {
+            product: "product-beyblade-burst-spryzen-video-demo",
+            heroSlide: "Live auctions",
+        },
+        expectedBehaviour: "A still goes through the proxy and is composited server-side. A video cannot be, within the platform's compute budget, so its mark has to be a client overlay reading the same settings — two consumers, one configuration. The case is whether every surface that plays a video has that second consumer.",
+        expectedUiState: "The poster frame carries the mark, and follows a position change.\n\n🛑 EXPECT THE PRODUCT VIDEO TO CARRY NO MARK, AND RECORD IT AS A FAILURE. The overlay lives in `<MediaVideo>`, which is mounted only by the homepage hero carousel and the two admin upload previews; a product video plays in the lightbox, which renders a bare `<video controls>` with no overlay layer. So expect: poster marked, product video unmarked, hero video marked. Report which of the three followed the position change — that comparison is the finding, and a bare 'the video has no watermark' does not distinguish a missing overlay from a broken one.",
+        expectedData: { posterMarked: true, productVideoMarked: false, heroVideoMarked: true },
+        endResult: "The position is restored. Parity between the paths is the case — a mark on the poster alone proves nothing about the frames a buyer actually watches.",
     },
 };

package/dist/features/tester/seed-data/authored/admin__orders-fulfillment.js

@@ -77,11 +77,11 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/orders and find the manual-payment filter chips.",
-            "Read every chip offered and write the list down.",
+            "Read every chip offered and write the list down — there are three: All, 'Awaiting payment' and 'Awaiting verification'.",
             "Select each in turn and read the rows returned.",
             "Check the awaiting-payment chip returns orders with NO proof uploaded.",
             "Check the awaiting-verification chip returns orders WITH a proof and no decision.",
-            "Read the URL and confirm the selection is encoded there.",
+            "Read the URL and confirm the selection is encoded there as ?paymentReview=awaiting_proof or ?paymentReview=awaiting_verification — a query param of its own, NOT a Sieve f= filter, which is the whole point of the case.",
         ],
         expectedBehaviour: "The queue is not an ordinary Sieve filter. 'Has a proof' cannot be expressed as a query predicate — an inequality on the proof field excludes every document where it was never written, which IS the awaiting-payment set, so the query would return only the opposite of what was asked. The queue runs one bounded query and refines in memory instead, reached through its own query parameter.",
         expectedUiState: "The awaiting-payment chip returns orders with no proof, and the awaiting-verification chip returns orders with a proof and no decision — two visibly different sets. A chip returning the inverse of its name is the predicate failure.",
@@ -206,7 +206,7 @@ export const authored = {
         startPage: "/admin/orders",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin returns surface and read the rows.",
+            "Open /admin/return-requests and read the rows.",
             "Check each row shows the item, the buyer's stated reason and the order it belongs to.",
             "Read the scope tabs and check which scope a return-requested order sits under.",
             "Open one and read the full reason before acting.",
@@ -222,7 +222,7 @@ export const authored = {
         startPage: "/admin/orders",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin fulfillment queue and read every row's primary label.",
+            "Open /admin/fulfillment and read every row's primary label.",
             "Check each names the ITEM and shows its thumbnail rather than only an order id.",
             "Read a multi-item order's row and check it indicates there is more than one item.",
             "Read the queue's ordering and check the oldest unfulfilled order is first.",
@@ -237,7 +237,7 @@ export const authored = {
         startPage: "/admin/shipments",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin shipments surface and read the existing shipments.",
+            "Open /admin/shipments and read the existing shipments.",
             "Create one named 'QA Shipment admin-crud' with a supplier and a date, and save.",
             "RELOAD and read every field.",
             "Add a lot and an item to it, save, RELOAD, and read them back.",

package/dist/features/tester/seed-data/authored/admin__prize-draws-lotteries.js

@@ -29,7 +29,7 @@ export const authored = {
             "Create a prize draw titled 'QA Prize Draw admin-create' at 80 per entry, 25 entries, instant-reveal mode.",
             "Define at least two prizes with names and save.",
             "RELOAD the editor and read the mode, the per-entry price, the entry count and the prizes.",
-            "Open the public page in a private window and read the purchase panel's wording.",
+            "Open the prize draw's public page at /prize-draws/{its id} in a private window and read the purchase panel's wording.",
             "Read whether the panel describes buying an ENTRY rather than buying the prize.",
         ],
         inputs: { title: "QA Prize Draw admin-create", pricePerEntry: 80, entryCount: 25 },
@@ -44,7 +44,7 @@ export const authored = {
             "Sign in as rehan.sheikh@gmail.com / TempPass123! and buy one entry in 'QA Prize Draw admin-create' with Cash on Delivery.",
             "Read what the order page shows immediately after payment.",
             "Sign out and sign in as admin@letitrip.in / TempPass123!.",
-            "Open the draw's admin view and read the entries and any reveal control.",
+            "Open /admin/prize-draws/{its id}/edit and read the entries and any reveal control.",
             "Trigger the reveal if the mode requires it, and read the assigned prize.",
             "Sign back in as the buyer and read the prize on their order.",
             "Compare the prize the admin sees against the one the buyer sees.",
@@ -74,11 +74,11 @@ export const authored = {
         startPage: "/admin/products",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open a prize draw's admin view and read what the reveal mechanism is described as.",
+            "Open /admin/prize-draws/prizedraw-beyblade-burst-collectors-draw/edit — a seeded draw that is still open — and read what the reveal mechanism is described as.",
             "Read whether the admin can choose WHO wins a specific prize.",
             "Read whether the admin can see, before revealing, which prize an entry will draw.",
             "Trigger a reveal and read whether the outcome was predictable from anything on screen beforehand.",
-            "Open the public page and read whether the odds or prize pool are disclosed to buyers.",
+            "Open the prize draw's public page at /prize-draws/{its id} and read whether the odds or prize pool are disclosed to buyers.",
         ],
         expectedBehaviour: "The draw is not steerable. Prizes are assigned by cryptographic randomness at reveal, so an admin cannot pick a winner and cannot see the outcome in advance — a prize draw an operator can steer is a rigged one, whatever else the page does correctly.",
         expectedUiState: "No control assigns a specific prize to a specific entry or buyer. Nothing on the admin screen discloses an entry's outcome before it is revealed. The public page states the prize pool so buyers know what they are entering.",
@@ -89,7 +89,7 @@ export const authored = {
         startPage: "/admin/products",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open a prize draw's entries view and read every column.",
+            "Open /admin/prize-draws/prizedraw-beyblade-metal-closed-revealed/entries — a CLOSED and revealed draw, so it has entries and a recorded winner to read rather than an empty table.",
             "Check each row shows enough to identify the entry without opening it.",
             "Read whether buyer identities are shown in full or masked.",
             "Read the row actions offered and check at least one lets you VIEW the entry.",
@@ -102,4 +102,28 @@ export const authored = {
         expectedData: { nonsenseResultCount: 0 },
         endResult: "Read-only. Delete 'QA Prize Draw admin-create' as the last action of this page.",
     },
+    "checklist-admin-prize-draws-lotteries-lottery-edit-preserves-bookings": {
+        roles: ["admin"],
+        startPage: "/admin/lotteries",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Open /admin/lotteries and find event-pokemon-number-draw-july-2026 — 25 total slots, of which FIVE are already booked in the seed.",
+            "Open its slot editor at /admin/lotteries/event-pokemon-number-draw-july-2026/edit.",
+            "WRITE DOWN which slot numbers show as booked and the buyer named against each.",
+            "Change something harmless and unrelated — rename ONE unbooked slot's prize — and save.",
+            "RELOAD the editor and read the booked slots again.",
+            "Compare every booked slot number and buyer against what you wrote down.",
+            "Read the prices shown on the slots too: they must be the real stored amounts, not zeros.",
+            "Restore the renamed slot and save again.",
+        ],
+        inputs: {
+            eventId: "event-pokemon-number-draw-july-2026",
+            totalSlots: 25,
+            bookedSlots: 5,
+        },
+        expectedBehaviour: "Editing a lottery's prizes leaves its bookings alone. This is the one save in the application that has destroyed buyer data: the editor once sent isBooked:false and weight:0 for every slot and dropped the buyer fields entirely, and because the event PATCH was passthrough, the first save of a live lottery marked every purchased slot available again and erased who had bought them — with a 200 and no error anywhere. The write shape now cannot even express booking state, and the merge reattaches bookings by slotNumber rather than by array position, so deleting a slot cannot hand slot 7's buyer slot 8's prize.",
+        expectedUiState: "All five booked slots are still booked after the reload, against the same buyers, and only the renamed prize differs. Prices read as their stored amounts. 🛑 EVERY SLOT SHOWING AS AVAILABLE is the catastrophic outcome and it looks like a successful save — the page re-renders, the toast is green, and only the buyers know. Every price reading zero is the same defect's twin, from seeding the form off the public projection, which strips price and weight.",
+        expectedData: { bookedSlotsAfterSave: 5, slotsPricedZero: 0 },
+        endResult: "The renamed slot is restored and all five bookings survive. If any booking is gone, STOP and report it immediately rather than continuing the batch — there is no undo, and the remaining cases on this page would be run against corrupted data.",
+    },
 };

package/dist/features/tester/seed-data/authored/admin__site-system.js

@@ -1,6 +1,27 @@
 /*
  * WHY: Authored six-part procedures for the admin/site-system checklist page.
- * WHAT: 35 case(s), keyed by full checklist id.
+ * WHAT: 37 case(s), keyed by full checklist id.
+ *
+ * 🛑 SITE SETTINGS IS PRESERVE-TIER, AND THE TESTER RULES SAY NEVER MODIFY IT.
+ * That rule and this page are not in conflict, but the reconciliation has to be
+ * stated or a tester following the rules literally answers `null` to all of them.
+ *
+ * The rule exists because `siteSettings` is NEVER wiped and NEVER reseeded — the
+ * lifecycle preserves it by design, so unlike the catalogue there is nothing to
+ * put it back. What it forbids is leaving it CHANGED, not touching it.
+ *
+ * So every mutating case here does three things, and a case that skips any of
+ * them is the defect rather than the coverage:
+ *
+ *   1. read and write down the existing value BEFORE editing,
+ *   2. make the smallest change that proves the point,
+ *   3. RESTORE the recorded value — not "clear the field", which is a different
+ *      destructive edit wearing the same clothes.
+ *
+ * Three cases had no restore at all until 2026-09-29, and one of them overwrote
+ * the PhonePe Client ID, Client Secret and both webhook credentials with QA
+ * values and walked away. Running it would have disabled online payment for real
+ * buyers, silently, until somebody with the real keys noticed.
  *
  * Written by hand, case by case, against the label each one states. There is no
  * generator: the authoring scripts were deleted once it was clear they were
@@ -51,18 +72,18 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/site and go to the credentials tab.",
-            "Read how existing credentials are displayed.",
-            "Type QA-CREDENTIAL-118427 into one credential field and save.",
+            "Read how existing credentials are displayed, and WRITE DOWN the masked value of every field on the tab before touching anything.",
+            "Pick a field whose masked value shows a *_PLACEHOLDER or is empty — never one holding a real key. Type QA-CREDENTIAL-118427 into that field and save.",
             "Read the confirmation and RELOAD the tab.",
             "Read how that credential now displays.",
             "Open /api/site-settings in a private window and search the response for QA-CREDENTIAL-118427.",
-            "Clear the field, save, and reload to confirm.",
+            "RESTORE the field to exactly what step 3 recorded — clearing it is NOT restoring it, and siteSettings survives every run, so a cleared real key is gone for good. Save and reload to confirm the original masked value is back.",
         ],
         inputs: { credential: "QA-CREDENTIAL-118427" },
         expectedBehaviour: "A credential is encrypted before storage and returned masked. The encryption helper THROWS when its key is unset — so a save that fails outright is a missing-key problem rather than a form bug, and a save that succeeds while storing plaintext is worse than either.",
         expectedUiState: "After the reload the credential shows masked rather than as the typed value or as raw ciphertext. The public settings response contains no trace of it. A save that errors should name the missing configuration rather than showing a stack trace.",
         expectedData: { credentialInPublicResponse: 0 },
-        endResult: "The field is cleared. A hit in the public response is a credential leak and fails the case outright.",
+        endResult: "The field holds exactly what it held before the case ran — restored, not cleared. A hit in the public response is a credential leak and fails the case outright.",
     },
     "checklist-admin-site-system-site-settings-credentials-partial-save-keeps-others": {
         roles: ["admin"],
@@ -120,11 +141,12 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/site and switch to the Integrations tab.",
-            "Read the current PhonePe Client ID, Client Secret, Client Version, Environment and both webhook credential fields.",
+            "WRITE DOWN the current PhonePe Client ID, Client Secret, Client Version, Environment and both webhook credential fields — the masked form of each. You must be able to put them back; nothing else will.",
             "Type QA-PHONEPE-CLIENT-991 into the Client ID field, QA-PHONEPE-SECRET-991 into the Client Secret field, and QA-WEBHOOK-USER-991 / QA-WEBHOOK-PASS-991 into the two webhook fields.",
             "Save, then hard-reload the page.",
             "Read how the Client Secret and both webhook fields display.",
             "Change only the PhonePe Environment dropdown, save again, and reload.",
+            "RESTORE every one of the six fields to exactly what step 3 recorded, save, and reload to confirm. This is not optional housekeeping: siteSettings is never reseeded, so QA values left in the PhonePe Client ID and Secret disable online payment for real buyers until someone notices and has the real keys to hand.",
         ],
         inputs: {
             clientId: "QA-PHONEPE-CLIENT-991",
@@ -142,11 +164,11 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/site and switch to the Shipping tab.",
-            "Read the current state of the 'PhonePe (online card/UPI) enabled' toggle.",
-            "Turn it OFF, save, and open /checkout in another tab (with an item in the cart) to confirm 'Pay Online (PhonePe)' is absent from the payment step.",
-            "Return to Site Settings, turn the toggle back ON, and save.",
-            "Reload the settings page to confirm it reads ON.",
-            "Reopen /checkout and confirm 'Pay Online (PhonePe)' is now offered.",
+            "Read the current state of the 'PhonePe (online card/UPI) enabled' toggle. It is seeded OFF (phonepeEnabled: false), so ON is the direction that proves anything here — turning OFF something already off would leave PhonePe absent from checkout for the reason it was always absent, and pass trivially.",
+            "Turn it ON, save, and open /checkout in another tab (with an item in the cart) to confirm 'Pay Online (PhonePe)' is now offered in the payment step.",
+            "Return to Site Settings, RELOAD, and confirm the toggle still reads ON — the save is not proven until the reload.",
+            "Turn it back OFF and save, restoring the seeded state.",
+            "Reopen /checkout and confirm 'Pay Online (PhonePe)' is absent again.",
         ],
         expectedBehaviour: "The toggle lives under the Shipping tab's 'Payment methods' section, not a dedicated Payments tab — the same admin field checkout's payment-method list reads from. It gates whether the PhonePe option is offered at all, independent of the manual-UPI and COD toggles beside it.",
         expectedUiState: "With the toggle OFF, /checkout offers only whichever of manual UPI/cash and COD are separately enabled — no 'Pay Online (PhonePe)' button. With it back ON, the button reappears.",
@@ -157,12 +179,12 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the WhatsApp settings and read every field and its current state.",
+            "Open /admin/site, switch to the Integrations tab, and WRITE DOWN every WhatsApp field and its current masked state before touching anything.",
             "Type QA-WA-TOKEN-552310 into the access-token field and fill any account identifier fields.",
             "Save and RELOAD, then read how each field displays.",
             "Open /api/site-settings in a private window and search for QA-WA-TOKEN-552310.",
             "Open a public store page's source and search for it too.",
-            "Clear the fields, save, and reload.",
+            "RESTORE every field to exactly what step 3 recorded — clearing is not restoring, and a real Meta token cleared here cannot be recovered from the seed. Save and reload to confirm.",
         ],
         inputs: { token: "QA-WA-TOKEN-552310" },
         expectedBehaviour: "The token is encrypted at rest and masked on read. It is also decrypted on every read of a store document, so any page handing a raw store document to a client component serialises it into public HTML — which is why both the settings response and a public store page are checked rather than the admin form alone.",
@@ -175,8 +197,8 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the WhatsApp settings and read every channel toggle and its state.",
-            "Turn one OFF and save.",
+            "Open /admin/site, switch to the Notifications tab, and read every channel toggle and its state. Four are listed: in-app, email, WhatsApp and SMS.",
+            "Turn the WHATSAPP channel off and save. Pick that one specifically — SMS is seeded OFF (and has no sender at all), so toggling it off would be a no-op that proves nothing.",
             "RELOAD and read every toggle.",
             "Check only the one changed.",
             "Turn it back on, save, and reload to confirm.",
@@ -285,7 +307,7 @@ export const authored = {
         startPage: "/admin/analytics",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin analytics page and read every card and chart.",
+            "Open /admin/analytics and read every card and chart.",
             "Write down any figure reading zero or a dash.",
             "Change the date range if one is offered and read the figures again.",
             "Reload and confirm the figures are stable.",
@@ -316,7 +338,7 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open the browser console and clear it.",
-            "Open the admin analytics page and wait for every card to settle.",
+            "Open /admin/analytics and wait for every card to settle.",
             "Read the console for any permission-denied message.",
             "Open the admin dashboard and read the console again.",
             "Note which card or widget was loading when any such message appeared.",
@@ -361,7 +383,7 @@ export const authored = {
         startPage: "/admin/maintenance",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the maintenance section and read every page it links to.",
+            "Open /admin/maintenance and read every page it links to.",
             "Open each in turn and confirm it renders content rather than an error.",
             "Note any that shows a failed-precondition or missing-index error.",
             "Note any that shows a permission or credentials error.",
@@ -376,10 +398,10 @@ export const authored = {
         startPage: "/admin/maintenance",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the server errors list and read the rows.",
+            "Open /admin/maintenance/server-errors and read the rows.",
             "Read whether rows carry a source, a code, a message and a time.",
-            "Open the client errors list and read its rows.",
-            "Open the function errors list and read its rows.",
+            "Open /admin/maintenance/client-errors and read its rows.",
+            "Open /admin/maintenance/function-errors and read its rows.",
             "Note which of the three lists is empty.",
             "Check the sort order puts the newest first.",
         ],
@@ -392,7 +414,7 @@ export const authored = {
         startPage: "/admin/maintenance",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the cloud logs page and read what renders.",
+            "Open /admin/maintenance/cloud-logs and read what renders.",
             "Read whether it shows log entries, an empty state, or an error.",
             "If it errors, read whether the message names the missing configuration.",
             "Reload and confirm the behaviour is consistent.",
@@ -407,7 +429,7 @@ export const authored = {
         startPage: "/admin",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the copilot or assistant surface and read what it offers.",
+            "Open /admin/copilot and read what it offers.",
             "Read whether it states which model or provider it uses.",
             "Submit a simple request and read the response.",
             "Read whether any error surfaces a provider key or a raw response body.",

package/dist/features/tester/seed-data/authored/admin__uncovered-admin-pages.js

@@ -12,6 +12,22 @@
  * speculative cases against a screen nobody has opened is how a checklist grows
  * cases that measure nothing.
  *
+ * Checked 2026-09-29, and three descriptions were wrong about the affordance:
+ *
+ *   · /admin/featured is "Featured Products" — `buildFilters: () => "featured==true"`
+ *     — so the row action REMOVES a product from the list rather than toggling a
+ *     two-state control. Re-featuring is done from /admin/products' Quick edit,
+ *     which is the only surface with a Featured toggle.
+ *   · /admin/deals is "Deals (Promoted Products)" and its rows DO open — via
+ *     `rowHrefTemplate` to /admin/products/{id}/edit, not to a detail of its own.
+ *   · /admin/stickers has exactly ONE facet, `filterKeys: ["status"]`, so "apply a
+ *     different filter" means a different status VALUE. Only `published` stickers
+ *     are seeded, so the other three statuses returning nothing is correct.
+ *
+ * All twelve guide routes named in the guides case exist, and all twelve are in
+ * ADMIN_NAV_GROUPS — verified rather than assumed, because the hrefs audit
+ * checks `href`/`startPage` only and cannot see a route named in step prose.
+ *
  * @tag domain:tester
  * @tag layer:seed
  * @tag pattern:none
@@ -130,13 +146,14 @@ export const authored = {
         startPage: "/admin/settings/actions",
         steps: [
             SIGN_IN_ADMIN,
-            "Open /admin/settings/actions.",
-            "Read what the page lets an admin change.",
-            "Change one setting and save.",
+            "Open /admin/settings/actions and read its two panels — the action-permissions manager and the nav-permissions panel.",
+            "Write down the current value of the one control you are about to change.",
+            "Change ONE action's permission — not a nav permission — and save.",
             "Reload and read whether the change held.",
-            "Restore the original value.",
+            "Restore the value written down in step 3 and reload once more to confirm it went back.",
         ],
-        expectedBehaviour: "A change made here persists. A settings save that returns success without writing is the most dangerous failure a settings screen has — there is no stale display to notice and no error to read, and it has happened on this codebase before.",
+        inputs: { panel: "action permissions" },
+        expectedBehaviour: "A change made here persists. A settings save that returns success without writing is the most dangerous failure a settings screen has — there is no stale display to notice and no error to read, and it has happened on this codebase before.\n\n🛑 Change an ACTION permission, not a nav permission. The nav panel drives the disabled-routes gate that runs in the proxy, so disabling the wrong entry 404s a real route for every later case in the run.",
         expectedUiState: "The changed value is still changed after the reload. A value that reverts is the finding, even though the save reported success.",
         endResult: "The original value is restored.",
     },
@@ -160,14 +177,16 @@ export const authored = {
         startPage: "/admin/stickers",
         steps: [
             SIGN_IN_ADMIN,
-            "Open /admin/stickers.",
-            "Read the rows listed and count them.",
-            "Apply a status filter and read the rows again.",
-            "Clear it and apply a different filter.",
-            "Check each filter returns a plausible, non-empty result where such rows exist.",
+            "Open /admin/stickers and read the rows listed, counting them — five sticker listings are seeded.",
+            "Open the filter drawer: this page has ONE facet, Status.",
+            "Select Published and read the rows.",
+            "Select Draft, then In Review, then Archived, reading the rows each time.",
+            "Type zzzznope into the search box and read the count.",
         ],
+        inputs: { seededStickerCount: 5, nonsenseQuery: "zzzznope" },
         expectedBehaviour: "The list and its filters return real sticker listings. A filter whose value does not exactly match a stored one returns zero rows forever with no error — the single most common silent defect in this product's listing surfaces, and it looks identical to an empty catalogue.",
-        expectedUiState: "Rows on the default view, and each filter returning a subset rather than nothing. An always-empty filter is the finding, named.",
+        expectedUiState: "Rows on the default view, and Published returning them. Draft, In Review and Archived are EXPECTED to return nothing — only published stickers are seeded, so an empty result there is correct and is not a finding. What would be a finding is Published returning nothing while the unfiltered list holds rows, which is the always-empty-filter shape. 'zzzznope' returns none.",
+        expectedData: { nonsenseResultCount: 0 },
         endResult: "Read-only.",
     },
     "checklist-admin-uncovered-admin-pages-admin-deals-renders": {
@@ -175,14 +194,16 @@ export const authored = {
         startPage: "/admin/deals",
         steps: [
             SIGN_IN_ADMIN,
-            "Open /admin/deals.",
-            "Read what the page lists.",
-            "Open one row.",
-            "Read what the detail shows.",
+            "Open /admin/deals and read its title — it lists promoted products.",
+            "Read the rows listed.",
+            "Click one row and read the URL it lands on.",
+            "Read whether the page it opened shows that product, and whether it is a product editor rather than a deal detail.",
             "Read the console for errors.",
         ],
+        inputs: { expectedRowDestination: "/admin/products/{id}/edit" },
         expectedBehaviour: "Rows can be opened. A row offering only mutations, or no way in at all, is a dead end — an admin can act on a record they were never able to read.",
-        expectedUiState: "Rows render and one opens to a readable detail. A list with no detail affordance is the finding.",
+        expectedUiState: "Rows render and one opens — to the product editor at /admin/products/{id}/edit, which is this page's detail affordance rather than a deal-specific view. That is a pass: the record being listed IS a product. A row that does nothing on click is the finding.",
+        expectedData: { consoleErrors: 0 },
         endResult: "Read-only.",
     },
     "checklist-admin-uncovered-admin-pages-admin-featured-renders": {
@@ -190,15 +211,19 @@ export const authored = {
         startPage: "/admin/featured",
         steps: [
             SIGN_IN_ADMIN,
-            "Open /admin/featured and read what it lists.",
-            "Toggle one record's featured state.",
-            "Reload the page and read the same record's state.",
-            "Open the public surface that shows featured content and check it followed.",
-            "Restore the original state.",
+            "Open /admin/featured, read its title and note which products it lists — every row is a product whose featured flag is set.",
+            "Write down the name of one of them.",
+            "Sign out and open /, find the 'Featured Products' section, and confirm that product is in it.",
+            "Sign back in, use the row action that removes that product from featured, and reload /admin/featured to confirm it is gone from the list.",
+            "Sign out and reload /, checking the 'Featured Products' section no longer carries it.",
+            "Sign back in, open /admin/products, find that product, and use the row menu's 'Quick edit' to turn its Featured toggle back on — this page can only remove, so restoring is done there.",
+            "Reload /admin/featured and confirm the product is listed again.",
         ],
-        expectedBehaviour: "A featured toggle persists and the public surface follows it. A list endpoint that omits a field the edit form sends back is how a toggle silently resets — saving any other field on the record re-sends a wrong default for the one the list never returned.",
-        expectedUiState: "The toggled state survives the reload and appears publicly. A state that reverts is the finding.",
-        endResult: "The original featured state is restored.",
+        inputs: { publicSection: "Featured Products", restoreVia: "/admin/products Quick edit" },
+        expectedBehaviour: "The featured flag persists and the homepage follows it, in both directions. This page is a FILTERED VIEW of products where `featured == true`, not a toggle board, so removal happens here and restoring happens on /admin/products — a case that expects one control to do both would report a missing affordance that was never there. A list endpoint that omits a field the edit form sends back is how such a flag silently resets: saving any other field on the record re-sends a wrong default for the one the list never returned.",
+        expectedUiState: "The removal survives a reload and the homepage's 'Featured Products' section loses the product; re-featuring from /admin/products brings it back to both. A state that reverts on its own is the finding. Note the section shows at most twelve products, so a product that does not appear may simply be beyond the cap — pick one that was visible in step 3 before concluding anything.",
+        expectedData: { removedFromPublicSection: true, restoredAfterQuickEdit: true },
+        endResult: "The product is featured again and back in the homepage section.",
     },
     "checklist-admin-uncovered-admin-pages-admin-features-renders": {
         roles: ["admin"],
@@ -222,13 +247,13 @@ export const authored = {
         steps: [
             SIGN_IN_ADMIN,
             "Open each of these by URL in turn: /admin/guide, /admin/guide/analytics, /admin/guide/catalog, /admin/guide/content, /admin/guide/orders, /admin/guide/payments, /admin/guide/site, /admin/guide/stores, /admin/guide/team, /admin/guide/trust, /admin/guide/users and /admin/guide/whatsapp.",
-            "Check every one of them is also linked from the Guide area rather than only reachable by URL.",
+            "Check every one of them is also reachable from the admin sidebar's Guides group rather than only by URL — all twelve have a nav entry, so a missing one is a finding.",
             "Record any that 404 or render empty.",
-            "On two of them, check the screen they describe still exists and is named the same way.",
-            "Record any guide describing a screen or a control that is no longer there.",
+            "Pick the Site Configuration and Content & Marketing guides and, for each screen or control they name, open it and check it still exists under that name.",
+            "Record any guide describing a screen or a control that is no longer there, naming both the guide and the screen.",
         ],
         expectedBehaviour: "Every guide page renders and describes something that still exists. A guide is documentation with no compiler behind it, so it rots silently — and a guide naming a deleted screen is worse than none, because it sends an employee looking for something that is gone.",
-        expectedUiState: "Every guide loads with real content. A 404 is a finding; so is a guide describing a screen that no longer exists, recorded with which guide and which screen.",
+        expectedUiState: "Every guide loads with real content and every one is in the sidebar's Guides group. A 404 is a finding; so is a guide describing a screen that no longer exists, recorded with which guide and which screen. The second is the likelier of the two and the reason this case exists — the routes are checked by an audit on every build, the PROSE inside them is checked by nobody.",
         expectedData: { guidePagesNotFound: 0 },
         endResult: "Read-only.",
     },