@withpotter/components 0.13.0-next.101

package/dist/sidebar/config.js

@@ -0,0 +1,186 @@
+import {
+  CreditCard,
+  Users,
+  Bell,
+  Scale,
+  UserRound,
+  LayoutGrid,
+  SlidersHorizontal,
+  ToggleLeft,
+  Database,
+  ShieldCheck,
+  Accessibility,
+  ChartColumn,
+  Sparkles
+} from "lucide-react";
+import { INTENT_ICON_MAP } from "@withpotter/lib/intents/icon-map";
+const ICON_MAP = INTENT_ICON_MAP;
+import {
+  INTENT_ITEM_PERMISSIONS,
+  CORE_TOOL_PERMISSIONS
+} from "./nav-permissions";
+const EXACT_MATCH_ROUTES = /* @__PURE__ */ new Set([
+  "/dashboard",
+  "/dashboard/settings"
+]);
+const PLATFORM_CONTENT_TYPES = /* @__PURE__ */ new Set(["product", "products"]);
+const PLATFORM_CONTENT_ROUTES = /* @__PURE__ */ new Set([
+  "/dashboard/content/product",
+  "/dashboard/content/products"
+]);
+const ACCOUNT_GROUPS = [
+  {
+    label: "Account",
+    items: [
+      { name: "Account", href: "/dashboard/settings/profile", icon: UserRound },
+      {
+        name: "Login & security",
+        href: "/dashboard/settings/devices",
+        icon: ShieldCheck
+      },
+      { name: "Businesses", href: "/dashboard/workspaces", icon: LayoutGrid },
+      {
+        name: "Preferences",
+        href: "/dashboard/settings/language",
+        icon: SlidersHorizontal
+      },
+      // Reachable from the mobile Me screen and from nowhere on desktop, so
+      // the setting a merchant needs in order to USE the product was the one
+      // they could not navigate to.
+      {
+        name: "Accessibility",
+        href: "/dashboard/settings/accessibility",
+        icon: Accessibility
+      },
+      {
+        name: "Data & privacy",
+        href: "/dashboard/settings/data-privacy",
+        icon: Database
+      },
+      { name: "Legal", href: "/dashboard/settings/legal", icon: Scale }
+    ]
+  }
+];
+const BUSINESS_GROUPS = [
+  {
+    // No heading. See the note above — the order is the structure.
+    label: "",
+    items: [
+      // IDENTITY — who this workspace is.
+      {
+        name: "General",
+        href: "/dashboard/settings",
+        match: ["/dashboard/settings/branding", "/dashboard/settings/regional"],
+        icon: SlidersHorizontal
+      },
+      // FEATURES — the switches no business type implies (Blog today).
+      // Business types themselves are Explore's, see below.
+      {
+        name: "Features",
+        href: "/dashboard/settings/features",
+        icon: ToggleLeft
+      },
+      // NO BUSINESS TYPE ROW. It moved out of Settings entirely on
+      // 2026-09-03 and became `/dashboard/explore` with a rail row of its own.
+      //
+      // The page always DID the right thing — picking a model derives the
+      // behaviour set that builds the sidebar — and nobody could find it. It
+      // was three names deep in the wrong place: behind Workspace settings,
+      // under a heading a merchant does not type when the thought is "can
+      // Box do events?". A settings list is where you go to change
+      // something you already have, and this is where you go to get something
+      // you do not.
+      //
+      // `/dashboard/settings/features` is Features again (above): it no longer
+      // holds the business model, only the switches no model implies.
+      // MONEY, then the PEOPLE who can spend it.
+      // A licensed box that bills outside the console hides the row.
+      ...process.env.NEXT_PUBLIC_BOX_HIDE_BILLING === "true" ? [] : [
+        {
+          // Per business: each tenant has its own subscription.
+          name: "Billing & plan",
+          href: "/dashboard/settings/billing",
+          icon: CreditCard
+        }
+      ],
+      {
+        // What the plan is being spent on: fees, credits, delivery. Billing is
+        // the bill; this is the meter behind it. Credits are bought from here.
+        name: "Usage",
+        href: "/dashboard/settings/usage",
+        match: ["/dashboard/settings/billing/credits"],
+        icon: ChartColumn
+      },
+      {
+        name: "Team & permissions",
+        href: "/dashboard/settings/team",
+        match: ["/dashboard/settings/roles", "/dashboard/settings/activity"],
+        icon: Users
+      },
+      // THE TERMS, and who gets told.
+      { name: "Policies", href: "/dashboard/settings/policies", icon: Scale },
+      {
+        // Configuration, not history. This sat beside Activity, which is the
+        // log — so the one screen that decides whether a customer is told
+        // anything was filed with the screen reporting what already happened.
+        name: "Notifications",
+        href: "/dashboard/settings/notifications",
+        icon: Bell
+      },
+      {
+        // Sample products, pages and pictures a business can start with, clear
+        // in one go, or add again. Owner and admins act; others see the state.
+        name: "Demo content",
+        href: "/dashboard/settings/demo-content",
+        icon: Sparkles
+      }
+      // Connectors moved to Customize (2026-10-03), beside Add more: both are
+      // "what is in this workspace". `/dashboard/settings/integrations` now
+      // redirects there; its sub-routes (calendar-sync, sales-channels,
+      // tracking, a single connection) still live under Settings.
+    ]
+  }
+];
+const ACCOUNT_ROUTE_PREFIXES = [
+  "/dashboard/settings/profile",
+  "/dashboard/settings/devices",
+  "/dashboard/settings/language",
+  "/dashboard/settings/data-privacy",
+  "/dashboard/settings/legal",
+  "/dashboard/settings/accessibility"
+];
+const parseSidebarHref = (href) => {
+  const [path, query = ""] = href.split("?");
+  const params = new URLSearchParams(query);
+  return {
+    path,
+    intent: params.get("intent"),
+    /**
+     * Everything else the row narrows by — `group`, `tab`, `view`.
+     *
+     * This was `group` alone, added because a business with more than one group
+     * of bookable things reaches the roster through rows that all lead to the
+     * same PATH: without it every row lit and the tie-break picked whichever
+     * href was longer. Every OTHER param is the same row on the same path, and
+     * was still invisible — see `active-href.ts`.
+     */
+    params
+  };
+};
+const intentKeySet = (intent) => new Set(
+  (intent ?? "").split(",").map((key) => key.trim()).filter(Boolean)
+);
+export {
+  ACCOUNT_GROUPS,
+  ACCOUNT_ROUTE_PREFIXES,
+  BUSINESS_GROUPS,
+  CORE_TOOL_PERMISSIONS,
+  EXACT_MATCH_ROUTES,
+  ICON_MAP,
+  INTENT_ITEM_PERMISSIONS,
+  PLATFORM_CONTENT_ROUTES,
+  PLATFORM_CONTENT_TYPES,
+  intentKeySet,
+  parseSidebarHref
+};
+//# sourceMappingURL=config.js.map

