@withpotter/lib 0.13.0-next.101

package/dist/order-discounts.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/order-discounts.ts"],"sourcesContent":["/**\n * Why an order came out cheaper, split by who gave the money away.\n *\n * `discountTotal` is one number and can now hold two reasons: a code the\n * customer typed, and the percentage a membership tier grants. A merchant\n * reading \"Discount −₦4,500\" cannot tell whether they ran a promotion or\n * whether the tier they set up months ago is doing what it promised — and the\n * second one is the question, because the member discount is applied silently\n * at checkout with nothing on the storefront saying it happened.\n *\n * `create-order.usecase.ts` records the member's share on `order.data` when it\n * applies one, so this reads that and treats whatever is left as the code.\n */\n\ninterface MemberDiscountRecord {\n  amount: number;\n  percentage: number;\n}\n\nexport interface DiscountLine {\n  label: string;\n  amount: number;\n}\n\nfunction memberShare(data: unknown): MemberDiscountRecord | null {\n  if (!data || typeof data !== 'object') return null;\n  const record = (data as Record<string, unknown>).memberDiscount;\n  if (!record || typeof record !== 'object') return null;\n  const { amount, percentage } = record as Record<string, unknown>;\n  if (typeof amount !== 'number' || amount <= 0) return null;\n  return {\n    amount,\n    percentage: typeof percentage === 'number' ? percentage : 0,\n  };\n}\n\n/**\n * One line per reason, in the order they were applied. Empty when nothing was\n * taken off, so a caller can spread it into a list of totals without a guard.\n */\nexport function describeOrderDiscounts(order: {\n  discountTotal?: number | null;\n  data?: unknown;\n}): DiscountLine[] {\n  const total = order.discountTotal ?? 0;\n  if (total <= 0) return [];\n\n  const member = memberShare(order.data);\n  if (!member) return [{ label: 'Discount', amount: total }];\n\n  const memberLabel = member.percentage\n    ? `Member discount (${member.percentage}%)`\n    : 'Member discount';\n\n  // The code's share is whatever the membership did not account for. Clamped,\n  // because a refund or a manual edit can move `discountTotal` underneath a\n  // record that was written at checkout.\n  const code = Math.max(0, total - member.amount);\n  const lines: DiscountLine[] = [];\n  if (code > 0) lines.push({ label: 'Discount', amount: code });\n  lines.push({ label: memberLabel, amount: Math.min(member.amount, total) });\n  return lines;\n}\n"],"mappings":"AAwBA,SAAS,YAAY,MAA4C;AAC/D,MAAI,CAAC,QAAQ,OAAO,SAAS,SAAU,QAAO;AAC9C,QAAM,SAAU,KAAiC;AACjD,MAAI,CAAC,UAAU,OAAO,WAAW,SAAU,QAAO;AAClD,QAAM,EAAE,QAAQ,WAAW,IAAI;AAC/B,MAAI,OAAO,WAAW,YAAY,UAAU,EAAG,QAAO;AACtD,SAAO;AAAA,IACL;AAAA,IACA,YAAY,OAAO,eAAe,WAAW,aAAa;AAAA,EAC5D;AACF;AAMO,SAAS,uBAAuB,OAGpB;AACjB,QAAM,QAAQ,MAAM,iBAAiB;AACrC,MAAI,SAAS,EAAG,QAAO,CAAC;AAExB,QAAM,SAAS,YAAY,MAAM,IAAI;AACrC,MAAI,CAAC,OAAQ,QAAO,CAAC,EAAE,OAAO,YAAY,QAAQ,MAAM,CAAC;AAEzD,QAAM,cAAc,OAAO,aACvB,oBAAoB,OAAO,UAAU,OACrC;AAKJ,QAAM,OAAO,KAAK,IAAI,GAAG,QAAQ,OAAO,MAAM;AAC9C,QAAM,QAAwB,CAAC;AAC/B,MAAI,OAAO,EAAG,OAAM,KAAK,EAAE,OAAO,YAAY,QAAQ,KAAK,CAAC;AAC5D,QAAM,KAAK,EAAE,OAAO,aAAa,QAAQ,KAAK,IAAI,OAAO,QAAQ,KAAK,EAAE,CAAC;AACzE,SAAO;AACT;","names":[]}

package/dist/order-shipping.d.ts

@@ -0,0 +1,33 @@
+import type { OrderDelivery } from './api/deliveries';
+import type { DeliveryMethod, OrderAddress } from './api/types';
+/**
+ * How an order's Shipping card reads. Pure, so the words are tested here.
+ *
+ * A walk-in sale comes back with an address object whose every field is
+ * empty, and the card printed it as a lone ",". Whether there is an address
+ * is a question about its words, not about whether the object exists.
+ */
+type AddressLike = Partial<OrderAddress> | null | undefined;
+/** True when the address has a street, town, region, postcode or country. */
+export declare function hasAddress(addr: AddressLike): boolean;
+/** "Ikeja, Lagos 100001", leaving out the parts that are empty. */
+export declare function cityLine(addr: AddressLike): string;
+/** What the card says when there is no address. */
+export declare function noAddressLabel(method: DeliveryMethod | null | undefined, hasRider: boolean): string;
+export interface RiderOnOrder {
+    /** "Delivered by Musa Bello" or "With Musa Bello". */
+    label: string;
+    /** "14 Oct, 2:10 pm" for a delivered order. */
+    at: string | null;
+    phone: string | null;
+    riderName: string;
+    delivered: boolean;
+}
+/** "14 Oct, 2:10 pm". */
+export declare function dayAndTime(iso: string): string;
+/**
+ * Who delivered the order, or who has it now. Null when no rider holds it
+ * and none delivered it (never sent, declined, failed or cancelled).
+ */
+export declare function riderOnOrder(delivery: OrderDelivery | null | undefined): RiderOnOrder | null;
+export {};

package/dist/order-shipping.js

@@ -0,0 +1,49 @@
+import { clockTime, isActiveDelivery } from "./rider-display";
+const filled = (v) => typeof v === "string" && v.trim().length > 0;
+function hasAddress(addr) {
+  if (!addr) return false;
+  return [addr.address1, addr.address2, addr.city, addr.state, addr.postalCode, addr.country].some(filled);
+}
+function cityLine(addr) {
+  if (!addr) return "";
+  const place = [addr.city, addr.state].filter(filled).map((s) => s.trim()).join(", ");
+  return [place, addr.postalCode?.trim()].filter(Boolean).join(" ");
+}
+function noAddressLabel(method, hasRider) {
+  if (hasRider || method === "delivery" || method === "shipping") return "No delivery address";
+  return "Collected in store";
+}
+function dayAndTime(iso) {
+  const day = new Date(iso).toLocaleDateString("en-GB", { day: "numeric", month: "short" });
+  return `${day}, ${clockTime(iso)}`;
+}
+function riderOnOrder(delivery) {
+  if (!delivery) return null;
+  const current = delivery.current;
+  if (current && isActiveDelivery(current.status)) {
+    return {
+      label: `With ${current.riderName}`,
+      at: null,
+      phone: current.riderPhone,
+      riderName: current.riderName,
+      delivered: false
+    };
+  }
+  const done = [current, ...delivery.history].find((a) => a?.status === "delivered");
+  if (!done) return null;
+  return {
+    label: `Delivered by ${done.riderName}`,
+    at: done.deliveredAt ? dayAndTime(done.deliveredAt) : null,
+    phone: done.riderPhone,
+    riderName: done.riderName,
+    delivered: true
+  };
+}
+export {
+  cityLine,
+  dayAndTime,
+  hasAddress,
+  noAddressLabel,
+  riderOnOrder
+};
+//# sourceMappingURL=order-shipping.js.map

package/dist/order-shipping.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/order-shipping.ts"],"sourcesContent":["import type { OrderDelivery } from './api/deliveries';\nimport type { DeliveryMethod, OrderAddress } from './api/types';\nimport { clockTime, isActiveDelivery } from './rider-display';\n\n/**\n * How an order's Shipping card reads. Pure, so the words are tested here.\n *\n * A walk-in sale comes back with an address object whose every field is\n * empty, and the card printed it as a lone \",\". Whether there is an address\n * is a question about its words, not about whether the object exists.\n */\n\ntype AddressLike = Partial<OrderAddress> | null | undefined;\n\nconst filled = (v: unknown) => typeof v === 'string' && v.trim().length > 0;\n\n/** True when the address has a street, town, region, postcode or country. */\nexport function hasAddress(addr: AddressLike): boolean {\n  if (!addr) return false;\n  return [addr.address1, addr.address2, addr.city, addr.state, addr.postalCode, addr.country].some(filled);\n}\n\n/** \"Ikeja, Lagos 100001\", leaving out the parts that are empty. */\nexport function cityLine(addr: AddressLike): string {\n  if (!addr) return '';\n  const place = [addr.city, addr.state].filter(filled).map((s) => s!.trim()).join(', ');\n  return [place, addr.postalCode?.trim()].filter(Boolean).join(' ');\n}\n\n/** What the card says when there is no address. */\nexport function noAddressLabel(method: DeliveryMethod | null | undefined, hasRider: boolean): string {\n  if (hasRider || method === 'delivery' || method === 'shipping') return 'No delivery address';\n  return 'Collected in store';\n}\n\nexport interface RiderOnOrder {\n  /** \"Delivered by Musa Bello\" or \"With Musa Bello\". */\n  label: string;\n  /** \"14 Oct, 2:10 pm\" for a delivered order. */\n  at: string | null;\n  phone: string | null;\n  riderName: string;\n  delivered: boolean;\n}\n\n/** \"14 Oct, 2:10 pm\". */\nexport function dayAndTime(iso: string): string {\n  const day = new Date(iso).toLocaleDateString('en-GB', { day: 'numeric', month: 'short' });\n  return `${day}, ${clockTime(iso)}`;\n}\n\n/**\n * Who delivered the order, or who has it now. Null when no rider holds it\n * and none delivered it (never sent, declined, failed or cancelled).\n */\nexport function riderOnOrder(delivery: OrderDelivery | null | undefined): RiderOnOrder | null {\n  if (!delivery) return null;\n  const current = delivery.current;\n  if (current && isActiveDelivery(current.status)) {\n    return {\n      label: `With ${current.riderName}`,\n      at: null,\n      phone: current.riderPhone,\n      riderName: current.riderName,\n      delivered: false,\n    };\n  }\n  const done = [current, ...delivery.history].find((a) => a?.status === 'delivered');\n  if (!done) return null;\n  return {\n    label: `Delivered by ${done.riderName}`,\n    at: done.deliveredAt ? dayAndTime(done.deliveredAt) : null,\n    phone: done.riderPhone,\n    riderName: done.riderName,\n    delivered: true,\n  };\n}\n"],"mappings":"AAEA,SAAS,WAAW,wBAAwB;AAY5C,MAAM,SAAS,CAAC,MAAe,OAAO,MAAM,YAAY,EAAE,KAAK,EAAE,SAAS;AAGnE,SAAS,WAAW,MAA4B;AACrD,MAAI,CAAC,KAAM,QAAO;AAClB,SAAO,CAAC,KAAK,UAAU,KAAK,UAAU,KAAK,MAAM,KAAK,OAAO,KAAK,YAAY,KAAK,OAAO,EAAE,KAAK,MAAM;AACzG;AAGO,SAAS,SAAS,MAA2B;AAClD,MAAI,CAAC,KAAM,QAAO;AAClB,QAAM,QAAQ,CAAC,KAAK,MAAM,KAAK,KAAK,EAAE,OAAO,MAAM,EAAE,IAAI,CAAC,MAAM,EAAG,KAAK,CAAC,EAAE,KAAK,IAAI;AACpF,SAAO,CAAC,OAAO,KAAK,YAAY,KAAK,CAAC,EAAE,OAAO,OAAO,EAAE,KAAK,GAAG;AAClE;AAGO,SAAS,eAAe,QAA2C,UAA2B;AACnG,MAAI,YAAY,WAAW,cAAc,WAAW,WAAY,QAAO;AACvE,SAAO;AACT;AAaO,SAAS,WAAW,KAAqB;AAC9C,QAAM,MAAM,IAAI,KAAK,GAAG,EAAE,mBAAmB,SAAS,EAAE,KAAK,WAAW,OAAO,QAAQ,CAAC;AACxF,SAAO,GAAG,GAAG,KAAK,UAAU,GAAG,CAAC;AAClC;AAMO,SAAS,aAAa,UAAiE;AAC5F,MAAI,CAAC,SAAU,QAAO;AACtB,QAAM,UAAU,SAAS;AACzB,MAAI,WAAW,iBAAiB,QAAQ,MAAM,GAAG;AAC/C,WAAO;AAAA,MACL,OAAO,QAAQ,QAAQ,SAAS;AAAA,MAChC,IAAI;AAAA,MACJ,OAAO,QAAQ;AAAA,MACf,WAAW,QAAQ;AAAA,MACnB,WAAW;AAAA,IACb;AAAA,EACF;AACA,QAAM,OAAO,CAAC,SAAS,GAAG,SAAS,OAAO,EAAE,KAAK,CAAC,MAAM,GAAG,WAAW,WAAW;AACjF,MAAI,CAAC,KAAM,QAAO;AAClB,SAAO;AAAA,IACL,OAAO,gBAAgB,KAAK,SAAS;AAAA,IACrC,IAAI,KAAK,cAAc,WAAW,KAAK,WAAW,IAAI;AAAA,IACtD,OAAO,KAAK;AAAA,IACZ,WAAW,KAAK;AAAA,IAChB,WAAW;AAAA,EACb;AACF;","names":[]}

package/dist/order-tax.d.ts

@@ -0,0 +1,28 @@
+/**
+ * What the tax on an order was called, at the time of the sale.
+ *
+ * Settings → Taxes takes a label — VAT, Sales tax, GST — and every surface
+ * that showed the number printed the word "Tax". Same miss as the storefront's
+ * two totals panels, which did the same thing beside the same number.
+ *
+ * It is read off `order.data`, not off today's settings, for the reason
+ * `create-order.usecase.ts` writes it there: a merchant who changes their rate
+ * or renames their tax next month must not restate what this customer was
+ * charged. An order printed six months ago says what it said.
+ *
+ * Same shape as `order-discounts.ts`, and for the same reason — the interesting
+ * detail sits on `data` and the panels should not each learn its layout.
+ */
+interface TaxBearingOrder {
+    data?: Record<string, unknown> | null;
+}
+/** "VAT", or "Tax" for an order written before the label was recorded. */
+export declare function orderTaxLabel(order: TaxBearingOrder): string;
+/**
+ * "VAT (7.5%)" where the rate is known, otherwise just the label.
+ *
+ * For the one place with room for it — the order's own totals panel. The rail
+ * is a narrow column and takes the label alone.
+ */
+export declare function orderTaxLabelWithRate(order: TaxBearingOrder): string;
+export {};

package/dist/order-tax.js

@@ -0,0 +1,21 @@
+function taxRecord(order) {
+  const record = order.data?.tax;
+  if (!record || typeof record !== "object") return void 0;
+  return record;
+}
+function orderTaxLabel(order) {
+  return taxRecord(order)?.label?.trim() || "Tax";
+}
+function orderTaxLabelWithRate(order) {
+  const record = taxRecord(order);
+  const label = record?.label?.trim() || "Tax";
+  const rateBps = Number(record?.rateBps) || 0;
+  if (rateBps <= 0) return label;
+  const percent = Number((rateBps / 100).toFixed(2));
+  return `${label} (${percent}%)`;
+}
+export {
+  orderTaxLabel,
+  orderTaxLabelWithRate
+};
+//# sourceMappingURL=order-tax.js.map

package/dist/order-tax.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/order-tax.ts"],"sourcesContent":["/**\n * What the tax on an order was called, at the time of the sale.\n *\n * Settings → Taxes takes a label — VAT, Sales tax, GST — and every surface\n * that showed the number printed the word \"Tax\". Same miss as the storefront's\n * two totals panels, which did the same thing beside the same number.\n *\n * It is read off `order.data`, not off today's settings, for the reason\n * `create-order.usecase.ts` writes it there: a merchant who changes their rate\n * or renames their tax next month must not restate what this customer was\n * charged. An order printed six months ago says what it said.\n *\n * Same shape as `order-discounts.ts`, and for the same reason — the interesting\n * detail sits on `data` and the panels should not each learn its layout.\n */\n\ninterface OrderTaxRecord {\n  amount?: number;\n  rateBps?: number;\n  label?: string;\n  mode?: 'disabled' | 'pass_through' | 'absorb';\n  inclusive?: boolean;\n}\n\ninterface TaxBearingOrder {\n  data?: Record<string, unknown> | null;\n}\n\nfunction taxRecord(order: TaxBearingOrder): OrderTaxRecord | undefined {\n  const record = order.data?.tax;\n  if (!record || typeof record !== 'object') return undefined;\n  return record as OrderTaxRecord;\n}\n\n/** \"VAT\", or \"Tax\" for an order written before the label was recorded. */\nexport function orderTaxLabel(order: TaxBearingOrder): string {\n  return taxRecord(order)?.label?.trim() || 'Tax';\n}\n\n/**\n * \"VAT (7.5%)\" where the rate is known, otherwise just the label.\n *\n * For the one place with room for it — the order's own totals panel. The rail\n * is a narrow column and takes the label alone.\n */\nexport function orderTaxLabelWithRate(order: TaxBearingOrder): string {\n  const record = taxRecord(order);\n  const label = record?.label?.trim() || 'Tax';\n  const rateBps = Number(record?.rateBps) || 0;\n  if (rateBps <= 0) return label;\n  // 750 → 7.5, 2000 → 20. Trailing zeros dropped: nobody writes \"VAT (20.00%)\".\n  const percent = Number((rateBps / 100).toFixed(2));\n  return `${label} (${percent}%)`;\n}\n"],"mappings":"AA4BA,SAAS,UAAU,OAAoD;AACrE,QAAM,SAAS,MAAM,MAAM;AAC3B,MAAI,CAAC,UAAU,OAAO,WAAW,SAAU,QAAO;AAClD,SAAO;AACT;AAGO,SAAS,cAAc,OAAgC;AAC5D,SAAO,UAAU,KAAK,GAAG,OAAO,KAAK,KAAK;AAC5C;AAQO,SAAS,sBAAsB,OAAgC;AACpE,QAAM,SAAS,UAAU,KAAK;AAC9B,QAAM,QAAQ,QAAQ,OAAO,KAAK,KAAK;AACvC,QAAM,UAAU,OAAO,QAAQ,OAAO,KAAK;AAC3C,MAAI,WAAW,EAAG,QAAO;AAEzB,QAAM,UAAU,QAAQ,UAAU,KAAK,QAAQ,CAAC,CAAC;AACjD,SAAO,GAAG,KAAK,KAAK,OAAO;AAC7B;","names":[]}

package/dist/page-intros.d.ts

@@ -0,0 +1,78 @@
+/**
+ * What a screen says for itself, the first time somebody opens it.
+ *
+ * THE ASK, from John: *"every page you are entering for the first time has to
+ * have a pop up modal to introduce you give you context"*, pointing at the
+ * connector page.
+ *
+ * WHY IT IS A REGISTRY AND NOT A PROP ON EIGHTY SCREENS. "Every page" is a
+ * promise about the whole app, and a promise like that kept screen-by-screen
+ * decays the same way every cross-cutting convention here has: the next new
+ * page forgets. One table, one mount in the shell, and adding a screen's
+ * introduction is adding an entry — which is also how `mobile-routes.ts` keeps
+ * its own promise about every route.
+ *
+ * WHAT AN ENTRY MAY SAY, and this is the part worth policing. It introduces the
+ * SCREEN — what this place is for, what it can do, what it will not do. It is
+ * not a tour, not a feature advert, and not a place to put an instruction that
+ * belongs on the control itself: a modal explaining a button is a bug report
+ * about that button. Two sentences is the shape; anything longer is a screen
+ * that has not been designed yet.
+ *
+ * NOUNS ARE TOKENS, NEVER TYPED. `{items}` and `{orders}` are resolved against
+ * `useEntityLabel` when the dialog renders, because a short-let calls a product
+ * a property and a padel club calls an order a booking — and an introduction
+ * that opens by calling the merchant's properties "products" has undone itself
+ * in its first sentence. Write `{items}`, `{item}`, `{orders}`, `{order}`;
+ * anything else stays literal.
+ *
+ * A PAGE WITH NO ENTRY SHOWS NOTHING. Silence is the default, so nobody has to
+ * write filler to stop an empty modal appearing — and the intros that do exist
+ * stay worth reading. That is the same reason the app has one live slot for
+ * feedback prompts: an interruption people learn to dismiss unread is worse
+ * than no interruption.
+ */
+export interface PageIntro {
+    /**
+     * Stable across copy edits and route moves. It is what "seen" is remembered
+     * against, so changing it re-shows the intro to everybody — which is
+     * occasionally what you want, and never what you want by accident.
+     */
+    key: string;
+    title: string;
+    /** Two sentences. What this place is, and what it is for. */
+    body: string;
+    /** The word on the way out. Defaults to "Got it". */
+    dismiss?: string;
+}
+/**
+ * Fill a body's noun tokens from the labels this business actually uses.
+ *
+ * Lower-cased mid-sentence, because the label store holds them capitalised for
+ * headings ("Properties") and an introduction is prose.
+ */
+export declare function fillIntroNouns(body: string, nouns: {
+    item: {
+        singular: string;
+        plural: string;
+    };
+    order: {
+        singular: string;
+        plural: string;
+    };
+}): string;
+export declare const PAGE_INTROS: Record<string, PageIntro>;
+export declare function introFor(pathname: string): PageIntro | undefined;
+/**
+ * Seen, per workspace, on this device.
+ *
+ * PER DEVICE IS A REAL LIMIT and it is the honest one to ship today: there is
+ * no per-account preference store on the API, and inventing one for this would
+ * be a table and a migration for a thing whose worst failure is a merchant
+ * reading a two-sentence introduction twice. Per WORKSPACE rather than per
+ * account, because somebody who runs two businesses meets the connections page
+ * fresh in each of them.
+ */
+export declare function introSeenKey(tenantSlug: string, key: string): string;
+export declare function hasSeenIntro(tenantSlug: string, key: string): boolean;
+export declare function markIntroSeen(tenantSlug: string, key: string): void;

package/dist/page-intros.js

@@ -0,0 +1,164 @@
+import { matchRoutePattern } from "./route-pattern";
+import {
+  BOX_EMAIL_ONLY,
+  BOX_HIDE_SMS,
+  BOX_HIDE_WHATSAPP
+} from "./box-channels";
+function fillIntroNouns(body, nouns) {
+  return body.replaceAll("{items}", nouns.item.plural.toLowerCase()).replaceAll("{item}", nouns.item.singular.toLowerCase()).replaceAll("{orders}", nouns.order.plural.toLowerCase()).replaceAll("{order}", nouns.order.singular.toLowerCase());
+}
+const PAGE_INTROS = {
+  /**
+   * Connections. The screen John named, and the one that most needs it: the
+   * word "integration" means nothing to a merchant, and the page's real subject
+   * — a permission you granted, which you can see the state of and take back —
+   * is not visible from a list of logos.
+   */
+  "/dashboard/settings/integrations": {
+    key: "connections.v1",
+    title: "What a connection is",
+    body: "An account you own somewhere else \u2014 a calendar, a shop, an accounting system \u2014 that Box has been given permission to use. Connect one here to see whether it is working, and take the permission back whenever you like."
+  },
+  /**
+   * Money. The boundary nobody guesses and everybody needs: Box never holds
+   * the money. Said here once, it stops the question that otherwise arrives as
+   * "where is my payout" support mail.
+   */
+  "/dashboard/payments": {
+    key: "money.v1",
+    title: "Where your money is",
+    body: "Everything a customer pays goes to your own bank account \u2014 Box never holds it, and never moves it for you. This is where you watch it arrive, chase what has not, and see what each payout was made of."
+  },
+  /**
+   * Orders absorbed Sales, so the page is wider than its name suggests — see
+   * [[potter-orders-absorbed-sales]]. The second sentence is the part a
+   * merchant cannot see: that bookings and invoices land here too.
+   */
+  "/dashboard/orders": {
+    key: "orders.v1",
+    title: "The queue you work",
+    body: "Every {order} in one line, wherever it came from. Work it top to bottom \u2014 take payment, pack, hand over \u2014 and anything still waiting on you stays at the front."
+  },
+  /**
+   * Customers. The one thing merchants hunt for and cannot find: stages and
+   * segments are in the FILTER, not in a rail — [[potter-customer-stages-live-in-the-filter]].
+   */
+  "/dashboard/customers": {
+    key: "customers.v1",
+    title: "Everyone who has bought from you",
+    body: "One row per person, built from what they actually did rather than from a form you filled in. Narrow it in the filters \u2014 new, regular, gone quiet \u2014 and what is left is a list you can message or export."
+  },
+  /**
+   * Marketing. Three nouns that sound alike (campaign, group, automation) and
+   * mean different things; the hub is where the difference has to be said.
+   */
+  "/dashboard/marketing": {
+    key: "marketing.v1",
+    title: "What you send, and what it earns",
+    body: "A campaign is one message to one audience. Group the ones that belong to the same promo and the earnings add up under a single name \u2014 which is the number worth looking at."
+  },
+  /**
+   * Promotions. Two objects under one roof, and the rule for which is which.
+   */
+  "/dashboard/marketing/promotions": {
+    key: "promotions.v1",
+    title: "What you offer people",
+    body: "Money off, or money already paid in: a discount code and a gift card sit together here because you weigh one against the other in the same sitting. Neither is a message \u2014 sending it is a campaign."
+  },
+  /**
+   * Automations. The distinction that makes the screen legible: these run
+   * without you, forever, which is exactly what makes them worth checking.
+   */
+  "/dashboard/marketing/automations": {
+    key: "automations.v1",
+    title: "Messages that send themselves",
+    body: "Set one up and it runs on its own \u2014 after a first purchase, when a cart is abandoned, before an appointment. They keep sending while you are asleep, so what you write here matters more than a one-off."
+  },
+  /**
+   * Analytics. The house rule stated to the merchant: a number is here because
+   * it can change a decision — [[potter-analytics-strictness]].
+   */
+  "/dashboard/analytics": {
+    key: "analytics.v1",
+    title: "The numbers that change something",
+    body: "What sold, who came back, and where they came from \u2014 over a window you choose. Nothing here is a vanity count: every figure is one you could act on this week."
+  },
+  /**
+   * Attribution. The word is jargon; the question under it is not.
+   */
+  "/dashboard/analytics/acquisition": {
+    key: "attribution.v1",
+    title: "Where the money came from",
+    body: "Every {order} carries a trace of how that customer reached you \u2014 a link you shared, a code they typed, a campaign they opened. This adds those up, and is honest about the share that arrived with nothing saying where from."
+  },
+  /**
+   * Inventory. `{items}` matters most here: this is the screen a short-let
+   * opens expecting properties.
+   */
+  /* `/dashboard/inventory` redirects here, so the entry lives on the route
+     that actually renders — a registry keyed on a redirect introduces a screen
+     nobody ever lands on. */
+  "/dashboard/catalog": {
+    key: "catalog.v1",
+    title: "Everything you sell",
+    body: "One row per {item}, with its price, its photo and what is left of it. What you put here is what your site shows, and what your {orders} are made of."
+  },
+  /**
+   * The website hub. A merchant's site is the one thing here that strangers
+   * see, and the boundary between "how it looks" and "what is in it" is the
+   * thing that confuses people.
+   */
+  "/dashboard/business": {
+    key: "website.v1",
+    title: "Your site, as customers see it",
+    body: "The address, the look, and whether it is open for business. What is IN it \u2014 your {items}, your prices, your hours \u2014 is kept where you already manage them, and the site shows whatever is there now."
+  },
+  /**
+   * Credits. A prepaid balance is an unusual object in a product like this,
+   * and merchants reasonably assume "my plan covers it".
+   */
+  "/dashboard/settings/billing/credits": {
+    key: "credits.v1",
+    title: "What credits pay for",
+    body: `${BOX_EMAIL_ONLY ? "Emails cost" : BOX_HIDE_SMS ? "WhatsApp messages and emails cost" : BOX_HIDE_WHATSAPP ? "Texts and emails cost" : "Texts, WhatsApp messages and emails cost"} a credit each time one goes out \u2014 your plan includes some every month, and you can buy more without changing plan. Credits you buy never expire; the ones your plan includes are for that month.`
+  },
+  /**
+   * Explore. John's own framing, 2026-09-03: this is a business being given
+   * something it could not do yesterday, not a contribution to Box.
+   */
+  "/dashboard/explore": {
+    key: "explore.v1",
+    title: "Add more to this business",
+    body: "Everything Box can do that you have not switched on \u2014 bookings, invoices, a loyalty programme, a shop. Turning one on adds it to this business only, and you can turn it off again."
+  }
+};
+function introFor(pathname) {
+  const pattern = matchRoutePattern(pathname, Object.keys(PAGE_INTROS));
+  return pattern ? PAGE_INTROS[pattern] : void 0;
+}
+function introSeenKey(tenantSlug, key) {
+  return `pb:intro:${tenantSlug}:${key}`;
+}
+function hasSeenIntro(tenantSlug, key) {
+  if (typeof window === "undefined") return true;
+  try {
+    return window.localStorage.getItem(introSeenKey(tenantSlug, key)) === "1";
+  } catch {
+    return true;
+  }
+}
+function markIntroSeen(tenantSlug, key) {
+  try {
+    window.localStorage.setItem(introSeenKey(tenantSlug, key), "1");
+  } catch {
+  }
+}
+export {
+  PAGE_INTROS,
+  fillIntroNouns,
+  hasSeenIntro,
+  introFor,
+  introSeenKey,
+  markIntroSeen
+};
+//# sourceMappingURL=page-intros.js.map

package/dist/page-intros.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/page-intros.ts"],"sourcesContent":["import { matchRoutePattern } from './route-pattern';\nimport {\n  BOX_EMAIL_ONLY,\n  BOX_HIDE_SMS,\n  BOX_HIDE_WHATSAPP,\n} from './box-channels';\n\n/**\n * What a screen says for itself, the first time somebody opens it.\n *\n * THE ASK, from John: *\"every page you are entering for the first time has to\n * have a pop up modal to introduce you give you context\"*, pointing at the\n * connector page.\n *\n * WHY IT IS A REGISTRY AND NOT A PROP ON EIGHTY SCREENS. \"Every page\" is a\n * promise about the whole app, and a promise like that kept screen-by-screen\n * decays the same way every cross-cutting convention here has: the next new\n * page forgets. One table, one mount in the shell, and adding a screen's\n * introduction is adding an entry — which is also how `mobile-routes.ts` keeps\n * its own promise about every route.\n *\n * WHAT AN ENTRY MAY SAY, and this is the part worth policing. It introduces the\n * SCREEN — what this place is for, what it can do, what it will not do. It is\n * not a tour, not a feature advert, and not a place to put an instruction that\n * belongs on the control itself: a modal explaining a button is a bug report\n * about that button. Two sentences is the shape; anything longer is a screen\n * that has not been designed yet.\n *\n * NOUNS ARE TOKENS, NEVER TYPED. `{items}` and `{orders}` are resolved against\n * `useEntityLabel` when the dialog renders, because a short-let calls a product\n * a property and a padel club calls an order a booking — and an introduction\n * that opens by calling the merchant's properties \"products\" has undone itself\n * in its first sentence. Write `{items}`, `{item}`, `{orders}`, `{order}`;\n * anything else stays literal.\n *\n * A PAGE WITH NO ENTRY SHOWS NOTHING. Silence is the default, so nobody has to\n * write filler to stop an empty modal appearing — and the intros that do exist\n * stay worth reading. That is the same reason the app has one live slot for\n * feedback prompts: an interruption people learn to dismiss unread is worse\n * than no interruption.\n */\nexport interface PageIntro {\n  /**\n   * Stable across copy edits and route moves. It is what \"seen\" is remembered\n   * against, so changing it re-shows the intro to everybody — which is\n   * occasionally what you want, and never what you want by accident.\n   */\n  key: string;\n  title: string;\n  /** Two sentences. What this place is, and what it is for. */\n  body: string;\n  /** The word on the way out. Defaults to \"Got it\". */\n  dismiss?: string;\n}\n\n/**\n * Fill a body's noun tokens from the labels this business actually uses.\n *\n * Lower-cased mid-sentence, because the label store holds them capitalised for\n * headings (\"Properties\") and an introduction is prose.\n */\nexport function fillIntroNouns(\n  body: string,\n  nouns: {\n    item: { singular: string; plural: string };\n    order: { singular: string; plural: string };\n  },\n): string {\n  return body\n    .replaceAll('{items}', nouns.item.plural.toLowerCase())\n    .replaceAll('{item}', nouns.item.singular.toLowerCase())\n    .replaceAll('{orders}', nouns.order.plural.toLowerCase())\n    .replaceAll('{order}', nouns.order.singular.toLowerCase());\n}\n\nexport const PAGE_INTROS: Record<string, PageIntro> = {\n  /**\n   * Connections. The screen John named, and the one that most needs it: the\n   * word \"integration\" means nothing to a merchant, and the page's real subject\n   * — a permission you granted, which you can see the state of and take back —\n   * is not visible from a list of logos.\n   */\n  '/dashboard/settings/integrations': {\n    key: 'connections.v1',\n    title: 'What a connection is',\n    body: 'An account you own somewhere else — a calendar, a shop, an accounting system — that Box has been given permission to use. Connect one here to see whether it is working, and take the permission back whenever you like.',\n  },\n\n  /**\n   * Money. The boundary nobody guesses and everybody needs: Box never holds\n   * the money. Said here once, it stops the question that otherwise arrives as\n   * \"where is my payout\" support mail.\n   */\n  '/dashboard/payments': {\n    key: 'money.v1',\n    title: 'Where your money is',\n    body: 'Everything a customer pays goes to your own bank account — Box never holds it, and never moves it for you. This is where you watch it arrive, chase what has not, and see what each payout was made of.',\n  },\n\n  /**\n   * Orders absorbed Sales, so the page is wider than its name suggests — see\n   * [[potter-orders-absorbed-sales]]. The second sentence is the part a\n   * merchant cannot see: that bookings and invoices land here too.\n   */\n  '/dashboard/orders': {\n    key: 'orders.v1',\n    title: 'The queue you work',\n    body: 'Every {order} in one line, wherever it came from. Work it top to bottom — take payment, pack, hand over — and anything still waiting on you stays at the front.',\n  },\n\n  /**\n   * Customers. The one thing merchants hunt for and cannot find: stages and\n   * segments are in the FILTER, not in a rail — [[potter-customer-stages-live-in-the-filter]].\n   */\n  '/dashboard/customers': {\n    key: 'customers.v1',\n    title: 'Everyone who has bought from you',\n    body: 'One row per person, built from what they actually did rather than from a form you filled in. Narrow it in the filters — new, regular, gone quiet — and what is left is a list you can message or export.',\n  },\n\n  /**\n   * Marketing. Three nouns that sound alike (campaign, group, automation) and\n   * mean different things; the hub is where the difference has to be said.\n   */\n  '/dashboard/marketing': {\n    key: 'marketing.v1',\n    title: 'What you send, and what it earns',\n    body: 'A campaign is one message to one audience. Group the ones that belong to the same promo and the earnings add up under a single name — which is the number worth looking at.',\n  },\n\n  /**\n   * Promotions. Two objects under one roof, and the rule for which is which.\n   */\n  '/dashboard/marketing/promotions': {\n    key: 'promotions.v1',\n    title: 'What you offer people',\n    body: 'Money off, or money already paid in: a discount code and a gift card sit together here because you weigh one against the other in the same sitting. Neither is a message — sending it is a campaign.',\n  },\n\n  /**\n   * Automations. The distinction that makes the screen legible: these run\n   * without you, forever, which is exactly what makes them worth checking.\n   */\n  '/dashboard/marketing/automations': {\n    key: 'automations.v1',\n    title: 'Messages that send themselves',\n    body: 'Set one up and it runs on its own — after a first purchase, when a cart is abandoned, before an appointment. They keep sending while you are asleep, so what you write here matters more than a one-off.',\n  },\n\n  /**\n   * Analytics. The house rule stated to the merchant: a number is here because\n   * it can change a decision — [[potter-analytics-strictness]].\n   */\n  '/dashboard/analytics': {\n    key: 'analytics.v1',\n    title: 'The numbers that change something',\n    body: 'What sold, who came back, and where they came from — over a window you choose. Nothing here is a vanity count: every figure is one you could act on this week.',\n  },\n\n  /**\n   * Attribution. The word is jargon; the question under it is not.\n   */\n  '/dashboard/analytics/acquisition': {\n    key: 'attribution.v1',\n    title: 'Where the money came from',\n    body: 'Every {order} carries a trace of how that customer reached you — a link you shared, a code they typed, a campaign they opened. This adds those up, and is honest about the share that arrived with nothing saying where from.',\n  },\n\n  /**\n   * Inventory. `{items}` matters most here: this is the screen a short-let\n   * opens expecting properties.\n   */\n  /* `/dashboard/inventory` redirects here, so the entry lives on the route\n     that actually renders — a registry keyed on a redirect introduces a screen\n     nobody ever lands on. */\n  '/dashboard/catalog': {\n    key: 'catalog.v1',\n    title: 'Everything you sell',\n    body: 'One row per {item}, with its price, its photo and what is left of it. What you put here is what your site shows, and what your {orders} are made of.',\n  },\n\n  /**\n   * The website hub. A merchant's site is the one thing here that strangers\n   * see, and the boundary between \"how it looks\" and \"what is in it\" is the\n   * thing that confuses people.\n   */\n  '/dashboard/business': {\n    key: 'website.v1',\n    title: 'Your site, as customers see it',\n    body: 'The address, the look, and whether it is open for business. What is IN it — your {items}, your prices, your hours — is kept where you already manage them, and the site shows whatever is there now.',\n  },\n\n  /**\n   * Credits. A prepaid balance is an unusual object in a product like this,\n   * and merchants reasonably assume \"my plan covers it\".\n   */\n  '/dashboard/settings/billing/credits': {\n    key: 'credits.v1',\n    title: 'What credits pay for',\n    body: `${BOX_EMAIL_ONLY ? 'Emails cost' : BOX_HIDE_SMS ? 'WhatsApp messages and emails cost' : BOX_HIDE_WHATSAPP ? 'Texts and emails cost' : 'Texts, WhatsApp messages and emails cost'} a credit each time one goes out — your plan includes some every month, and you can buy more without changing plan. Credits you buy never expire; the ones your plan includes are for that month.`,\n  },\n\n  /**\n   * Explore. John's own framing, 2026-09-03: this is a business being given\n   * something it could not do yesterday, not a contribution to Box.\n   */\n  '/dashboard/explore': {\n    key: 'explore.v1',\n    title: 'Add more to this business',\n    body: 'Everything Box can do that you have not switched on — bookings, invoices, a loyalty programme, a shop. Turning one on adds it to this business only, and you can turn it off again.',\n  },\n};\n\nexport function introFor(pathname: string): PageIntro | undefined {\n  const pattern = matchRoutePattern(pathname, Object.keys(PAGE_INTROS));\n  return pattern ? PAGE_INTROS[pattern] : undefined;\n}\n\n/**\n * Seen, per workspace, on this device.\n *\n * PER DEVICE IS A REAL LIMIT and it is the honest one to ship today: there is\n * no per-account preference store on the API, and inventing one for this would\n * be a table and a migration for a thing whose worst failure is a merchant\n * reading a two-sentence introduction twice. Per WORKSPACE rather than per\n * account, because somebody who runs two businesses meets the connections page\n * fresh in each of them.\n */\nexport function introSeenKey(tenantSlug: string, key: string): string {\n  return `pb:intro:${tenantSlug}:${key}`;\n}\n\nexport function hasSeenIntro(tenantSlug: string, key: string): boolean {\n  if (typeof window === 'undefined') return true;\n  try {\n    return window.localStorage.getItem(introSeenKey(tenantSlug, key)) === '1';\n  } catch {\n    /* Storage blocked: better to stay quiet than to interrupt on every visit. */\n    return true;\n  }\n}\n\nexport function markIntroSeen(tenantSlug: string, key: string): void {\n  try {\n    window.localStorage.setItem(introSeenKey(tenantSlug, key), '1');\n  } catch {\n    /* Nothing to do; the dialog is closing either way. */\n  }\n}\n"],"mappings":"AAAA,SAAS,yBAAyB;AAClC;AAAA,EACE;AAAA,EACA;AAAA,EACA;AAAA,OACK;AAwDA,SAAS,eACd,MACA,OAIQ;AACR,SAAO,KACJ,WAAW,WAAW,MAAM,KAAK,OAAO,YAAY,CAAC,EACrD,WAAW,UAAU,MAAM,KAAK,SAAS,YAAY,CAAC,EACtD,WAAW,YAAY,MAAM,MAAM,OAAO,YAAY,CAAC,EACvD,WAAW,WAAW,MAAM,MAAM,SAAS,YAAY,CAAC;AAC7D;AAEO,MAAM,cAAyC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAOpD,oCAAoC;AAAA,IAClC,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAOA,uBAAuB;AAAA,IACrB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAOA,qBAAqB;AAAA,IACnB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA,EAMA,wBAAwB;AAAA,IACtB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA,EAMA,wBAAwB;AAAA,IACtB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA,EAKA,mCAAmC;AAAA,IACjC,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA,EAMA,oCAAoC;AAAA,IAClC,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA,EAMA,wBAAwB;AAAA,IACtB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA,EAKA,oCAAoC;AAAA,IAClC,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EASA,sBAAsB;AAAA,IACpB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAOA,uBAAuB;AAAA,IACrB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA,EAMA,uCAAuC;AAAA,IACrC,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM,GAAG,iBAAiB,gBAAgB,eAAe,sCAAsC,oBAAoB,0BAA0B,0CAA0C;AAAA,EACzL;AAAA;AAAA;AAAA;AAAA;AAAA,EAMA,sBAAsB;AAAA,IACpB,KAAK;AAAA,IACL,OAAO;AAAA,IACP,MAAM;AAAA,EACR;AACF;AAEO,SAAS,SAAS,UAAyC;AAChE,QAAM,UAAU,kBAAkB,UAAU,OAAO,KAAK,WAAW,CAAC;AACpE,SAAO,UAAU,YAAY,OAAO,IAAI;AAC1C;AAYO,SAAS,aAAa,YAAoB,KAAqB;AACpE,SAAO,YAAY,UAAU,IAAI,GAAG;AACtC;AAEO,SAAS,aAAa,YAAoB,KAAsB;AACrE,MAAI,OAAO,WAAW,YAAa,QAAO;AAC1C,MAAI;AACF,WAAO,OAAO,aAAa,QAAQ,aAAa,YAAY,GAAG,CAAC,MAAM;AAAA,EACxE,QAAQ;AAEN,WAAO;AAAA,EACT;AACF;AAEO,SAAS,cAAc,YAAoB,KAAmB;AACnE,MAAI;AACF,WAAO,aAAa,QAAQ,aAAa,YAAY,GAAG,GAAG,GAAG;AAAA,EAChE,QAAQ;AAAA,EAER;AACF;","names":[]}

package/dist/page-transition.d.ts

@@ -0,0 +1,20 @@
+export type PageDirection = 'forward' | 'back' | 'slide-forward' | 'slide-back';
+/**
+ * Navigate with a direction-aware view transition.
+ *
+ * Ported from MetaMask's onboarding (docs/METAMASK_ONBOARDING_MOTION.md): the
+ * direction is written to `data-page-transition` on the document element, and
+ * CSS in globals.css pairs the outgoing and incoming animations for it. Forward
+ * and back are deliberately not symmetric — arriving screens grow into place
+ * from `--page-scale-distance`, leaving screens shrink away to it.
+ *
+ * The View Transitions API is the right tool for an actual route change. Step
+ * to step inside onboarding is state, not navigation, and stays with
+ * AnimatePresence.
+ *
+ * Degrades to a plain call: browsers without the API, and anyone with
+ * reduced motion, simply navigate. Nothing is gated on the transition
+ * resolving, so a business is never left uncreated because an animation
+ * did not run.
+ */
+export declare function navigateWithTransition(direction: PageDirection, navigate: () => void): void;

package/dist/page-transition.js

@@ -0,0 +1,19 @@
+"use client";
+function navigateWithTransition(direction, navigate) {
+  const root = typeof document !== "undefined" ? document.documentElement : null;
+  const start = document?.startViewTransition;
+  if (!root || typeof start !== "function") return navigate();
+  root.setAttribute("data-page-transition", direction);
+  try {
+    const transition = start.call(document, navigate);
+    void transition.finished.catch(() => {
+    }).finally(() => root.removeAttribute("data-page-transition"));
+  } catch {
+    root.removeAttribute("data-page-transition");
+    navigate();
+  }
+}
+export {
+  navigateWithTransition
+};
+//# sourceMappingURL=page-transition.js.map

package/dist/page-transition.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/page-transition.ts"],"sourcesContent":["'use client';\n\nexport type PageDirection = 'forward' | 'back' | 'slide-forward' | 'slide-back';\n\n/**\n * Navigate with a direction-aware view transition.\n *\n * Ported from MetaMask's onboarding (docs/METAMASK_ONBOARDING_MOTION.md): the\n * direction is written to `data-page-transition` on the document element, and\n * CSS in globals.css pairs the outgoing and incoming animations for it. Forward\n * and back are deliberately not symmetric — arriving screens grow into place\n * from `--page-scale-distance`, leaving screens shrink away to it.\n *\n * The View Transitions API is the right tool for an actual route change. Step\n * to step inside onboarding is state, not navigation, and stays with\n * AnimatePresence.\n *\n * Degrades to a plain call: browsers without the API, and anyone with\n * reduced motion, simply navigate. Nothing is gated on the transition\n * resolving, so a business is never left uncreated because an animation\n * did not run.\n */\nexport function navigateWithTransition(\n  direction: PageDirection,\n  navigate: () => void,\n): void {\n  const root =\n    typeof document !== 'undefined' ? document.documentElement : null;\n  const start = (\n    document as Document & {\n      startViewTransition?: (cb: () => void) => { finished: Promise<void> };\n    }\n  )?.startViewTransition;\n\n  if (!root || typeof start !== 'function') return navigate();\n\n  root.setAttribute('data-page-transition', direction);\n  try {\n    const transition = start.call(document, navigate);\n    void transition.finished\n      .catch(() => {})\n      .finally(() => root.removeAttribute('data-page-transition'));\n  } catch {\n    root.removeAttribute('data-page-transition');\n    navigate();\n  }\n}\n"],"mappings":";AAsBO,SAAS,uBACd,WACA,UACM;AACN,QAAM,OACJ,OAAO,aAAa,cAAc,SAAS,kBAAkB;AAC/D,QAAM,QACJ,UAGC;AAEH,MAAI,CAAC,QAAQ,OAAO,UAAU,WAAY,QAAO,SAAS;AAE1D,OAAK,aAAa,wBAAwB,SAAS;AACnD,MAAI;AACF,UAAM,aAAa,MAAM,KAAK,UAAU,QAAQ;AAChD,SAAK,WAAW,SACb,MAAM,MAAM;AAAA,IAAC,CAAC,EACd,QAAQ,MAAM,KAAK,gBAAgB,sBAAsB,CAAC;AAAA,EAC/D,QAAQ;AACN,SAAK,gBAAgB,sBAAsB;AAC3C,aAAS;AAAA,EACX;AACF;","names":[]}

package/dist/pages-api-response.d.ts

@@ -0,0 +1,8 @@
+interface PaginatedResponse<T> {
+    items: T[];
+}
+export type PageApiDialect = 'potter' | 'box';
+export declare function detectPageApiDialect<T>(response: T[] | PaginatedResponse<T>): PageApiDialect;
+export declare function getPageBySlugPath(slug: string, dialect: PageApiDialect): string;
+export declare function normalizePageList<T>(response: T[] | PaginatedResponse<T>): T[];
+export {};

package/dist/pages-api-response.js

@@ -0,0 +1,18 @@
+function detectPageApiDialect(response) {
+  if (Array.isArray(response)) return "potter";
+  if (response && Array.isArray(response.items)) return "box";
+  throw new Error("Invalid pages response");
+}
+function getPageBySlugPath(slug, dialect) {
+  const encodedSlug = encodeURIComponent(slug);
+  return dialect === "box" ? `/pages/slug/${encodedSlug}` : `/pages/${encodedSlug}`;
+}
+function normalizePageList(response) {
+  return detectPageApiDialect(response) === "potter" ? response : response.items;
+}
+export {
+  detectPageApiDialect,
+  getPageBySlugPath,
+  normalizePageList
+};
+//# sourceMappingURL=pages-api-response.js.map

package/dist/pages-api-response.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/pages-api-response.ts"],"sourcesContent":["interface PaginatedResponse<T> {\n  items: T[];\n}\n\nexport type PageApiDialect = 'potter' | 'box';\n\nexport function detectPageApiDialect<T>(\n  response: T[] | PaginatedResponse<T>,\n): PageApiDialect {\n  if (Array.isArray(response)) return 'potter';\n  if (response && Array.isArray(response.items)) return 'box';\n  throw new Error('Invalid pages response');\n}\n\nexport function getPageBySlugPath(\n  slug: string,\n  dialect: PageApiDialect,\n): string {\n  const encodedSlug = encodeURIComponent(slug);\n  return dialect === 'box'\n    ? `/pages/slug/${encodedSlug}`\n    : `/pages/${encodedSlug}`;\n}\n\nexport function normalizePageList<T>(\n  response: T[] | PaginatedResponse<T>,\n): T[] {\n  return detectPageApiDialect(response) === 'potter'\n    ? (response as T[])\n    : (response as PaginatedResponse<T>).items;\n}"],"mappings":"AAMO,SAAS,qBACd,UACgB;AAChB,MAAI,MAAM,QAAQ,QAAQ,EAAG,QAAO;AACpC,MAAI,YAAY,MAAM,QAAQ,SAAS,KAAK,EAAG,QAAO;AACtD,QAAM,IAAI,MAAM,wBAAwB;AAC1C;AAEO,SAAS,kBACd,MACA,SACQ;AACR,QAAM,cAAc,mBAAmB,IAAI;AAC3C,SAAO,YAAY,QACf,eAAe,WAAW,KAC1B,UAAU,WAAW;AAC3B;AAEO,SAAS,kBACd,UACK;AACL,SAAO,qBAAqB,QAAQ,MAAM,WACrC,WACA,SAAkC;AACzC;","names":[]}

package/dist/payment-method-label.d.ts

@@ -0,0 +1,6 @@
+/**
+ * A payment method in words. Card, transfer, cash, USSD and QR are said as they are; every other value
+ * (a gateway's own word such as "api", or "online") reads as an online payment, because that is all it
+ * tells the person looking. Nothing is guessed: an empty value is left off.
+ */
+export declare function paymentMethodLabel(method: string | null | undefined): string | null;

package/dist/payment-method-label.js

@@ -0,0 +1,14 @@
+function paymentMethodLabel(method) {
+  const value = (method ?? "").trim().toLowerCase().replace(/[\s-]+/g, "_");
+  if (!value) return null;
+  if (value === "card") return "Card";
+  if (["bank_transfer", "transfer", "bank"].includes(value)) return "Bank transfer";
+  if (value === "cash") return "Cash";
+  if (value === "ussd") return "USSD";
+  if (value === "qr") return "QR code";
+  return "Online payment";
+}
+export {
+  paymentMethodLabel
+};
+//# sourceMappingURL=payment-method-label.js.map

package/dist/payment-method-label.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/payment-method-label.ts"],"sourcesContent":["/**\n * A payment method in words. Card, transfer, cash, USSD and QR are said as they are; every other value\n * (a gateway's own word such as \"api\", or \"online\") reads as an online payment, because that is all it\n * tells the person looking. Nothing is guessed: an empty value is left off.\n */\nexport function paymentMethodLabel(\n  method: string | null | undefined,\n): string | null {\n  const value = (method ?? '').trim().toLowerCase().replace(/[\\s-]+/g, '_');\n\n  if (!value) return null;\n  if (value === 'card') return 'Card';\n  if (['bank_transfer', 'transfer', 'bank'].includes(value)) return 'Bank transfer';\n  if (value === 'cash') return 'Cash';\n  if (value === 'ussd') return 'USSD';\n  if (value === 'qr') return 'QR code';\n\n  return 'Online payment';\n}\n"],"mappings":"AAKO,SAAS,mBACd,QACe;AACf,QAAM,SAAS,UAAU,IAAI,KAAK,EAAE,YAAY,EAAE,QAAQ,WAAW,GAAG;AAExE,MAAI,CAAC,MAAO,QAAO;AACnB,MAAI,UAAU,OAAQ,QAAO;AAC7B,MAAI,CAAC,iBAAiB,YAAY,MAAM,EAAE,SAAS,KAAK,EAAG,QAAO;AAClE,MAAI,UAAU,OAAQ,QAAO;AAC7B,MAAI,UAAU,OAAQ,QAAO;AAC7B,MAAI,UAAU,KAAM,QAAO;AAE3B,SAAO;AACT;","names":[]}

package/dist/permission-aliases.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Dashboard permission keys the team package does not grant, and the keys it
+ * grants for the same pages.
+ *
+ * The menu and the route guard gate the website pages on editor, blog, domain
+ * and business-profile keys, and the till pages on hardware keys. The team
+ * package (api-next `packages/team`, `team-permission-features.ts`) has one
+ * feature for each instead: Website (`canViewWebsite` / `canManageWebsite`),
+ * Point of sale (`canViewPos` / `canManagePos`) and business Settings
+ * (`canManageSettings`). A staff member whose role gave them the website was
+ * still refused the Editor, Blog and Domains, and sent back to Home.
+ *
+ * A key is held when it is granted itself, or when any key it stands for is.
+ * The old keys keep working wherever an api still sends them.
+ */
+export declare const PERMISSION_ALIASES: Readonly<Record<string, readonly string[]>>;
+/** Whether `key` is granted in a permission map, directly or through its alias. */
+export declare function grantsKey(granted: Record<string, unknown>, key: string): boolean;

package/dist/permission-aliases.js

@@ -0,0 +1,20 @@
+const PERMISSION_ALIASES = {
+  canManageEditor: ["canManageWebsite"],
+  canManageBlog: ["canManageWebsite"],
+  canManageDomains: ["canManageWebsite"],
+  canManageBusinessProfile: ["canManageSettings"],
+  canViewBlog: ["canViewWebsite"],
+  canManageHardware: ["canManagePos"],
+  canViewHardware: ["canViewPos"]
+};
+function grantsKey(granted, key) {
+  if (granted[key]) return true;
+  return (PERMISSION_ALIASES[key] ?? []).some(
+    (alias) => Boolean(granted[alias])
+  );
+}
+export {
+  PERMISSION_ALIASES,
+  grantsKey
+};
+//# sourceMappingURL=permission-aliases.js.map

package/dist/permission-aliases.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/permission-aliases.ts"],"sourcesContent":["/**\n * Dashboard permission keys the team package does not grant, and the keys it\n * grants for the same pages.\n *\n * The menu and the route guard gate the website pages on editor, blog, domain\n * and business-profile keys, and the till pages on hardware keys. The team\n * package (api-next `packages/team`, `team-permission-features.ts`) has one\n * feature for each instead: Website (`canViewWebsite` / `canManageWebsite`),\n * Point of sale (`canViewPos` / `canManagePos`) and business Settings\n * (`canManageSettings`). A staff member whose role gave them the website was\n * still refused the Editor, Blog and Domains, and sent back to Home.\n *\n * A key is held when it is granted itself, or when any key it stands for is.\n * The old keys keep working wherever an api still sends them.\n */\nexport const PERMISSION_ALIASES: Readonly<Record<string, readonly string[]>> = {\n  canManageEditor: ['canManageWebsite'],\n  canManageBlog: ['canManageWebsite'],\n  canManageDomains: ['canManageWebsite'],\n  canManageBusinessProfile: ['canManageSettings'],\n  canViewBlog: ['canViewWebsite'],\n  canManageHardware: ['canManagePos'],\n  canViewHardware: ['canViewPos'],\n};\n\n/** Whether `key` is granted in a permission map, directly or through its alias. */\nexport function grantsKey(\n  granted: Record<string, unknown>,\n  key: string,\n): boolean {\n  if (granted[key]) return true;\n  return (PERMISSION_ALIASES[key] ?? []).some((alias) =>\n    Boolean(granted[alias]),\n  );\n}\n"],"mappings":"AAeO,MAAM,qBAAkE;AAAA,EAC7E,iBAAiB,CAAC,kBAAkB;AAAA,EACpC,eAAe,CAAC,kBAAkB;AAAA,EAClC,kBAAkB,CAAC,kBAAkB;AAAA,EACrC,0BAA0B,CAAC,mBAAmB;AAAA,EAC9C,aAAa,CAAC,gBAAgB;AAAA,EAC9B,mBAAmB,CAAC,cAAc;AAAA,EAClC,iBAAiB,CAAC,YAAY;AAChC;AAGO,SAAS,UACd,SACA,KACS;AACT,MAAI,QAAQ,GAAG,EAAG,QAAO;AACzB,UAAQ,mBAAmB,GAAG,KAAK,CAAC,GAAG;AAAA,IAAK,CAAC,UAC3C,QAAQ,QAAQ,KAAK,CAAC;AAAA,EACxB;AACF;","names":[]}

package/dist/permission-catalog-fallback.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Client-side fallback for the permission catalog served by
+ * `GET /team/permissions/catalog`.
+ *
+ * The api owns the canonical list (see
+ * `api/src/modules/team/permission-catalog.ts`). This file mirrors it so
+ * the role editor is usable even when the endpoint is unreachable
+ * (e.g. staging api mid-deploy, dashboard preview pointing at an older
+ * api build). If the api response differs, the api wins — this file is
+ * only consulted when the network call fails.
+ *
+ * Keys MUST stay in sync with the api's `TeamPermissions` interface.
+ */
+import type { PermissionCatalogItem, PermissionCatalogResponse } from '@withpotter/lib/api/types';
+export declare const FALLBACK_PERMISSION_CATALOG: PermissionCatalogItem[];
+export declare const FALLBACK_PERMISSION_GROUPS: string[];
+export declare const FALLBACK_PERMISSION_CATALOG_RESPONSE: PermissionCatalogResponse;