@mohasinac/appkit 4.58.0 → 4.59.0

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

@@ -1,144 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/bundles page.
- * WHAT: 4 case(s), keyed by full checklist id.
- *
- * 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
- * scaffolding around work that is simply writing.
- *
- * 🛑 A BUNDLE IS A CATEGORY ROW, not a listing type, and its member list is
- * MIRRORED onto the bundle for index-friendly reads. Every public reader consults
- * that mirror, so a write path that updates the rule and forgets the mirror
- * produces a bundle that renders as "0 items" with no error anywhere.
- *
- * 🛑 THREE MEMBERS MINIMUM, AND EVERY CASE HERE ASKED FOR TWO (fixed 2026-09-29).
- *
- * BUNDLE_MIN_ITEMS is 3 (bundle-config.ts:10) and bundle-form.ts's superRefine
- * enforces it with "Select at least 3 products (currently 2)." So the create
- * case could never save, and the two cases that READ that bundle were testing
- * something which had never been created — three verdicts of "could not test"
- * for a rule the editor states on its own field label.
- *
- * Every member is now a real seeded id with its real price, so the undiscounted
- * total is arithmetic a tester can check rather than a number to trust.
- *
- * 🛑 EVERY STANDARD LISTING IN THE CATALOGUE BELONGS TO store-beyblade-arena.
- * The only other seller with stock is store-letitrip-official, whose six
- * listings are all prize draws — so the cross-store refusal is exercised with
- * one of those. The guard reads storeId and does not care about listing type.
- * (CLAUDE.md claims product-tester-crossstore-a/b are seeded for exactly this;
- * they are not, anywhere — recorded in OUTOFSCOPE.)
- *
- * 🛑 THE SLUG IS DERIVED AND THEREFORE KNOWABLE: the route slugifies the name
- * and prefixes "bundle-", so 'QA Bundle admin-create' is always
- * /bundles/bundle-qa-bundle-admin-create. The cases used to say "/bundles/{slug}"
- * without saying how to learn it.
- *
- * audit-tester-created-id: bundle-qa-bundle-admin-create — created by case 1 step 2
- * and visited by cases 1-3. It is not a seed fixture and must not be one: the point
- * is to exercise the CREATE path, and a pre-seeded bundle would skip it.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-admin-bundles-bundle-create": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/bundles",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/bundles/new and set Name to 'QA Bundle admin-create'.",
-            "Leave the member-source select on its static option, add exactly TWO members — product-beyblade-burst-valkyrie and product-beyblade-x-wizard-arrow — set 'Bundle price (₹)' to 1500, and try to save.",
-            "Read the refusal: the minimum is three, and the field label states the range.",
-            "Add product-beyblade-x-knife-shinobi (₹949) as the third member and save.",
-            "RELOAD the editor and read the members, the price and the original total.",
-            "Open /bundles/bundle-qa-bundle-admin-create — the slug is the name slugified under a 'bundle-' prefix — and read the members, price and discount badge.",
-            "Back in the editor add prizedraw-beyblade-mystery-box, which belongs to store-letitrip-official, as a fourth member, save, and read what happens.",
-            "Remove that fourth member and save, leaving the bundle at its three arena members.",
-        ],
-        inputs: {
-            name: "QA Bundle admin-create",
-            member1: "product-beyblade-burst-valkyrie",
-            member2: "product-beyblade-x-wizard-arrow",
-            member3: "product-beyblade-x-knife-shinobi",
-            crossStoreMember: "prizedraw-beyblade-mystery-box",
-            bundlePrice: 1500,
-            memberTotal: 2847,
-        },
-        expectedBehaviour: "A bundle holds at least three members, stores its locked price, and derives the members' undiscounted total SERVER-SIDE — the editor never sends that total, and it is what drives the discount badge, so a bundle without it shows a price and no saving. Members must come from one store: the store id is the order-splitting and payout key, so a cross-store bundle would produce an order belonging to one seller while holding another seller's products.",
-        expectedUiState: "The two-member save is refused inline with 'Select at least 3 products (currently 2).' — not a silent no-op and not a generic banner. With the third added, the reload lists all three, a bundle price of ₹1,500 against an original total of ₹2,847, and the public page shows the three members with a discount badge of roughly 47% off. The cross-store save is refused with a message naming how many sellers the members span, not a 500.",
-        expectedData: { memberCount: 3, bundlePrice: 1500, bundleOriginalTotal: 2847 },
-        endResult: "The bundle survives with its three arena members — the next two cases read it. The cross-store member is NOT part of it.",
-    },
-    "checklist-admin-bundles-bundle-stock-sync": {
-        roles: ["admin", "seller", "guest"],
-        startPage: "/admin/bundles",
-        steps: [
-            "Open /bundles/bundle-qa-bundle-admin-create signed out and note that it offers purchase.",
-            "Sign in as tyson@beybladearena.in / TempPass123!, open /store/products, edit product-beyblade-x-wizard-arrow, and set its stock quantity from 12 to 0.",
-            "Reload /bundles/bundle-qa-bundle-admin-create and read its availability.",
-            "Sign in as admin@letitrip.in / TempPass123!, open /admin/bundles and read the bundle's row.",
-            "Sign back in as tyson@beybladearena.in and set that product's stock back to 12.",
-            "Reload /bundles/bundle-qa-bundle-admin-create and read its availability again.",
-        ],
-        inputs: { member: "product-beyblade-x-wizard-arrow", stockBefore: 12, stockDuring: 0 },
-        expectedBehaviour: "A bundle is all-or-nothing, so one member going out of stock makes the whole bundle unavailable. That is kept in sync by a hook on the member's stock change rather than computed per request — which is what makes the reverse direction worth testing too: restoring the stock must restore the bundle.",
-        expectedUiState: "With the member at zero the bundle reads as unavailable and offers no purchase control. After the stock is restored it becomes purchasable again. A bundle still offering purchase with a zero-stock member is the failure; so is one that stays unavailable after the stock returns.",
-        expectedData: { stockAfterRestore: 12 },
-        endResult: "The member's stock is back at 12 and the bundle is purchasable. Both directions matter — a sync that only ever disables is half a sync, and leaving the stock at zero silently breaks the next case.",
-    },
-    "checklist-admin-bundles-bundle-edit-delete": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/bundles",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/bundles, open 'QA Bundle admin-create' for editing, and write down every field — name, description, price, the three members, cover image, brand and active.",
-            "Change ONLY 'Bundle price (₹)' to 1400 and save.",
-            "RELOAD the editor and compare every field against what was written down.",
-            "SWAP one member rather than dropping one: remove product-beyblade-x-knife-shinobi (₹949), add product-beyblade-burst-regalia-genesis (₹1,399), keeping three. Save, RELOAD, and read the member list and the original total.",
-            "Open /bundles/bundle-qa-bundle-admin-create and read the members and the discount badge.",
-            "Back in the editor click the delete control, confirm, and check the bundle is gone from /admin/bundles and from /bundles.",
-        ],
-        inputs: {
-            priceBefore: 1500,
-            priceAfter: 1400,
-            memberRemoved: "product-beyblade-x-knife-shinobi",
-            memberAdded: "product-beyblade-burst-regalia-genesis",
-            totalBefore: 2847,
-            totalAfter: 3297,
-        },
-        expectedBehaviour: "An edit writes back only what changed, and changing the member list recomputes the undiscounted total server-side — a stale total makes the discount badge claim a saving that no longer exists. A SWAP rather than a bare removal is what makes this readable: the count stays at the legal minimum of three while the total must move, so a total that did not change cannot be excused as the member rule having been left alone.",
-        expectedUiState: "After the price edit only the price differs — every other field matches what was written down. After the swap the list holds three members and the original total reads ₹3,297 rather than ₹2,847, so the badge's saving shrinks. After the delete the bundle is absent from /admin/bundles and /bundles, and its own URL no longer renders it.",
-        expectedData: { memberCountAfterSwap: 3, bundleOriginalTotalAfterSwap: 3297 },
-        endResult: "The bundle is deleted. A public page still rendering a deleted bundle is a cache or projection failure worth naming.",
-    },
-    "checklist-admin-bundles-bundle-brand-picker": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/bundles",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/bundles/new, set Name to 'QA Bundle brand-picker', and add THREE members from Beyblade Arena — product-beyblade-burst-valkyrie, product-beyblade-x-wizard-arrow and product-beyblade-x-knife-shinobi. Fewer than three is refused.",
-            "Set 'Bundle price (₹)' to 2000.",
-            "Find the 'Brand' select and read what it offers.",
-            "Select Beyblade and save.",
-            "RELOAD the editor and read the brand.",
-            "Open /brands/brand-beyblade signed out and find the bundle in its Bundles tab.",
-            "Back in the editor set Brand to 'No specific brand', save, reload the brand page, and check the bundle has left that tab.",
-            "Delete the bundle.",
-        ],
-        inputs: {
-            name: "QA Bundle brand-picker",
-            brand: "Beyblade",
-            clearedTo: "No specific brand",
-            bundlePrice: 2000,
-        },
-        expectedBehaviour: "A bundle's own brand tag is a DIFFERENT field from any brand filter inside a dynamic member rule — the tag says which brand the bundle belongs to regardless of how its members were resolved, and it is what the brand page's Bundles tab filters on. Not every bundle needs one; a genuinely cross-brand bundle leaves it unset.",
-        expectedUiState: "The select offers the real seeded brands plus a 'No specific brand' option — not a free-text box and not an empty list. With Beyblade set the bundle appears in that brand's Bundles tab; with it cleared it leaves. Worth watching: two of the three members are tagged Takara-Tomy rather than Beyblade, so a bundle still appearing under Beyblade after the tag is cleared means the tab is filtering on the MEMBERS instead of the tag.",
-        expectedData: { brandAfterReload: "Beyblade" },
-        endResult: "The bundle is deleted by the final step, so /brands/brand-beyblade's Bundles tab holds only the seeded bundles again.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__buyer-data-admin.d.ts

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

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

