@withpotter/lib 0.13.0-next.101

package/dist/money-minor.js

@@ -0,0 +1,53 @@
+function exponentOf(currency) {
+  try {
+    return new Intl.NumberFormat("en", {
+      style: "currency",
+      currency,
+      currencyDisplay: "narrowSymbol"
+    }).resolvedOptions().maximumFractionDigits;
+  } catch {
+    return 2;
+  }
+}
+function formatMinor(minor, currency, options = {}) {
+  const negative = minor.startsWith("-");
+  const digits = (negative ? minor.slice(1) : minor).replace(/^0+(?=\d)/, "");
+  const exponent = exponentOf(currency);
+  const padded = digits.padStart(exponent + 1, "0");
+  const whole = padded.slice(0, padded.length - exponent);
+  const fraction = padded.slice(padded.length - exponent);
+  const decimal = fraction ? `${whole}.${fraction}` : whole;
+  let text;
+  try {
+    text = new Intl.NumberFormat("en", {
+      style: "currency",
+      currency,
+      currencyDisplay: "narrowSymbol"
+    }).format(decimal);
+  } catch {
+    text = `${currency} ${decimal}`;
+  }
+  if (options.trimZeros) text = text.replace(/[.,]0+(?=\D*$)/, "");
+  return negative ? `-${text}` : text;
+}
+function parseMajorToMinor(input, currency) {
+  const text = input.replace(/,/g, "").trim();
+  if (!/^\d+(\.\d+)?$/.test(text)) return null;
+  const exponent = exponentOf(currency);
+  const [whole, fraction = ""] = text.split(".");
+  if (fraction.length > exponent) return null;
+  const minor = (whole + fraction.padEnd(exponent, "0")).replace(
+    /^0+(?=\d)/,
+    ""
+  );
+  return /^0+$/.test(minor) ? null : minor;
+}
+function sumMinor(values) {
+  return values.reduce((total, v) => total + BigInt(v), BigInt(0)).toString();
+}
+export {
+  formatMinor,
+  parseMajorToMinor,
+  sumMinor
+};
+//# sourceMappingURL=money-minor.js.map

