@mohasinac/appkit 4.58.0 → 4.59.0

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

@@ -1,260 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/uncovered-admin-pages page.
- * WHAT: 14 case(s), keyed by full checklist id.
- *
- * Every page here was found by a sweep, not by a report: a built `page.tsx` with
- * zero cases naming it anywhere in the catalogue. A page nothing tests is
- * invisible to this whole mechanism, and four of them are observability surfaces —
- * the screens somebody reaches for precisely when something else is already wrong.
- *
- * These are deliberately one case each. A page nobody has looked at needs "does it
- * render, and does its main affordance work" before it needs depth; writing six
- * 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
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-const SIGN_IN_ADMIN = "Sign in as admin@letitrip.in / TempPass123!.";
-export const authored = {
-    "checklist-admin-uncovered-admin-pages-action-index-renders": {
-        roles: ["admin"],
-        startPage: "/admin/action-index",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/action-index with the browser console open.",
-            "Read what the page lists.",
-            "Pick one action and read its label, its kind and whether it carries a confirmation.",
-            "Check a destructive action shows that it has a confirmation configured.",
-            "Read the console for errors.",
-        ],
-        expectedBehaviour: "The page renders the registered CTA catalogue. Every action in the product is supposed to be declared there rather than written inline at its call site, so this page is the readable form of that rule — and a destructive action with no confirmation is exactly what it exists to surface.",
-        expectedUiState: "A populated list of actions with labels and kinds, no error boundary, clean console. Any destructive action showing no confirmation is a finding, named.",
-        expectedData: { consoleErrors: 0 },
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-admin-notifications-renders": {
-        roles: ["admin"],
-        startPage: "/admin/admin-notifications",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/admin-notifications.",
-            "Read the rows listed and note their types.",
-            "Open one row's detail.",
-            "Read the full body and any linked record.",
-            "Follow the link, if there is one, and read where it lands.",
-        ],
-        expectedBehaviour: "Notification rows can be opened and read in full. A list-only surface is a dead end — an admin can see that something happened and never what it said, which is the shape a whole sweep of dashboard lists was found in.",
-        expectedUiState: "Rows render with their types, a row opens to show the full body, and any link lands on a real page. A list with no way to open a row is the finding.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-maintenance-analysis-renders": {
-        roles: ["admin"],
-        startPage: "/admin/maintenance/analysis",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/maintenance/analysis with the console open.",
-            "Read whether the page renders content or an error boundary.",
-            "Read the console and the network panel for failures.",
-            "Reload once and read the same.",
-        ],
-        expectedBehaviour: "The page renders rather than throwing. Maintenance pages read external systems, and an unguarded read there is both a runtime error boundary and — because the build attempts to prerender pages under a session-reading layout — a way to fail the production build outright.",
-        expectedUiState: "Content renders with no error boundary and a clean console. A failed request that leaves the page empty but silent is also a finding.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-maintenance-client-errors-renders": {
-        roles: ["admin"],
-        startPage: "/admin/maintenance/client-errors",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/maintenance/client-errors.",
-            "Read whether rows are listed and in what order.",
-            "Check the newest is first.",
-            "Open one row and read its message, its reference code and its component trace.",
-            "Note whether a reference code shown on an error screen could be searched for here.",
-        ],
-        expectedBehaviour: "Browser-reported errors land here with the reference code an error screen shows the user, which is the join key between what they quote and what was recorded. The registration that forwards them has been silently absent twice, and its failure mode is an empty list rather than an error — so an empty list is only correct if nothing has genuinely been reported.",
-        expectedUiState: "Rows newest-first, each opening to a message and a reference code. Record whether the list is empty, since that is the exact symptom of a missing registration.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-maintenance-function-errors-renders": {
-        roles: ["admin"],
-        startPage: "/admin/maintenance/function-errors",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/maintenance/function-errors.",
-            "Read what the page shows.",
-            "Check an empty list reads as 'none recorded' rather than as a blank area.",
-            "Read the console for errors.",
-        ],
-        expectedBehaviour: "This error source has no production producer today, so an empty list is the expected and correct state. What must not happen is a blank region indistinguishable from a page that failed to load — the difference between 'nothing to show' and 'nothing loaded' is the whole value of an observability screen.",
-        expectedUiState: "Either rows, or an explicit empty state saying none are recorded. A bare blank area is the finding.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-maintenance-payment-rollbacks-renders": {
-        roles: ["admin"],
-        startPage: "/admin/maintenance/payment-rollbacks",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/maintenance/payment-rollbacks.",
-            "Read the rows listed, or the empty state.",
-            "Open one row.",
-            "Read what it shows about the order and the rollback.",
-            "Read the console for errors.",
-        ],
-        expectedBehaviour: "Rollback records can be opened and traced back to their order. A payment rollback is a money event, so a row that cannot be opened leaves an admin knowing an amount moved and not which order it belonged to.",
-        expectedUiState: "Rows open to show the order and the reason, or an explicit empty state. A row that cannot be opened is the finding.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-payment-method-clusters-renders": {
-        roles: ["admin"],
-        startPage: "/admin/payment-methods/clusters",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/payment-methods/clusters.",
-            "Read what a cluster represents on this page.",
-            "Open one cluster.",
-            "Read the accounts or methods grouped inside it.",
-            "Check any payment identifier shown is masked.",
-        ],
-        expectedBehaviour: "Clusters open to show what they group, and every payment identifier is masked. A masking helper that only spreads its input instead of masking is invisible everywhere except to a human who recognises a real value — which is exactly how one shipped and sat.",
-        expectedUiState: "A cluster opens and lists its members, with every account number or payment handle partially hidden. An unmasked identifier is the finding, and it is a leak rather than a display bug.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-settings-actions-renders": {
-        roles: ["admin"],
-        startPage: "/admin/settings/actions",
-        steps: [
-            SIGN_IN_ADMIN,
-            "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 value written down in step 3 and reload once more to confirm it went back.",
-        ],
-        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.",
-    },
-    "checklist-admin-uncovered-admin-pages-shipments-projections-renders": {
-        roles: ["admin"],
-        startPage: "/admin/shipments/projections",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/shipments/projections.",
-            "Read the figures shown.",
-            "Open /admin/shipments and note a real shipment's value.",
-            "Check the projection reflects real shipment data rather than zeros.",
-            "Check no figure looks inflated by a factor of a hundred.",
-        ],
-        expectedBehaviour: "Projections are computed from real shipment data. Money on this codebase is stored in whole rupees with decimals, and a fixture written in the older hundredth-unit scale inflated procurement projections a hundredfold — a figure that is obviously wrong only if somebody knows what it should be.",
-        expectedUiState: "Figures that correspond to the shipments list, with no order-of-magnitude jump. All zeros against real shipments, or a hundredfold figure, are both findings.",
-        endResult: "Read-only.",
-    },
-    "checklist-admin-uncovered-admin-pages-admin-stickers-renders": {
-        roles: ["admin"],
-        startPage: "/admin/stickers",
-        steps: [
-            SIGN_IN_ADMIN,
-            "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 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": {
-        roles: ["admin"],
-        startPage: "/admin/deals",
-        steps: [
-            SIGN_IN_ADMIN,
-            "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 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": {
-        roles: ["admin"],
-        startPage: "/admin/featured",
-        steps: [
-            SIGN_IN_ADMIN,
-            "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.",
-        ],
-        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"],
-        startPage: "/admin/features",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/features and read the features listed.",
-            "Create a feature named 'QA Feature Probe'.",
-            "Save it and check it appears in the list.",
-            "Reload and check it is still there.",
-            "Delete it.",
-        ],
-        inputs: { name: "QA Feature Probe" },
-        expectedBehaviour: "A product feature can be created, appears in the list and survives a reload. Reloading is the whole test — an in-memory row that never reached storage looks identical until then.",
-        expectedUiState: "The new feature is listed before and after the reload, and is gone after the delete.",
-        endResult: "The QA feature is deleted.",
-    },
-    "checklist-admin-uncovered-admin-pages-admin-guides-all-render": {
-        roles: ["admin"],
-        startPage: "/admin/guide",
-        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 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.",
-            "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 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.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__users-trust.d.ts

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