package/dist/sidebar/config.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/config.ts"],"sourcesContent":["/**\n * The sidebar's static shape: icon and permission maps, the nav types, the\n * route sets that decide what counts as active, and the settings drill-in\n * groups.\n *\n * Split out of sidebar.tsx, which had grown to 1,510 lines — three times the\n * house limit. None of this depends on component state, so it does not belong\n * inside the component that renders it.\n */\nimport {\n  CreditCard,\n  Users,\n  Bell,\n  Scale,\n  UserRound,\n  LayoutGrid,\n  SlidersHorizontal,\n  ToggleLeft,\n  Database,\n  ShieldCheck,\n  Accessibility,\n  Globe2,\n  Palette,\n  ChartColumn,\n  Sparkles,\n} from 'lucide-react';\nimport type { LucideIcon } from 'lucide-react';\nimport { INTENT_ICON_MAP } from '@withpotter/lib/intents/icon-map';\nimport type { PermissionKey } from '@withpotter/lib/use-permissions';\n\n/** Map string icon names from IntentConfig to Lucide components */\nexport const ICON_MAP = INTENT_ICON_MAP;\n\n// The nav permission maps are data and live in ./nav-permissions, so the\n// coverage test can read them without pulling this file's icon imports in.\n// Re-exported here because every existing importer reaches for them via config.\nexport {\n  INTENT_ITEM_PERMISSIONS,\n  CORE_TOOL_PERMISSIONS,\n} from './nav-permissions';\n\nexport interface NavItem {\n  id: string;\n  name: string;\n  href: string;\n  icon: LucideIcon;\n  requiredBehavior?: string[];\n  /**\n   * The row is only drawn on a box whose capability list carries this key. A\n   * box that published no list is unchanged, so the main app keeps every row.\n   * For a screen whose backend only some engines have: without it the row led\n   * to \"Cannot GET /referrals/stats\" on a box that never had that module.\n   */\n  requiredCapability?: string;\n  /**\n   * The item is only rendered when the current team member has AT LEAST ONE of\n   * these permissions (OWNER always passes). Undefined or empty means the item\n   * is hidden from every non-owner — see INTENT_ITEM_PERMISSIONS for why the\n   * default is closed rather than open.\n   */\n  requiredPermission?: PermissionKey[];\n  /**\n   * Rows revealed under this one. An item with children renders with the same\n   * disclosure the fixed spine hubs use, so an Operations surface can carry a\n   * smaller surface (Appointments → Waitlist) without claiming a second\n   * top-level row for it.\n   */\n  children?: NavItem[];\n  /**\n   * Names this row's own landing page once it carries children.\n   *\n   * A work row with children renders through `renderHub`, which moves the\n   * row's own screen into the group as its first child — a row is a place or a\n   * container, never both. Without this the child falls back to \"Overview\",\n   * which the hub renderer says outright no new hub should rely on: every hub\n   * could carry one, so the word tells the merchant nothing about which hub\n   * they are in. `{label}` interpolates the row's post-rename label, so a\n   * tenant calling them Bookings gets \"All bookings\" rather than a literal.\n   */\n  landingLabel?: string;\n}\n\nexport interface NavGroupSection {\n  id: string;\n  label: string;\n  items: NavItem[];\n}\n\nexport interface NavGroup {\n  id: string;\n  label: string;\n  icon: LucideIcon;\n  items?: NavItem[];\n  sections?: NavGroupSection[];\n  /**\n   * With no `items`, the group is a flat top-level destination (rendered like\n   * the Home link — no chevron, no children).\n   *\n   * With `items`, this is the group's landing page, and it is rendered as the\n   * FIRST CHILD rather than on the group's own row. A row is either a place or\n   * a container, never both: a row that navigated *and* disclosed gave two\n   * answers to one click, and the highlight landed on the parent while the\n   * list that had just opened underneath it looked like a menu you had yet to\n   * choose from. See `landingLabel` for what the child is called.\n   */\n  href?: string;\n  /**\n   * What this group's landing page is called once it sits among its own\n   * children. Defaults to \"Overview\". Ignored unless the group has both an\n   * `href` and `items`.\n   *\n   * `{label}` interpolates the group's OWN label, after renaming. A hub named\n   * for a merchant-facing noun is renamed per tenant — Customers becomes\n   * Guests, Clients, Members — and a literal \"All customers\" would have sat\n   * under a hub reading \"Guests\", which is the exact mismatch `renameGroup`\n   * exists to prevent. Write `All {label}`, not `All customers`.\n   */\n  landingLabel?: string;\n  /**\n   * Where the landing page sits among the children, counting from 0. Absent, it\n   * leads, which every hub but Money wants. Money puts the wallet above its\n   * Transactions page (John, 2026-10-11): the balance a business holds is the\n   * first question, the log of what moved it the second.\n   */\n  landingAt?: number;\n  /**\n   * Only meaningful for flat (href) groups: gate visibility on AT LEAST ONE\n   * of these permissions (OWNER always passes). Collapsible groups gate at\n   * the item level instead.\n   */\n  requiredPermission?: PermissionKey[];\n  /**\n   * Render as a disclosure hub even with a single child (normally a 1-child\n   * group collapses to a flat link). Used by Inventory so Collections shows\n   * inside it.\n   */\n  alwaysHub?: boolean;\n}\n\nexport const EXACT_MATCH_ROUTES = new Set([\n  '/dashboard',\n  '/dashboard/settings',\n]);\nexport const PLATFORM_CONTENT_TYPES = new Set(['product', 'products']);\nexport const PLATFORM_CONTENT_ROUTES = new Set([\n  '/dashboard/content/product',\n  '/dashboard/content/products',\n]);\n\n/** Settings sub-nav — shown in the sidebar (drill-in) when on a settings route. */\nexport type SettingsItem = {\n  name: string;\n  href: string;\n  requires?: string;\n  requiresAny?: string[];\n  /** Extra routes that also mark this (collapsed) entry active, e.g. tabs. */\n  match?: string[];\n  /** Rail glyph. The settings rail had labels only, so it was the one nav in\n   *  the app you had to read rather than recognise — and it's the nav people\n   *  visit least often, which is exactly where recognition helps most. */\n  icon: LucideIcon;\n};\n// The settings drill-in is context-aware. At the ACCOUNT level (account,\n// security, the Workspaces hub) it shows the account's own settings. When you\n// drill into a specific workspace's setting, it becomes THAT workspace's rail.\n// BUSINESS_GROUPS is now the only place these sections are listed — the\n// per-workspace hub page that used to mirror them was a screen whose only job\n// was linking to what this rail already shows, so it was deleted.\n// Login & security is its OWN rail item, not folded into Account.\n//\n// It was meant to be folded — the note here said so — but the fold was never\n// finished: the standalone page kept passkeys, connected sign-in and the device\n// list, gained no row, and was linked from nowhere, so the richest security\n// surface in the app could only be reached by typing the URL and nothing lit up\n// when you got there. Worse, the half that DID move was duplicated rather than\n// moved: two-factor and sessions rendered on both pages, so switching 2FA on in\n// one left the other showing it off until a reload.\n//\n// One page owns security now. Account keeps who you are and the door out.\nexport const ACCOUNT_GROUPS: { label: string; items: SettingsItem[] }[] = [\n  {\n    label: 'Account',\n    items: [\n      { name: 'Account', href: '/dashboard/settings/profile', icon: UserRound },\n      {\n        name: 'Login & security',\n        href: '/dashboard/settings/devices',\n        icon: ShieldCheck,\n      },\n      { name: 'Businesses', href: '/dashboard/workspaces', icon: LayoutGrid },\n      {\n        name: 'Preferences',\n        href: '/dashboard/settings/language',\n        icon: SlidersHorizontal,\n      },\n      // Reachable from the mobile Me screen and from nowhere on desktop, so\n      // the setting a merchant needs in order to USE the product was the one\n      // they could not navigate to.\n      {\n        name: 'Accessibility',\n        href: '/dashboard/settings/accessibility',\n        icon: Accessibility,\n      },\n      {\n        name: 'Data & privacy',\n        href: '/dashboard/settings/data-privacy',\n        icon: Database,\n      },\n      { name: 'Legal', href: '/dashboard/settings/legal', icon: Scale },\n    ],\n  },\n];\n\n/**\n * ONE ORDERED LIST, NO GROUP HEADINGS.\n *\n * These rows sat under `Setup` / `Selling` / `Records` and the headings were\n * doing no work. `Setup` held Billing and Notifications, which you visit for\n * years after setting up. `Records` held exactly one row. And a merchant\n * looking for Taxes does not first decide which of the three thirds it is in —\n * they scan for the word \"Taxes\".\n *\n * Shopify carries nineteen settings rows with no headings at all and it reads\n * fine, because every label is a noun the merchant already owns. What does the\n * work there is the ORDER, and it is not alphabetical: identity, then money,\n * then people, then selling, then places, then the storefront, then the log.\n * That is the order below.\n *\n * ON THE LABELS: an ampersand is fine when the second half says what else is\n * inside — `Team & permissions`, `Billing & plan`, `Login & security`,\n * `Data & privacy` each tell you something the first word alone does not. What\n * is not fine is a word from our side of the fence:\n *\n * `Operations` → **Locations**. An umbrella nobody says out loud; the row lands\n * on the locations list, hours and booking policy are tabs of a location, and\n * Locations is what both Shopify and Square call it.\n *\n * `Integrations` → **Connections**. Integration is a developer's word for what\n * a merchant experiences as connecting their WhatsApp or their Google Calendar.\n * Not `Apps` — that is Shopify's word for a marketplace we do not have, and the\n * label would promise a store that isn't there.\n *\n * `Tracking`, not Shopify's `Customer events`: a merchant running Meta ads\n * already calls it tracking, and \"customer events\" is a platform's internal\n * noun leaking into the nav.\n */\nexport const BUSINESS_GROUPS: { label: string; items: SettingsItem[] }[] = [\n  {\n    // No heading. See the note above — the order is the structure.\n    label: '',\n    items: [\n      // IDENTITY — who this workspace is.\n      {\n        name: 'General',\n        href: '/dashboard/settings',\n        match: ['/dashboard/settings/branding', '/dashboard/settings/regional'],\n        icon: SlidersHorizontal,\n      },\n      // FEATURES — the switches no business type implies (Blog today).\n      // Business types themselves are Explore's, see below.\n      {\n        name: 'Features',\n        href: '/dashboard/settings/features',\n        icon: ToggleLeft,\n      },\n      // NO BUSINESS TYPE ROW. It moved out of Settings entirely on\n      // 2026-09-03 and became `/dashboard/explore` with a rail row of its own.\n      //\n      // The page always DID the right thing — picking a model derives the\n      // behaviour set that builds the sidebar — and nobody could find it. It\n      // was three names deep in the wrong place: behind Workspace settings,\n      // under a heading a merchant does not type when the thought is \"can\n      // Box do events?\". A settings list is where you go to change\n      // something you already have, and this is where you go to get something\n      // you do not.\n      //\n      // `/dashboard/settings/features` is Features again (above): it no longer\n      // holds the business model, only the switches no model implies.\n\n      // MONEY, then the PEOPLE who can spend it.\n      // A licensed box that bills outside the console hides the row.\n      ...(process.env.NEXT_PUBLIC_BOX_HIDE_BILLING === 'true'\n        ? []\n        : [\n            {\n              // Per business: each tenant has its own subscription.\n              name: 'Billing & plan',\n              href: '/dashboard/settings/billing',\n              icon: CreditCard,\n            },\n          ]),\n      {\n        // What the plan is being spent on: fees, credits, delivery. Billing is\n        // the bill; this is the meter behind it. Credits are bought from here.\n        name: 'Usage',\n        href: '/dashboard/settings/usage',\n        match: ['/dashboard/settings/billing/credits'],\n        icon: ChartColumn,\n      },\n      {\n        name: 'Team & permissions',\n        href: '/dashboard/settings/team',\n        match: ['/dashboard/settings/roles', '/dashboard/settings/activity'],\n        icon: Users,\n      },\n\n      // THE TERMS, and who gets told.\n      { name: 'Policies', href: '/dashboard/settings/policies', icon: Scale },\n      {\n        // Configuration, not history. This sat beside Activity, which is the\n        // log — so the one screen that decides whether a customer is told\n        // anything was filed with the screen reporting what already happened.\n        name: 'Notifications',\n        href: '/dashboard/settings/notifications',\n        icon: Bell,\n      },\n      {\n        // Sample products, pages and pictures a business can start with, clear\n        // in one go, or add again. Owner and admins act; others see the state.\n        name: 'Demo content',\n        href: '/dashboard/settings/demo-content',\n        icon: Sparkles,\n      },\n\n      // Connectors moved to Customize (2026-10-03), beside Add more: both are\n      // \"what is in this workspace\". `/dashboard/settings/integrations` now\n      // redirects there; its sub-routes (calendar-sync, sales-channels,\n      // tracking, a single connection) still live under Settings.\n    ],\n  },\n];\n\n// Settings routes that belong to the PERSON, not a business. Everything else\n// under /dashboard/settings is a business setting and gets the business rail.\nexport const ACCOUNT_ROUTE_PREFIXES = [\n  '/dashboard/settings/profile',\n  '/dashboard/settings/devices',\n  '/dashboard/settings/language',\n  '/dashboard/settings/data-privacy',\n  '/dashboard/settings/legal',\n  '/dashboard/settings/accessibility',\n];\n\nexport const parseSidebarHref = (href: string) => {\n  const [path, query = ''] = href.split('?');\n  const params = new URLSearchParams(query);\n  return {\n    path,\n    intent: params.get('intent'),\n    /**\n     * Everything else the row narrows by — `group`, `tab`, `view`.\n     *\n     * This was `group` alone, added because a business with more than one group\n     * of bookable things reaches the roster through rows that all lead to the\n     * same PATH: without it every row lit and the tie-break picked whichever\n     * href was longer. Every OTHER param is the same row on the same path, and\n     * was still invisible — see `active-href.ts`.\n     */\n    params,\n  };\n};\n\n/**\n * The archetypes an `?intent=` narrows to.\n *\n * A comma list, because a collapsed row stands for every archetype behind it —\n * a restaurant's Menu is `dine-in,food-orders`, which is neither one archetype\n * nor all of them. One key is still the common case; empty means not narrowed.\n */\nexport const intentKeySet = (intent: string | null | undefined): Set<string> =>\n  new Set(\n    (intent ?? '')\n      .split(',')\n      .map((key) => key.trim())\n      .filter(Boolean),\n  );\n"],"mappings":"AASA;AAAA,EACE;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EAGA;AAAA,EACA;AAAA,OACK;AAEP,SAAS,uBAAuB;AAIzB,MAAM,WAAW;AAKxB;AAAA,EACE;AAAA,EACA;AAAA,OACK;AAoGA,MAAM,qBAAqB,oBAAI,IAAI;AAAA,EACxC;AAAA,EACA;AACF,CAAC;AACM,MAAM,yBAAyB,oBAAI,IAAI,CAAC,WAAW,UAAU,CAAC;AAC9D,MAAM,0BAA0B,oBAAI,IAAI;AAAA,EAC7C;AAAA,EACA;AACF,CAAC;AAgCM,MAAM,iBAA6D;AAAA,EACxE;AAAA,IACE,OAAO;AAAA,IACP,OAAO;AAAA,MACL,EAAE,MAAM,WAAW,MAAM,+BAA+B,MAAM,UAAU;AAAA,MACxE;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA,MACA,EAAE,MAAM,cAAc,MAAM,yBAAyB,MAAM,WAAW;AAAA,MACtE;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA;AAAA;AAAA;AAAA,MAIA;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA,MACA;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA,MACA,EAAE,MAAM,SAAS,MAAM,6BAA6B,MAAM,MAAM;AAAA,IAClE;AAAA,EACF;AACF;AAmCO,MAAM,kBAA8D;AAAA,EACzE;AAAA;AAAA,IAEE,OAAO;AAAA,IACP,OAAO;AAAA;AAAA,MAEL;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,OAAO,CAAC,gCAAgC,8BAA8B;AAAA,QACtE,MAAM;AAAA,MACR;AAAA;AAAA;AAAA,MAGA;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAiBA,GAAI,QAAQ,IAAI,iCAAiC,SAC7C,CAAC,IACD;AAAA,QACE;AAAA;AAAA,UAEE,MAAM;AAAA,UACN,MAAM;AAAA,UACN,MAAM;AAAA,QACR;AAAA,MACF;AAAA,MACJ;AAAA;AAAA;AAAA,QAGE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,OAAO,CAAC,qCAAqC;AAAA,QAC7C,MAAM;AAAA,MACR;AAAA,MACA;AAAA,QACE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,OAAO,CAAC,6BAA6B,8BAA8B;AAAA,QACnE,MAAM;AAAA,MACR;AAAA;AAAA,MAGA,EAAE,MAAM,YAAY,MAAM,gCAAgC,MAAM,MAAM;AAAA,MACtE;AAAA;AAAA;AAAA;AAAA,QAIE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA,MACA;AAAA;AAAA;AAAA,QAGE,MAAM;AAAA,QACN,MAAM;AAAA,QACN,MAAM;AAAA,MACR;AAAA;AAAA;AAAA;AAAA;AAAA,IAMF;AAAA,EACF;AACF;AAIO,MAAM,yBAAyB;AAAA,EACpC;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAEO,MAAM,mBAAmB,CAAC,SAAiB;AAChD,QAAM,CAAC,MAAM,QAAQ,EAAE,IAAI,KAAK,MAAM,GAAG;AACzC,QAAM,SAAS,IAAI,gBAAgB,KAAK;AACxC,SAAO;AAAA,IACL;AAAA,IACA,QAAQ,OAAO,IAAI,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAU3B;AAAA,EACF;AACF;AASO,MAAM,eAAe,CAAC,WAC3B,IAAI;AAAA,GACD,UAAU,IACR,MAAM,GAAG,EACT,IAAI,CAAC,QAAQ,IAAI,KAAK,CAAC,EACvB,OAAO,OAAO;AACnB;","names":[]}

