@withpotter/components 0.13.0-next.101

package/dist/sidebar/spine-money.js

@@ -0,0 +1,168 @@
+import {
+  Banknote,
+  Landmark,
+  ReceiptText,
+  Scale,
+  Tablet,
+  Wallet
+} from "lucide-react";
+import { WALLET_SETTLEMENT } from "@withpotter/lib/wallet-settlement";
+const POS_IN_MONEY = process.env.NEXT_PUBLIC_BOX_POS_IN_MONEY === "true";
+function buildMoneyGroup({
+  filterItems,
+  canSeeFinance,
+  intentOwnsInvoices
+}) {
+  return {
+    id: "payments",
+    // A hardware-only role gets this group as a plain Hardware link: the
+    // renderer draws a hub with one child as a flat link for the GROUP, so
+    // leaving it as "Money" would point them at Transactions, a page they cannot
+    // open. Finance roles get the hub, as before.
+    label: canSeeFinance ? "Money" : "POS terminal",
+    icon: canSeeFinance ? Banknote : Tablet,
+    href: canSeeFinance ? "/dashboard/payments" : "/dashboard/hardware",
+    /**
+     * The page inside it.
+     *
+     * Called Payments until the list was looked at properly: it holds refunds,
+     * failed attempts and cash recorded by hand, none of which is a payment
+     * taken. Naming a list after the happiest thing in it is the same defect
+     * this whole pass has been fixing, and Transactions is the word both the
+     * trade and every bank alert in this market already use.
+     */
+    landingLabel: canSeeFinance ? "Transactions" : void 0,
+    // The wallet leads, then Transactions: see `landingAt`.
+    landingAt: canSeeFinance ? 1 : 0,
+    // Finance, or hardware: Hardware is a row in this group, and a role built
+    // around the machines alone must still reach it. Each row below declares
+    // its own permission, so widening the group shows a hardware-only role the
+    // Hardware row and nothing else.
+    requiredPermission: [
+      "canViewFinance",
+      "canManageFinance",
+      "canViewHardware",
+      "canManageHardware"
+    ],
+    alwaysHub: canSeeFinance,
+    items: filterItems(
+      [
+        // The wallet is a child of Money again (it was in More).
+        {
+          id: "wallet",
+          name: "Wallet",
+          href: "/dashboard/wallet",
+          icon: Wallet,
+          requiredPermission: ["canViewFinance", "canManageFinance"]
+        },
+        /*
+         * NO SALES ROW. It was here, and it was the register across every
+         * rail — orders, bookings and invoices, with `paymentState` as a
+         * column, which is this hub's own question.
+         *
+         * It went because the word was the problem, not the filing. Orders is
+         * a queue you work and Sales was the read over the top, and no
+         * merchant could infer that from two nouns sitting as peers in one
+         * sidebar. The register is now `?rail=all` on Orders, where the noun a
+         * merchant actually uses for both already lives, and the old route
+         * redirects there. Square and Shopify each ship exactly one such row.
+         */
+        /**
+         * The surface's own logs, in the order money moves.
+         *
+         * This group used to list a bank form and a gift-card screen, while
+         * the three things the hub actually contains were invisible: they were
+         * `?view=` lenses, and a query param cannot be a nav row, cannot be
+         * gated by permission and cannot be bookmarked. So the nav listed
+         * whatever happened to have a route rather than what the hub is made of.
+         *
+         * INVOICES, for everyone not already billing from their own group.
+         *
+         * There was no row here, on the reasoning that every archetype
+         * definition emits one into the merchant's own workflow group. Ten
+         * configs declare an `invoices` item and `INTENT_NAV_DEFINITIONS`
+         * renders exactly one — `send-invoices` — so for the other nine the row
+         * existed in a config and nowhere on screen, reachable only through a
+         * text link on the rail. Any business can be owed money.
+         *
+         * The billing archetype keeps its own row, at the top, where its work
+         * is; `intentOwnsInvoices` drops this one rather than saying Invoices
+         * twice, because `shares` cannot see across the two builders.
+         */
+        !intentOwnsInvoices && {
+          id: "invoices",
+          name: "Invoices",
+          href: "/dashboard/invoices",
+          icon: ReceiptText,
+          requiredPermission: ["canViewFinance", "canManageFinance"]
+        },
+        // A box that settles into its own wallet has no bank account to pay out
+        // to, and the Wallet row above is already where the money is.
+        !WALLET_SETTLEMENT && {
+          id: "payouts",
+          name: "Payouts",
+          href: "/dashboard/payments/payouts",
+          icon: Landmark,
+          requiredPermission: ["canViewFinance", "canManageFinance"]
+        },
+        {
+          id: "disputes",
+          name: "Disputes",
+          href: "/dashboard/payments/disputes",
+          icon: Scale,
+          requiredPermission: ["canViewFinance", "canManageFinance"]
+        },
+        /**
+         * HARDWARE, from 2026-10-05 (John's call), and ONLY HERE FOR A ROLE WITH
+         * NO FINANCE. For everyone who can open the money pages it moved to More
+         * on 2026-10-06, beside Wallet; this row is the one way a role built
+         * around the machines alone still reaches them, drawn as a plain link by
+         * the group's own label.
+         *
+         * Earlier history: It sat in Settings from
+         * 2026-09-03 and before that here, as "Devices", until it was taken off
+         * on 2026-08-24 for the reason written below. It is back as ONE row,
+         * the machines and the requests for more of them, because the tills and
+         * readers a business owns are the part of Money it can touch.
+         *
+         * Gated the way the Hardware pages are on the api: hardware first, with
+         * finance as the fallback, so a custom role built around Finance keeps
+         * reaching the machines it always could. `/dashboard/hardware/requests`
+         * and the device records light this row by their address.
+         */
+        (canSeeFinance === false || POS_IN_MONEY) && {
+          id: "hardware",
+          name: "POS terminal",
+          href: "/dashboard/hardware",
+          icon: Tablet,
+          requiredPermission: [
+            "canViewHardware",
+            "canManageHardware",
+            "canViewFinance"
+          ]
+        }
+        /**
+         * NO BANDS ROW, and Devices is the Hardware row above. Both were here
+         * and were taken off the rail on 2026-08-24 (John's call): a permanent
+         * row in a hub a merchant opens to answer "what came in" had not been
+         * earned.
+         *
+         * Bands still builds and still routes. Nothing links to it: this was its
+         * only entry, and the payments hub layout names it in `ROUTE_TITLES`
+         * without offering a way in. Whatever brings it back has to bring a link
+         * with it, and as its own row, not a fourth money log.
+         *
+         * Devices sat here because every device registered today takes money —
+         * but a door reader produces no transaction and a credential issuer
+         * produces no money, so Money was never an exact parent for it. It is
+         * here again as a row about the machines, not as a money log.
+         */
+      ].filter(Boolean)
+    )
+  };
+}
+export {
+  POS_IN_MONEY,
+  buildMoneyGroup
+};
+//# sourceMappingURL=spine-money.js.map