package/dist/money-minor.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/money-minor.ts"],"sourcesContent":["/**\n * Minor-unit strings to display text, without ever becoming a float.\n *\n * The wallet ledger is bigint and the API sends amounts as decimal strings.\n * `Number(\"9007199254740993\")` is 9007199254740992, so the conversion splits\n * the digits at the currency's exponent and hands Intl a decimal STRING, which\n * it formats exactly. The exponent comes from Intl itself (₦ and $ are 2, ¥ is\n * 0, د.ك is 3), so a new currency needs no table here.\n */\nfunction exponentOf(currency: string): number {\n  try {\n    return new Intl.NumberFormat('en', {\n      style: 'currency',\n      currency,\n      currencyDisplay: 'narrowSymbol',\n    }).resolvedOptions().maximumFractionDigits as number;\n  } catch {\n    // Not an ISO code Intl knows. Two is the ledger's overwhelming case.\n    return 2;\n  }\n}\n\nexport function formatMinor(\n  minor: string,\n  currency: string,\n  options: { trimZeros?: boolean } = {},\n): string {\n  const negative = minor.startsWith('-');\n  const digits = (negative ? minor.slice(1) : minor).replace(/^0+(?=\\d)/, '');\n  const exponent = exponentOf(currency);\n  const padded = digits.padStart(exponent + 1, '0');\n  const whole = padded.slice(0, padded.length - exponent);\n  const fraction = padded.slice(padded.length - exponent);\n  const decimal = fraction ? `${whole}.${fraction}` : whole;\n\n  let text: string;\n  try {\n    // Intl accepts a decimal string and formats it without a Number round trip.\n    text = new Intl.NumberFormat('en', {\n      style: 'currency',\n      currency,\n      currencyDisplay: 'narrowSymbol',\n    }).format(decimal as unknown as number);\n  } catch {\n    text = `${currency} ${decimal}`;\n  }\n  // A whole amount reads as ₦245,000, not ₦245,000.00; one with kobo keeps them.\n  if (options.trimZeros) text = text.replace(/[.,]0+(?=\\D*$)/, '');\n\n  return negative ? `-${text}` : text;\n}\n\n/**\n * What a person typed (\"1,500.5\") to the minor-unit string the API takes.\n *\n * Digit arithmetic, not `Number(x) * 100`: 19.99 * 100 is 1998.9999999999998.\n * Returns null for anything that is not a positive amount with no more decimals\n * than the currency has, so the caller can say so instead of rounding someone's\n * money.\n */\nexport function parseMajorToMinor(\n  input: string,\n  currency: string,\n): string | null {\n  const text = input.replace(/,/g, '').trim();\n  if (!/^\\d+(\\.\\d+)?$/.test(text)) return null;\n  const exponent = exponentOf(currency);\n  const [whole, fraction = ''] = text.split('.');\n  if (fraction.length > exponent) return null;\n  const minor = (whole + fraction.padEnd(exponent, '0')).replace(\n    /^0+(?=\\d)/,\n    '',\n  );\n  return /^0+$/.test(minor) ? null : minor;\n}\n\n/**\n * Minor-unit strings added as bigints, never as floats: the ledger's amounts go\n * up to 19 digits, past where a JS number stops being exact.\n */\nexport function sumMinor(values: readonly string[]): string {\n  return values.reduce((total, v) => total + BigInt(v), BigInt(0)).toString();\n}\n"],"mappings":"AASA,SAAS,WAAW,UAA0B;AAC5C,MAAI;AACF,WAAO,IAAI,KAAK,aAAa,MAAM;AAAA,MACjC,OAAO;AAAA,MACP;AAAA,MACA,iBAAiB;AAAA,IACnB,CAAC,EAAE,gBAAgB,EAAE;AAAA,EACvB,QAAQ;AAEN,WAAO;AAAA,EACT;AACF;AAEO,SAAS,YACd,OACA,UACA,UAAmC,CAAC,GAC5B;AACR,QAAM,WAAW,MAAM,WAAW,GAAG;AACrC,QAAM,UAAU,WAAW,MAAM,MAAM,CAAC,IAAI,OAAO,QAAQ,aAAa,EAAE;AAC1E,QAAM,WAAW,WAAW,QAAQ;AACpC,QAAM,SAAS,OAAO,SAAS,WAAW,GAAG,GAAG;AAChD,QAAM,QAAQ,OAAO,MAAM,GAAG,OAAO,SAAS,QAAQ;AACtD,QAAM,WAAW,OAAO,MAAM,OAAO,SAAS,QAAQ;AACtD,QAAM,UAAU,WAAW,GAAG,KAAK,IAAI,QAAQ,KAAK;AAEpD,MAAI;AACJ,MAAI;AAEF,WAAO,IAAI,KAAK,aAAa,MAAM;AAAA,MACjC,OAAO;AAAA,MACP;AAAA,MACA,iBAAiB;AAAA,IACnB,CAAC,EAAE,OAAO,OAA4B;AAAA,EACxC,QAAQ;AACN,WAAO,GAAG,QAAQ,IAAI,OAAO;AAAA,EAC/B;AAEA,MAAI,QAAQ,UAAW,QAAO,KAAK,QAAQ,kBAAkB,EAAE;AAE/D,SAAO,WAAW,IAAI,IAAI,KAAK;AACjC;AAUO,SAAS,kBACd,OACA,UACe;AACf,QAAM,OAAO,MAAM,QAAQ,MAAM,EAAE,EAAE,KAAK;AAC1C,MAAI,CAAC,gBAAgB,KAAK,IAAI,EAAG,QAAO;AACxC,QAAM,WAAW,WAAW,QAAQ;AACpC,QAAM,CAAC,OAAO,WAAW,EAAE,IAAI,KAAK,MAAM,GAAG;AAC7C,MAAI,SAAS,SAAS,SAAU,QAAO;AACvC,QAAM,SAAS,QAAQ,SAAS,OAAO,UAAU,GAAG,GAAG;AAAA,IACrD;AAAA,IACA;AAAA,EACF;AACA,SAAO,OAAO,KAAK,KAAK,IAAI,OAAO;AACrC;AAMO,SAAS,SAAS,QAAmC;AAC1D,SAAO,OAAO,OAAO,CAAC,OAAO,MAAM,QAAQ,OAAO,CAAC,GAAG,OAAO,CAAC,CAAC,EAAE,SAAS;AAC5E;","names":[]}

package/dist/money-visibility.d.ts

@@ -0,0 +1,38 @@
+import type { PermissionKey } from './use-permissions';
+/**
+ * Whether this person is allowed to see money, split into the two questions a
+ * merchant actually asks separately.
+ *
+ * When this was one switch, the two getters below resolved to the same
+ * permission and the comment said splitting them was a later problem. The Today
+ * screen settled it. `RecordPaymentModal` is how a desk person takes payment,
+ * and it needs the amount owed. Front desk — the preset whose whole description
+ * is "takes bookings, checks people in" — holds `canViewFinance: false`, so
+ * gating that modal on finance would have broken the exact role it exists for.
+ *
+ * The line is not "how much money" but WHOSE:
+ *
+ *   amounts   the value of a transaction in front of you. What this booking
+ *             costs, what this order came to, what is owed on this invoice.
+ *             Anyone trusted to see an order is trusted to see its total —
+ *             a total is part of an order, not a separate secret — so this
+ *             follows the orders grant.
+ *
+ *   earnings  the state of the business's money. Revenue, payouts, the
+ *             settlement balance, average sale. This is the grant
+ *             MONEY_PERMISSIONS exists to keep out of a job preset, and it
+ *             stays on canViewFinance alone.
+ *
+ * A front desk can therefore charge ₦10,000 for court 1 and still not know what
+ * the club took last month, which is exactly what the role description promises.
+ *
+ * Kept as a pure function so it can be tested against the real presets without
+ * a React renderer; `useMoneyVisibility` is the thin hook over it.
+ */
+export interface MoneyVisibility {
+    /** Order totals, line prices, invoice amounts, what is owed right now. */
+    canSeeAmounts: boolean;
+    /** Revenue, payouts, balances — the state of the business's money. */
+    canSeeEarnings: boolean;
+}
+export declare function resolveMoneyVisibility(can: (permission: PermissionKey) => boolean): MoneyVisibility;

package/dist/money-visibility.js

@@ -0,0 +1,13 @@
+function resolveMoneyVisibility(can) {
+  const canSeeEarnings = can("canViewFinance");
+  return {
+    // Finance implies amounts: someone who can see the payout account is not
+    // then hidden from an order total.
+    canSeeAmounts: canSeeEarnings || can("canViewOrders"),
+    canSeeEarnings
+  };
+}
+export {
+  resolveMoneyVisibility
+};
+//# sourceMappingURL=money-visibility.js.map

package/dist/money-visibility.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/money-visibility.ts"],"sourcesContent":["import type { PermissionKey } from './use-permissions';\n\n/**\n * Whether this person is allowed to see money, split into the two questions a\n * merchant actually asks separately.\n *\n * When this was one switch, the two getters below resolved to the same\n * permission and the comment said splitting them was a later problem. The Today\n * screen settled it. `RecordPaymentModal` is how a desk person takes payment,\n * and it needs the amount owed. Front desk — the preset whose whole description\n * is \"takes bookings, checks people in\" — holds `canViewFinance: false`, so\n * gating that modal on finance would have broken the exact role it exists for.\n *\n * The line is not \"how much money\" but WHOSE:\n *\n *   amounts   the value of a transaction in front of you. What this booking\n *             costs, what this order came to, what is owed on this invoice.\n *             Anyone trusted to see an order is trusted to see its total —\n *             a total is part of an order, not a separate secret — so this\n *             follows the orders grant.\n *\n *   earnings  the state of the business's money. Revenue, payouts, the\n *             settlement balance, average sale. This is the grant\n *             MONEY_PERMISSIONS exists to keep out of a job preset, and it\n *             stays on canViewFinance alone.\n *\n * A front desk can therefore charge ₦10,000 for court 1 and still not know what\n * the club took last month, which is exactly what the role description promises.\n *\n * Kept as a pure function so it can be tested against the real presets without\n * a React renderer; `useMoneyVisibility` is the thin hook over it.\n */\nexport interface MoneyVisibility {\n  /** Order totals, line prices, invoice amounts, what is owed right now. */\n  canSeeAmounts: boolean;\n  /** Revenue, payouts, balances — the state of the business's money. */\n  canSeeEarnings: boolean;\n}\n\nexport function resolveMoneyVisibility(\n  can: (permission: PermissionKey) => boolean,\n): MoneyVisibility {\n  const canSeeEarnings = can('canViewFinance');\n\n  return {\n    // Finance implies amounts: someone who can see the payout account is not\n    // then hidden from an order total.\n    canSeeAmounts: canSeeEarnings || can('canViewOrders'),\n    canSeeEarnings,\n  };\n}\n"],"mappings":"AAuCO,SAAS,uBACd,KACiB;AACjB,QAAM,iBAAiB,IAAI,gBAAgB;AAE3C,SAAO;AAAA;AAAA;AAAA,IAGL,eAAe,kBAAkB,IAAI,eAAe;AAAA,IACpD;AAAA,EACF;AACF;","names":[]}

package/dist/motion.d.ts

@@ -0,0 +1,160 @@
+/**
+ * Motion system.
+ *
+ * ONE source of truth for how things move. Spring values, durations and easings
+ * are defined here and mirrored into CSS custom properties in globals.css
+ * (`--motion-*`), so a component animating in JS and a component animating in
+ * CSS agree by construction rather than by memory.
+ *
+ * ---------------------------------------------------------------------------
+ * WHICH TOOL FOR WHICH JOB
+ *
+ * CSS transition (`transition-colors`, `--motion-fast`) — the default.
+ *   Hover, focus, colour, opacity, small state flips. Cheap, no JS, no bundle.
+ *   Reach for this first; most of the app should never touch a spring.
+ *
+ * Spring (`springs.*`, this file) — only for things that MOVE.
+ *   Sheets, drawers, popovers, drag, list reorder, anything a user can grab or
+ *   interrupt. A spring carries velocity, so an interaction reversed halfway
+ *   continues from where it is instead of snapping or restarting. That is the
+ *   one thing CSS transitions structurally cannot do, and the only reason this
+ *   dependency is here.
+ *
+ * Neither — most of the app.
+ *   Both design docs are explicit. POTTER_BRAND_DIRECTION.md §11: "purposeful,
+ *   <=300ms, physical; craft not flash." potter-console DESIGN-LANGUAGE.md:
+ *   "motion never load-bearing." If motion carries meaning that the layout does
+ *   not already carry, the layout is wrong.
+ * ---------------------------------------------------------------------------
+ */
+import type { Variants } from 'motion/react';
+/**
+ * Retuned 2026-08-21 so the 300ms ceiling means one thing.
+ *
+ * The ceiling is declared on `durations` and a spring does not read it, so two
+ * presets finished after the limit the system sets for itself: `soft` settled
+ * at 333ms and `bouncy` at 400ms. Both now land at 296ms and 300ms with their
+ * character held — damping ratio is what carries the feel, and it is unchanged
+ * to three decimals. `bouncy` keeps its 19.7% overshoot, which is the whole
+ * point of it; it simply stopped being the slowest thing in the product.
+ *
+ * The house sits at ζ ≈ 0.8: underdamped, so things arrive with weight rather
+ * than stopping dead, overshooting about one percent, which you feel and do
+ * not see. `bouncy` at ζ 0.46 is the deliberate exception.
+ */
+export declare const springs: {
+    /** Snappy, minimal overshoot. Buttons, toggles, small controls. (fast) */
+    snappy: {
+        type: "spring";
+        stiffness: number;
+        damping: number;
+        mass: number;
+    };
+    /** Default surface motion. Cards, panels, sheets, page blocks. (moderate) */
+    gentle: {
+        type: "spring";
+        stiffness: number;
+        damping: number;
+        mass: number;
+    };
+    /** Soft settle with a touch of life. Hero / featured arrivals. (slow) */
+    soft: {
+        type: "spring";
+        stiffness: number;
+        damping: number;
+        mass: number;
+    };
+    /**
+     * Visible overshoot — a spring that pops and settles. For deliberate delight
+     * only (a milestone, a successful pop-in). "Motion that communicates"
+     * (Fluid Functionalism): use where the bounce means something, not by default.
+     */
+    bouncy: {
+        type: "spring";
+        stiffness: number;
+        damping: number;
+        mass: number;
+    };
+};
+export type SpringName = keyof typeof springs;
+export declare const durations: {
+    /** Press feedback, checkbox flips. */
+    readonly instant: 0.1;
+    /** Hover, focus, colour. The workhorse. */
+    readonly fast: 0.12;
+    /** Route/opacity fades. */
+    readonly normal: 0.18;
+    /** The ceiling. Brand direction says nothing exceeds 300ms. */
+    readonly slow: 0.3;
+};
+/**
+ * Curated easing curves (from easing.dev), mirrored to CSS as
+ * `--motion-ease-*`. A small named set, not the whole gallery: each earns its
+ * place. Reach for `out` by default; the rest are for a specific feel.
+ */
+export declare const eases: {
+    /** Standard decelerate. Things arrive and stop. The default. */
+    readonly out: readonly [0, 0, 0.2, 1];
+    /** Expo-out. A weighted settle — comes to rest rather than popping. */
+    readonly settle: readonly [0.16, 1, 0.3, 1];
+    /** Quart-out. Quick off the mark, smooth arrival. Menus, popovers. */
+    readonly quart: readonly [0.25, 1, 0.5, 1];
+    /** Circ-out. Hangs, then finishes fast. Reveals with a little drama. */
+    readonly circ: readonly [0, 0.55, 0.45, 1];
+    /** Symmetric swift in-out (Material). Moves that travel both ways. */
+    readonly swift: readonly [0.4, 0, 0.2, 1];
+    /** In-out expo. Dramatic, decisive. Big spatial moves only. */
+    readonly emphasize: readonly [0.87, 0, 0.13, 1];
+    /** Back-out. A small overshoot pop. Playful confirmations. */
+    readonly overshoot: readonly [0.34, 1.56, 0.64, 1];
+    /** In-back. Pulls back before it goes — draws the eye first. */
+    readonly anticipate: readonly [0.36, 0, 0.66, -0.56];
+};
+export declare const revealVariants: Variants;
+/** Press feedback. Matches console's `.ui-btn:active { transform: scale(.985) }`. */
+export declare const PRESS_SCALE = 0.985;
+/**
+ * The deeper press, for anything where 0.985 reads as nothing.
+ *
+ * "Large" is the press, not the element. Two different shapes need it for
+ * opposite reasons and both were inventing their own number: a card or tile is
+ * big enough that one and a half percent is lost in it, and a 36px round icon
+ * button is small enough that the same percentage is half a pixel. Nine sites
+ * had five values between them — 0.92, 0.94, 0.97, 0.985, 0.99 — for one
+ * gesture, so a workspace card and a template tile beside it answered the same
+ * press differently.
+ */
+export declare const PRESS_SCALE_LARGE = 0.97;
+export declare const step: {
+    readonly duration: 0.22;
+    /** Arriving. Decelerates into place. */
+    readonly easeOut: readonly [0.4, 0, 0.2, 1];
+    /** Leaving. Accelerates away. */
+    readonly easeIn: readonly [0.4, 0, 1, 1];
+    /** How far a screen scales when it is not the one you are looking at. */
+    readonly scaleDistance: 0.97;
+};
+export type StepDirection = 'forward' | 'back';
+/** Direction-aware enter/exit for a whole step. */
+export declare const stepVariants: Variants;
+export declare const pipeline: {
+    readonly duration: 0.2;
+    /** How far the arriving list travels. Any further reads as a page change. */
+    readonly travel: 10;
+};
+/** -1 when the new reading sits above the old one in the rail, +1 below. */
+export type PipelineDirection = -1 | 1;
+export declare const pipelineVariants: Variants;
+/** First-load stagger. The column arrives in reading order, once. */
+export declare const columnVariants: Variants;
+export declare const columnItemVariants: Variants;
+/**
+ * Entrance for each section of the home board, staggered by its container.
+ *
+ * It lived in `dashboard/page.tsx` with its curve written out as
+ * `[0.22, 1, 0.36, 1]` — a hand-typed cubic-bezier, which is the one thing the
+ * motion rule names outright, and a fourth curve in a system that has three.
+ * `eases.settle` is the same shape and is the one every other arrival in this
+ * product already uses.
+ */
+export declare const homeRise: Variants;

package/dist/motion.js

@@ -0,0 +1,130 @@
+const springs = {
+  /** Snappy, minimal overshoot. Buttons, toggles, small controls. (fast) */
+  snappy: { type: "spring", stiffness: 520, damping: 34, mass: 0.9 },
+  /** Default surface motion. Cards, panels, sheets, page blocks. (moderate) */
+  gentle: { type: "spring", stiffness: 320, damping: 30, mass: 1 },
+  /** Soft settle with a touch of life. Hero / featured arrivals. (slow) */
+  soft: { type: "spring", stiffness: 260, damping: 27, mass: 1 },
+  /**
+   * Visible overshoot — a spring that pops and settles. For deliberate delight
+   * only (a milestone, a successful pop-in). "Motion that communicates"
+   * (Fluid Functionalism): use where the bounce means something, not by default.
+   */
+  bouncy: { type: "spring", stiffness: 760, damping: 24, mass: 0.9 }
+};
+const durations = {
+  /** Press feedback, checkbox flips. */
+  instant: 0.1,
+  /** Hover, focus, colour. The workhorse. */
+  fast: 0.12,
+  /** Route/opacity fades. */
+  normal: 0.18,
+  /** The ceiling. Brand direction says nothing exceeds 300ms. */
+  slow: 0.3
+};
+const eases = {
+  /** Standard decelerate. Things arrive and stop. The default. */
+  out: [0, 0, 0.2, 1],
+  /** Expo-out. A weighted settle — comes to rest rather than popping. */
+  settle: [0.16, 1, 0.3, 1],
+  /** Quart-out. Quick off the mark, smooth arrival. Menus, popovers. */
+  quart: [0.25, 1, 0.5, 1],
+  /** Circ-out. Hangs, then finishes fast. Reveals with a little drama. */
+  circ: [0, 0.55, 0.45, 1],
+  /** Symmetric swift in-out (Material). Moves that travel both ways. */
+  swift: [0.4, 0, 0.2, 1],
+  /** In-out expo. Dramatic, decisive. Big spatial moves only. */
+  emphasize: [0.87, 0, 0.13, 1],
+  /** Back-out. A small overshoot pop. Playful confirmations. */
+  overshoot: [0.34, 1.56, 0.64, 1],
+  /** In-back. Pulls back before it goes — draws the eye first. */
+  anticipate: [0.36, 0, 0.66, -0.56]
+};
+const revealVariants = {
+  hidden: { opacity: 0, y: 14 },
+  shown: { opacity: 1, y: 0 }
+};
+const PRESS_SCALE = 0.985;
+const PRESS_SCALE_LARGE = 0.97;
+const step = {
+  duration: 0.22,
+  /** Arriving. Decelerates into place. */
+  easeOut: [0.4, 0, 0.2, 1],
+  /** Leaving. Accelerates away. */
+  easeIn: [0.4, 0, 1, 1],
+  /** How far a screen scales when it is not the one you are looking at. */
+  scaleDistance: 0.97
+};
+const stepVariants = {
+  enter: (direction) => ({
+    opacity: 0,
+    scale: direction === "forward" ? step.scaleDistance : 1
+  }),
+  center: {
+    opacity: 1,
+    scale: 1,
+    transition: { duration: step.duration, ease: step.easeOut }
+  },
+  exit: (direction) => ({
+    opacity: 0,
+    scale: direction === "forward" ? 1 : step.scaleDistance,
+    transition: { duration: step.duration, ease: step.easeIn }
+  })
+};
+const pipeline = {
+  duration: 0.2,
+  /** How far the arriving list travels. Any further reads as a page change. */
+  travel: 10
+};
+const pipelineVariants = {
+  enter: (direction) => ({
+    opacity: 0,
+    y: direction * pipeline.travel
+  }),
+  center: {
+    opacity: 1,
+    y: 0,
+    transition: { duration: pipeline.duration, ease: step.easeOut }
+  },
+  exit: (direction) => ({
+    opacity: 0,
+    y: direction * -pipeline.travel,
+    transition: { duration: pipeline.duration, ease: step.easeIn }
+  })
+};
+const columnVariants = {
+  hidden: {},
+  shown: { transition: { staggerChildren: 0.07, delayChildren: 0.04 } }
+};
+const columnItemVariants = {
+  hidden: { opacity: 0, y: 10 },
+  shown: {
+    opacity: 1,
+    y: 0,
+    transition: { duration: 0.45, ease: eases.settle }
+  }
+};
+const homeRise = {
+  hidden: { opacity: 0, y: 10 },
+  show: {
+    opacity: 1,
+    y: 0,
+    transition: { duration: 0.32, ease: eases.settle }
+  }
+};
+export {
+  PRESS_SCALE,
+  PRESS_SCALE_LARGE,
+  columnItemVariants,
+  columnVariants,
+  durations,
+  eases,
+  homeRise,
+  pipeline,
+  pipelineVariants,
+  revealVariants,
+  springs,
+  step,
+  stepVariants
+};
+//# sourceMappingURL=motion.js.map

package/dist/motion.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/motion.ts"],"sourcesContent":["/**\n * Motion system.\n *\n * ONE source of truth for how things move. Spring values, durations and easings\n * are defined here and mirrored into CSS custom properties in globals.css\n * (`--motion-*`), so a component animating in JS and a component animating in\n * CSS agree by construction rather than by memory.\n *\n * ---------------------------------------------------------------------------\n * WHICH TOOL FOR WHICH JOB\n *\n * CSS transition (`transition-colors`, `--motion-fast`) — the default.\n *   Hover, focus, colour, opacity, small state flips. Cheap, no JS, no bundle.\n *   Reach for this first; most of the app should never touch a spring.\n *\n * Spring (`springs.*`, this file) — only for things that MOVE.\n *   Sheets, drawers, popovers, drag, list reorder, anything a user can grab or\n *   interrupt. A spring carries velocity, so an interaction reversed halfway\n *   continues from where it is instead of snapping or restarting. That is the\n *   one thing CSS transitions structurally cannot do, and the only reason this\n *   dependency is here.\n *\n * Neither — most of the app.\n *   Both design docs are explicit. POTTER_BRAND_DIRECTION.md §11: \"purposeful,\n *   <=300ms, physical; craft not flash.\" potter-console DESIGN-LANGUAGE.md:\n *   \"motion never load-bearing.\" If motion carries meaning that the layout does\n *   not already carry, the layout is wrong.\n * ---------------------------------------------------------------------------\n */\nimport type { Transition, Variants } from 'motion/react';\n\n/* -------------------------------------------------------------------------\n   Springs — ported verbatim from potter-console/src/motion.tsx so the two\n   codebases feel identical. Do not tune these per call site; add a preset.\n   ------------------------------------------------------------------------- */\n/**\n * Retuned 2026-08-21 so the 300ms ceiling means one thing.\n *\n * The ceiling is declared on `durations` and a spring does not read it, so two\n * presets finished after the limit the system sets for itself: `soft` settled\n * at 333ms and `bouncy` at 400ms. Both now land at 296ms and 300ms with their\n * character held — damping ratio is what carries the feel, and it is unchanged\n * to three decimals. `bouncy` keeps its 19.7% overshoot, which is the whole\n * point of it; it simply stopped being the slowest thing in the product.\n *\n * The house sits at ζ ≈ 0.8: underdamped, so things arrive with weight rather\n * than stopping dead, overshooting about one percent, which you feel and do\n * not see. `bouncy` at ζ 0.46 is the deliberate exception.\n */\nexport const springs = {\n  /** Snappy, minimal overshoot. Buttons, toggles, small controls. (fast) */\n  snappy: { type: 'spring', stiffness: 520, damping: 34, mass: 0.9 },\n  /** Default surface motion. Cards, panels, sheets, page blocks. (moderate) */\n  gentle: { type: 'spring', stiffness: 320, damping: 30, mass: 1 },\n  /** Soft settle with a touch of life. Hero / featured arrivals. (slow) */\n  soft: { type: 'spring', stiffness: 260, damping: 27, mass: 1 },\n  /**\n   * Visible overshoot — a spring that pops and settles. For deliberate delight\n   * only (a milestone, a successful pop-in). \"Motion that communicates\"\n   * (Fluid Functionalism): use where the bounce means something, not by default.\n   */\n  bouncy: { type: 'spring', stiffness: 760, damping: 24, mass: 0.9 },\n} satisfies Record<string, Transition>;\n\nexport type SpringName = keyof typeof springs;\n\n/* -------------------------------------------------------------------------\n   Durations + easings (seconds; CSS mirrors these in ms as --motion-*).\n   ------------------------------------------------------------------------- */\nexport const durations = {\n  /** Press feedback, checkbox flips. */\n  instant: 0.1,\n  /** Hover, focus, colour. The workhorse. */\n  fast: 0.12,\n  /** Route/opacity fades. */\n  normal: 0.18,\n  /** The ceiling. Brand direction says nothing exceeds 300ms. */\n  slow: 0.3,\n} as const;\n\n/**\n * Curated easing curves (from easing.dev), mirrored to CSS as\n * `--motion-ease-*`. A small named set, not the whole gallery: each earns its\n * place. Reach for `out` by default; the rest are for a specific feel.\n */\nexport const eases = {\n  /** Standard decelerate. Things arrive and stop. The default. */\n  out: [0, 0, 0.2, 1],\n  /** Expo-out. A weighted settle — comes to rest rather than popping. */\n  settle: [0.16, 1, 0.3, 1],\n  /** Quart-out. Quick off the mark, smooth arrival. Menus, popovers. */\n  quart: [0.25, 1, 0.5, 1],\n  /** Circ-out. Hangs, then finishes fast. Reveals with a little drama. */\n  circ: [0, 0.55, 0.45, 1],\n  /** Symmetric swift in-out (Material). Moves that travel both ways. */\n  swift: [0.4, 0, 0.2, 1],\n  /** In-out expo. Dramatic, decisive. Big spatial moves only. */\n  emphasize: [0.87, 0, 0.13, 1],\n  /** Back-out. A small overshoot pop. Playful confirmations. */\n  overshoot: [0.34, 1.56, 0.64, 1],\n  /** In-back. Pulls back before it goes — draws the eye first. */\n  anticipate: [0.36, 0, 0.66, -0.56],\n} as const;\n\n/* -------------------------------------------------------------------------\n   Shared variants.\n   ------------------------------------------------------------------------- */\nexport const revealVariants: Variants = {\n  hidden: { opacity: 0, y: 14 },\n  shown: { opacity: 1, y: 0 },\n};\n\n/** Press feedback. Matches console's `.ui-btn:active { transform: scale(.985) }`. */\nexport const PRESS_SCALE = 0.985;\n\n/**\n * The deeper press, for anything where 0.985 reads as nothing.\n *\n * \"Large\" is the press, not the element. Two different shapes need it for\n * opposite reasons and both were inventing their own number: a card or tile is\n * big enough that one and a half percent is lost in it, and a 36px round icon\n * button is small enough that the same percentage is half a pixel. Nine sites\n * had five values between them — 0.92, 0.94, 0.97, 0.985, 0.99 — for one\n * gesture, so a workspace card and a template tile beside it answered the same\n * press differently.\n */\nexport const PRESS_SCALE_LARGE = 0.97;\n\n/* -------------------------------------------------------------------------\n   Step choreography — onboarding and any other forward/back flow.\n\n   Measured off MetaMask's onboarding (docs/METAMASK_ONBOARDING_MOTION.md) and\n   retuned for Box. Two ideas are taken and one is rejected.\n\n   Taken: forward and back are NOT symmetric. Going forward the arriving screen\n   grows into place from `scaleDistance`; going back the leaving screen shrinks\n   away to it. Depth is implied by three percent of scale and nothing else, so\n   the direction of travel is legible without a slide.\n\n   Taken: sequencing gated on readiness rather than on guessed delays. The art\n   leads, and the column follows when the image has actually decoded.\n\n   Rejected: their 180ms. A wallet popup is fast because speed is the product;\n   this is two considered questions beside a photograph. 220ms sits between our\n   `normal` and `slow` and still reads as responsiveness rather than animation.\n   ------------------------------------------------------------------------- */\nexport const step = {\n  duration: 0.22,\n  /** Arriving. Decelerates into place. */\n  easeOut: [0.4, 0, 0.2, 1],\n  /** Leaving. Accelerates away. */\n  easeIn: [0.4, 0, 1, 1],\n  /** How far a screen scales when it is not the one you are looking at. */\n  scaleDistance: 0.97,\n} as const;\n\nexport type StepDirection = 'forward' | 'back';\n\n/** Direction-aware enter/exit for a whole step. */\nexport const stepVariants: Variants = {\n  enter: (direction: StepDirection) => ({\n    opacity: 0,\n    scale: direction === 'forward' ? step.scaleDistance : 1,\n  }),\n  center: {\n    opacity: 1,\n    scale: 1,\n    transition: { duration: step.duration, ease: step.easeOut },\n  },\n  exit: (direction: StepDirection) => ({\n    opacity: 0,\n    scale: direction === 'forward' ? 1 : step.scaleDistance,\n    transition: { duration: step.duration, ease: step.easeIn },\n  }),\n};\n\n/* -------------------------------------------------------------------------\n   Pipeline choreography — a rail of readings beside the list each one opens.\n\n   Taken from Family's design doctrine (benji.org/family-values), whose rule is\n   that motion is architectural: \"each animation serves a purpose from an\n   architectural perspective, aiding users in understanding their path from\n   A → B\", and directional motion mirrors the user's action — tap something to\n   the left, the content arrives from the left.\n\n   A reading rail is a VERTICAL column, so the axis is vertical: press a reading\n   further down the pipeline and the list it opens arrives from below. That makes\n   the rail's order mean something. Cross-fading instead says the two lists are\n   unrelated views, which is the one thing a pipeline is not.\n\n   Deliberately small. This fires on a control a merchant presses all day, and\n   Family's own rule for frequently used surfaces is little things, never a\n   performance: \"doing too much would quickly diminish potential delight\".\n   ------------------------------------------------------------------------- */\nexport const pipeline = {\n  duration: 0.2,\n  /** How far the arriving list travels. Any further reads as a page change. */\n  travel: 10,\n} as const;\n\n/** -1 when the new reading sits above the old one in the rail, +1 below. */\nexport type PipelineDirection = -1 | 1;\n\nexport const pipelineVariants: Variants = {\n  enter: (direction: PipelineDirection) => ({\n    opacity: 0,\n    y: direction * pipeline.travel,\n  }),\n  center: {\n    opacity: 1,\n    y: 0,\n    transition: { duration: pipeline.duration, ease: step.easeOut },\n  },\n  exit: (direction: PipelineDirection) => ({\n    opacity: 0,\n    y: direction * -pipeline.travel,\n    transition: { duration: pipeline.duration, ease: step.easeIn },\n  }),\n};\n\n/** First-load stagger. The column arrives in reading order, once. */\nexport const columnVariants: Variants = {\n  hidden: {},\n  shown: { transition: { staggerChildren: 0.07, delayChildren: 0.04 } },\n};\n\nexport const columnItemVariants: Variants = {\n  hidden: { opacity: 0, y: 10 },\n  shown: {\n    opacity: 1,\n    y: 0,\n    transition: { duration: 0.45, ease: eases.settle },\n  },\n};\n\n/**\n * Entrance for each section of the home board, staggered by its container.\n *\n * It lived in `dashboard/page.tsx` with its curve written out as\n * `[0.22, 1, 0.36, 1]` — a hand-typed cubic-bezier, which is the one thing the\n * motion rule names outright, and a fourth curve in a system that has three.\n * `eases.settle` is the same shape and is the one every other arrival in this\n * product already uses.\n */\nexport const homeRise: Variants = {\n  hidden: { opacity: 0, y: 10 },\n  show: {\n    opacity: 1,\n    y: 0,\n    transition: { duration: 0.32, ease: eases.settle },\n  },\n};\n"],"mappings":"AAiDO,MAAM,UAAU;AAAA;AAAA,EAErB,QAAQ,EAAE,MAAM,UAAU,WAAW,KAAK,SAAS,IAAI,MAAM,IAAI;AAAA;AAAA,EAEjE,QAAQ,EAAE,MAAM,UAAU,WAAW,KAAK,SAAS,IAAI,MAAM,EAAE;AAAA;AAAA,EAE/D,MAAM,EAAE,MAAM,UAAU,WAAW,KAAK,SAAS,IAAI,MAAM,EAAE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAM7D,QAAQ,EAAE,MAAM,UAAU,WAAW,KAAK,SAAS,IAAI,MAAM,IAAI;AACnE;AAOO,MAAM,YAAY;AAAA;AAAA,EAEvB,SAAS;AAAA;AAAA,EAET,MAAM;AAAA;AAAA,EAEN,QAAQ;AAAA;AAAA,EAER,MAAM;AACR;AAOO,MAAM,QAAQ;AAAA;AAAA,EAEnB,KAAK,CAAC,GAAG,GAAG,KAAK,CAAC;AAAA;AAAA,EAElB,QAAQ,CAAC,MAAM,GAAG,KAAK,CAAC;AAAA;AAAA,EAExB,OAAO,CAAC,MAAM,GAAG,KAAK,CAAC;AAAA;AAAA,EAEvB,MAAM,CAAC,GAAG,MAAM,MAAM,CAAC;AAAA;AAAA,EAEvB,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC;AAAA;AAAA,EAEtB,WAAW,CAAC,MAAM,GAAG,MAAM,CAAC;AAAA;AAAA,EAE5B,WAAW,CAAC,MAAM,MAAM,MAAM,CAAC;AAAA;AAAA,EAE/B,YAAY,CAAC,MAAM,GAAG,MAAM,KAAK;AACnC;AAKO,MAAM,iBAA2B;AAAA,EACtC,QAAQ,EAAE,SAAS,GAAG,GAAG,GAAG;AAAA,EAC5B,OAAO,EAAE,SAAS,GAAG,GAAG,EAAE;AAC5B;AAGO,MAAM,cAAc;AAapB,MAAM,oBAAoB;AAoB1B,MAAM,OAAO;AAAA,EAClB,UAAU;AAAA;AAAA,EAEV,SAAS,CAAC,KAAK,GAAG,KAAK,CAAC;AAAA;AAAA,EAExB,QAAQ,CAAC,KAAK,GAAG,GAAG,CAAC;AAAA;AAAA,EAErB,eAAe;AACjB;AAKO,MAAM,eAAyB;AAAA,EACpC,OAAO,CAAC,eAA8B;AAAA,IACpC,SAAS;AAAA,IACT,OAAO,cAAc,YAAY,KAAK,gBAAgB;AAAA,EACxD;AAAA,EACA,QAAQ;AAAA,IACN,SAAS;AAAA,IACT,OAAO;AAAA,IACP,YAAY,EAAE,UAAU,KAAK,UAAU,MAAM,KAAK,QAAQ;AAAA,EAC5D;AAAA,EACA,MAAM,CAAC,eAA8B;AAAA,IACnC,SAAS;AAAA,IACT,OAAO,cAAc,YAAY,IAAI,KAAK;AAAA,IAC1C,YAAY,EAAE,UAAU,KAAK,UAAU,MAAM,KAAK,OAAO;AAAA,EAC3D;AACF;AAoBO,MAAM,WAAW;AAAA,EACtB,UAAU;AAAA;AAAA,EAEV,QAAQ;AACV;AAKO,MAAM,mBAA6B;AAAA,EACxC,OAAO,CAAC,eAAkC;AAAA,IACxC,SAAS;AAAA,IACT,GAAG,YAAY,SAAS;AAAA,EAC1B;AAAA,EACA,QAAQ;AAAA,IACN,SAAS;AAAA,IACT,GAAG;AAAA,IACH,YAAY,EAAE,UAAU,SAAS,UAAU,MAAM,KAAK,QAAQ;AAAA,EAChE;AAAA,EACA,MAAM,CAAC,eAAkC;AAAA,IACvC,SAAS;AAAA,IACT,GAAG,YAAY,CAAC,SAAS;AAAA,IACzB,YAAY,EAAE,UAAU,SAAS,UAAU,MAAM,KAAK,OAAO;AAAA,EAC/D;AACF;AAGO,MAAM,iBAA2B;AAAA,EACtC,QAAQ,CAAC;AAAA,EACT,OAAO,EAAE,YAAY,EAAE,iBAAiB,MAAM,eAAe,KAAK,EAAE;AACtE;AAEO,MAAM,qBAA+B;AAAA,EAC1C,QAAQ,EAAE,SAAS,GAAG,GAAG,GAAG;AAAA,EAC5B,OAAO;AAAA,IACL,SAAS;AAAA,IACT,GAAG;AAAA,IACH,YAAY,EAAE,UAAU,MAAM,MAAM,MAAM,OAAO;AAAA,EACnD;AACF;AAWO,MAAM,WAAqB;AAAA,EAChC,QAAQ,EAAE,SAAS,GAAG,GAAG,GAAG;AAAA,EAC5B,MAAM;AAAA,IACJ,SAAS;AAAA,IACT,GAAG;AAAA,IACH,YAAY,EAAE,UAAU,MAAM,MAAM,MAAM,OAAO;AAAA,EACnD;AACF;","names":[]}

package/dist/nav-pending.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Whether the sidebar is waiting on a change to the business to come through.
+ *
+ * Turning a business type on is saved after a short pause and then the tenant
+ * is fetched again; the answer is in well under a second, which is too quick
+ * to register as anything but a row popping in. John asked for it to take two
+ * or three seconds with a loader (2026-10-11), so the loader is held for at
+ * least `MIN_MS` from the press, and the new rows come in when it lifts.
+ *
+ * The toggle calls `beginNavPending` the moment it is pressed and the save
+ * calls `endNavPending` once the new tenant is in. A safety timer ends it
+ * regardless, so a save that never answers cannot leave the loader running.
+ */
+export declare const NAV_PENDING_MIN_MS = 2000;
+interface State {
+    pending: boolean;
+    label: string;
+    startedAt: number;
+}
+/** `label` is what is being added, for the loader to say. */
+export declare function beginNavPending(label?: string): void;
+/** The change has landed; the loader lifts once it has been up for `MIN_MS`. */
+export declare function endNavPending(): void;
+/**
+ * Whether new sidebar rows are the answer to a change the merchant just made:
+ * the loader is up, or came down a moment ago. Rows that arrive for any other
+ * reason (the whole rail redrawing on a route change) must not animate in.
+ */
+export declare function navChangeIsRecent(withinMs?: number): boolean;
+/**
+ * A change is on its way that has no loader: a removal just dissolves the rows
+ * when the sidebar drops them. This says the next removal is the answer to it
+ * (the save takes a second or two, so the window is generous).
+ */
+export declare function markNavChange(forMs?: number): void;
+/** Whether the loader is up right now. */
+export declare function navIsPending(): boolean;
+/** Runs once, when the loader next lifts. */
+export declare function onNavPendingEnd(cb: () => void): void;
+export declare function useNavPending(): boolean;
+export declare function useNavPendingState(): State;
+export {};

package/dist/nav-pending.js

@@ -0,0 +1,84 @@
+import { useSyncExternalStore } from "react";
+const NAV_PENDING_MIN_MS = 2e3;
+const SAFETY_MS = 8e3;
+let state = { pending: false, label: "", startedAt: 0 };
+let lastEndedAt = 0;
+let changeUntil = 0;
+let safety = null;
+let hold = null;
+const listeners = /* @__PURE__ */ new Set();
+const endListeners = /* @__PURE__ */ new Set();
+function set(next) {
+  state = next;
+  listeners.forEach((l) => l());
+}
+function beginNavPending(label = "") {
+  if (hold) clearTimeout(hold);
+  hold = null;
+  if (safety) clearTimeout(safety);
+  safety = setTimeout(finish, SAFETY_MS);
+  set({
+    pending: true,
+    label: label || state.label,
+    // A second press while the loader is up keeps the clock it started.
+    startedAt: state.pending ? state.startedAt : Date.now()
+  });
+}
+function finish() {
+  if (safety) clearTimeout(safety);
+  safety = null;
+  hold = null;
+  if (!state.pending) return;
+  lastEndedAt = Date.now();
+  set({ ...state, pending: false });
+  endListeners.forEach((l) => l());
+  endListeners.clear();
+}
+function endNavPending() {
+  if (!state.pending || hold) return;
+  const wait = Math.max(0, NAV_PENDING_MIN_MS - (Date.now() - state.startedAt));
+  if (wait === 0) finish();
+  else hold = setTimeout(finish, wait);
+}
+function navChangeIsRecent(withinMs = 2e3) {
+  return state.pending || Date.now() < changeUntil || Date.now() - lastEndedAt < withinMs;
+}
+function markNavChange(forMs = 8e3) {
+  changeUntil = Date.now() + forMs;
+}
+function navIsPending() {
+  return state.pending;
+}
+function onNavPendingEnd(cb) {
+  endListeners.add(cb);
+}
+function subscribe(cb) {
+  listeners.add(cb);
+  return () => listeners.delete(cb);
+}
+function useNavPending() {
+  return useSyncExternalStore(
+    subscribe,
+    () => state.pending,
+    () => false
+  );
+}
+function useNavPendingState() {
+  return useSyncExternalStore(
+    subscribe,
+    () => state,
+    () => state
+  );
+}
+export {
+  NAV_PENDING_MIN_MS,
+  beginNavPending,
+  endNavPending,
+  markNavChange,
+  navChangeIsRecent,
+  navIsPending,
+  onNavPendingEnd,
+  useNavPending,
+  useNavPendingState
+};
+//# sourceMappingURL=nav-pending.js.map

package/dist/nav-pending.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/nav-pending.ts"],"sourcesContent":["import { useSyncExternalStore } from 'react';\n\n/**\n * Whether the sidebar is waiting on a change to the business to come through.\n *\n * Turning a business type on is saved after a short pause and then the tenant\n * is fetched again; the answer is in well under a second, which is too quick\n * to register as anything but a row popping in. John asked for it to take two\n * or three seconds with a loader (2026-10-11), so the loader is held for at\n * least `MIN_MS` from the press, and the new rows come in when it lifts.\n *\n * The toggle calls `beginNavPending` the moment it is pressed and the save\n * calls `endNavPending` once the new tenant is in. A safety timer ends it\n * regardless, so a save that never answers cannot leave the loader running.\n */\nexport const NAV_PENDING_MIN_MS = 2000;\nconst SAFETY_MS = 8000;\n\ninterface State {\n  pending: boolean;\n  label: string;\n  startedAt: number;\n}\n\nlet state: State = { pending: false, label: '', startedAt: 0 };\nlet lastEndedAt = 0;\nlet changeUntil = 0;\nlet safety: ReturnType<typeof setTimeout> | null = null;\nlet hold: ReturnType<typeof setTimeout> | null = null;\nconst listeners = new Set<() => void>();\nconst endListeners = new Set<() => void>();\n\nfunction set(next: State) {\n  state = next;\n  listeners.forEach((l) => l());\n}\n\n/** `label` is what is being added, for the loader to say. */\nexport function beginNavPending(label = '') {\n  if (hold) clearTimeout(hold);\n  hold = null;\n  if (safety) clearTimeout(safety);\n  safety = setTimeout(finish, SAFETY_MS);\n  set({\n    pending: true,\n    label: label || state.label,\n    // A second press while the loader is up keeps the clock it started.\n    startedAt: state.pending ? state.startedAt : Date.now(),\n  });\n}\n\nfunction finish() {\n  if (safety) clearTimeout(safety);\n  safety = null;\n  hold = null;\n  if (!state.pending) return;\n  lastEndedAt = Date.now();\n  set({ ...state, pending: false });\n  endListeners.forEach((l) => l());\n  endListeners.clear();\n}\n\n/** The change has landed; the loader lifts once it has been up for `MIN_MS`. */\nexport function endNavPending() {\n  if (!state.pending || hold) return;\n  const wait = Math.max(0, NAV_PENDING_MIN_MS - (Date.now() - state.startedAt));\n  if (wait === 0) finish();\n  else hold = setTimeout(finish, wait);\n}\n\n/**\n * Whether new sidebar rows are the answer to a change the merchant just made:\n * the loader is up, or came down a moment ago. Rows that arrive for any other\n * reason (the whole rail redrawing on a route change) must not animate in.\n */\nexport function navChangeIsRecent(withinMs = 2000): boolean {\n  return (\n    state.pending ||\n    Date.now() < changeUntil ||\n    Date.now() - lastEndedAt < withinMs\n  );\n}\n\n/**\n * A change is on its way that has no loader: a removal just dissolves the rows\n * when the sidebar drops them. This says the next removal is the answer to it\n * (the save takes a second or two, so the window is generous).\n */\nexport function markNavChange(forMs = 8000) {\n  changeUntil = Date.now() + forMs;\n}\n\n/** Whether the loader is up right now. */\nexport function navIsPending(): boolean {\n  return state.pending;\n}\n\n/** Runs once, when the loader next lifts. */\nexport function onNavPendingEnd(cb: () => void) {\n  endListeners.add(cb);\n}\n\nfunction subscribe(cb: () => void) {\n  listeners.add(cb);\n  return () => listeners.delete(cb);\n}\n\nexport function useNavPending(): boolean {\n  return useSyncExternalStore(\n    subscribe,\n    () => state.pending,\n    () => false,\n  );\n}\n\nexport function useNavPendingState(): State {\n  return useSyncExternalStore(\n    subscribe,\n    () => state,\n    () => state,\n  );\n}\n"],"mappings":"AAAA,SAAS,4BAA4B;AAe9B,MAAM,qBAAqB;AAClC,MAAM,YAAY;AAQlB,IAAI,QAAe,EAAE,SAAS,OAAO,OAAO,IAAI,WAAW,EAAE;AAC7D,IAAI,cAAc;AAClB,IAAI,cAAc;AAClB,IAAI,SAA+C;AACnD,IAAI,OAA6C;AACjD,MAAM,YAAY,oBAAI,IAAgB;AACtC,MAAM,eAAe,oBAAI,IAAgB;AAEzC,SAAS,IAAI,MAAa;AACxB,UAAQ;AACR,YAAU,QAAQ,CAAC,MAAM,EAAE,CAAC;AAC9B;AAGO,SAAS,gBAAgB,QAAQ,IAAI;AAC1C,MAAI,KAAM,cAAa,IAAI;AAC3B,SAAO;AACP,MAAI,OAAQ,cAAa,MAAM;AAC/B,WAAS,WAAW,QAAQ,SAAS;AACrC,MAAI;AAAA,IACF,SAAS;AAAA,IACT,OAAO,SAAS,MAAM;AAAA;AAAA,IAEtB,WAAW,MAAM,UAAU,MAAM,YAAY,KAAK,IAAI;AAAA,EACxD,CAAC;AACH;AAEA,SAAS,SAAS;AAChB,MAAI,OAAQ,cAAa,MAAM;AAC/B,WAAS;AACT,SAAO;AACP,MAAI,CAAC,MAAM,QAAS;AACpB,gBAAc,KAAK,IAAI;AACvB,MAAI,EAAE,GAAG,OAAO,SAAS,MAAM,CAAC;AAChC,eAAa,QAAQ,CAAC,MAAM,EAAE,CAAC;AAC/B,eAAa,MAAM;AACrB;AAGO,SAAS,gBAAgB;AAC9B,MAAI,CAAC,MAAM,WAAW,KAAM;AAC5B,QAAM,OAAO,KAAK,IAAI,GAAG,sBAAsB,KAAK,IAAI,IAAI,MAAM,UAAU;AAC5E,MAAI,SAAS,EAAG,QAAO;AAAA,MAClB,QAAO,WAAW,QAAQ,IAAI;AACrC;AAOO,SAAS,kBAAkB,WAAW,KAAe;AAC1D,SACE,MAAM,WACN,KAAK,IAAI,IAAI,eACb,KAAK,IAAI,IAAI,cAAc;AAE/B;AAOO,SAAS,cAAc,QAAQ,KAAM;AAC1C,gBAAc,KAAK,IAAI,IAAI;AAC7B;AAGO,SAAS,eAAwB;AACtC,SAAO,MAAM;AACf;AAGO,SAAS,gBAAgB,IAAgB;AAC9C,eAAa,IAAI,EAAE;AACrB;AAEA,SAAS,UAAU,IAAgB;AACjC,YAAU,IAAI,EAAE;AAChB,SAAO,MAAM,UAAU,OAAO,EAAE;AAClC;AAEO,SAAS,gBAAyB;AACvC,SAAO;AAAA,IACL;AAAA,IACA,MAAM,MAAM;AAAA,IACZ,MAAM;AAAA,EACR;AACF;AAEO,SAAS,qBAA4B;AAC1C,SAAO;AAAA,IACL;AAAA,IACA,MAAM;AAAA,IACN,MAAM;AAAA,EACR;AACF;","names":[]}

package/dist/navigation-groups.d.ts

@@ -0,0 +1,52 @@
+import type { LucideIcon } from 'lucide-react';
+export interface NavigationItem {
+    id: string;
+    name: string;
+    href: string;
+    icon: LucideIcon;
+    requiredBehavior?: string[];
+}
+export declare const customizationItems: NavigationItem[];
+/**
+ * `settingsItems` used to live here: a second list of settings rows, read by
+ * the mobile settings hub while the desktop rail read `BUSINESS_GROUPS` in
+ * `components/sidebar/config.ts`.
+ *
+ * The two disagreed. The rail carried Team, Integrations, Operations and
+ * Delivery; this list carried Navigation, SEO and Bank account instead — and
+ * two of those three pointed at redirect stubs, so tapping them in settings
+ * threw the merchant into the website editor. A phone and a laptop were being
+ * shown two different products.
+ *
+ * There is one list now, and it is the rail's, because the rail's rows carry
+ * their own behaviour gates. `settings-nav-coverage.test.ts` fails the build if
+ * a second one appears.
+ */
+export declare const businessItems: NavigationItem[];
+/**
+ * Per WORKSPACE, not per account — verified against the schema, not inferred.
+ *
+ * `billing_subscriptions.tenantId` is `unique: true`, so a tenant has exactly
+ * one subscription and an account with three workspaces pays three times.
+ * Credits are the same: `tenant_messaging_credit_balances`,
+ * `tenant_email_credits`, `tenant_email_credit_balances` — every one of them
+ * keyed on `tenantId` and named for it.
+ *
+ * The two sidebar sources used to assert opposite things about this in
+ * comments (`config.ts` said per-business, `spine-groups.ts` said per-ACCOUNT),
+ * and this file filed it under an ACCOUNT heading on the mobile hub. So the
+ * screen told a merchant their plan belonged to them rather than to the
+ * business they were looking at — which is the one thing it must not say when
+ * switching workspace switches the bill.
+ */
+export declare const billingItem: NavigationItem;
+export declare const profileItem: NavigationItem;
+/**
+ * Things that belong to the PERSON, across every workspace they hold.
+ *
+ * Empty on purpose right now, and that is the finding rather than an
+ * oversight: the only row that was ever here was Billing, which is
+ * per-workspace. Profile is the natural first genuine member — it is declared
+ * above as `profileItem` and reached through the account menu.
+ */
+export declare const accountItems: NavigationItem[];