package/dist/sidebar/customize-row.d.ts

@@ -0,0 +1,27 @@
+/**
+ * CUSTOMIZE — a row in the general list, with Home, Products and the rest.
+ *
+ * It used to be the last thing in the rail under its own "Your business"
+ * heading, as a section of one: a heading over a single row, which this rail's
+ * own rule says it must not do ("a heading earns its row by grouping"), and
+ * placed apart from everything else a merchant reaches for. It is one of the
+ * places a merchant goes, so it sits with them.
+ *
+ * It opens Customize, which holds Add more, Connectors and — next — the sidebar
+ * itself. The history of the label: "Add to Box" (written from the platform's
+ * side of the glass; John, 2026-09-03, *"this is a business, so you don't add to
+ * all Box na, just this business"*), then "Add more", then "Explore" before
+ * either. It is Customize now because the page is no longer only about adding.
+ *
+ * UNGATED. Adding a business model is a settings-level act and the page's own
+ * controls are gated by the model hook — but LOOKING is not, and hiding the
+ * catalogue from staff is how a merchant never finds out Box does bookings.
+ */
+export declare function CustomizeRow({ active, collapsed, highlight, label, }: {
+    /** The merchant's word for the row, when they gave one. */
+    label?: string;
+    active: boolean;
+    collapsed: boolean;
+    /** The travelling active pill, owned by the rail. */
+    highlight: (active: boolean) => React.ReactNode;
+}): import("react").JSX.Element;