@@ -1,265 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/buyer-data-admin page.
- * WHAT: 12 case(s), keyed by full checklist id.
- *
- * 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
- * scaffolding around work that is simply writing.
- *
- * 🛑 THIS PAGE IS BUYER DATA, so two questions run through every case: can the
- * admin READ a row before acting on it, and is more PII exposed than the task
- * needs. Several of these listings were dead ends — a row you could see and never
- * open — and two of them are dead ends for a legitimate reason: their list query
- * returns a per-user summary only, so the honest fix was to route to the owning
- * user rather than widen the payload.
- *
- * 🛑 /admin/addresses IS AN OWNER-SCOPED LOOKUP, NOT A LISTING (fixed 2026-09-29).
- *
- * It renders `AdminAddressBookView`: an 'Owner type' select (user | store), an
- * 'Owner ID' text field placeholdered `user-...` / `store-...`, and a Search
- * button. There are no columns, no sort dropdown, no filter drawer and no
- * free-text search of addresses — and nothing at all is shown until an owner id
- * is searched. Three cases here described a listing with owner-type filters and
- * a sort default; none of that exists on this page.
- *
- * The banned-address queue those descriptions actually fit is a DIFFERENT
- * route, `ROUTES.ADMIN.BANNED_ADDRESSES` ("Banned Addresses"), backed by
- * `AdminAddressesView` — similar name, different page. Worth stating because
- * reading the plausibly-named component instead of following the route is how
- * this was nearly mis-audited.
- *
- * Its editor DOES exist, at /admin/addresses/new and /admin/addresses/[id]/edit,
- * and per its own header the postal code is now validated per country by schema
- * rather than by `length === 6` — so 'abcdef' should be REJECTED, and the CRUD
- * case expects a pass.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-admin-buyer-data-admin-carts-admin-view": {
-        roles: ["admin"],
-        startPage: "/admin/carts",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/carts and read every column.",
-            "Check each row identifies whose cart it is and how many items it holds.",
-            "Read whether guest carts are distinguishable from signed-in ones.",
-            "Use every filter and sort offered, confirming each changes the rows.",
-            "Search zzzznope and read the count.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "The list identifies each cart and its size. A cart document is keyed on the user id for signed-in buyers and on a session id for guests, so both kinds appear and the row has to say which it is — an unattributed row is a cart nobody can act on.",
-        expectedUiState: "Rows show an owner and an item count. Guest carts are marked as such rather than showing a blank owner. Filters and sorts change the rows and 'zzzznope' returns none.",
-        expectedData: { nonsenseResultCount: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-buyer-data-admin-carts-admin-row-opens-items": {
-        roles: ["admin"],
-        startPage: "/admin/carts",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/carts and find a row whose item count is greater than one.",
-            "Click the row and read what opens — it should be a 'Cart Details' modal.",
-            "Read its badge: a guest cart reads 'Guest' and a signed-in one reads 'Authenticated'.",
-            "Read its fields — Session or User, Last updated, Cart ID.",
-            "Read the 'Items in cart' section and check each item carries a title, a quantity and a price.",
-            "Close and open a different row the same way.",
-        ],
-        inputs: { modalTitle: "Cart Details", itemsHeading: "Items in cart" },
-        expectedBehaviour: "A row opens to show the cart's items. The list already computes the item count from the items array and then discards it, so the data needed to render the detail is present at list time — this is a UI wiring gap rather than a missing query, and the fix is a detail view rather than a wider payload.",
-        expectedUiState: "Clicking a row opens the 'Cart Details' modal showing each item with its title, quantity and price under 'Items in cart'. A row that does nothing on click, or opens a modal whose items section is empty for a cart the list counted as non-empty, is the dead-end failure this page family exists to close.",
-        endResult: "Read-only; close without acting.",
-    },
-    "checklist-admin-buyer-data-admin-wishlists-admin-view": {
-        roles: ["admin"],
-        startPage: "/admin/wishlists",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/wishlists and read every column.",
-            "Check each row names the owning user and the number of items.",
-            "Read whether the item titles themselves are shown in the list.",
-            "Use every filter and sort offered.",
-            "Search zzzznope and read the count.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "One wishlist exists per user, so the list is one row per owner with a count. The list query deliberately returns a per-user SUMMARY rather than every item — widening it to carry each wishlist's contents would load unbounded data on a page that only needs counts.",
-        expectedUiState: "Rows name the owner and the item count. Item titles are not expected in the list itself. Filters change the rows and 'zzzznope' returns none.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-buyer-data-admin-wishlists-history-admin-row-opens-user": {
-        roles: ["admin"],
-        startPage: "/admin/wishlists",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/wishlists and click a row.",
-            "Read the URL it lands on — it should be that row's owner under /admin/users/{userId}, not a wishlist detail.",
-            "Go back, open /admin/history, and click a row there.",
-            "Read the URL that lands on.",
-            "From the user page reached, check the wishlist or history is readable in context.",
-        ],
-        inputs: { expectedDestination: "/admin/users/{userId}" },
-        expectedBehaviour: "These two rows route to the owning user rather than to a per-record detail, and that is the correct answer rather than a shortcut: their list queries return only a per-user summary, so a detail view would have to fetch separately, and the user page is where the rest of that person's data already is.",
-        expectedUiState: "Both rows navigate to /admin/users/{userId} for that row's owner. Neither is inert. From there the wishlist or history contents are reachable. A row that does nothing at all is the failure; a row routing to the user is a pass. A row whose owner id is missing, so the click does nothing, is also a failure — the navigation is guarded on it.",
-        endResult: "Read-only; close without acting.",
-    },
-    "checklist-admin-buyer-data-admin-history-admin-view": {
-        roles: ["admin"],
-        startPage: "/admin/history",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/history and read every column.",
-            "Check each row names the owning user and the number of entries.",
-            "Read the highest entry count in the list.",
-            "Use every filter and sort offered.",
-            "Search zzzznope and read the count.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope", historyCap: 50 },
-        expectedBehaviour: "History is one document per user, capped at fifty entries with the oldest silently evicted. So no row should report more than fifty — a higher count means the cap is not being applied on write and the document grows without bound.",
-        expectedUiState: "Rows name the owner and an entry count, and no count exceeds fifty. Filters change the rows and 'zzzznope' returns none.",
-        expectedData: { maxEntryCount: 50 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-buyer-data-admin-notifications-admin-view": {
-        roles: ["admin"],
-        startPage: "/admin/notifications",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/notifications and read every column.",
-            "Read every type filter offered and select each, noting any that returns nothing.",
-            "For each empty filter, check the unfiltered list for rows of that type.",
-            "Open a row menu's 'View details' action and read the full body and payload in the modal it opens.",
-            "Read whether the recipient is identified.",
-            "Search zzzznope and read the count.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "Every type chip names a value notifications actually carry, and the union has THIRTY values today. The type union is a single runtime list, and for a long time the filters were built from a nine-value copy — most types were unfilterable and two could not be allow-listed for any channel at all. Count the chips against thirty rather than against the seeded data, which covers only ten of them.",
-        expectedUiState: "Every type filter returns its own rows or is empty with none unfiltered either. A row opens to show the full body and payload rather than only the title. 'zzzznope' returns none. A chip MISSING for a real type is as much a finding as a chip that matches nothing — record the count you saw.",
-        expectedData: { nonsenseResultCount: 0, typeChipCount: 30 },
-        endResult: "Read-only. A chip empty while matching rows sit unfiltered is the finding, named by type.",
-    },
-    "checklist-admin-buyer-data-admin-reviews-admin-view": {
-        roles: ["admin"],
-        startPage: "/admin/reviews",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/reviews and read every column, including any review images. Roughly 15-20% of the 79 seeded reviews carry one.",
-            "Check each image tile renders rather than showing a placeholder icon.",
-            "Read the search box's placeholder for how it matches.",
-            "Type a reviewer's FULL name and read the results.",
-            "Type only the first half and read the results.",
-            "Search zzzznope and read the count.",
-            "Open a review and read its full body, rating and any seller response.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "Reviewer names are PII-encrypted at rest, so they match exactly through a blind index and a partial cannot match — by design rather than omission, which is why the box must SAY so. Review images are stored as plain URL strings; a renderer expecting objects reads undefined off each and falls back to a placeholder, which makes every review photo vanish at once.",
-        expectedUiState: "Image tiles render real photos rather than placeholder icons. The full name returns rows, the partial returns none, and the box states that matching is exact. 'zzzznope' returns none.",
-        expectedData: { partialMatchCount: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-buyer-data-admin-store-addresses-admin": {
-        roles: ["admin"],
-        startPage: "/admin/addresses",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/addresses and read what the page offers before any input — an 'Owner type' select, an 'Owner ID' field and a Search button.",
-            "Read whether anything is listed before a search is run.",
-            "Leave Owner type on 'user', enter user-admin-letitrip, and click Search.",
-            "Read every field shown for each address returned, and record exactly how much of the name and phone number is displayed.",
-            "Switch Owner type to 'store', enter store-beyblade-arena, and Search.",
-            "Enter zzzznope as the Owner ID and Search.",
-        ],
-        inputs: {
-            userOwner: "user-admin-letitrip",
-            storeOwner: "store-beyblade-arena",
-            nonsenseOwner: "zzzznope",
-        },
-        expectedBehaviour: "Both buyer delivery and store pickup addresses live in one collection discriminated by owner type, and this page reaches them one OWNER at a time rather than as a browsable list — which is why the owner type is an input rather than a filter. Names, phones and street lines are PII-encrypted at rest, so how much this page decrypts and displays is worth recording rather than assuming.",
-        expectedUiState: "Before a search the page lists nothing, which is correct here rather than an empty-state bug. A searched owner returns their addresses; a nonsense owner id returns 'No addresses found for this owner.' rather than an error or the full collection. Record exactly how much of each name and phone is shown.\n\nNote what this page is NOT: there are no columns, no sort dropdown, no filter drawer and no free-text address search. A case expecting those is describing the Banned Addresses queue, which is a different route.",
-        expectedData: { listedBeforeSearch: 0, nonsenseOwnerResultCount: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-buyer-data-admin-store-addresses-admin-row-opens-detail": {
-        roles: ["admin"],
-        startPage: "/admin/addresses",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/addresses, search Owner type 'store' with store-beyblade-arena, and read the card rendered for each address.",
-            "Record which fields the card shows — label, full name, street, city, state, postal code, phone — and specifically whether the LANDMARK appears.",
-            "Check whether the card is openable at all: a link, a click target or an edit affordance leading to /admin/addresses/{id}/edit.",
-            "Search Owner type 'user' with user-admin-letitrip and read the same for a buyer-owned address.",
-            "Open /admin/addresses/{one of those ids}/edit directly and compare the fields there against what the card showed.",
-        ],
-        inputs: { storeOwner: "store-beyblade-arena", userOwner: "user-admin-letitrip" },
-        expectedBehaviour: "An admin can read every stored field of an address, for both owner types. The landmark is the field worth naming: a form that cannot express it sends undefined and overwrites, so a surface that never shows it hides whether the value survived.",
-        expectedUiState: "Both owner types render cards carrying the stored fields. The editor at /admin/addresses/{id}/edit shows every field including the landmark. Record any field the editor has and the card does not — a card that omits the landmark while the editor can write it is the gap this case is for.",
-        endResult: "Read-only; close the editor without saving.",
-    },
-    "checklist-admin-buyer-data-admin-addresses-crud-admin": {
-        roles: ["admin"],
-        startPage: "/admin/addresses",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/addresses/new and create one for Owner type 'user', Owner ID user-admin-letitrip: label 'QA Address admin-crud', '13 Test Lane', Indore, Madhya Pradesh, 452010, landmark 'Beside the arena'.",
-            "Save, then find it again via /admin/addresses searching that owner, open /admin/addresses/{its id}/edit, and read every field including the landmark.",
-            "Edit ONLY the street to '14 Test Lane', save, REOPEN the editor, and read every field again.",
-            "Type abcdef into the postal code field and attempt to save.",
-            "Read where the error appears — on the field, or as a banner, or not at all.",
-            "Restore the postal code, then delete the address and search that owner again to confirm it is gone.",
-        ],
-        inputs: {
-            name: "QA Address admin-crud",
-            streetBefore: "13 Test Lane",
-            streetAfter: "14 Test Lane",
-            landmark: "Beside the arena",
-            badPostcode: "abcdef",
-        },
-        expectedBehaviour: "Create, edit and delete persist and an edit to one field leaves the rest alone. The postal code is validated by FORMAT rather than by length: a length-only rule accepts 'abcdef' as a valid six-character Indian PIN code, and one admin route did exactly that.",
-        expectedUiState: "After each reopen every value holds, including the landmark after the street edit — a landmark that vanishes when only the street changed is the overwrite this case is for. 'abcdef' is rejected ON THE POSTAL CODE FIELD before any request is sent, not returned as a server error with nothing marked. This half is expected to PASS: the form validates per country by schema now, where it once checked only that the value was six characters long — which 'abcdef' satisfies.",
-        endResult: "The address is deleted by the final step.",
-    },
-    "checklist-admin-buyer-data-admin-stores-admin-view": {
-        roles: ["admin"],
-        startPage: "/admin/stores",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/stores and read every column and status chip.",
-            "Select each status chip in turn and read the rows returned — the seed carries store-blader-bazaar as pending and store-vintage-vault-co as suspended, so neither chip should be empty.",
-            "Open store-letitrip-official — verified and featured — for editing and write down its verified flag, its featured flag, its capabilities and its admin notes.",
-            "Change ONLY its description and save.",
-            "RELOAD and read all four of those back.",
-            "Restore the description.",
-        ],
-        inputs: {
-            store: "store-letitrip-official",
-            pendingStore: "store-blader-bazaar",
-            suspendedStore: "store-vintage-vault-co",
-        },
-        expectedBehaviour: "🛑 This is the highest-severity case on the page. The list serializer once omitted the verified, featured, capabilities and notes fields, so the editor seeded them as undefined and the save handler sent those defaults back unconditionally — saving ANY unrelated field silently un-verified the store and reset its capabilities. The seed carries a pending and a suspended store precisely so those chips are not permanently empty.",
-        expectedUiState: "Every status chip returns rows; the pending and suspended chips have a seeded store each. After the description save and reload the store is STILL verified, still featured, its capabilities are unchanged and its admin notes are intact. A store that quietly lost its verified badge is the failure, and the save reported success. This is expected to PASS — the list serializer now carries all five of those fields — but it is the case worth re-running after any change to that route, because the failure is silent and destructive.",
-        expectedData: { verifiedPreserved: true, featuredPreserved: true, capabilitiesPreserved: true },
-        endResult: "The description is restored and the store's flags are as they were. Re-read every flag after the reload, not just the one that was edited.",
-    },
-    "checklist-admin-buyer-data-admin-admin-store-detail-page": {
-        roles: ["admin"],
-        startPage: "/admin/stores",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/stores and open store-beyblade-arena's detail panel from the list.",
-            "Write down every field label it shows, then close the panel.",
-            "Open /admin/stores/store-beyblade-arena/view directly.",
-            "Write down every field label there and compare the two lists.",
-            "Reload that page and confirm it loads the same store rather than 404ing or resetting.",
-            "Search both surfaces, and the page source of the standalone one, for a WhatsApp access token.",
-        ],
-        inputs: { store: "store-beyblade-arena", standalonePage: "/admin/stores/{id}/view" },
-        expectedBehaviour: "The panel and the page render from one shared content component, so their fields match by construction. The store document's WhatsApp token is decrypted on every read, so any surface that does not deliberately project it is handling plaintext — an admin page is allowed to show more than a public one, but not the raw credential.",
-        expectedUiState: "Both surfaces show the same fields and the standalone page survives a reload. The access token is masked or absent on both. A field in one and not the other means a second copy of the content component has appeared.",
-        expectedData: { rawTokenShown: 0 },
-        endResult: "Read-only; nothing persists.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__catalog-listings.d.ts

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