package/dist/sidebar/spine-money.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/spine-money.ts"],"sourcesContent":["/**\n * The Money hub, lifted out of `spine-groups.ts`.\n *\n * Same cut as `spine-website.ts`, and for the same reason: that file sits over\n * the house limit, and a hub whose rows are the money instruments — what is\n * promised, what is out, what is at risk — reads on its own. Taking exactly\n * what it reads keeps the archetype question (does the merchant already bill\n * from their own group?) in the signature rather than in a closure.\n */\nimport {\n  Banknote,\n  Landmark,\n  ReceiptText,\n  Scale,\n  Tablet,\n  Wallet,\n} from 'lucide-react';\nimport { WALLET_SETTLEMENT } from '@withpotter/lib/wallet-settlement';\nimport { type NavItem, type NavGroup } from './config';\n\n/**\n * A box that files the machines under Money for everyone sets this. The row\n * then shows for finance roles too, and Operations drops its own.\n */\nexport const POS_IN_MONEY =\n  process.env.NEXT_PUBLIC_BOX_POS_IN_MONEY === 'true';\n\nexport interface MoneyGroupDeps {\n  filterItems: (items: NavItem[]) => NavItem[];\n  /**\n   * Whether this person can open the money pages. The group's own landing row is\n   * Transactions, a finance page, so without this a hardware-only role would be\n   * shown a link it cannot open. It then keeps one row, Hardware, drawn flat.\n   */\n  canSeeFinance: boolean;\n  /** The billing archetype puts Invoices in its own group; this drops ours. */\n  intentOwnsInvoices: boolean;\n}\n\nexport function buildMoneyGroup({\n  filterItems,\n  canSeeFinance,\n  intentOwnsInvoices,\n}: MoneyGroupDeps): NavGroup {\n  /**\n   * Money.\n   *\n   * The group was called Payments and so was its landing row and so was the\n   * page, which put the same word on screen three times inside one dropdown.\n   * \"All payments\" fixed the repetition and not the cause: a container and the\n   * page inside it are not the same thing, and this container holds more than\n   * payments. Invoices is money promised, payouts is money out, disputes is\n   * money at risk, and the bank account is where all of it lands.\n   *\n   * Money is the word for that set. It is what Square calls the same section,\n   * it is one plain noun rather than a phrase, and it leaves every child free\n   * to be the specific thing it is. Deliberately not Finance, which this\n   * surface was called before and was renamed away from.\n   *\n   * The id stays `payments`. Ids are looked up in three other files for icons,\n   * destinations and renames, and changing one is how the catalog rows\n   * collided.\n   */\n  return {\n    id: 'payments',\n    // A hardware-only role gets this group as a plain Hardware link: the\n    // renderer draws a hub with one child as a flat link for the GROUP, so\n    // leaving it as \"Money\" would point them at Transactions, a page they cannot\n    // open. Finance roles get the hub, as before.\n    label: canSeeFinance ? 'Money' : 'POS terminal',\n    icon: canSeeFinance ? Banknote : Tablet,\n    href: canSeeFinance ? '/dashboard/payments' : '/dashboard/hardware',\n    /**\n     * The page inside it.\n     *\n     * Called Payments until the list was looked at properly: it holds refunds,\n     * failed attempts and cash recorded by hand, none of which is a payment\n     * taken. Naming a list after the happiest thing in it is the same defect\n     * this whole pass has been fixing, and Transactions is the word both the\n     * trade and every bank alert in this market already use.\n     */\n    landingLabel: canSeeFinance ? 'Transactions' : undefined,\n    // The wallet leads, then Transactions: see `landingAt`.\n    landingAt: canSeeFinance ? 1 : 0,\n    // Finance, or hardware: Hardware is a row in this group, and a role built\n    // around the machines alone must still reach it. Each row below declares\n    // its own permission, so widening the group shows a hardware-only role the\n    // Hardware row and nothing else.\n    requiredPermission: [\n      'canViewFinance',\n      'canManageFinance',\n      'canViewHardware',\n      'canManageHardware',\n    ],\n    alwaysHub: canSeeFinance,\n    items: filterItems(\n      [\n        // The wallet is a child of Money again (it was in More).\n        {\n          id: 'wallet',\n          name: 'Wallet',\n          href: '/dashboard/wallet',\n          icon: Wallet,\n          requiredPermission: ['canViewFinance', 'canManageFinance'],\n        },\n        /*\n         * NO SALES ROW. It was here, and it was the register across every\n         * rail — orders, bookings and invoices, with `paymentState` as a\n         * column, which is this hub's own question.\n         *\n         * It went because the word was the problem, not the filing. Orders is\n         * a queue you work and Sales was the read over the top, and no\n         * merchant could infer that from two nouns sitting as peers in one\n         * sidebar. The register is now `?rail=all` on Orders, where the noun a\n         * merchant actually uses for both already lives, and the old route\n         * redirects there. Square and Shopify each ship exactly one such row.\n         */\n        /**\n         * The surface's own logs, in the order money moves.\n         *\n         * This group used to list a bank form and a gift-card screen, while\n         * the three things the hub actually contains were invisible: they were\n         * `?view=` lenses, and a query param cannot be a nav row, cannot be\n         * gated by permission and cannot be bookmarked. So the nav listed\n         * whatever happened to have a route rather than what the hub is made of.\n         *\n         * INVOICES, for everyone not already billing from their own group.\n         *\n         * There was no row here, on the reasoning that every archetype\n         * definition emits one into the merchant's own workflow group. Ten\n         * configs declare an `invoices` item and `INTENT_NAV_DEFINITIONS`\n         * renders exactly one — `send-invoices` — so for the other nine the row\n         * existed in a config and nowhere on screen, reachable only through a\n         * text link on the rail. Any business can be owed money.\n         *\n         * The billing archetype keeps its own row, at the top, where its work\n         * is; `intentOwnsInvoices` drops this one rather than saying Invoices\n         * twice, because `shares` cannot see across the two builders.\n         */\n        !intentOwnsInvoices && {\n          id: 'invoices',\n          name: 'Invoices',\n          href: '/dashboard/invoices',\n          icon: ReceiptText,\n          requiredPermission: ['canViewFinance', 'canManageFinance'],\n        },\n        // A box that settles into its own wallet has no bank account to pay out\n        // to, and the Wallet row above is already where the money is.\n        !WALLET_SETTLEMENT && {\n          id: 'payouts',\n          name: 'Payouts',\n          href: '/dashboard/payments/payouts',\n          icon: Landmark,\n          requiredPermission: ['canViewFinance', 'canManageFinance'],\n        },\n        {\n          id: 'disputes',\n          name: 'Disputes',\n          href: '/dashboard/payments/disputes',\n          icon: Scale,\n          requiredPermission: ['canViewFinance', 'canManageFinance'],\n        },\n        /**\n         * HARDWARE, from 2026-10-05 (John's call), and ONLY HERE FOR A ROLE WITH\n         * NO FINANCE. For everyone who can open the money pages it moved to More\n         * on 2026-10-06, beside Wallet; this row is the one way a role built\n         * around the machines alone still reaches them, drawn as a plain link by\n         * the group's own label.\n         *\n         * Earlier history: It sat in Settings from\n         * 2026-09-03 and before that here, as \"Devices\", until it was taken off\n         * on 2026-08-24 for the reason written below. It is back as ONE row,\n         * the machines and the requests for more of them, because the tills and\n         * readers a business owns are the part of Money it can touch.\n         *\n         * Gated the way the Hardware pages are on the api: hardware first, with\n         * finance as the fallback, so a custom role built around Finance keeps\n         * reaching the machines it always could. `/dashboard/hardware/requests`\n         * and the device records light this row by their address.\n         */\n        (canSeeFinance === false || POS_IN_MONEY) && {\n          id: 'hardware',\n          name: 'POS terminal',\n          href: '/dashboard/hardware',\n          icon: Tablet,\n          requiredPermission: [\n            'canViewHardware',\n            'canManageHardware',\n            'canViewFinance',\n          ],\n        },\n        /**\n         * NO BANDS ROW, and Devices is the Hardware row above. Both were here\n         * and were taken off the rail on 2026-08-24 (John's call): a permanent\n         * row in a hub a merchant opens to answer \"what came in\" had not been\n         * earned.\n         *\n         * Bands still builds and still routes. Nothing links to it: this was its\n         * only entry, and the payments hub layout names it in `ROUTE_TITLES`\n         * without offering a way in. Whatever brings it back has to bring a link\n         * with it, and as its own row, not a fourth money log.\n         *\n         * Devices sat here because every device registered today takes money —\n         * but a door reader produces no transaction and a credential issuer\n         * produces no money, so Money was never an exact parent for it. It is\n         * here again as a row about the machines, not as a money log.\n         */\n      ].filter(Boolean) as NavItem[],\n    ),\n  };\n}\n"],"mappings":"AASA;AAAA,EACE;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,OACK;AACP,SAAS,yBAAyB;AAO3B,MAAM,eACX,QAAQ,IAAI,iCAAiC;AAcxC,SAAS,gBAAgB;AAAA,EAC9B;AAAA,EACA;AAAA,EACA;AACF,GAA6B;AAoB3B,SAAO;AAAA,IACL,IAAI;AAAA;AAAA;AAAA;AAAA;AAAA,IAKJ,OAAO,gBAAgB,UAAU;AAAA,IACjC,MAAM,gBAAgB,WAAW;AAAA,IACjC,MAAM,gBAAgB,wBAAwB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAU9C,cAAc,gBAAgB,iBAAiB;AAAA;AAAA,IAE/C,WAAW,gBAAgB,IAAI;AAAA;AAAA;AAAA;AAAA;AAAA,IAK/B,oBAAoB;AAAA,MAClB;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,IACF;AAAA,IACA,WAAW;AAAA,IACX,OAAO;AAAA,MACL;AAAA;AAAA,QAEE;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,kBAAkB,kBAAkB;AAAA,QAC3D;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,QAmCA,CAAC,sBAAsB;AAAA,UACrB,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,kBAAkB,kBAAkB;AAAA,QAC3D;AAAA;AAAA;AAAA,QAGA,CAAC,qBAAqB;AAAA,UACpB,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,kBAAkB,kBAAkB;AAAA,QAC3D;AAAA,QACA;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,kBAAkB,kBAAkB;AAAA,QAC3D;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,SAmBC,kBAAkB,SAAS,iBAAiB;AAAA,UAC3C,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB;AAAA,YAClB;AAAA,YACA;AAAA,YACA;AAAA,UACF;AAAA,QACF;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAiBF,EAAE,OAAO,OAAO;AAAA,IAClB;AAAA,EACF;AACF;","names":[]}

package/dist/sidebar/spine-operations.d.ts

@@ -0,0 +1,10 @@
+import { type NavGroup, type NavItem } from './config';
+export declare function buildOperationsGroup(filterItems: (items: NavItem[]) => NavItem[], { staffTaken, }?: {
+    /**
+     * The business already draws a row called Staff. A business that books
+     * people lists them under that word, and the same word twice in one
+     * sidebar names two things alike, so ours reads "Staff access" there: the
+     * logins and what they may do, as against the people who can be booked.
+     */
+    staffTaken?: boolean;
+}): NavGroup;

package/dist/sidebar/spine-operations.js

@@ -0,0 +1,90 @@
+import {
+  BarChart3,
+  Briefcase,
+  Clock3,
+  MapPin,
+  Tablet,
+  Truck,
+  UserCog
+} from "lucide-react";
+import { DELIVERY_NAV, LOCATIONS_NAV } from "@withpotter/lib/fulfilment-nav";
+import { hideLetting } from "@withpotter/lib/box-letting";
+import { POS_IN_MONEY } from "./spine-money";
+const hideReports = () => process.env.NEXT_PUBLIC_BOX_HIDE_REPORTS === "true";
+function buildOperationsGroup(filterItems, {
+  staffTaken = false
+} = {}) {
+  return {
+    id: "operations",
+    label: "Operations",
+    icon: Briefcase,
+    requiredPermission: ["canManageSettings"],
+    alwaysHub: true,
+    items: filterItems([
+      // When you are open, and where you are. Ungated: an online-only shop
+      // still has an address it ships from and hours it answers on. Hours and
+      // booking policy are tabs of this page.
+      {
+        id: "locations",
+        name: LOCATIONS_NAV.label,
+        href: "/dashboard/operations/locations",
+        icon: MapPin,
+        requiredPermission: ["canManageSettings"]
+      },
+      // The machines on the counter. Called what a merchant calls them.
+      // A box that files them under Money (POS_IN_MONEY) has the row there.
+      ...POS_IN_MONEY ? [] : [
+        {
+          id: "pos-terminal",
+          name: "POS terminal",
+          href: "/dashboard/hardware",
+          icon: Tablet,
+          requiredPermission: ["canManageSettings"]
+        }
+      ],
+      // Only where something is let: the policy every property inherits.
+      // A box that hides it (NEXT_PUBLIC_BOX_HIDE_LETTING) keeps Rentals.
+      ...hideLetting() ? [] : [
+        {
+          id: "letting",
+          name: "Letting",
+          href: "/dashboard/operations/letting",
+          icon: Clock3,
+          requiredBehavior: ["rentable"],
+          requiredPermission: ["canManageSettings"]
+        }
+      ],
+      {
+        id: "shipping",
+        name: DELIVERY_NAV.label,
+        href: "/dashboard/business/shipping",
+        icon: Truck,
+        requiredBehavior: ["shippable"],
+        requiredPermission: ["canManageSettings"]
+      },
+      // Staff and Reports are pages whose sections hold what would otherwise
+      // be rows: Employees and Permissions, and the four reports. A row that
+      // opens onto more rows is a second menu inside the first.
+      {
+        id: "team",
+        name: staffTaken ? "Staff access" : "Staff",
+        href: "/dashboard/staff",
+        icon: UserCog,
+        requiredPermission: ["canManageTeam"]
+      },
+      ...hideReports() ? [] : [
+        {
+          id: "reports",
+          name: "Reports",
+          href: "/dashboard/analytics/reports",
+          icon: BarChart3,
+          requiredPermission: ["canViewAnalytics"]
+        }
+      ]
+    ])
+  };
+}
+export {
+  buildOperationsGroup
+};
+//# sourceMappingURL=spine-operations.js.map

package/dist/sidebar/spine-operations.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/spine-operations.ts"],"sourcesContent":["/**\n * Operations: how the business gets orders to people, and where it works from.\n *\n * It holds a row only where there is a real page behind it. Shipping is one:\n * its page is a normal page of its own, `/dashboard/business/shipping`, and\n * this row links to it rather than carrying a second copy of the settings.\n * Staff and Reports are rows too, each a page of sections. Shifts, Attendance\n * and Tasks join Staff when they have pages. A box that does not offer Reports\n * sets NEXT_PUBLIC_BOX_HIDE_REPORTS, the same way one hides Automations.\n */\nimport {\n  BarChart3,\n  Briefcase,\n  Clock3,\n  MapPin,\n  Tablet,\n  Truck,\n  UserCog,\n} from 'lucide-react';\nimport { DELIVERY_NAV, LOCATIONS_NAV } from '@withpotter/lib/fulfilment-nav';\nimport { hideLetting } from '@withpotter/lib/box-letting';\nimport { type NavGroup, type NavItem } from './config';\nimport { POS_IN_MONEY } from './spine-money';\n\n/** Read when the group is built, so a test can set it. NEXT_PUBLIC_* is inlined at build. */\nconst hideReports = () => process.env.NEXT_PUBLIC_BOX_HIDE_REPORTS === 'true';\n\nexport function buildOperationsGroup(\n  filterItems: (items: NavItem[]) => NavItem[],\n  {\n    staffTaken = false,\n  }: {\n    /**\n     * The business already draws a row called Staff. A business that books\n     * people lists them under that word, and the same word twice in one\n     * sidebar names two things alike, so ours reads \"Staff access\" there: the\n     * logins and what they may do, as against the people who can be booked.\n     */\n    staffTaken?: boolean;\n  } = {},\n): NavGroup {\n  return {\n    id: 'operations',\n    label: 'Operations',\n    icon: Briefcase,\n    requiredPermission: ['canManageSettings'],\n    alwaysHub: true,\n    items: filterItems([\n      // When you are open, and where you are. Ungated: an online-only shop\n      // still has an address it ships from and hours it answers on. Hours and\n      // booking policy are tabs of this page.\n      {\n        id: 'locations',\n        name: LOCATIONS_NAV.label,\n        href: '/dashboard/operations/locations',\n        icon: MapPin,\n        requiredPermission: ['canManageSettings'],\n      },\n      // The machines on the counter. Called what a merchant calls them.\n      // A box that files them under Money (POS_IN_MONEY) has the row there.\n      ...(POS_IN_MONEY\n        ? []\n        : [\n            {\n              id: 'pos-terminal',\n              name: 'POS terminal',\n              href: '/dashboard/hardware',\n              icon: Tablet,\n              requiredPermission: ['canManageSettings'],\n            } satisfies NavItem,\n          ]),\n      // Only where something is let: the policy every property inherits.\n      // A box that hides it (NEXT_PUBLIC_BOX_HIDE_LETTING) keeps Rentals.\n      ...(hideLetting()\n        ? []\n        : [\n            {\n              id: 'letting',\n              name: 'Letting',\n              href: '/dashboard/operations/letting',\n              icon: Clock3,\n              requiredBehavior: ['rentable'],\n              requiredPermission: ['canManageSettings'],\n            } satisfies NavItem,\n          ]),\n      {\n        id: 'shipping',\n        name: DELIVERY_NAV.label,\n        href: '/dashboard/business/shipping',\n        icon: Truck,\n        requiredBehavior: ['shippable'],\n        requiredPermission: ['canManageSettings'],\n      },\n      // Staff and Reports are pages whose sections hold what would otherwise\n      // be rows: Employees and Permissions, and the four reports. A row that\n      // opens onto more rows is a second menu inside the first.\n      {\n        id: 'team',\n        name: staffTaken ? 'Staff access' : 'Staff',\n        href: '/dashboard/staff',\n        icon: UserCog,\n        requiredPermission: ['canManageTeam'],\n      },\n      ...(hideReports()\n        ? []\n        : [\n            {\n              id: 'reports',\n              name: 'Reports',\n              href: '/dashboard/analytics/reports',\n              icon: BarChart3,\n              requiredPermission: ['canViewAnalytics'],\n            } satisfies NavItem,\n          ]),\n    ]),\n  };\n}\n"],"mappings":"AAUA;AAAA,EACE;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,OACK;AACP,SAAS,cAAc,qBAAqB;AAC5C,SAAS,mBAAmB;AAE5B,SAAS,oBAAoB;AAG7B,MAAM,cAAc,MAAM,QAAQ,IAAI,iCAAiC;AAEhE,SAAS,qBACd,aACA;AAAA,EACE,aAAa;AACf,IAQI,CAAC,GACK;AACV,SAAO;AAAA,IACL,IAAI;AAAA,IACJ,OAAO;AAAA,IACP,MAAM;AAAA,IACN,oBAAoB,CAAC,mBAAmB;AAAA,IACxC,WAAW;AAAA,IACX,OAAO,YAAY;AAAA;AAAA;AAAA;AAAA,MAIjB;AAAA,QACE,IAAI;AAAA,QACJ,MAAM,cAAc;AAAA,QACpB,MAAM;AAAA,QACN,MAAM;AAAA,QACN,oBAAoB,CAAC,mBAAmB;AAAA,MAC1C;AAAA;AAAA;AAAA,MAGA,GAAI,eACA,CAAC,IACD;AAAA,QACE;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,mBAAmB;AAAA,QAC1C;AAAA,MACF;AAAA;AAAA;AAAA,MAGJ,GAAI,YAAY,IACZ,CAAC,IACD;AAAA,QACE;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,kBAAkB,CAAC,UAAU;AAAA,UAC7B,oBAAoB,CAAC,mBAAmB;AAAA,QAC1C;AAAA,MACF;AAAA,MACJ;AAAA,QACE,IAAI;AAAA,QACJ,MAAM,aAAa;AAAA,QACnB,MAAM;AAAA,QACN,MAAM;AAAA,QACN,kBAAkB,CAAC,WAAW;AAAA,QAC9B,oBAAoB,CAAC,mBAAmB;AAAA,MAC1C;AAAA;AAAA;AAAA;AAAA,MAIA;AAAA,QACE,IAAI;AAAA,QACJ,MAAM,aAAa,iBAAiB;AAAA,QACpC,MAAM;AAAA,QACN,MAAM;AAAA,QACN,oBAAoB,CAAC,eAAe;AAAA,MACtC;AAAA,MACA,GAAI,YAAY,IACZ,CAAC,IACD;AAAA,QACE;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,kBAAkB;AAAA,QACzC;AAAA,MACF;AAAA,IACN,CAAC;AAAA,EACH;AACF;","names":[]}

package/dist/sidebar/spine-website.d.ts

@@ -0,0 +1,6 @@
+import { type NavItem, type NavGroup } from './config';
+export interface WebsiteGroupDeps {
+    filterItems: (items: NavItem[]) => NavItem[];
+    coreItem: (id: string, labelOverride?: string) => NavItem | null;
+}
+export declare function buildWebsiteGroup({ filterItems, coreItem, }: WebsiteGroupDeps): NavGroup;

package/dist/sidebar/spine-website.js

@@ -0,0 +1,90 @@
+import { Globe, Images, Link2, SlidersHorizontal } from "lucide-react";
+function buildWebsiteGroup({
+  filterItems,
+  coreItem
+}) {
+  return {
+    id: "website",
+    label: "Website",
+    icon: Globe,
+    href: "/dashboard/business",
+    /**
+     * The last "Overview" in the spine, and the word named nothing here either.
+     * Every other hub says what you are about to look at — Transactions,
+     * Campaigns, Sales, All customers — and this page is the most literal of
+     * the lot: it opens on the site itself, a live preview with the template
+     * it is running, whether it is published, and what is unsaved. Its own
+     * body comment makes the point, that the page should open on the site and
+     * not on a URL.
+     *
+     * "Your site" rather than "Site": the group above already reads Website,
+     * and a child echoing its parent one indent down is the confusion the
+     * Analytics hub spelled out when it refused to call its own view
+     * Customers. The possessive does the same work "All" does for the customer
+     * directory — it makes the row a place rather than a repeat.
+     */
+    landingLabel: "Your site",
+    // Anybody may look at the shop window. Every row inside this group needs a
+    // manage grant, so without this the group vanished for the person whose
+    // job most depends on seeing the site — somebody adding products, checking
+    // how one appears to a customer. Editing still needs canManageEditor.
+    requiredPermission: [
+      "canViewWebsite",
+      "canManageEditor",
+      "canManageBusinessProfile"
+    ],
+    items: filterItems(
+      [
+        // Templates (Change template) is reached from the hub and is not
+        // duplicated here.
+        //
+        // Domains IS a row. It was left off on the same reasoning — "reached
+        // from the hub's Address card" — which held only while the hub was a
+        // screen you landed on. It has since grown a list, an add flow, a
+        // record view, renewals, DNS records and transfers, and none of that
+        // is an address card. A surface with three routes and no way in from
+        // the nav is the same hole Campaigns was in.
+        {
+          id: "domains",
+          name: "Domains",
+          href: "/dashboard/business/domains",
+          icon: Link2,
+          requiredPermission: ["canManageDomains"]
+        },
+        //
+        // Pages is not here either, and no longer has a screen of its own.
+        // It was a list whose only verb was "Edit", which opened the editor;
+        // the editor now owns the page list, create, and publish, in the
+        // place the work happens. What is left in this group is everything
+        // about the site that is not the site's layout.
+        // Gallery is every business's: the editor's image picker reads these
+        // photos, so they need a home outside the editor whether or not the
+        // site publishes a gallery page (`showcase` gates only that page).
+        {
+          id: "gallery",
+          name: "Gallery",
+          href: "/dashboard/business/gallery",
+          icon: Images,
+          requiredPermission: ["canManageProducts"]
+        },
+        // Checkout is not a row: it is a section of Site settings (John,
+        // 2026-10-11), at /dashboard/business/preferences?section=checkout.
+        {
+          id: "preferences",
+          // "Site settings", the page's own title: identity, domain, search,
+          // social, access, accounts, privacy and integrations in one place.
+          name: "Site settings",
+          href: "/dashboard/business/preferences",
+          icon: SlidersHorizontal,
+          requiredPermission: ["canManageSettings"]
+        },
+        // Blog is content/CMS — it belongs with the Website, not Marketing.
+        coreItem("blog", "Blog")
+      ].filter(Boolean)
+    )
+  };
+}
+export {
+  buildWebsiteGroup
+};
+//# sourceMappingURL=spine-website.js.map

package/dist/sidebar/spine-website.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/spine-website.ts"],"sourcesContent":["/**\n * The Website hub, lifted out of `spine-groups.ts`.\n *\n * Not an arbitrary cut. That file crossed the 500-line house limit, and this is\n * the group with the least in common with the rest of the spine: every other\n * hub in there is a view over the business's records, and this one is the shop\n * window plus the tools that build it. It is also the only group whose shape\n * changes with the merchant's template rather than with their permissions\n * alone, which is why it carries the most explanation per row.\n *\n * It takes exactly what it reads and nothing else, so what the Website rows\n * depend on is a signature rather than a search through a closure.\n */\nimport { Globe, Images, Link2, SlidersHorizontal } from 'lucide-react';\nimport { type NavItem, type NavGroup } from './config';\n\nexport interface WebsiteGroupDeps {\n  filterItems: (items: NavItem[]) => NavItem[];\n  coreItem: (id: string, labelOverride?: string) => NavItem | null;\n}\n\nexport function buildWebsiteGroup({\n  filterItems,\n  coreItem,\n}: WebsiteGroupDeps): NavGroup {\n  return {\n    id: 'website',\n    label: 'Website',\n    icon: Globe,\n    href: '/dashboard/business',\n    /**\n     * The last \"Overview\" in the spine, and the word named nothing here either.\n     * Every other hub says what you are about to look at — Transactions,\n     * Campaigns, Sales, All customers — and this page is the most literal of\n     * the lot: it opens on the site itself, a live preview with the template\n     * it is running, whether it is published, and what is unsaved. Its own\n     * body comment makes the point, that the page should open on the site and\n     * not on a URL.\n     *\n     * \"Your site\" rather than \"Site\": the group above already reads Website,\n     * and a child echoing its parent one indent down is the confusion the\n     * Analytics hub spelled out when it refused to call its own view\n     * Customers. The possessive does the same work \"All\" does for the customer\n     * directory — it makes the row a place rather than a repeat.\n     */\n    landingLabel: 'Your site',\n    // Anybody may look at the shop window. Every row inside this group needs a\n    // manage grant, so without this the group vanished for the person whose\n    // job most depends on seeing the site — somebody adding products, checking\n    // how one appears to a customer. Editing still needs canManageEditor.\n    requiredPermission: [\n      'canViewWebsite',\n      'canManageEditor',\n      'canManageBusinessProfile',\n    ],\n    items: filterItems(\n      [\n        // Templates (Change template) is reached from the hub and is not\n        // duplicated here.\n        //\n        // Domains IS a row. It was left off on the same reasoning — \"reached\n        // from the hub's Address card\" — which held only while the hub was a\n        // screen you landed on. It has since grown a list, an add flow, a\n        // record view, renewals, DNS records and transfers, and none of that\n        // is an address card. A surface with three routes and no way in from\n        // the nav is the same hole Campaigns was in.\n        {\n          id: 'domains',\n          name: 'Domains',\n          href: '/dashboard/business/domains',\n          icon: Link2,\n          requiredPermission: ['canManageDomains'],\n        },\n        //\n        // Pages is not here either, and no longer has a screen of its own.\n        // It was a list whose only verb was \"Edit\", which opened the editor;\n        // the editor now owns the page list, create, and publish, in the\n        // place the work happens. What is left in this group is everything\n        // about the site that is not the site's layout.\n        // Gallery is every business's: the editor's image picker reads these\n        // photos, so they need a home outside the editor whether or not the\n        // site publishes a gallery page (`showcase` gates only that page).\n        {\n          id: 'gallery',\n          name: 'Gallery',\n          href: '/dashboard/business/gallery',\n          icon: Images,\n          requiredPermission: ['canManageProducts'],\n        },\n        // Checkout is not a row: it is a section of Site settings (John,\n        // 2026-10-11), at /dashboard/business/preferences?section=checkout.\n        {\n          id: 'preferences',\n          // \"Site settings\", the page's own title: identity, domain, search,\n          // social, access, accounts, privacy and integrations in one place.\n          name: 'Site settings',\n          href: '/dashboard/business/preferences',\n          icon: SlidersHorizontal,\n          requiredPermission: ['canManageSettings'],\n        },\n        // Blog is content/CMS — it belongs with the Website, not Marketing.\n        coreItem('blog', 'Blog'),\n      ].filter(Boolean) as NavItem[],\n    ),\n  };\n}\n"],"mappings":"AAaA,SAAS,OAAO,QAAQ,OAAO,yBAAyB;AAQjD,SAAS,kBAAkB;AAAA,EAChC;AAAA,EACA;AACF,GAA+B;AAC7B,SAAO;AAAA,IACL,IAAI;AAAA,IACJ,OAAO;AAAA,IACP,MAAM;AAAA,IACN,MAAM;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAgBN,cAAc;AAAA;AAAA;AAAA;AAAA;AAAA,IAKd,oBAAoB;AAAA,MAClB;AAAA,MACA;AAAA,MACA;AAAA,IACF;AAAA,IACA,OAAO;AAAA,MACL;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,QAUE;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,kBAAkB;AAAA,QACzC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,QAUA;AAAA,UACE,IAAI;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,mBAAmB;AAAA,QAC1C;AAAA;AAAA;AAAA,QAGA;AAAA,UACE,IAAI;AAAA;AAAA;AAAA,UAGJ,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,UACN,oBAAoB,CAAC,mBAAmB;AAAA,QAC1C;AAAA;AAAA,QAEA,SAAS,QAAQ,MAAM;AAAA,MACzB,EAAE,OAAO,OAAO;AAAA,IAClB;AAAA,EACF;AACF;","names":[]}

package/dist/sidebar/takes-money.d.ts

@@ -0,0 +1,15 @@
+import type { ContentBehavior } from '@withpotter/lib/template-types';
+/**
+ * Whether anything is ever charged a customer in this shell.
+ *
+ * What it decides: the Money group (Payments, Payouts, Disputes) and the
+ * Loyalty row. A pure `capture-leads` business — an estate agent, a school, an
+ * insurance broker — never takes a payment on Box, and was being handed
+ * three screens that cannot have a row in them plus a rewards programme for
+ * people who cannot buy anything.
+ *
+ * It is the same argument the absent Orders row already makes for
+ * `capture-leads` and `send-invoices`: an always-empty screen reads as broken
+ * software, not as an empty state.
+ */
+export declare function shellTakesMoney(behaviors: readonly ContentBehavior[]): boolean;

package/dist/sidebar/takes-money.js

@@ -0,0 +1,12 @@
+const NEVER_CHARGES = [
+  "leadCapture",
+  "publishable",
+  "showcase"
+];
+function shellTakesMoney(behaviors) {
+  return behaviors.some((behavior) => !NEVER_CHARGES.includes(behavior));
+}
+export {
+  shellTakesMoney
+};
+//# sourceMappingURL=takes-money.js.map

package/dist/sidebar/takes-money.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/takes-money.ts"],"sourcesContent":["import type { ContentBehavior } from '@withpotter/lib/template-types';\n\n/**\n * The behaviours where nothing is ever charged on Box.\n *\n * Stated as the exclusions rather than as a list of paying behaviours, and\n * deliberately: a new transactional behaviour added later counts as money\n * without anyone remembering to come back here, and the failure direction is\n * the safe one — showing Money to a business that does not need it is a much\n * smaller mistake than hiding it from one that does.\n *\n * `billable` is NOT here. An invoice gets paid, and `record-payment` on the API\n * writes a transaction that lands on exactly the screens this gates.\n */\nconst NEVER_CHARGES: readonly string[] = [\n  'leadCapture',\n  'publishable',\n  'showcase',\n];\n\n/**\n * Whether anything is ever charged a customer in this shell.\n *\n * What it decides: the Money group (Payments, Payouts, Disputes) and the\n * Loyalty row. A pure `capture-leads` business — an estate agent, a school, an\n * insurance broker — never takes a payment on Box, and was being handed\n * three screens that cannot have a row in them plus a rewards programme for\n * people who cannot buy anything.\n *\n * It is the same argument the absent Orders row already makes for\n * `capture-leads` and `send-invoices`: an always-empty screen reads as broken\n * software, not as an empty state.\n */\nexport function shellTakesMoney(\n  behaviors: readonly ContentBehavior[],\n): boolean {\n  return behaviors.some((behavior) => !NEVER_CHARGES.includes(behavior));\n}\n"],"mappings":"AAcA,MAAM,gBAAmC;AAAA,EACvC;AAAA,EACA;AAAA,EACA;AACF;AAeO,SAAS,gBACd,WACS;AACT,SAAO,UAAU,KAAK,CAAC,aAAa,CAAC,cAAc,SAAS,QAAQ,CAAC;AACvE;","names":[]}

package/dist/sidebar/use-nav-badges.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Counts a nav row is allowed to wear, keyed by nav item id.
+ *
+ * The rule this follows, and the reason there is only one entry: **a badge
+ * counts work, not population.** Every shop always has abandoned carts, so a
+ * badge on the whole list would never read zero, and a number that never
+ * empties is wallpaper inside a week — which costs you the one occasion it
+ * mattered. `needsAttention` is the subset a person is the only remaining
+ * answer for: past the window the recovery sweep gives up on, still open, and
+ * attached to someone we hold an address for. It reaches zero, so it is worth
+ * looking at.
+ *
+ * Anything added here has to clear the same bar. A count that cannot be driven
+ * to zero by doing the work does not belong in the sidebar.
+ *
+ * MERCHANT NOTIFICATIONS JOIN THEM (John, 2026-09-03: *"the navs should have
+ * their own notifications, we don't need a centre notification icon"*). They
+ * clear the bar for the same reason the others do — arriving at the section
+ * reads them — and the routing is in `use-nav-notifications`, which is where
+ * the argument for distributing the bell is written down.
+ */
+export declare function useNavBadges(): Record<string, number>;

package/dist/sidebar/use-nav-badges.js

@@ -0,0 +1,60 @@
+"use client";
+import { useApiQuery } from "@withpotter/hooks/use-api-query";
+import { useDemoMode } from "@withpotter/hooks/use-demo-mode";
+import { abandonedCartApi } from "@withpotter/lib/api/abandoned-cart";
+import { conversationsApi } from "@withpotter/lib/api/conversations";
+import { BOX_HIDE_WHATSAPP } from "@withpotter/lib/box-channels";
+import { waitlistApi } from "@withpotter/lib/api/waitlist";
+import { useIntentConfig } from "@withpotter/lib/intents/use-intent-config";
+import { useEnabledBehaviors } from "@withpotter/hooks/use-enabled-behaviors";
+import { useNavNotifications } from "./use-nav-notifications";
+import { DEMO_ABANDONED_CART_STATS } from "@withpotter/pages-marketing/dashboard/(marketing)/marketing/automations/abandoned-cart/demo-data";
+function useNavBadges() {
+  const demo = useDemoMode();
+  const intentConfig = useIntentConfig();
+  const hasAbandonedRow = useEnabledBehaviors().includes("sellable");
+  const stats = useApiQuery(
+    ["abandoned-cart-stats"],
+    (s) => abandonedCartApi.getStats(s),
+    { enabled: !demo && hasAbandonedRow }
+  );
+  const needsAttention = demo ? DEMO_ABANDONED_CART_STATS.needsAttention : stats.data?.needsAttention ?? 0;
+  const booksItsQueue = intentConfig.all.some(
+    (config) => config.navigation.groups.some(
+      (group) => group.items.some(
+        (item) => item.id === "orders" && item.href.startsWith("/dashboard/bookings")
+      )
+    )
+  );
+  const today = /* @__PURE__ */ new Date();
+  const day = `${today.getFullYear()}-${String(today.getMonth() + 1).padStart(
+    2,
+    "0"
+  )}-${String(today.getDate()).padStart(2, "0")}`;
+  const queue = useApiQuery(
+    ["nav-waitlist-today", day],
+    (s) => waitlistApi.queue(s, day),
+    { enabled: !demo && booksItsQueue }
+  );
+  const waitingToday = Array.isArray(queue.data) ? queue.data.length : queue.data?.data?.length ?? 0;
+  const conversations = useApiQuery(
+    ["nav-unread-conversations"],
+    (s) => conversationsApi.unread(s),
+    // Threads are WhatsApp; a box without WhatsApp has nothing to count.
+    { enabled: !demo && !BOX_HIDE_WHATSAPP }
+  );
+  const unreadThreads = demo || BOX_HIDE_WHATSAPP ? 0 : conversations.data?.threads ?? 0;
+  const notifications = useNavNotifications();
+  const merged = { ...notifications };
+  const add = (id, n) => {
+    if (n > 0) merged[id] = (merged[id] ?? 0) + n;
+  };
+  add("abandoned", needsAttention);
+  if (booksItsQueue) add("orders", waitingToday);
+  add("inbox", unreadThreads);
+  return merged;
+}
+export {
+  useNavBadges
+};
+//# sourceMappingURL=use-nav-badges.js.map

package/dist/sidebar/use-nav-badges.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/use-nav-badges.ts"],"sourcesContent":["'use client';\n\nimport { useApiQuery } from '@withpotter/hooks/use-api-query';\nimport { useDemoMode } from '@withpotter/hooks/use-demo-mode';\nimport { abandonedCartApi } from '@withpotter/lib/api/abandoned-cart';\nimport { conversationsApi } from '@withpotter/lib/api/conversations';\nimport { BOX_HIDE_WHATSAPP } from '@withpotter/lib/box-channels';\nimport { waitlistApi } from '@withpotter/lib/api/waitlist';\nimport { useIntentConfig } from '@withpotter/lib/intents/use-intent-config';\nimport { useEnabledBehaviors } from '@withpotter/hooks/use-enabled-behaviors';\nimport { useNavNotifications } from './use-nav-notifications';\nimport { DEMO_ABANDONED_CART_STATS } from '@withpotter/pages-marketing/dashboard/(marketing)/marketing/automations/abandoned-cart/demo-data';\n\n/**\n * Counts a nav row is allowed to wear, keyed by nav item id.\n *\n * The rule this follows, and the reason there is only one entry: **a badge\n * counts work, not population.** Every shop always has abandoned carts, so a\n * badge on the whole list would never read zero, and a number that never\n * empties is wallpaper inside a week — which costs you the one occasion it\n * mattered. `needsAttention` is the subset a person is the only remaining\n * answer for: past the window the recovery sweep gives up on, still open, and\n * attached to someone we hold an address for. It reaches zero, so it is worth\n * looking at.\n *\n * Anything added here has to clear the same bar. A count that cannot be driven\n * to zero by doing the work does not belong in the sidebar.\n *\n * MERCHANT NOTIFICATIONS JOIN THEM (John, 2026-09-03: *\"the navs should have\n * their own notifications, we don't need a centre notification icon\"*). They\n * clear the bar for the same reason the others do — arriving at the section\n * reads them — and the routing is in `use-nav-notifications`, which is where\n * the argument for distributing the bell is written down.\n */\nexport function useNavBadges(): Record<string, number> {\n  const demo = useDemoMode();\n  const intentConfig = useIntentConfig();\n\n  /**\n   * Whether this business HAS an abandoned-carts row to badge.\n   *\n   * A salon does not have a cart to abandon, and the row only exists where\n   * there is a storefront checkout. This asked anyway, from the sidebar, which\n   * is on every page — one request per page load, on every screen, for a number\n   * with nowhere to go.\n   *\n   * It used to ask the navigation itself, walking every archetype's groups for\n   * an item id, on the principle that the badge and the row it hangs on cannot\n   * then disagree. That principle survived the row moving to Marketing on\n   * 2026-09-03 and the walk did not: the configs stopped declaring\n   * `abandoned`, so the check silently answered false everywhere and the badge\n   * went quiet on a row that was still on the screen. A count that turns\n   * itself off is worse than one that was never built, because the sidebar\n   * still looks answered.\n   *\n   * So it asks the same question the row does, in the same words —\n   * `enabledBehaviors.includes('sellable')`, which is the gate in\n   * `spine-groups`. Two copies of one condition, and they are one grep apart.\n   */\n  const hasAbandonedRow = useEnabledBehaviors().includes('sellable');\n\n  /**\n   * One small GET, shared by every screen through the query cache.\n   *\n   * `enabled` is off in demo so the seed answers instead — the sidebar is on\n   * every page, and a demo tenant whose API 500s would otherwise paint the\n   * failure into the chrome of the entire app.\n   */\n  const stats = useApiQuery(\n    ['abandoned-cart-stats'],\n    (s) => abandonedCartApi.getStats(s),\n    { enabled: !demo && hasAbandonedRow },\n  );\n\n  const needsAttention = demo\n    ? DEMO_ABANDONED_CART_STATS.needsAttention\n    : (stats.data?.needsAttention ?? 0);\n\n  /**\n   * Whether this business's Orders row is actually an appointment book.\n   *\n   * The row carries the id `orders` for every archetype — a shop's queue and a\n   * salon's day are the same id pointing at different screens — so the badge\n   * has to ask where the row goes rather than what it is called. A shop must\n   * never get a waitlist count on Orders.\n   */\n  const booksItsQueue = intentConfig.all.some((config) =>\n    config.navigation.groups.some((group) =>\n      group.items.some(\n        (item) =>\n          item.id === 'orders' && item.href.startsWith('/dashboard/bookings'),\n      ),\n    ),\n  );\n\n  /**\n   * People waiting for a slot TODAY, not everybody on the list.\n   *\n   * The rule above is the reason for the narrowing. A salon's waitlist is\n   * never empty, so a badge counting all of it would never read zero and would\n   * be wallpaper inside a week. Today's queue empties every night and is the\n   * number a desk acts on: it is who to ring the moment something frees.\n   */\n  const today = new Date();\n  const day = `${today.getFullYear()}-${String(today.getMonth() + 1).padStart(\n    2,\n    '0',\n  )}-${String(today.getDate()).padStart(2, '0')}`;\n  const queue = useApiQuery(\n    ['nav-waitlist-today', day],\n    (s) => waitlistApi.queue(s, day),\n    { enabled: !demo && booksItsQueue },\n  );\n  const waitingToday = Array.isArray(queue.data)\n    ? queue.data.length\n    : (queue.data?.data?.length ?? 0);\n\n  /**\n   * Somebody messaged the business and nobody has read it.\n   *\n   * The only thing on this list that arrives while the merchant is looking at\n   * another screen. An abandoned cart and a waitlist entry are states you go\n   * and check; a WhatsApp message is a person waiting for an answer, and until\n   * now nothing anywhere said one had come in — the Inbox showed it only to\n   * someone who already thought to open the Inbox.\n   *\n   * THREADS, not messages. Six messages from one person is one conversation to\n   * open, and a badge reading \"6\" over one thing to do is a number a merchant\n   * stops believing within a week — the same reasoning the waitlist count is\n   * narrowed to today under.\n   *\n   * Not gated on anything. Every business can be messaged, and an API without\n   * inbound simply fails this request: `useApiQuery` leaves the count at zero\n   * and the row wears no badge, which is the correct chrome for a deployment\n   * that cannot receive.\n   */\n  const conversations = useApiQuery(\n    ['nav-unread-conversations'],\n    (s) => conversationsApi.unread(s),\n    // Threads are WhatsApp; a box without WhatsApp has nothing to count.\n    { enabled: !demo && !BOX_HIDE_WHATSAPP },\n  );\n  const unreadThreads =\n    demo || BOX_HIDE_WHATSAPP ? 0 : (conversations.data?.threads ?? 0);\n\n  /**\n   * Everything that HAPPENED, on the row it happened to — the bell's contents,\n   * distributed. See `use-nav-notifications`.\n   */\n  const notifications = useNavNotifications();\n\n  /**\n   * Merged, and a row that has both ADDS them.\n   *\n   * Orders can carry a waitlist count (people to ring) and a notification\n   * count (an order that arrived while you were elsewhere) at the same time,\n   * and both are work waiting on that row. Two numbers on one row would be the\n   * merchant doing the addition; showing the larger would hide the other.\n   */\n  const merged: Record<string, number> = { ...notifications };\n  const add = (id: string, n: number) => {\n    if (n > 0) merged[id] = (merged[id] ?? 0) + n;\n  };\n  add('abandoned', needsAttention);\n  if (booksItsQueue) add('orders', waitingToday);\n  add('inbox', unreadThreads);\n\n  return merged;\n}\n"],"mappings":";AAEA,SAAS,mBAAmB;AAC5B,SAAS,mBAAmB;AAC5B,SAAS,wBAAwB;AACjC,SAAS,wBAAwB;AACjC,SAAS,yBAAyB;AAClC,SAAS,mBAAmB;AAC5B,SAAS,uBAAuB;AAChC,SAAS,2BAA2B;AACpC,SAAS,2BAA2B;AACpC,SAAS,iCAAiC;AAuBnC,SAAS,eAAuC;AACrD,QAAM,OAAO,YAAY;AACzB,QAAM,eAAe,gBAAgB;AAuBrC,QAAM,kBAAkB,oBAAoB,EAAE,SAAS,UAAU;AASjE,QAAM,QAAQ;AAAA,IACZ,CAAC,sBAAsB;AAAA,IACvB,CAAC,MAAM,iBAAiB,SAAS,CAAC;AAAA,IAClC,EAAE,SAAS,CAAC,QAAQ,gBAAgB;AAAA,EACtC;AAEA,QAAM,iBAAiB,OACnB,0BAA0B,iBACzB,MAAM,MAAM,kBAAkB;AAUnC,QAAM,gBAAgB,aAAa,IAAI;AAAA,IAAK,CAAC,WAC3C,OAAO,WAAW,OAAO;AAAA,MAAK,CAAC,UAC7B,MAAM,MAAM;AAAA,QACV,CAAC,SACC,KAAK,OAAO,YAAY,KAAK,KAAK,WAAW,qBAAqB;AAAA,MACtE;AAAA,IACF;AAAA,EACF;AAUA,QAAM,QAAQ,oBAAI,KAAK;AACvB,QAAM,MAAM,GAAG,MAAM,YAAY,CAAC,IAAI,OAAO,MAAM,SAAS,IAAI,CAAC,EAAE;AAAA,IACjE;AAAA,IACA;AAAA,EACF,CAAC,IAAI,OAAO,MAAM,QAAQ,CAAC,EAAE,SAAS,GAAG,GAAG,CAAC;AAC7C,QAAM,QAAQ;AAAA,IACZ,CAAC,sBAAsB,GAAG;AAAA,IAC1B,CAAC,MAAM,YAAY,MAAM,GAAG,GAAG;AAAA,IAC/B,EAAE,SAAS,CAAC,QAAQ,cAAc;AAAA,EACpC;AACA,QAAM,eAAe,MAAM,QAAQ,MAAM,IAAI,IACzC,MAAM,KAAK,SACV,MAAM,MAAM,MAAM,UAAU;AAqBjC,QAAM,gBAAgB;AAAA,IACpB,CAAC,0BAA0B;AAAA,IAC3B,CAAC,MAAM,iBAAiB,OAAO,CAAC;AAAA;AAAA,IAEhC,EAAE,SAAS,CAAC,QAAQ,CAAC,kBAAkB;AAAA,EACzC;AACA,QAAM,gBACJ,QAAQ,oBAAoB,IAAK,cAAc,MAAM,WAAW;AAMlE,QAAM,gBAAgB,oBAAoB;AAU1C,QAAM,SAAiC,EAAE,GAAG,cAAc;AAC1D,QAAM,MAAM,CAAC,IAAY,MAAc;AACrC,QAAI,IAAI,EAAG,QAAO,EAAE,KAAK,OAAO,EAAE,KAAK,KAAK;AAAA,EAC9C;AACA,MAAI,aAAa,cAAc;AAC/B,MAAI,cAAe,KAAI,UAAU,YAAY;AAC7C,MAAI,SAAS,aAAa;AAE1B,SAAO;AACT;","names":[]}

package/dist/sidebar/use-nav-notifications.d.ts

@@ -0,0 +1 @@
+export declare function useNavNotifications(): Record<string, number>;