package/dist/sidebar/customize-row.js

@@ -0,0 +1,29 @@
+import { jsx, jsxs } from "react/jsx-runtime";
+import Link from "next/link";
+import { Toolbox } from "lucide-react";
+import { RailLabel } from "./rail-label";
+function CustomizeRow({
+  active,
+  collapsed,
+  highlight,
+  label = "Toolkit"
+}) {
+  return /* @__PURE__ */ jsx("li", { className: "navitem", children: /* @__PURE__ */ jsx(RailLabel, { label, collapsed, children: /* @__PURE__ */ jsxs(
+    Link,
+    {
+      href: "/dashboard/toolkit",
+      prefetch: false,
+      className: `navlink${active ? " active" : ""}`,
+      "aria-label": collapsed ? label : void 0,
+      children: [
+        highlight(active),
+        /* @__PURE__ */ jsx("span", { className: "ic", children: /* @__PURE__ */ jsx(Toolbox, { width: 18, height: 18 }) }),
+        /* @__PURE__ */ jsx("span", { className: "lbl", children: label })
+      ]
+    }
+  ) }) });
+}
+export {
+  CustomizeRow
+};
+//# sourceMappingURL=customize-row.js.map

package/dist/sidebar/customize-row.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/customize-row.tsx"],"sourcesContent":["import Link from 'next/link';\nimport { Toolbox } from 'lucide-react';\nimport { RailLabel } from './rail-label';\n\n/**\n * CUSTOMIZE — a row in the general list, with Home, Products and the rest.\n *\n * It used to be the last thing in the rail under its own \"Your business\"\n * heading, as a section of one: a heading over a single row, which this rail's\n * own rule says it must not do (\"a heading earns its row by grouping\"), and\n * placed apart from everything else a merchant reaches for. It is one of the\n * places a merchant goes, so it sits with them.\n *\n * It opens Customize, which holds Add more, Connectors and — next — the sidebar\n * itself. The history of the label: \"Add to Box\" (written from the platform's\n * side of the glass; John, 2026-09-03, *\"this is a business, so you don't add to\n * all Box na, just this business\"*), then \"Add more\", then \"Explore\" before\n * either. It is Customize now because the page is no longer only about adding.\n *\n * UNGATED. Adding a business model is a settings-level act and the page's own\n * controls are gated by the model hook — but LOOKING is not, and hiding the\n * catalogue from staff is how a merchant never finds out Box does bookings.\n */\nexport function CustomizeRow({\n  active,\n  collapsed,\n  highlight,\n  label = 'Toolkit',\n}: {\n  /** The merchant's word for the row, when they gave one. */\n  label?: string;\n  active: boolean;\n  collapsed: boolean;\n  /** The travelling active pill, owned by the rail. */\n  highlight: (active: boolean) => React.ReactNode;\n}) {\n  return (\n    <li className=\"navitem\">\n      <RailLabel label={label} collapsed={collapsed}>\n        <Link\n          href=\"/dashboard/toolkit\"\n          prefetch={false}\n          className={`navlink${active ? ' active' : ''}`}\n          aria-label={collapsed ? label : undefined}\n        >\n          {highlight(active)}\n          <span className=\"ic\">\n            <Toolbox width={18} height={18} />\n          </span>\n          <span className=\"lbl\">{label}</span>\n        </Link>\n      </RailLabel>\n    </li>\n  );\n}\n"],"mappings":"AAuCQ,SAQI,KARJ;AAvCR,OAAO,UAAU;AACjB,SAAS,eAAe;AACxB,SAAS,iBAAiB;AAqBnB,SAAS,aAAa;AAAA,EAC3B;AAAA,EACA;AAAA,EACA;AAAA,EACA,QAAQ;AACV,GAOG;AACD,SACE,oBAAC,QAAG,WAAU,WACZ,8BAAC,aAAU,OAAc,WACvB;AAAA,IAAC;AAAA;AAAA,MACC,MAAK;AAAA,MACL,UAAU;AAAA,MACV,WAAW,UAAU,SAAS,YAAY,EAAE;AAAA,MAC5C,cAAY,YAAY,QAAQ;AAAA,MAE/B;AAAA,kBAAU,MAAM;AAAA,QACjB,oBAAC,UAAK,WAAU,MACd,8BAAC,WAAQ,OAAO,IAAI,QAAQ,IAAI,GAClC;AAAA,QACA,oBAAC,UAAK,WAAU,OAAO,iBAAM;AAAA;AAAA;AAAA,EAC/B,GACF,GACF;AAEJ;","names":[]}

package/dist/sidebar/declared-screens.d.ts

