@mohasinac/appkit 4.52.5 → 4.53.1

package/dist/features/tester/seed-data/authored/selling__media-limits.js

@@ -18,6 +18,7 @@
  * @tag consumers:seed-data/authored/index.ts
  * @tag sideEffects:none
  */
+import { PRODUCT_MAX_IMAGES } from "../../../../_internal/shared/media/limits.js";
 export const authored = {
     "checklist-selling-media-limits-media-gallery-accepts-images-and-video": {
         roles: ["seller"],
@@ -41,39 +42,40 @@ export const authored = {
         expectedUiState: "Three image previews and one video poster frame, each showing its own content rather than a generic icon. No error toast on any of the four.",
         endResult: "Leave the editor without saving so no draft product is created.",
     },
-    "checklist-selling-media-limits-media-tenth-image-uploads": {
+    "checklist-selling-media-limits-media-last-allowed-image-uploads": {
         roles: ["seller"],
         startPage: "/store/products/new",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and type 'QA Product media-tenth' as the title.",
+            "Open /store/products/new and type 'QA Product media-boundary' as the title.",
             "Click 'Show all fields (advanced)' before touching any media. 🛑 /store/products/new opens the QUICK form by default for a create of a standard listing, and it has ONE field — 'Product Image' — with no gallery and no video field at all. Every media step below needs the advanced form.",
-            "Upload public/test-media/sample-image.png to the gallery nine times, counting the previews after each.",
-            "Upload it a tenth time.",
-            "Read the preview count and any message about the limit.",
+            `Read the counter under the gallery and note the cap it advertises. It must read ${PRODUCT_MAX_IMAGES}. 🛑 Do NOT assume a number here — the cap is one constant (\`PRODUCT_MAX_IMAGES\`) and this case is written against whatever it currently is.`,
+            "Upload public/test-media/sample-image.png to the gallery repeatedly, one at a time, counting the previews after each, until the control refuses one.",
+            "Record the preview count reached at the moment of the first refusal.",
         ],
-        inputs: { title: "QA Product media-tenth", uploadCount: 10, cap: 10 },
-        expectedBehaviour: "The tenth image is accepted, because the cap is ten and a cap is inclusive of its own number. An off-by-one that refuses the tenth is the most likely error and the least likely to be noticed, since nine images look like plenty.",
-        expectedUiState: "Ten previews are present after the tenth upload. Any limit message reads as 'you have reached the limit' rather than as a rejection of the tenth file.",
-        expectedData: { imageCount: 10 },
+        inputs: { title: "QA Product media-boundary", cap: PRODUCT_MAX_IMAGES },
+        expectedBehaviour: `Every upload up to and including the ${PRODUCT_MAX_IMAGES}th is accepted, because a cap is inclusive of its own number. An off-by-one that refuses the last one is the most likely error and the least likely to be noticed, since one short of the cap still looks like plenty.`,
+        expectedUiState: `The preview count reached before the first refusal is exactly ${PRODUCT_MAX_IMAGES}. The counter's own advertised cap and the count actually reachable must be the SAME number — a form that says ${PRODUCT_MAX_IMAGES} and allows ${PRODUCT_MAX_IMAGES - 1} is the failure, whichever number it says.`,
+        expectedData: { imageCount: PRODUCT_MAX_IMAGES },
         endResult: "Leave the editor without saving.",
     },
-    "checklist-selling-media-limits-media-eleventh-image-refused-client-side": {
+    "checklist-selling-media-limits-media-over-cap-image-refused-client-side": {
         roles: ["seller"],
         startPage: "/store/products/new",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and upload public/test-media/sample-image.png ten times.",
+            "Open /store/products/new.",
             "Click 'Show all fields (advanced)' before touching any media. 🛑 /store/products/new opens the QUICK form by default for a create of a standard listing, and it has ONE field — 'Product Image' — with no gallery and no video field at all. Every media step below needs the advanced form.",
+            `Fill the gallery to its cap with public/test-media/sample-image.png (${PRODUCT_MAX_IMAGES} uploads).`,
             "Open the browser's Network panel.",
-            "Attempt an eleventh upload of the same file.",
+            "Attempt one more upload of the same file.",
             "Read the message shown and count the previews.",
-            "Check the Network panel for any upload request made by that eleventh attempt.",
+            "Check the Network panel for any signed-URL or upload request made by that over-cap attempt.",
         ],
-        inputs: { cap: 10, attemptCount: 11 },
-        expectedBehaviour: "The eleventh is refused in the browser, before any signed URL is requested. Refusing it only after the bytes have reached storage leaves an orphaned object behind and spends the seller's upload time on a file that was never going to be kept.",
-        expectedUiState: "A readable message names the ten-image limit, the preview count stays at ten, and the Network panel shows NO upload request for the eleventh attempt. A refusal that appears only after a round trip is the failure.",
-        expectedData: { imageCount: 10, uploadRequestsForEleventh: 0 },
+        inputs: { cap: PRODUCT_MAX_IMAGES, attemptCount: PRODUCT_MAX_IMAGES + 1 },
+        expectedBehaviour: "The over-cap file is refused in the browser, before any signed URL is requested. Refusing it only after the bytes have reached storage leaves an orphaned object behind and spends the seller's upload time on a file that was never going to be kept.",
+        expectedUiState: `A readable message NAMES the limit as ${PRODUCT_MAX_IMAGES}, the preview count stays at ${PRODUCT_MAX_IMAGES}, and the Network panel shows NO upload request for the over-cap attempt. A refusal that appears only after a round trip is the failure, and so is a refusal that does not say what the limit is.`,
+        expectedData: { imageCount: PRODUCT_MAX_IMAGES, uploadRequestsForOverCap: 0 },
         endResult: "Leave the editor without saving.",
     },
     "checklist-selling-media-limits-media-second-video-refused-first-kept": {

package/dist/features/tester/seed-data/authored/selling__product-upload-details.js

@@ -7,13 +7,18 @@
  *
  *   Main image    ImageUpload,      label "Main Image", enableAdvancedCrop,
  *                                   cropAspectRatio 1, max 10 MB, index 1
- *   Gallery       MediaUploadList,  label "Gallery (up to 10 images + 1 video)",
- *                                   maxItems 11, maxImages 10, maxVideos 1,
- *                                   maxSizeMB 50, indices 2..11
+ *   Gallery       MediaUploadList,  label "Gallery (up to N images + 1 video)",
+ *                                   maxItems PRODUCT_MAX_IMAGES + PRODUCT_MAX_VIDEOS,
+ *                                   maxSizeMB 50, indices 2..PRODUCT_IMAGE_INDEX_MAX
  *   Video panel   MediaUploadField, YouTube / external URL / trim / poster
  *
- * The existing pages already cover the CAPS (selling/media-limits: 10th uploads,
- * 11th refused, second video refused) and the basics (selling/listing-a-product:
+ * 🛑 The caps are deliberately named here rather than numbered. They are one
+ * constant (`_internal/shared/media/limits.ts`) and they MOVE — 5 -> 10 -> 24 so
+ * far — and every previous revision of this comment pinned the number of the day.
+ *
+ * The existing pages already cover the CAPS (selling/media-limits: the last
+ * allowed image uploads, the first over the cap is refused client-side, a second
+ * video is refused) and the basics (selling/listing-a-product:
  * upload, preview, remove, crop, multiple). This page covers what neither does:
  * refusal copy, type refusal, ordering, index collision, and the video path that
  * was returning a 500 until 2026-09.

package/dist/features/tester/seed-data/authored/selling__spares-and-group-editing.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/selling__spares-and-group-editing.js

@@ -0,0 +1,77 @@
+/*
+ * WHY: Authored six-part procedures for the seller side of Part Two —
+ *      listing a spare, and the shared group-stock/rules editor.
+ * WHAT: 4 case(s), keyed by full checklist id.
+ *
+ * 🛑 "Stock is independent per listing" is the whole premise of the shared
+ * editor, so the round trip that proves it (edit one, reload, check the
+ * OTHER member) is the case that actually matters here — not whether the
+ * form submits.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+const SELLER_SIGNIN = "Sign in as a seller account that owns store-beyblade-arena.";
+export const authored = {
+    "checklist-selling-spares-seller-and-group-editing-seller-can-list-a-spare": {
+        roles: ["seller"],
+        startPage: "/store/spares",
+        steps: [
+            SELLER_SIGNIN,
+            "Click \"List a Spare\".",
+            "Fill in title, price, colourway, and a stock quantity, then Publish.",
+            "Return to /store/spares.",
+        ],
+        expectedBehaviour: "The seller product-shell accepts `listingType: \"spares\"` the same way it accepts the other nine types — this is the one new entry in `ProductListingMode`, so a missing wiring here would show as a form that silently fails to save or a blank listing-type dropdown.",
+        expectedUiState: "The new spare appears in the /store/spares list with the colourway shown as its distinguishing column (not a size column, which the other print types use), the price entered, and status Published.",
+        endResult: "BEFORE spares existed, there was no seller-facing way to list one at all. AFTER: creating one is the same shape as creating a sticker or an art print, just under a different type.",
+    },
+    "checklist-selling-spares-seller-and-group-editing-group-stock-edit-is-independent": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            SELLER_SIGNIN,
+            "Open the editor for a group PARENT product (one with \"isGroupParent\").",
+            "In the Members list, note the current stock figures for two different children, A and B.",
+            "In the shared stock editor, change ONLY child A's stock to a new number. Leave B's input untouched.",
+            "Click \"Save group stock\".",
+            "Reload the editor and re-read both children's stock figures.",
+        ],
+        expectedBehaviour: "`PATCH .../group/stock` writes ONLY the member rows named in the request body — `saveGroupStock()` sends just the touched ids via `stockDraft`/`motDraft`, never a blanket broadcast across every child. Stock is independent per listing by design: a spare is one physical object a seller happens to have, and selling or restocking one must not touch another's figure.",
+        expectedUiState: "After reload, child A shows the NEW figure you entered. Child B shows EXACTLY the figure it had before — unchanged to the unit. This is the single most important assertion in this group: a shared pool bug would show up as B silently changing when only A was edited.",
+        endResult: "BEFORE this editor existed, each child's stock could only be edited by opening its own separate product page — tedious but safe. AFTER: editing is faster AND must remain exactly as safe. If B's figure moved at all, the editor is pooling stock rather than editing independent listings, which contradicts the feature's entire premise.",
+    },
+    "checklist-selling-spares-seller-and-group-editing-group-rules-save-and-reload": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            SELLER_SIGNIN,
+            "Open a group parent's editor and find the \"Selection rules\" form.",
+            "Change the min, max, per-item cap, and discount fields to new values different from what they currently show.",
+            "Click \"Save rules\".",
+            "Reload the editor page.",
+            "As a buyer (different tab/session), open that group's public picker.",
+        ],
+        expectedBehaviour: "`PATCH .../group` writes only the keys present in the body, via the `in` test rather than a spread — so saving rules must not blank the group title, and reloading must show exactly what was saved, not a stale cached value. The public picker reads the SAME stored fields through `readGroupRules`, so it must reflect the new numbers on its very next load, with no separate publish step.",
+        expectedUiState: "After reload, the editor's four rule fields show the NEW values you typed, not the old ones and not blank. The buyer-facing picker, opened fresh, states the NEW rules in its rule-summary text — if it still shows the old numbers, something is caching the group document past this write.",
+        endResult: "BEFORE: a group had no rules to edit at all. AFTER: a seller's edit is live on the storefront immediately, and a reload of the editor proves the write actually persisted rather than only updating client-side state.",
+    },
+    "checklist-selling-spares-seller-and-group-editing-group-stock-partial-failure-reported": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            SELLER_SIGNIN,
+            "Open a group parent's editor in TWO browser tabs.",
+            "In tab 1, unlink one child from the group and confirm it.",
+            "Switch to tab 2 (which still shows the now-unlinked child in its member list) and, without reloading, edit that same child's stock PLUS a different, still-valid child's stock.",
+            "Click \"Save group stock\" in tab 2.",
+        ],
+        expectedBehaviour: "The route re-fetches the CURRENT member list server-side before writing, so the unlinked child's id is no longer a member and is rejected — but the request must not fail as a whole. The still-valid child's stock edit must still be written. This is the 207-style partial result the route is built for.",
+        expectedUiState: "A toast or message reports a partial result (e.g. \"Updated 1; 1 could not be updated.\"). Reloading the editor shows the still-valid child's stock at its NEW value — the save for that row was not discarded just because the other row was stale.",
+        endResult: "BEFORE this endpoint existed, there was no shared editor and so no partial-failure case to handle. AFTER: a stale row (the common case when two admins or two tabs edit the same group near-simultaneously) costs nothing to the rows that were still valid.",
+    },
+};

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.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-tracer.js

@@ -0,0 +1,284 @@
+/*
+ * WHY: Authored six-part procedures for the sticker-sheet kiss-cut tracer.
+ * WHAT: 16 case(s), keyed by full checklist id.
+ *
+ * 🛑 EVERY CASE IS AN EXPLICIT BEFORE → AFTER, because almost every defect this
+ * feature can have returns HTTP 200 with plausible content. A case reading
+ * "check the tracer works" would pass against the bug. The first three restate
+ * the two failures that caused this feature to be built, as assertions.
+ *
+ * 🛑 THE FIXTURE IS /test-media/sticker-sheet-fixture.jpg AND ITS SIZE IS
+ * LOAD-BEARING. It is the real 5024x3024 scan, and shrinking it was measured
+ * and rejected: a 145 KB WebP traces into 237 fragments where the original
+ * gives 15 (public/test-media/README.md carries the table). A case asserting a
+ * part count against a shrunken fixture would fail for a reason that is not a
+ * bug. Do not "optimise" it.
+ *
+ * 🛑 PART COUNTS ARE DELIBERATELY NOT ASSERTED AS EXACT NUMBERS. The probe
+ * measured 15 at draft tier on this machine, but the count moves with tier and
+ * with any tuning of the ridge thresholds — so the cases assert RELATIONS
+ * ("more than one", "the same count twice", "fewer after raising the minimum")
+ * which stay true across tuning. An exact number here would be a case that
+ * fails every time somebody improves the detector.
+ *
+ * 🛑 The tracer is ADMIN-ONLY and /tools/sticker-tracer is server-gated, so the
+ * buyer and guest cases assert the redirect rather than a hidden control.
+ *
+ * @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!.";
+const FIXTURE = "/test-media/sticker-sheet-fixture.jpg";
+export const authored = {
+    /* ---- the two reported failures, restated as assertions ---------------- */
+    "checklist-tools-sticker-tracer-enclosed-region-opaque": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            `Download ${FIXTURE} and choose it with "Choose a scan".`,
+            "Wait for the outlines to draw over the preview.",
+            "Find a sticker that contains an enclosed area the same colour as the paper around the sheet — on the Driger G sheet the lighter interior panels.",
+            "Zoom the browser to 200% and look at whether that interior area is covered by the outline or cut out of it.",
+        ],
+        expectedBehaviour: "Opacity is decided by REACHABILITY from the sheet border, not by colour. The flood fills inward from the edge and a sticker is whatever the flood could not reach — so an enclosed region is inside the outline no matter what colour it is.",
+        expectedUiState: "The magenta outline runs around the sticker's silhouette only. It does not loop around interior light-coloured areas, and no interior region is excluded from the shape.",
+        endResult: "BEFORE: the prior Python attempt thresholded colour, so a region matching the background was made transparent even inside a sticker. AFTER: interior regions stay part of the sticker. Nothing is persisted — this is the in-browser tuner.",
+    },
+    "checklist-tools-sticker-tracer-white-on-white-edge": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            `Choose ${FIXTURE}.`,
+            "Find the winder sticker — the one whose top edge is near-white against the near-white paper.",
+            "Zoom to 200% and check whether that top edge carries an outline.",
+            "Read the Result card's part count.",
+        ],
+        expectedBehaviour: "The cut line is found from the EMBOSS RIDGE, which the plan measured at 10-20x above noise precisely where colour carries none. No per-sticker parameter is involved.",
+        expectedUiState: "The white top edge has a magenta outline following it. The Result card shows more than one part.",
+        endResult: "BEFORE: a colour threshold ate that edge, and the old script needed a hand-authored --cap flag naming one sticker's coordinates on one sheet. AFTER: it is found with the default parameters and no per-sticker tuning.",
+    },
+    "checklist-tools-sticker-tracer-background-model-named": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            `Choose ${FIXTURE}.`,
+            "Read the line under the Result heading that begins 'background:'.",
+            "Change 'Paper tolerance' from its default to 60 and watch the part count.",
+            "Set it back to its default.",
+        ],
+        expectedBehaviour: "The tool states which of the two segmentation models ran. Paper floods inward from the sheet edge; art partitions on cut lines because there is no background to flood. Paper tolerance only affects the paper model, which is why knowing which ran is the difference between a parameter that does nothing and one that is simply set wrong.",
+        expectedUiState: "The Result card reads 'background: paper' for this scan. Changing Paper tolerance changes the part count.",
+        endResult: "BEFORE: there was no way to tell which model ran, so an operator adjusting paper tolerance on an art sheet saw no effect and no explanation. AFTER: the model is named on screen.",
+    },
+    /* ---- the mandatory name ---------------------------------------------- */
+    "checklist-tools-sticker-tracer-name-required": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            `Choose ${FIXTURE} and scroll to "Commit this as a run".`,
+            "Leave 'Name this sheet' EMPTY and try to press 'Upload and run'.",
+            "Type a single space into the name and try again.",
+            "Type 'QA tracer run 1' and press 'Upload and run'.",
+        ],
+        inputs: { name: "QA tracer run 1" },
+        expectedBehaviour: "A name is mandatory and is enforced in three places — the disabled button, the route's schema, and requireName in the action. No sheet document and no Storage object is created while the name is empty.",
+        expectedUiState: "'Upload and run' is disabled with the name empty and with a single space. It enables once real text is entered, then reads 'Uploading and starting…'.",
+        expectedData: { sheetsCreatedWhileNameEmpty: 0 },
+        endResult: "BEFORE: nothing stopped an unnamed attempt, and the whole point of keeping every run is being able to tell them apart later. AFTER: a run cannot exist without a name. The named run persists and appears under Attempts after a reload.",
+    },
+    /* ---- watermark + originals ------------------------------------------- */
+    "checklist-tools-sticker-tracer-no-watermark-on-original": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Open a sheet whose run has finished and been accepted.",
+            "In Attempts, press 'Preview' on the accepted run — it opens a new tab.",
+            "Look at the opened image for a watermark, and copy its URL.",
+            "Check the URL's host: it should be a storage.googleapis.com signed link, NOT a /media/ path on this site.",
+        ],
+        expectedBehaviour: "Tracer artifacts live under private/sticker-sheets/ and are served by 5-minute signed GCS URLs, which bypass /api/media/[...slug] — the proxy that always watermarks. The printable original must stay clean or the cut-out is ruined.",
+        expectedUiState: "The opened image carries NO watermark. Its URL is on storage.googleapis.com with query parameters, not /media/<slug>.",
+        endResult: "BEFORE: every image through the media proxy was watermarked, which would ruin a cut-out and the printed mosaic. AFTER: originals are unwatermarked and reachable only through a short-lived signed link.",
+    },
+    /* ---- live progress ---------------------------------------------------- */
+    "checklist-tools-sticker-tracer-progress-names-stage": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            `Choose ${FIXTURE}, name the run 'QA progress', pick tier Standard and press 'Upload and run'.`,
+            "Watch the card titled 'Running' without reloading.",
+            "Write down two different stage names you see.",
+        ],
+        expectedBehaviour: "Progress is pushed over the run's own RTDB channel, not polled. The label names the STAGE because that is what distinguishes a halftone scan stuck in the detector from one stuck in the upload.",
+        expectedUiState: "A 'Running' card shows text like 'ridge 22%' or 'parts 4/15' and ADVANCES. It is never a bare spinner and never only a percentage.",
+        endResult: "BEFORE: a trace took minutes with nothing to look at. AFTER: the current stage is visible throughout. The card disappears when the run ends; the outcome persists in Attempts.",
+    },
+    "checklist-tools-sticker-tracer-failure-names-stage": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Find a sheet with a FAILED run in Attempts. If none exists, create one: commit a run with 'Minimum part area' set to 100000, which leaves nothing above the threshold.",
+            "Read the failed row.",
+            "Reload the page and read it again.",
+        ],
+        inputs: { minPartAreaMm2: 100000 },
+        expectedBehaviour: "A failure records the stage it died in and a user-safe message, and the row survives. The requirement was 'even if we fail we know'.",
+        expectedUiState: "The row shows a red 'failed' badge and a line beginning 'Failed at <stage>' with a readable message — never 'Something went wrong', and never a raw server error or a stack trace.",
+        endResult: "BEFORE: a failed trace was indistinguishable from a hang. AFTER: the stage is named and the failed attempt stays in history after a reload.",
+    },
+    /* ---- history ---------------------------------------------------------- */
+    "checklist-tools-sticker-tracer-runs-never-overwrite": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            `Choose ${FIXTURE}, name the run 'QA attempt A', tier Standard, and commit it.`,
+            "Wait for it to finish.",
+            "Commit a SECOND run on the same sheet named 'QA attempt B' at tier Precise.",
+            "Reload the page and read the Attempts list.",
+        ],
+        inputs: { runA: "QA attempt A", runB: "QA attempt B" },
+        expectedBehaviour: "A retry or a second run creates a NEW run document. Nothing overwrites an earlier attempt, which is what makes comparing tiers on one sheet possible weeks later.",
+        expectedUiState: "Both 'QA attempt A' and 'QA attempt B' appear, newest first, each with its own tier label and its own part count. Both are still openable.",
+        endResult: "BEFORE: there was nothing listing runs at all — the documents existed with no reader. AFTER: every attempt is listed by the name that was typed, and both survive a reload.",
+    },
+    "checklist-tools-sticker-tracer-accepted-differs-from-succeeded": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "On a sheet with two successful runs, read the badges on both rows.",
+            "Press 'Accept & render' on the one that is not currently accepted.",
+            "Reload and read both rows again.",
+        ],
+        expectedBehaviour: "'succeeded' and 'accepted' are different facts: a run can succeed without being the sheet's current result, which is normal once three tiers have been tried. Accepting one moves the badge and starts the full-resolution render.",
+        expectedUiState: "Both rows show a green 'succeeded' badge; exactly ONE shows 'accepted'. After accepting the other, exactly one still shows 'accepted' and it is the one just pressed.",
+        expectedData: { acceptedRunsPerSheet: 1 },
+        endResult: "BEFORE: isPromoted and activeRunId were read by the UI and written by nothing — promoteRun had zero callers. AFTER: accepting a run is a real action and the badge reflects it after a reload.",
+    },
+    /* ---- promote gates full-res ------------------------------------------- */
+    "checklist-tools-sticker-tracer-fullres-only-after-accept": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Commit a fresh run and wait for it to succeed WITHOUT accepting it.",
+            "Look for a 'Print & export' card on the page.",
+            "Press 'Accept & render' on that run.",
+            "Wait for the render, reload, and look again.",
+        ],
+        expectedBehaviour: "Full-resolution parts and the export surface exist only for an ACCEPTED run. An exploratory run costs about 1 MB; rendering full-res parts on every attempt costs roughly 500 MB a sheet — the difference between about 52 sheets inside 5 GB and about 8.",
+        expectedUiState: "No 'Print & export' card before accepting. After accepting it appears, with a machine and page picker.",
+        endResult: "BEFORE: nothing rendered full-resolution parts at all — the mode:\"full\" path had no caller. AFTER: they are rendered once, for the run actually chosen, and the export surface follows.",
+    },
+    /* ---- DPI honesty ------------------------------------------------------ */
+    "checklist-tools-sticker-tracer-no-dpi-no-mm": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Open an accepted sheet whose scan declares no usable DPI — upload a screenshot or a web-saved image if none exists, since those declare 72 or 96.",
+            "Open 'Print & export' and read what it says.",
+            "Try to press 'Download cut file'.",
+        ],
+        expectedBehaviour: "Millimetres are WITHHELD when the DPI cannot be trusted. A cut file must be millimetre-true, so the export refuses rather than inventing a scale — a fabricated millimetre on a cut file is a physical production error, not a cosmetic one.",
+        expectedUiState: "A warning reading that the scan has no confirmed DPI and that confirming it makes the export available. The download buttons are DISABLED. No plausible-looking millimetre figure appears anywhere.",
+        endResult: "BEFORE: nothing distinguished a real DPI from the 72 that five of nine reference scans falsely declare. AFTER: the tool says so and refuses, naming the fix.",
+    },
+    /* ---- export refusals before download ---------------------------------- */
+    "checklist-tools-sticker-tracer-oversized-named-not-scaled": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Open an accepted sheet with a confirmed DPI and scroll to 'Print & export'.",
+            "Set Machine to 'Cricut Joy 2 — Print Then Cut' and Page to A4.",
+            "Read the warning block listing parts.",
+            "Switch Machine to 'Print shop (Roland / Graphtec)' and read the same area again.",
+        ],
+        expectedBehaviour: "A part wider than the machine's cut area is NAMED before export, never scaled. The Joy 2's A4 Print-Then-Cut area is a column about 78 mm wide, and several stickers on a typical sheet exceed it. Scaling would produce a cut file that looks correct and yields stickers the wrong physical size.",
+        expectedUiState: "Under the Cricut PTC profile, a warning lists parts BY NAME with their measured width and a reason mentioning the cut width. Under the print-shop profile that warning is gone, because it has no width limit.",
+        endResult: "BEFORE: there was no way to learn a part was too wide except by cutting it. AFTER: the refusal is on screen before the download, and the print-shop profile is offered as the alternative.",
+    },
+    "checklist-tools-sticker-tracer-node-budget-reported": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "In 'Print & export', set Machine to a Cricut profile and read the badges under the pickers.",
+            "Switch to 'Print shop' and read them again.",
+        ],
+        expectedBehaviour: "Export simplification is a SEPARATE budget from the trace's. A Cricut profile re-simplifies to its node ceiling and reports the resulting deviation in millimetres; the print-shop profile has no ceiling and so does not simplify.",
+        expectedUiState: "A node-count badge is shown. Under a Cricut profile, when simplification occurred, a line reads 'Simplified from N nodes…' and states a worst-case deviation in mm. Under the print shop no deviation is claimed.",
+        endResult: "BEFORE: a max-tier trace could silently produce a file Design Space cannot open. AFTER: the node count and the cost of fitting it are both on screen before export.",
+    },
+    /* ---- retry clamp ------------------------------------------------------ */
+    "checklist-tools-sticker-tracer-retry-shows-clamp": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "In Attempts, press 'Retry from this' on any finished run.",
+            "In the retry form, open 'Where it restarts' and set 'Resume from' to 'parts'.",
+            "Change Tier to a different one — this changes ridge parameters, which belong to an earlier stage.",
+            "Read the message that appears in that section before submitting.",
+        ],
+        expectedBehaviour: "The resume point is clamped forward to the earliest stage whose parameters changed, and the clamp is SHOWN. Without it, a run resumed from 'parts' would carry artifacts generated under different parameters than the run records, with nothing anywhere contradicting it.",
+        expectedUiState: "A warning reading that a parameter from an earlier stage changed, so the run restarts from that stage rather than resuming from 'parts'. It names both stages.",
+        endResult: "BEFORE: explainResume() returned that sentence and nothing rendered it. AFTER: the operator sees the clamp before submitting, and the server applies the same decision.",
+    },
+    /* ---- access control ---------------------------------------------------- */
+    "checklist-tools-sticker-tracer-buyer-redirected": {
+        roles: ["buyer"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            "Sign in as a normal buyer account (not admin).",
+            "Navigate directly to /tools/sticker-tracer by typing the URL.",
+            "Open the Tools entry in the main navigation and read its children.",
+            "Visit /tools and read the 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": {
+        roles: ["guest"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            "Sign out completely, or use a private window.",
+            "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 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": {
+        roles: ["admin"],
+        startPage: "/tools/sticker-tracer",
+        steps: [
+            ADMIN_SIGNIN,
+            "Call GET /api/admin/sticker-sheets/usage in the browser address bar.",
+            "Read the per-sheet rows: each carries bytes AND an object count.",
+            "Compare the biggest sheet's byte figure against the number of runs it has.",
+            "Check whether the response carries a 'truncated' field and what it says.",
+        ],
+        expectedBehaviour: "The meter reports object COUNT beside bytes, because GCS meters them separately — which is the entire reason review thumbnails are one sprite atlas rather than sixty files. It measures at most 25 sheets per call and says when it truncated.",
+        expectedUiState: "JSON with rows sorted biggest-first, each having bytes and objects, plus totalBytes, totalObjects, measured and truncated.",
+        expectedData: { truncatedReportedExplicitly: true },
+        endResult: "BEFORE: storage cost was discoverable only in the GCP console, which is how the project was paused once before. AFTER: it is a route an operator can read, and a partial measurement says it is partial rather than understating the total.",
+    },
+};