@@ -0,0 +1,33 @@
+/**
+ * The screens an archetype declares, for the sidebar walkthrough tests.
+ *
+ * An intent with a composer file declares them there, at its own routes. Any
+ * other archetype's are the rows listed in the nav definitions AND declared by
+ * its config, since the builder takes the href from the config and drops
+ * anything the config never declared.
+ *
+ * The two lists do drift — `sell-products` is listed as contributing
+ * Fulfillment but its config declares `service-areas` instead, so no shippable
+ * merchant has ever had a Fulfillment row. That is a real gap, and a separate
+ * one; `warnOnUnreachableNavItems` shouts about the mirror image of it in dev.
+ */
+export declare const declaredItems: (key: string) => {
+    label: string;
+    href: string;
+}[];
+/**
+ * Screens a business's archetypes declare that no sidebar row reaches.
+ *
+ * `reachable` holds row ids AND destinations: an id going missing is not a
+ * screen going missing, because a collapsed row keeps only the first
+ * claimant's id. Spine-owned ids are matched by id and skipped here.
+ */
+export declare function missingScreens(keys: readonly string[], reachable: ReadonlySet<string>, spineOwned: ReadonlySet<string>): string[];
+/**
+ * Run `fn` as if no intent had a composer file, so the shared-row system that
+ * still serves a business with no archetype can be tested with its original
+ * fixtures. A test seam: nothing outside tests calls it.
+ */
+export declare function withoutComposedIntents<T>(fn: () => T): T;
+/** A test of the shared-row system, which no composed intent goes through. */
+export declare const legacyTest: (name: string, fn: () => void) => Promise<void>;

package/dist/sidebar/declared-screens.js

@@ -0,0 +1,68 @@
+import assert from "node:assert/strict";
+import test from "node:test";
+import { COMPOSED_INTENT_KEYS } from "./composed-groups";
+import { INTENTS } from "@withpotter/components/intents";
+import { INTENT_NAV_DEFINITIONS } from "@withpotter/lib/intents/intent-nav";
+import { getIntentConfig } from "@withpotter/lib/intents/registry";
+const configFor = (key) => {
+  const config = getIntentConfig(key);
+  assert.ok(config, `no intent config registered for ${key}`);
+  return config;
+};
+const declaredItems = (key) => {
+  const composed = INTENTS.find((intent) => intent.key === key);
+  if (composed)
+    return composed.routes.filter((r) => !r.hidden).map((r) => ({
+      label: r.label,
+      href: `/dashboard/${r.path}`
+    }));
+  const config = configFor(key);
+  const declared = new Map(
+    config.navigation.groups.flatMap(
+      (g) => g.items.map((i) => [i.id, i.href])
+    )
+  );
+  return (INTENT_NAV_DEFINITIONS.find((d) => d.key === key)?.items ?? []).filter((item) => declared.has(item.id)).map((item) => ({ ...item, href: declared.get(item.id) }));
+};
+function missingScreens(keys, reachable, spineOwned) {
+  return keys.flatMap((key) => {
+    const composed = INTENTS.find((intent) => intent.key === key);
+    if (composed)
+      return composed.routes.filter(
+        (r) => !r.hidden && !reachable.has(`/dashboard/${r.path}`) && // A route whose nav id the spine owns (Enquiries, now the
+        // top-level Inbox) is matched by id like every other spine row.
+        !(r.navId && spineOwned.has(r.navId))
+      ).map((r) => `${key} \u2192 ${r.path}`);
+    const definition = INTENT_NAV_DEFINITIONS.find((d) => d.key === key);
+    const hrefById = new Map(
+      configFor(key).navigation.groups.flatMap(
+        (g) => g.items.map((i) => [i.id, i.href?.split("?")[0]])
+      )
+    );
+    const ids = (definition?.items ?? []).flatMap((i) => [
+      i.id,
+      ...(i.children ?? []).map((c) => c.id)
+    ]);
+    return ids.filter((id) => {
+      const href = hrefById.get(id);
+      return !reachable.has(id) && !(href && reachable.has(href)) && !spineOwned.has(id);
+    }).map((id) => `${key} \u2192 ${id}`);
+  });
+}
+function withoutComposedIntents(fn) {
+  const saved = [...COMPOSED_INTENT_KEYS];
+  COMPOSED_INTENT_KEYS.clear();
+  try {
+    return fn();
+  } finally {
+    for (const key of saved) COMPOSED_INTENT_KEYS.add(key);
+  }
+}
+const legacyTest = (name, fn) => test(name, () => withoutComposedIntents(fn));
+export {
+  declaredItems,
+  legacyTest,
+  missingScreens,
+  withoutComposedIntents
+};
+//# sourceMappingURL=declared-screens.js.map

package/dist/sidebar/declared-screens.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/declared-screens.ts"],"sourcesContent":["import assert from 'node:assert/strict';\nimport test from 'node:test';\nimport { COMPOSED_INTENT_KEYS } from './composed-groups';\nimport { INTENTS } from '@withpotter/components/intents';\nimport { INTENT_NAV_DEFINITIONS } from '@withpotter/lib/intents/intent-nav';\nimport { getIntentConfig } from '@withpotter/lib/intents/registry';\n\nconst configFor = (key: string) => {\n  const config = getIntentConfig(key);\n  assert.ok(config, `no intent config registered for ${key}`);\n  return config;\n};\n\n/**\n * The screens an archetype declares, for the sidebar walkthrough tests.\n *\n * An intent with a composer file declares them there, at its own routes. Any\n * other archetype's are the rows listed in the nav definitions AND declared by\n * its config, since the builder takes the href from the config and drops\n * anything the config never declared.\n *\n * The two lists do drift — `sell-products` is listed as contributing\n * Fulfillment but its config declares `service-areas` instead, so no shippable\n * merchant has ever had a Fulfillment row. That is a real gap, and a separate\n * one; `warnOnUnreachableNavItems` shouts about the mirror image of it in dev.\n */\nexport const declaredItems = (key: string) => {\n  const composed = INTENTS.find((intent) => intent.key === key);\n  if (composed)\n    return composed.routes\n      .filter((r) => !r.hidden)\n      .map((r) => ({\n        label: r.label,\n        href: `/dashboard/${r.path}`,\n      }));\n\n  const config = configFor(key);\n  const declared = new Map(\n    config.navigation.groups.flatMap((g) =>\n      g.items.map((i) => [i.id, i.href] as const),\n    ),\n  );\n  return (INTENT_NAV_DEFINITIONS.find((d) => d.key === key)?.items ?? [])\n    .filter((item) => declared.has(item.id))\n    .map((item) => ({ ...item, href: declared.get(item.id)! }));\n};\n\n/**\n * Screens a business's archetypes declare that no sidebar row reaches.\n *\n * `reachable` holds row ids AND destinations: an id going missing is not a\n * screen going missing, because a collapsed row keeps only the first\n * claimant's id. Spine-owned ids are matched by id and skipped here.\n */\nexport function missingScreens(\n  keys: readonly string[],\n  reachable: ReadonlySet<string>,\n  spineOwned: ReadonlySet<string>,\n): string[] {\n  return keys.flatMap((key) => {\n    const composed = INTENTS.find((intent) => intent.key === key);\n    if (composed)\n      return composed.routes\n        .filter(\n          (r) =>\n            !r.hidden &&\n            !reachable.has(`/dashboard/${r.path}`) &&\n            // A route whose nav id the spine owns (Enquiries, now the\n            // top-level Inbox) is matched by id like every other spine row.\n            !(r.navId && spineOwned.has(r.navId)),\n        )\n        .map((r) => `${key} → ${r.path}`);\n\n    const definition = INTENT_NAV_DEFINITIONS.find((d) => d.key === key);\n    const hrefById = new Map(\n      configFor(key).navigation.groups.flatMap((g) =>\n        g.items.map((i) => [i.id, i.href?.split('?')[0]] as const),\n      ),\n    );\n    const ids = (definition?.items ?? []).flatMap((i) => [\n      i.id,\n      ...(i.children ?? []).map((c) => c.id),\n    ]);\n    return ids\n      .filter((id) => {\n        const href = hrefById.get(id);\n        return (\n          !reachable.has(id) &&\n          !(href && reachable.has(href)) &&\n          !spineOwned.has(id)\n        );\n      })\n      .map((id) => `${key} → ${id}`);\n  });\n}\n\n/**\n * Run `fn` as if no intent had a composer file, so the shared-row system that\n * still serves a business with no archetype can be tested with its original\n * fixtures. A test seam: nothing outside tests calls it.\n */\nexport function withoutComposedIntents<T>(fn: () => T): T {\n  const saved = [...COMPOSED_INTENT_KEYS];\n  COMPOSED_INTENT_KEYS.clear();\n  try {\n    return fn();\n  } finally {\n    for (const key of saved) COMPOSED_INTENT_KEYS.add(key);\n  }\n}\n\n/** A test of the shared-row system, which no composed intent goes through. */\nexport const legacyTest = (name: string, fn: () => void) =>\n  test(name, () => withoutComposedIntents(fn));\n"],"mappings":"AAAA,OAAO,YAAY;AACnB,OAAO,UAAU;AACjB,SAAS,4BAA4B;AACrC,SAAS,eAAe;AACxB,SAAS,8BAA8B;AACvC,SAAS,uBAAuB;AAEhC,MAAM,YAAY,CAAC,QAAgB;AACjC,QAAM,SAAS,gBAAgB,GAAG;AAClC,SAAO,GAAG,QAAQ,mCAAmC,GAAG,EAAE;AAC1D,SAAO;AACT;AAeO,MAAM,gBAAgB,CAAC,QAAgB;AAC5C,QAAM,WAAW,QAAQ,KAAK,CAAC,WAAW,OAAO,QAAQ,GAAG;AAC5D,MAAI;AACF,WAAO,SAAS,OACb,OAAO,CAAC,MAAM,CAAC,EAAE,MAAM,EACvB,IAAI,CAAC,OAAO;AAAA,MACX,OAAO,EAAE;AAAA,MACT,MAAM,cAAc,EAAE,IAAI;AAAA,IAC5B,EAAE;AAEN,QAAM,SAAS,UAAU,GAAG;AAC5B,QAAM,WAAW,IAAI;AAAA,IACnB,OAAO,WAAW,OAAO;AAAA,MAAQ,CAAC,MAChC,EAAE,MAAM,IAAI,CAAC,MAAM,CAAC,EAAE,IAAI,EAAE,IAAI,CAAU;AAAA,IAC5C;AAAA,EACF;AACA,UAAQ,uBAAuB,KAAK,CAAC,MAAM,EAAE,QAAQ,GAAG,GAAG,SAAS,CAAC,GAClE,OAAO,CAAC,SAAS,SAAS,IAAI,KAAK,EAAE,CAAC,EACtC,IAAI,CAAC,UAAU,EAAE,GAAG,MAAM,MAAM,SAAS,IAAI,KAAK,EAAE,EAAG,EAAE;AAC9D;AASO,SAAS,eACd,MACA,WACA,YACU;AACV,SAAO,KAAK,QAAQ,CAAC,QAAQ;AAC3B,UAAM,WAAW,QAAQ,KAAK,CAAC,WAAW,OAAO,QAAQ,GAAG;AAC5D,QAAI;AACF,aAAO,SAAS,OACb;AAAA,QACC,CAAC,MACC,CAAC,EAAE,UACH,CAAC,UAAU,IAAI,cAAc,EAAE,IAAI,EAAE;AAAA;AAAA,QAGrC,EAAE,EAAE,SAAS,WAAW,IAAI,EAAE,KAAK;AAAA,MACvC,EACC,IAAI,CAAC,MAAM,GAAG,GAAG,WAAM,EAAE,IAAI,EAAE;AAEpC,UAAM,aAAa,uBAAuB,KAAK,CAAC,MAAM,EAAE,QAAQ,GAAG;AACnE,UAAM,WAAW,IAAI;AAAA,MACnB,UAAU,GAAG,EAAE,WAAW,OAAO;AAAA,QAAQ,CAAC,MACxC,EAAE,MAAM,IAAI,CAAC,MAAM,CAAC,EAAE,IAAI,EAAE,MAAM,MAAM,GAAG,EAAE,CAAC,CAAC,CAAU;AAAA,MAC3D;AAAA,IACF;AACA,UAAM,OAAO,YAAY,SAAS,CAAC,GAAG,QAAQ,CAAC,MAAM;AAAA,MACnD,EAAE;AAAA,MACF,IAAI,EAAE,YAAY,CAAC,GAAG,IAAI,CAAC,MAAM,EAAE,EAAE;AAAA,IACvC,CAAC;AACD,WAAO,IACJ,OAAO,CAAC,OAAO;AACd,YAAM,OAAO,SAAS,IAAI,EAAE;AAC5B,aACE,CAAC,UAAU,IAAI,EAAE,KACjB,EAAE,QAAQ,UAAU,IAAI,IAAI,MAC5B,CAAC,WAAW,IAAI,EAAE;AAAA,IAEtB,CAAC,EACA,IAAI,CAAC,OAAO,GAAG,GAAG,WAAM,EAAE,EAAE;AAAA,EACjC,CAAC;AACH;AAOO,SAAS,uBAA0B,IAAgB;AACxD,QAAM,QAAQ,CAAC,GAAG,oBAAoB;AACtC,uBAAqB,MAAM;AAC3B,MAAI;AACF,WAAO,GAAG;AAAA,EACZ,UAAE;AACA,eAAW,OAAO,MAAO,sBAAqB,IAAI,GAAG;AAAA,EACvD;AACF;AAGO,MAAM,aAAa,CAAC,MAAc,OACvC,KAAK,MAAM,MAAM,uBAAuB,EAAE,CAAC;","names":[]}

package/dist/sidebar/flatten-work-groups.d.ts

@@ -0,0 +1,48 @@
+import type { NavGroup, NavItem } from './config';
+/**
+ * The spine's own groups. Everything else is flattened.
+ *
+ * These render as hubs with their children disclosed inline; `settings` is
+ * pinned in the foot. Any other group is either a hoisted shared row (which
+ * carries an href and survives as a row) or an archetype label (which does
+ * not, and whose children become top-level rows).
+ *
+ * `hardware` joined them when it grew children. Without it here, Hardware,
+ * Requests and Shifts drew as three rows at one level under Operations, which
+ * reads as three unrelated destinations rather than a place and what is inside
+ * it — the exact thing a hub exists to say.
+ */
+export declare const FIXED_GROUP_IDS: Set<string>;
+/** A group's rows, wherever it keeps them. */
+export declare const groupItems: (group: NavGroup) => NavItem[];
+/**
+ * `buildNavGroups`' output, as the sidebar actually draws it.
+ *
+ * This transform lived inline in `sidebar.tsx` and nowhere else, which meant
+ * nothing but the browser could see the real nav. The file's own comment says
+ * what that cost: "Every test in the suite asserts on what `buildNavGroups`
+ * returns, which was correct the whole time. Nothing looked at what the sidebar
+ * drew." Orders and Catalog were absent from every multi-archetype sidebar for
+ * a while, with a green suite throughout.
+ *
+ * It is exported now so the three things that need to agree about the nav can
+ * share one answer: the sidebar that renders it, the test that guards it, and
+ * `scripts/archetype-shape.mts`, which had grown its own copy of this rule and
+ * got it wrong — printing archetype group headers the sidebar discards, which
+ * produced two confident and incorrect findings in one sitting.
+ *
+ * A flat group is a ROW, not just a container for rows. A group with an href
+ * belongs to no archetype — Catalog, Orders — so it survives as a row of its
+ * own with its children beneath. A group without one is a label (Dine-in,
+ * Events, Bookings) and its children are the destinations.
+ */
+export declare function flattenWorkGroups(groups: NavGroup[]): NavItem[];
+/**
+ * Every row the merchant can actually click, flattened to one list.
+ *
+ * Children included, because a child is a row too — one disclosure down. This
+ * is the list a duplicate-destination check has to run over: the bug that
+ * started this audit was `abandoned` repeating as a CHILD, which every guard in
+ * the suite was structurally unable to see.
+ */
+export declare function renderedRows(groups: NavGroup[]): NavItem[];

package/dist/sidebar/flatten-work-groups.js

@@ -0,0 +1,58 @@
+const FIXED_GROUP_IDS = /* @__PURE__ */ new Set([
+  "customers",
+  "payments",
+  "hardware",
+  "analytics",
+  "marketing",
+  "operations",
+  "website",
+  "settings"
+]);
+const groupItems = (group) => group.items ?? group.sections?.flatMap((section) => section.items) ?? [];
+function flattenWorkGroups(groups) {
+  return groups.filter((group) => !FIXED_GROUP_IDS.has(group.id)).flatMap((group) => {
+    const items = groupItems(group);
+    if (!group.href) return items;
+    return [
+      {
+        id: group.id,
+        name: group.label,
+        href: group.href,
+        icon: group.icon,
+        requiredPermission: group.requiredPermission
+      },
+      ...items
+    ];
+  });
+}
+function renderedRows(groups) {
+  const out = [];
+  const walk = (rows) => {
+    for (const row of rows) {
+      out.push(row);
+      if (row.children?.length) walk(row.children);
+    }
+  };
+  walk(flattenWorkGroups(groups));
+  for (const group of groups.filter((g) => FIXED_GROUP_IDS.has(g.id))) {
+    if (group.href)
+      out.push({
+        id: group.id,
+        name: (group.landingLabel ?? group.label).replace(
+          "{label}",
+          group.label.toLowerCase()
+        ),
+        href: group.href,
+        icon: group.icon
+      });
+    walk(groupItems(group));
+  }
+  return out;
+}
+export {
+  FIXED_GROUP_IDS,
+  flattenWorkGroups,
+  groupItems,
+  renderedRows
+};
+//# sourceMappingURL=flatten-work-groups.js.map

package/dist/sidebar/flatten-work-groups.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/flatten-work-groups.ts"],"sourcesContent":["import type { NavGroup, NavItem } from './config';\n\n/**\n * The spine's own groups. Everything else is flattened.\n *\n * These render as hubs with their children disclosed inline; `settings` is\n * pinned in the foot. Any other group is either a hoisted shared row (which\n * carries an href and survives as a row) or an archetype label (which does\n * not, and whose children become top-level rows).\n *\n * `hardware` joined them when it grew children. Without it here, Hardware,\n * Requests and Shifts drew as three rows at one level under Operations, which\n * reads as three unrelated destinations rather than a place and what is inside\n * it — the exact thing a hub exists to say.\n */\nexport const FIXED_GROUP_IDS = new Set([\n  'customers',\n  'payments',\n  'hardware',\n  'analytics',\n  'marketing',\n  'operations',\n  'website',\n  'settings',\n]);\n\n/** A group's rows, wherever it keeps them. */\nexport const groupItems = (group: NavGroup): NavItem[] =>\n  group.items ?? group.sections?.flatMap((section) => section.items) ?? [];\n\n/**\n * `buildNavGroups`' output, as the sidebar actually draws it.\n *\n * This transform lived inline in `sidebar.tsx` and nowhere else, which meant\n * nothing but the browser could see the real nav. The file's own comment says\n * what that cost: \"Every test in the suite asserts on what `buildNavGroups`\n * returns, which was correct the whole time. Nothing looked at what the sidebar\n * drew.\" Orders and Catalog were absent from every multi-archetype sidebar for\n * a while, with a green suite throughout.\n *\n * It is exported now so the three things that need to agree about the nav can\n * share one answer: the sidebar that renders it, the test that guards it, and\n * `scripts/archetype-shape.mts`, which had grown its own copy of this rule and\n * got it wrong — printing archetype group headers the sidebar discards, which\n * produced two confident and incorrect findings in one sitting.\n *\n * A flat group is a ROW, not just a container for rows. A group with an href\n * belongs to no archetype — Catalog, Orders — so it survives as a row of its\n * own with its children beneath. A group without one is a label (Dine-in,\n * Events, Bookings) and its children are the destinations.\n */\nexport function flattenWorkGroups(groups: NavGroup[]): NavItem[] {\n  return groups\n    .filter((group) => !FIXED_GROUP_IDS.has(group.id))\n    .flatMap((group) => {\n      const items = groupItems(group);\n      if (!group.href) return items;\n      return [\n        {\n          id: group.id,\n          name: group.label,\n          href: group.href,\n          icon: group.icon,\n          requiredPermission: group.requiredPermission,\n        } as NavItem,\n        ...items,\n      ];\n    });\n}\n\n/**\n * Every row the merchant can actually click, flattened to one list.\n *\n * Children included, because a child is a row too — one disclosure down. This\n * is the list a duplicate-destination check has to run over: the bug that\n * started this audit was `abandoned` repeating as a CHILD, which every guard in\n * the suite was structurally unable to see.\n */\nexport function renderedRows(groups: NavGroup[]): NavItem[] {\n  const out: NavItem[] = [];\n  const walk = (rows: NavItem[]) => {\n    for (const row of rows) {\n      out.push(row);\n      if (row.children?.length) walk(row.children as NavItem[]);\n    }\n  };\n  walk(flattenWorkGroups(groups));\n  for (const group of groups.filter((g) => FIXED_GROUP_IDS.has(g.id))) {\n    /**\n     * The hub's own row. `renderHub` draws the group and, when it has children,\n     * repeats its href as a landing row among them — so the group's own\n     * destination is reachable either way and belongs in this list.\n     *\n     * NAMED THE WAY renderHub NAMES IT, which is `landingLabel`, not `label`.\n     *\n     * This used to push `group.label`, and that hid a real collision from the\n     * two guards that read this list: Money's `Sales` child and the Analytics\n     * hub's landing row are both drawn to the merchant as \"Sales\", in one\n     * sidebar, pointing at two different screens — and \"no word is drawn twice\"\n     * stayed green throughout, because the word it compared was \"Analytics\".\n     *\n     * The file's own note says a test that MODELS the transform instead of\n     * calling it is the bug one level up. This was that, three lines below the\n     * note. The substitution matches `nav-renderers.tsx` exactly, so a hub whose\n     * landing label carries `{label}` reads the same here as on screen.\n     */\n    if (group.href)\n      out.push({\n        id: group.id,\n        name: (group.landingLabel ?? group.label).replace(\n          '{label}',\n          group.label.toLowerCase(),\n        ),\n        href: group.href,\n        icon: group.icon,\n      } as NavItem);\n    walk(groupItems(group));\n  }\n  return out;\n}\n"],"mappings":"AAeO,MAAM,kBAAkB,oBAAI,IAAI;AAAA,EACrC;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF,CAAC;AAGM,MAAM,aAAa,CAAC,UACzB,MAAM,SAAS,MAAM,UAAU,QAAQ,CAAC,YAAY,QAAQ,KAAK,KAAK,CAAC;AAuBlE,SAAS,kBAAkB,QAA+B;AAC/D,SAAO,OACJ,OAAO,CAAC,UAAU,CAAC,gBAAgB,IAAI,MAAM,EAAE,CAAC,EAChD,QAAQ,CAAC,UAAU;AAClB,UAAM,QAAQ,WAAW,KAAK;AAC9B,QAAI,CAAC,MAAM,KAAM,QAAO;AACxB,WAAO;AAAA,MACL;AAAA,QACE,IAAI,MAAM;AAAA,QACV,MAAM,MAAM;AAAA,QACZ,MAAM,MAAM;AAAA,QACZ,MAAM,MAAM;AAAA,QACZ,oBAAoB,MAAM;AAAA,MAC5B;AAAA,MACA,GAAG;AAAA,IACL;AAAA,EACF,CAAC;AACL;AAUO,SAAS,aAAa,QAA+B;AAC1D,QAAM,MAAiB,CAAC;AACxB,QAAM,OAAO,CAAC,SAAoB;AAChC,eAAW,OAAO,MAAM;AACtB,UAAI,KAAK,GAAG;AACZ,UAAI,IAAI,UAAU,OAAQ,MAAK,IAAI,QAAqB;AAAA,IAC1D;AAAA,EACF;AACA,OAAK,kBAAkB,MAAM,CAAC;AAC9B,aAAW,SAAS,OAAO,OAAO,CAAC,MAAM,gBAAgB,IAAI,EAAE,EAAE,CAAC,GAAG;AAmBnE,QAAI,MAAM;AACR,UAAI,KAAK;AAAA,QACP,IAAI,MAAM;AAAA,QACV,OAAO,MAAM,gBAAgB,MAAM,OAAO;AAAA,UACxC;AAAA,UACA,MAAM,MAAM,YAAY;AAAA,QAC1B;AAAA,QACA,MAAM,MAAM;AAAA,QACZ,MAAM,MAAM;AAAA,MACd,CAAY;AACd,SAAK,WAAW,KAAK,CAAC;AAAA,EACxB;AACA,SAAO;AACT;","names":[]}

package/dist/sidebar/home-row.d.ts

@@ -0,0 +1,10 @@
+/**
+ * HOME, the first row of the rail. Lifted out of `sidebar.tsx`, which is over
+ * the 500-line house limit and may only shrink.
+ */
+export declare function HomeRow({ active, collapsed, highlight, }: {
+    active: boolean;
+    collapsed: boolean;
+    /** The travelling active pill, owned by the rail. */
+    highlight: (active: boolean) => React.ReactNode;
+}): import("react").JSX.Element;

package/dist/sidebar/home-row.js

@@ -0,0 +1,28 @@
+import { jsx, jsxs } from "react/jsx-runtime";
+import Link from "next/link";
+import { LayoutDashboard } from "lucide-react";
+import { RailLabel } from "./rail-label";
+function HomeRow({
+  active,
+  collapsed,
+  highlight
+}) {
+  return /* @__PURE__ */ jsx("li", { className: "navitem", children: /* @__PURE__ */ jsx(RailLabel, { label: "Home", collapsed, children: /* @__PURE__ */ jsxs(
+    Link,
+    {
+      href: "/dashboard",
+      prefetch: false,
+      className: "navlink" + (active ? " active" : ""),
+      "aria-label": collapsed ? "Home" : void 0,
+      children: [
+        highlight(active),
+        /* @__PURE__ */ jsx("span", { className: "ic", children: /* @__PURE__ */ jsx(LayoutDashboard, { width: 18, height: 18 }) }),
+        /* @__PURE__ */ jsx("span", { className: "lbl", children: "Home" })
+      ]
+    }
+  ) }) });
+}
+export {
+  HomeRow
+};
+//# sourceMappingURL=home-row.js.map

package/dist/sidebar/home-row.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/sidebar/home-row.tsx"],"sourcesContent":["import Link from 'next/link';\nimport { LayoutDashboard } from 'lucide-react';\nimport { RailLabel } from './rail-label';\n\n/**\n * HOME, the first row of the rail. Lifted out of `sidebar.tsx`, which is over\n * the 500-line house limit and may only shrink.\n */\nexport function HomeRow({\n  active,\n  collapsed,\n  highlight,\n}: {\n  active: boolean;\n  collapsed: boolean;\n  /** The travelling active pill, owned by the rail. */\n  highlight: (active: boolean) => React.ReactNode;\n}) {\n  return (\n    <li className=\"navitem\">\n      <RailLabel label=\"Home\" collapsed={collapsed}>\n        <Link\n          href=\"/dashboard\"\n          prefetch={false}\n          className={'navlink' + (active ? ' active' : '')}\n          aria-label={collapsed ? 'Home' : undefined}\n        >\n          {highlight(active)}\n          <span className=\"ic\">\n            <LayoutDashboard width={18} height={18} />\n          </span>\n          <span className=\"lbl\">Home</span>\n        </Link>\n      </RailLabel>\n    </li>\n  );\n}\n"],"mappings":"AAqBQ,SAQI,KARJ;AArBR,OAAO,UAAU;AACjB,SAAS,uBAAuB;AAChC,SAAS,iBAAiB;AAMnB,SAAS,QAAQ;AAAA,EACtB;AAAA,EACA;AAAA,EACA;AACF,GAKG;AACD,SACE,oBAAC,QAAG,WAAU,WACZ,8BAAC,aAAU,OAAM,QAAO,WACtB;AAAA,IAAC;AAAA;AAAA,MACC,MAAK;AAAA,MACL,UAAU;AAAA,MACV,WAAW,aAAa,SAAS,YAAY;AAAA,MAC7C,cAAY,YAAY,SAAS;AAAA,MAEhC;AAAA,kBAAU,MAAM;AAAA,QACjB,oBAAC,UAAK,WAAU,MACd,8BAAC,mBAAgB,OAAO,IAAI,QAAQ,IAAI,GAC1C;AAAA,QACA,oBAAC,UAAK,WAAU,OAAM,kBAAI;AAAA;AAAA;AAAA,EAC5B,GACF,GACF;AAEJ;","names":[]}

package/dist/sidebar/inbox-row.d.ts

@@ -0,0 +1,44 @@
+import type { PermissionKey } from '@withpotter/lib/use-permissions';
+import type { NavGroup, NavItem } from './config';
+export declare const INBOX_HREF = "/dashboard/inbox";
+/**
+ * Any of the four, because the page holds both kinds of mail.
+ *
+ * Deliberately NOT behaviour-gated, for the reason Enquiries never was: every
+ * storefront template ships a contact page, so mail arrives whether or not
+ * `leadCapture` is on, and an inbox that hides itself while mail piles up is
+ * the failure this row exists to prevent.
+ */
+export declare const INBOX_PERMISSIONS: PermissionKey[];
+export interface InboxRowDeps {
+    hiddenModules: string[] | undefined;
+    moduleLabels: Record<string, string> | undefined;
+    can: (permission: PermissionKey) => boolean;
+    isOwner: boolean;
+    permissionsLoading: boolean;
+}
+/**
+ * The row, or null when this member should not see it.
+ *
+ * While permissions load only the owner gets it. The rows in the groups are
+ * shown optimistically during that window so an owner does not flicker into a
+ * reduced rail, but this one is a single row at the very top: showing it to
+ * staff who lack the permission and then pulling it would shove everything
+ * beneath it up a line.
+ */
+export declare function buildInboxRow({ hiddenModules, moduleLabels, can, isOwner, permissionsLoading, }: InboxRowDeps): NavItem | null;
+/**
+ * Whether the Inbox row owns the `inquiries` destination for this member.
+ *
+ * `capture-leads` declares an Enquiries row to the same `/dashboard/inbox`.
+ * Two rows to one page is what the nav guard fails on, and the top-level row
+ * wins: it carries the count. While permissions load it claims the page too,
+ * so the archetype's row never flashes in and out; once loaded, a member the
+ * Inbox does not admit keeps whatever the archetype gave them.
+ */
+export declare function inboxOwnsInquiries(deps: InboxRowDeps): boolean;
+/** The archetype groups and shared rows, minus the Enquiries row. */
+export declare function withoutInquiries(groups: NavGroup[], sharedRows: NavItem[]): {
+    intentGroups: NavGroup[];
+    sharedRows: NavItem[];
+};