@withpotter/components 0.13.0-next.101

package/dist/shared/status-badge.js

@@ -0,0 +1,71 @@
+import { jsx, jsxs } from "react/jsx-runtime";
+import { BADGE_SIZES } from "@withpotter/ui-kit/badge";
+import { DEFAULT_COLOR, SCOPE_COLORS, STATUS_COLORS } from "./status-colors";
+function statusTextClass(status, scope) {
+  const key = status.toLowerCase();
+  return ((scope ? SCOPE_COLORS[scope]?.[key] : void 0) ?? STATUS_COLORS[key] ?? DEFAULT_COLOR).text;
+}
+function StatusBadge({
+  status,
+  variant = "default",
+  neutral = false,
+  scope,
+  icon,
+  size = "sm",
+  label: labelOverride,
+  className = ""
+}) {
+  const key = status.toLowerCase();
+  const toned = (scope ? SCOPE_COLORS[scope]?.[key] : void 0) ?? STATUS_COLORS[key] ?? DEFAULT_COLOR;
+  const colors = neutral ? DEFAULT_COLOR : toned;
+  const iconTone = neutral ? toned.text : "";
+  const label = labelOverride ?? status.charAt(0).toUpperCase() + status.slice(1).toLowerCase().replace(/[_-]+/g, " ");
+  if (variant === "text") {
+    return /* @__PURE__ */ jsxs(
+      "span",
+      {
+        className: `inline-flex items-center gap-1 whitespace-nowrap text-xs font-medium ${colors.text} ${className}`,
+        children: [
+          icon && /* @__PURE__ */ jsx("span", { className: iconTone, children: icon }),
+          label
+        ]
+      }
+    );
+  }
+  if (variant === "dot") {
+    return /* @__PURE__ */ jsxs(
+      "span",
+      {
+        className: `inline-flex items-center gap-2 whitespace-nowrap text-xs font-medium ${colors.text} ${className}`,
+        children: [
+          /* @__PURE__ */ jsx(
+            "span",
+            {
+              className: `w-1.5 h-1.5 rounded-full ${colors.bg.replace("100", "500")}`
+            }
+          ),
+          label
+        ]
+      }
+    );
+  }
+  return /* @__PURE__ */ jsxs(
+    "span",
+    {
+      className: `badge inline-flex items-center gap-1 whitespace-nowrap rounded-[var(--radius-badge)] ${BADGE_SIZES[size]} text-xs font-medium ${colors.bg} ${colors.text} ${className}`,
+      children: [
+        icon && /* @__PURE__ */ jsx("span", { className: iconTone, children: icon }),
+        label
+      ]
+    }
+  );
+}
+function getStatusColors(status) {
+  return STATUS_COLORS[status.toLowerCase()] || DEFAULT_COLOR;
+}
+export {
+  StatusBadge,
+  getStatusColors,
+  statusTextClass
+};
+//# sourceMappingURL=status-badge.js.map

package/dist/shared/status-badge.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/shared/status-badge.tsx"],"sourcesContent":["import type { ReactNode } from 'react';\nimport { BADGE_SIZES, type BadgeSize } from '@withpotter/ui-kit/badge';\nimport { DEFAULT_COLOR, SCOPE_COLORS, STATUS_COLORS } from './status-colors';\n\n/**\n * Reusable status badge component used across domains, subscriptions,\n * finance, billing, and other pages.\n */\ninterface StatusBadgeProps {\n  status: string;\n  /**\n   * How the status is presented. The MAPPING above is shared by all three;\n   * only the shape differs.\n   *\n   * - `default` — a pill. A status column of its own.\n   * - `text`    — a coloured word, no pill. For a status that is a FOOTNOTE to\n   *               a figure: the ledger prints it small under the amount, and\n   *               the invoice table prints it beside one. Both kept private\n   *               copies of \"success is green, failed is red\" to get this\n   *               shape, and one of those copies had already drifted — it\n   *               painted `pending` amber, which this file reserves for \"this\n   *               needs you\" and argues at length.\n   * - `dot`     — a coloured dot and a label.\n   */\n  variant?: 'default' | 'dot' | 'text';\n  /**\n   * Drop the colour, keep the word.\n   *\n   * For a table carrying MORE THAN ONE status column. Orders has three —\n   * Status, Payment, Fulfillment — and colouring them put up to three hues in\n   * every row, restating words that already said the same thing. Colour ranks\n   * rows, and three competing rankings rank nothing; worse, it ranked wrong,\n   * pulling the eye to a finished order in red on a page whose real priority\n   * is money waiting on a human.\n   *\n   * The rule the app settles on: COLOUR MARKS ATTENTION, NOT STATE. One status\n   * column may carry it, because there the colour means \"this one needs you\".\n   * More than one, and the column set goes neutral.\n   */\n  neutral?: boolean;\n  /**\n   * The domain asking, for the words two domains disagree about.\n   *\n   * Only `invoice` needs one today: a `sent` campaign is finished and a `sent`\n   * invoice is money still out. Everything else resolves from the one map.\n   */\n  scope?: keyof typeof SCOPE_COLORS;\n  /** A glyph inside the pill, as the order and booking chips carry. */\n  icon?: ReactNode;\n  /**\n   * The two heights Badge has, and for the same reason.\n   *\n   * `sm` (22px) is a pill inside a table row or a list, where a full-height\n   * one would set the row height. `md` (28px) matches a `md` Button exactly,\n   * for a pill that sits beside one in a header.\n   *\n   * It exists because a header holding both kinds of pill could not make them\n   * agree: `Badge` had the sizes and this did not, so the facts stood at 28px\n   * beside 22px statuses and the only fix available at the call site was a\n   * hand-typed height — which is how `px-3` ended up in a page and failed\n   * the spacing rule.\n   */\n  size?: BadgeSize;\n  /**\n   * Say the label outright, and let `status` decide only the colour.\n   *\n   * The archetype lists resolve their own wording first — an events merchant's\n   * config names `checked_in` \"Checked In\", a gym's might name it \"Entered\" —\n   * and the sentence-casing below would have flattened those to \"Checked in\"\n   * and re-decided a word the merchant's own config had already chosen.\n   */\n  label?: string;\n  className?: string;\n}\n\n/**\n * What colour a status is, without the pill.\n *\n * Three logs on the money surface annotate a status inline rather than badging\n * it, for reasons each of them is right about: the ledger prints it small under\n * the amount because it is a footnote to the figure, and the payouts table\n * prints the settled date instead whenever there is one. So they were never\n * going to render this component, and each kept its own copy of \"success is\n * green, failed is red\" instead.\n *\n * A duplicated colour map is the part that actually costs something: it drifts,\n * and it already had — one copy painted `pending` amber while this file\n * reserves amber for \"this needs you\" and documents why at length. So the\n * mapping is shared and the presentation is not.\n */\nexport function statusTextClass(\n  status: string,\n  scope?: keyof typeof SCOPE_COLORS,\n): string {\n  const key = status.toLowerCase();\n  return (\n    (scope ? SCOPE_COLORS[scope]?.[key] : undefined) ??\n    STATUS_COLORS[key] ??\n    DEFAULT_COLOR\n  ).text;\n}\n\nexport function StatusBadge({\n  status,\n  variant = 'default',\n  neutral = false,\n  scope,\n  icon,\n  size = 'sm',\n  label: labelOverride,\n  className = '',\n}: StatusBadgeProps) {\n  const key = status.toLowerCase();\n  const toned =\n    (scope ? SCOPE_COLORS[scope]?.[key] : undefined) ??\n    STATUS_COLORS[key] ??\n    DEFAULT_COLOR;\n  const colors = neutral ? DEFAULT_COLOR : toned;\n\n  /**\n   * Neutral keeps the PILL grey and lets the GLYPH carry the tone.\n   *\n   * The rule this sits under is \"colour marks attention, not state\": a table\n   * where every row is a coloured pill ranks the rows by hue, and it ranks them\n   * wrong — a finished order pulls the eye on a page whose real priority is\n   * money waiting on someone. That argument is about the fill, which is a block\n   * of colour the size of the word.\n   *\n   * An icon is a few pixels. It can be amber for waiting and green for done\n   * without any row shouting over another, and it gives the glance something\n   * to sort on that reading each word does not. So `neutral` now means a quiet\n   * pill with a coloured mark, rather than no colour at all.\n   */\n  const iconTone = neutral ? toned.text : '';\n  /**\n   * Sentence case, with the database's separator taken out.\n   *\n   * A snake_case status rendered \"Awaiting_merchant\" — this only started\n   * mattering when statuses arrived with more than one word in them, and the\n   * fix belongs here rather than at each call site, which is how the\n   * partially_refunded rows in the ledger already read.\n   */\n  const label =\n    labelOverride ??\n    status.charAt(0).toUpperCase() +\n      status.slice(1).toLowerCase().replace(/[_-]+/g, ' ');\n\n  if (variant === 'text') {\n    return (\n      <span\n        className={`inline-flex items-center gap-1 whitespace-nowrap text-xs font-medium ${colors.text} ${className}`}\n      >\n        {icon && <span className={iconTone}>{icon}</span>}\n        {label}\n      </span>\n    );\n  }\n\n  if (variant === 'dot') {\n    return (\n      <span\n        className={`inline-flex items-center gap-2 whitespace-nowrap text-xs font-medium ${colors.text} ${className}`}\n      >\n        <span\n          className={`w-1.5 h-1.5 rounded-full ${colors.bg.replace('100', '500')}`}\n        />\n        {label}\n      </span>\n    );\n  }\n\n  return (\n    <span\n      // `rounded-[var(--radius-badge)]`, not `rounded-md`. The radius scale is collapsed to a\n      // flat 10px, so `rounded-md` on a 20px-tall pill lands just short of a\n      // stadium and reads as neither — and every other pill in the app (tier\n      // marks, tab counts, category pills, programme status) is fully round.\n      // `badge` is the same marker Badge carries, and it was missing here.\n      // A container promotes every badge inside it in one place —\n      // `DetailHeader` does it with `[&_.badge]:h-7` so a pill beside a page\n      // title matches the button across from it. With only one of the two pill\n      // components opting in, a header holding both got 28px facts beside 22px\n      // statuses, and no call site could fix it without hard-coding a height.\n      className={`badge inline-flex items-center gap-1 whitespace-nowrap rounded-[var(--radius-badge)] ${BADGE_SIZES[size]} text-xs font-medium ${colors.bg} ${colors.text} ${className}`}\n    >\n      {icon && <span className={iconTone}>{icon}</span>}\n      {label}\n    </span>\n  );\n}\n\n/** Get color config for a status string without rendering a component. */\nexport function getStatusColors(status: string) {\n  return STATUS_COLORS[status.toLowerCase()] || DEFAULT_COLOR;\n}\n"],"mappings":"AAqJM,SAGW,KAHX;AApJN,SAAS,mBAAmC;AAC5C,SAAS,eAAe,cAAc,qBAAqB;AAwFpD,SAAS,gBACd,QACA,OACQ;AACR,QAAM,MAAM,OAAO,YAAY;AAC/B,WACG,QAAQ,aAAa,KAAK,IAAI,GAAG,IAAI,WACtC,cAAc,GAAG,KACjB,eACA;AACJ;AAEO,SAAS,YAAY;AAAA,EAC1B;AAAA,EACA,UAAU;AAAA,EACV,UAAU;AAAA,EACV;AAAA,EACA;AAAA,EACA,OAAO;AAAA,EACP,OAAO;AAAA,EACP,YAAY;AACd,GAAqB;AACnB,QAAM,MAAM,OAAO,YAAY;AAC/B,QAAM,SACH,QAAQ,aAAa,KAAK,IAAI,GAAG,IAAI,WACtC,cAAc,GAAG,KACjB;AACF,QAAM,SAAS,UAAU,gBAAgB;AAgBzC,QAAM,WAAW,UAAU,MAAM,OAAO;AASxC,QAAM,QACJ,iBACA,OAAO,OAAO,CAAC,EAAE,YAAY,IAC3B,OAAO,MAAM,CAAC,EAAE,YAAY,EAAE,QAAQ,UAAU,GAAG;AAEvD,MAAI,YAAY,QAAQ;AACtB,WACE;AAAA,MAAC;AAAA;AAAA,QACC,WAAW,wEAAwE,OAAO,IAAI,IAAI,SAAS;AAAA,QAE1G;AAAA,kBAAQ,oBAAC,UAAK,WAAW,UAAW,gBAAK;AAAA,UACzC;AAAA;AAAA;AAAA,IACH;AAAA,EAEJ;AAEA,MAAI,YAAY,OAAO;AACrB,WACE;AAAA,MAAC;AAAA;AAAA,QACC,WAAW,wEAAwE,OAAO,IAAI,IAAI,SAAS;AAAA,QAE3G;AAAA;AAAA,YAAC;AAAA;AAAA,cACC,WAAW,4BAA4B,OAAO,GAAG,QAAQ,OAAO,KAAK,CAAC;AAAA;AAAA,UACxE;AAAA,UACC;AAAA;AAAA;AAAA,IACH;AAAA,EAEJ;AAEA,SACE;AAAA,IAAC;AAAA;AAAA,MAWC,WAAW,wFAAwF,YAAY,IAAI,CAAC,wBAAwB,OAAO,EAAE,IAAI,OAAO,IAAI,IAAI,SAAS;AAAA,MAEhL;AAAA,gBAAQ,oBAAC,UAAK,WAAW,UAAW,gBAAK;AAAA,QACzC;AAAA;AAAA;AAAA,EACH;AAEJ;AAGO,SAAS,gBAAgB,QAAgB;AAC9C,SAAO,cAAc,OAAO,YAAY,CAAC,KAAK;AAChD;","names":[]}

package/dist/shared/status-colors.d.ts

@@ -0,0 +1,39 @@
+/**
+ * What colour every status in the product is.
+ *
+ * Split out of `status-badge.tsx` when the Connect vocabulary took that file
+ * past the 500-line rule. Nothing about the doctrine changed: this is still
+ * ONE map, with a scope for the handful of words two domains genuinely
+ * disagree about, and a status the map does not know still belongs IN it with
+ * a line saying which way it was sorted, rather than in a ternary beside the
+ * screen that happened to need it.
+ */
+export declare const STATUS_COLORS: Record<string, {
+    bg: string;
+    text: string;
+}>;
+/**
+ * The same word asking a different question.
+ *
+ * `sent` on a campaign is finished work — it went out, nothing is owed, green
+ * is right. `sent` on an invoice is money NOT yet in, and green said the
+ * opposite of the truth on every unpaid invoice in the list. One map still, and
+ * a scope for the handful of words two domains genuinely disagree about, rather
+ * than a private copy per screen — which is what the invoice screens had.
+ */
+export declare const SCOPE_COLORS: Record<string, Record<string, (typeof STATUS_COLORS)[string]>>;
+/**
+ * The quiet badge, and the hairline is not decoration.
+ *
+ * `--bg-muted` is rgb(32,32,35). A hovered table row is `#ffffff09` over the
+ * card, which lands on rgb(33,33,36) — one value away — so the pill dissolved
+ * into the row exactly when you were pointing at it. A fill can collide with a
+ * background; an edge cannot, because it is a boundary rather than a tone.
+ *
+ * `--border-subtle` is the same hairline every card and row already uses, so
+ * this adds an edge without adding a colour.
+ */
+export declare const DEFAULT_COLOR: {
+    bg: string;
+    text: string;
+};

package/dist/shared/status-colors.js

@@ -0,0 +1,457 @@
+const STATUS_COLORS = {
+  active: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  completed: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  paid: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  published: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  fulfilled: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  // Amber is reserved for "this needs you": overdue, failed, out of credit.
+  // Pending and processing are neither — nothing is wrong, the thing simply has
+  // not finished yet. Painting them amber spent the loudest colour in the
+  // palette on the most ordinary state, and beside a genuinely overdue row it
+  // made both look equally urgent. They read as in-progress instead: the quiet
+  // surface draft uses, with full-strength secondary text so they stay legible
+  // rather than fading into the row.
+  pending: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-secondary)]" },
+  processing: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  draft: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-secondary)]" },
+  /* A merchant's own emphasis, not a state of the record — warning is the
+     right weight for it: findable, and not claiming anything is wrong. */
+  featured: { bg: "bg-[var(--warning-bg)]", text: "text-[var(--warning)]" },
+  cancelled: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  /**
+   * The money statuses.
+   *
+   * `success` was missing, which is why the payments ledger and the payouts log
+   * each kept a private colour map beside this file rather than using it: a
+   * successful payment would have resolved to the default grey. A reversal and
+   * a part-refund are the same reading as a refund — money went back, nothing
+   * is wrong, nothing needs doing — so they take its treatment rather than an
+   * alarm colour.
+   */
+  success: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  partially_refunded: {
+    bg: "bg-[var(--accent-secondary)]/10",
+    text: "text-[var(--accent-secondary)]"
+  },
+  reversed: {
+    bg: "bg-[var(--accent-secondary)]/10",
+    text: "text-[var(--accent-secondary)]"
+  },
+  failed: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  overdue: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  refunded: {
+    bg: "bg-[var(--accent-secondary)]/10",
+    text: "text-[var(--accent-secondary)]"
+  },
+  partial: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  /**
+   * Invoice lifecycle, which had two private copies — one in the list's
+   * helpers, one in the detail hook — because these three words were missing
+   * and would have come out grey.
+   *
+   * Sorted by the same question. `viewed` is the client opening the document:
+   * a milestone, nothing to do, so info rather than the fifth hue the fork
+   * spent on it. `partially_paid` is money owed and not yet late, which is
+   * ordinary business — amber belongs to `overdue`, one row down. `void` is
+   * `voided` under the name the API uses.
+   */
+  viewed: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  partially_paid: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  void: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  // Campaign and cart lifecycle. Without these, a sent campaign and a draft
+  // rendered in the same grey, which is the one distinction that page is for.
+  sent: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  // The provider confirming it landed, which is not the same fact as `sent`
+  // and is the one a merchant is actually asking about.
+  delivered: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  /**
+   * Hardware on its way, and hardware asked for.
+   *
+   * `shipped` takes the info blue rather than amber: a box on a van is
+   * progress, not a thing needing the merchant. `requested` takes the muted
+   * grey for the same reason `draft` does — it is waiting on us, and a colour
+   * on it would be asking somebody to act on a state they cannot move.
+   *
+   * Both were painted by a hardware order before they were in here, which is
+   * the drift this file exists to stop.
+   */
+  shipped: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  requested: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  scheduled: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  recovered: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  // Tab lifecycle
+  open: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  /**
+   * Dispute lifecycle. `awaiting_merchant` is amber because it is the most
+   * literal case of "this needs you" in the product: doing nothing loses the
+   * money. `awaiting_provider` is grey — answered, nothing left to do.
+   */
+  awaiting_merchant: {
+    bg: "bg-[var(--warning-bg)]",
+    text: "text-[var(--warning)]"
+  },
+  awaiting_provider: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  /**
+   * Support cases, sorted by the only question this file asks: does this need
+   * a human on the merchant's side?
+   *
+   * `waiting_on_tenant` does — we have asked them something and the case stops
+   * until they answer — so it takes amber, the same job `awaiting_merchant`
+   * has one block up. `waiting_on_potter` is grey: it is with us, and a colour
+   * there would ask them to act on a queue they cannot move. `resolved` is
+   * green because it is finished, and `closed` is grey because it is only
+   * over. `open` is deliberately absent — it already resolves, from the tab
+   * lifecycle above.
+   */
+  waiting_on_tenant: {
+    bg: "bg-[var(--warning-bg)]",
+    text: "text-[var(--warning)]"
+  },
+  waiting_on_potter: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  waiting_on_customer: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  resolved: {
+    bg: "bg-[var(--success-bg)]",
+    text: "text-[var(--success)]"
+  },
+  closed: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  won: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  lost: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  // The merchant chose this. The money is gone either way, but a decision is
+  // not a failure and should not read in the loss colour.
+  accepted: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  settled: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  /**
+   * Money held and not yet taken — a deposit, a pre-auth, a tap a terminal has
+   * captured and not had confirmed.
+   *
+   * Sorted the way everything here is: does it need a human? It does not. The
+   * customer is already committed and the provider is doing its job, so this is
+   * `confirmed`'s sibling — agreed and not yet due — and takes info rather than
+   * the amber this file reserves for something going wrong. It matters that it
+   * is not green: nothing has actually been collected yet, and painting it as
+   * success is how held money gets counted as revenue.
+   */
+  authorized: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  voided: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  paused: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-secondary)]" },
+  /**
+   * Priority, which is the one axis colour is unambiguously for.
+   *
+   * "Colour marks attention, not state" cuts both ways: a status column of
+   * ordinary lifecycle words goes neutral, and a column that exists ONLY to say
+   * how badly something needs a human keeps its colour. The waitlist held these
+   * two privately; they belong with every other colour decision.
+   */
+  /**
+   * TEAM PRESENCE — a person's standing on the roster, sorted by the same
+   * question this file asks of everything: does it need a human?
+   *
+   * It does for an invite that has lapsed, and for one about to: somebody
+   * believes they were added and cannot sign in, and only the manager can fix
+   * it. That is amber's actual job here.
+   *
+   * It does not for the rest. `here` is green because it is the one live fact
+   * on the page — that person is at the counter right now — and everything else
+   * is ordinary: signed in earlier, signed in a while ago, invited and still
+   * within the window, never came back, gone. Those are the roster's normal
+   * weather and they read grey rather than ranking each other by hue.
+   *
+   * Hyphenated keys because `MemberPresence` spells them that way; the label
+   * is written by `readPresence` and passed as an override, so these decide
+   * colour only.
+   */
+  here: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  today: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-secondary)]" },
+  away: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-secondary)]" },
+  never: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  invited: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-secondary)]" },
+  "invite-expiring": {
+    bg: "bg-[var(--warning-bg)]",
+    text: "text-[var(--warning)]"
+  },
+  "invite-expired": {
+    bg: "bg-[var(--warning-bg)]",
+    text: "text-[var(--warning)]"
+  },
+  removed: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  urgent: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  high: { bg: "bg-[var(--warning-bg)]", text: "text-[var(--warning)]" },
+  expired: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  /**
+   * Integration lifecycle. Calendar-sync kept a private five-arm switch for
+   * these purely because `connected` and `error` were missing here and would
+   * have resolved to the default grey — a disconnected calendar and a working
+   * one rendered identically, which is the single distinction that page is for.
+   *
+   * `syncing` and `disconnected` are deliberately NOT added: they fall through
+   * to the default grey, which is what the map already decided for `pending`
+   * and `processing`. Nothing is wrong while a calendar is syncing, so it does
+   * not get a colour. The fork painted it brand-500 and spent an accent on the
+   * most ordinary state.
+   */
+  connected: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+  error: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  /**
+   * Booking lifecycle, which had TWO private copies — one in the list's
+   * constants file and one in the detail hook — and the detail copy is the
+   * drift this file's `pending` comment is about: it painted a pending booking
+   * amber. It also painted `waitlist` amber and `cancelled` grey, so a booking
+   * nobody had cancelled shouted and a cancelled one whispered, which is the
+   * ranking exactly backwards.
+   *
+   * Sorted the same way everything else here is: does it need a human?
+   *  - `confirmed` is agreed and not yet due, like `scheduled`: info.
+   *  - `checked_in` is a milestone reached, not a task: info.
+   *  - `in_progress` and `waitlist` are the booking equivalents of
+   *    `processing` and `pending` — nothing is wrong, it has not finished —
+   *    so they take the same quiet grey rather than an accent.
+   *  - `no_show` costs the merchant the slot and the money: error.
+   *  - `unpaid` is money owed, which is the most literal "this needs you"
+   *    there is after a dispute: warning.
+   */
+  confirmed: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  checked_in: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+  in_progress: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  waitlist: {
+    bg: "bg-[var(--bg-muted)]",
+    text: "text-[var(--text-secondary)]"
+  },
+  no_show: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  unpaid: { bg: "bg-[var(--warning-bg)]", text: "text-[var(--warning)]" },
+  /**
+   * On / off / put away. Five screens spelled the off state three ways —
+   * `--text-muted`, `--text-tertiary`, `--text-secondary` on the same grey —
+   * because each wrote its own ternary rather than looking one up.
+   *
+   * `suspended` is the only one with a colour: it is a state a human put the
+   * record into and a human has to take it out of. `inactive` and `archived`
+   * are resting states, and nothing resting needs a hue.
+   */
+  /**
+   * What a live address is doing, from the four-hourly watch.
+   *
+   * Sorted by the rule this file argues elsewhere — amber is "this needs you",
+   * red is "this is broken now". A store that cannot be reached and a store
+   * serving an error page are both costing the merchant customers this minute,
+   * so both are red. A missing certificate is amber: the store still loads, the
+   * visitor is just warned on the way in, and it usually clears itself.
+   */
+  dns_broken: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  not_responding: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  serving_errors: { bg: "bg-[var(--error-bg)]", text: "text-[var(--error)]" },
+  no_certificate: {
+    bg: "bg-[var(--warning-bg)]",
+    text: "text-[var(--warning)]"
+  },
+  inactive: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  archived: { bg: "bg-[var(--bg-muted)]", text: "text-[var(--text-tertiary)]" },
+  suspended: { bg: "bg-[var(--warning-bg)]", text: "text-[var(--warning)]" }
+};
+const SCOPE_COLORS = {
+  invoice: {
+    sent: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" }
+  },
+  /**
+   * A bill the business owes, where `open` means the opposite of what it means
+   * everywhere else.
+   *
+   * The shared map paints `open` green, which is right for a dispute or a shift
+   * — the thing is live and healthy. A bill that is open is money not yet paid.
+   * Green there tells a merchant scanning a due list that the row is settled,
+   * which is the one thing it is not. Neutral: it is ordinary, it is not done,
+   * and it is not late. Late is `overdue`, which the shared map already reads
+   * red, and that is the row that should pull the eye.
+   */
+  bill: {
+    open: { bg: "bg-[var(--bg-subtle)]", text: "text-[var(--text-secondary)]" }
+  },
+  /**
+   * Connect: a managed connection, and the life of one command.
+   *
+   * Sorted on the question the operator is actually asking, which is "does
+   * this need a human?" — so amber is spent only where the answer is yes.
+   *
+   * `reconciling` is the one that earns it. It means the provider may have
+   * acted and did not say so clearly: the invoice might exist, the message
+   * might have gone. Nothing is broken and nothing is finished, and retrying
+   * blindly is how a merchant gets billed twice. That is a person's decision,
+   * so it reads amber alongside `attention_required`, which is a connection
+   * whose credential is failing.
+   *
+   * `retry_scheduled` is deliberately NOT amber. The system knows what it is
+   * doing and will do it again shortly; colouring it the same as the case that
+   * needs a human would make the amber mean nothing by volume.
+   *
+   * `accepted` and `published` are grey against the global map's green. Work
+   * that is durably recorded has not happened yet, and green on a command the
+   * provider has never seen says it did.
+   *
+   * The availability words are the point of the whole surface. `pilot` is
+   * info; `sandbox_certified`, `fixture_certified`, `implemented` and
+   * `defined` stay grey no matter how much code exists behind them, because
+   * only `generally_available` may read as live. A green pill on a connector
+   * that has never carried production traffic is the lie this vocabulary was
+   * written to prevent.
+   */
+  connect: {
+    /**
+     * A managed sending identity's life.
+     *
+     * Sorted the same way as everything above it: amber only where a person
+     * has to do something. `action_required` is the literal case — a DNS
+     * record nobody added — and `expiring` earns it for the reason this state
+     * exists at all: a renewal that lapses is indistinguishable from a working
+     * identity right up until the morning delivery stops, so it has to shout
+     * while there is still time to act.
+     *
+     * `verifying` and `requested` stay grey. Box is waiting on a provider,
+     * nothing is wrong, and colouring them would say otherwise.
+     *
+     * `suspended` and `released` take the same tertiary grey as
+     * `disconnected`: stopped, and not by anything the merchant can undo from
+     * this screen. Amber on a state with no action attached is amber spent for
+     * nothing, and spends the colour the two rows above it need.
+     */
+    /**
+     * A route's health, which is not a connection's.
+     *
+     * `degraded` is amber because it needs a person to know, not to act —
+     * their work is slower and nothing is lost. `unavailable` is grey rather
+     * than red for the reason the panel says out loud: work waits instead of
+     * failing, so painting it as an error would tell a merchant they had lost
+     * something they had not.
+     */
+    degraded: {
+      bg: "bg-[var(--warning-bg)]",
+      text: "text-[var(--warning)]"
+    },
+    healthy: {
+      bg: "bg-[var(--success-bg)]",
+      text: "text-[var(--success)]"
+    },
+    requested: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-secondary)]"
+    },
+    verifying: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-secondary)]"
+    },
+    action_required: {
+      bg: "bg-[var(--warning-bg)]",
+      text: "text-[var(--warning)]"
+    },
+    expiring: {
+      bg: "bg-[var(--warning-bg)]",
+      text: "text-[var(--warning)]"
+    },
+    suspended: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    released: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    accepted: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-secondary)]"
+    },
+    published: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-secondary)]"
+    },
+    processing: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+    retry_scheduled: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+    reconciling: {
+      bg: "bg-[var(--warning-bg)]",
+      text: "text-[var(--warning)]"
+    },
+    succeeded: { bg: "bg-[var(--success-bg)]", text: "text-[var(--success)]" },
+    attention_required: {
+      bg: "bg-[var(--warning-bg)]",
+      text: "text-[var(--warning)]"
+    },
+    disconnected: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    unavailable: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    revoked: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    generally_available: {
+      bg: "bg-[var(--success-bg)]",
+      text: "text-[var(--success)]"
+    },
+    pilot: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+    sandbox_certified: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-secondary)]"
+    },
+    fixture_certified: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-secondary)]"
+    },
+    implemented: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    defined: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    retired: {
+      bg: "bg-[var(--bg-muted)]",
+      text: "text-[var(--text-tertiary)]"
+    },
+    // A sync's own states. `needs_repair` is amber for the same reason
+    // `reconciling` is: it has lost its place and cannot recover without
+    // somebody deciding. `rate_limited` and `running` are not, because the
+    // system knows what it is doing and will carry on.
+    running: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" },
+    needs_repair: {
+      bg: "bg-[var(--warning-bg)]",
+      text: "text-[var(--warning)]"
+    },
+    rate_limited: { bg: "bg-[var(--info-bg)]", text: "text-[var(--info)]" }
+  }
+};
+const DEFAULT_COLOR = {
+  bg: "bg-[var(--bg-muted)] ring-1 ring-inset ring-[var(--border-subtle)]",
+  text: "text-[var(--text-secondary)]"
+};
+export {
+  DEFAULT_COLOR,
+  SCOPE_COLORS,
+  STATUS_COLORS
+};
+//# sourceMappingURL=status-colors.js.map

package/dist/shared/status-colors.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/shared/status-colors.ts"],"sourcesContent":["/**\n * What colour every status in the product is.\n *\n * Split out of `status-badge.tsx` when the Connect vocabulary took that file\n * past the 500-line rule. Nothing about the doctrine changed: this is still\n * ONE map, with a scope for the handful of words two domains genuinely\n * disagree about, and a status the map does not know still belongs IN it with\n * a line saying which way it was sorted, rather than in a ternary beside the\n * screen that happened to need it.\n */\n\nexport const STATUS_COLORS: Record<string, { bg: string; text: string }> = {\n  active: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  completed: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  paid: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  published: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  fulfilled: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  // Amber is reserved for \"this needs you\": overdue, failed, out of credit.\n  // Pending and processing are neither — nothing is wrong, the thing simply has\n  // not finished yet. Painting them amber spent the loudest colour in the\n  // palette on the most ordinary state, and beside a genuinely overdue row it\n  // made both look equally urgent. They read as in-progress instead: the quiet\n  // surface draft uses, with full-strength secondary text so they stay legible\n  // rather than fading into the row.\n  pending: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-secondary)]' },\n  processing: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  draft: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-secondary)]' },\n  /* A merchant's own emphasis, not a state of the record — warning is the\n     right weight for it: findable, and not claiming anything is wrong. */\n  featured: { bg: 'bg-[var(--warning-bg)]', text: 'text-[var(--warning)]' },\n  cancelled: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  /**\n   * The money statuses.\n   *\n   * `success` was missing, which is why the payments ledger and the payouts log\n   * each kept a private colour map beside this file rather than using it: a\n   * successful payment would have resolved to the default grey. A reversal and\n   * a part-refund are the same reading as a refund — money went back, nothing\n   * is wrong, nothing needs doing — so they take its treatment rather than an\n   * alarm colour.\n   */\n  success: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  partially_refunded: {\n    bg: 'bg-[var(--accent-secondary)]/10',\n    text: 'text-[var(--accent-secondary)]',\n  },\n  reversed: {\n    bg: 'bg-[var(--accent-secondary)]/10',\n    text: 'text-[var(--accent-secondary)]',\n  },\n  failed: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  overdue: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  refunded: {\n    bg: 'bg-[var(--accent-secondary)]/10',\n    text: 'text-[var(--accent-secondary)]',\n  },\n  partial: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  /**\n   * Invoice lifecycle, which had two private copies — one in the list's\n   * helpers, one in the detail hook — because these three words were missing\n   * and would have come out grey.\n   *\n   * Sorted by the same question. `viewed` is the client opening the document:\n   * a milestone, nothing to do, so info rather than the fifth hue the fork\n   * spent on it. `partially_paid` is money owed and not yet late, which is\n   * ordinary business — amber belongs to `overdue`, one row down. `void` is\n   * `voided` under the name the API uses.\n   */\n  viewed: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  partially_paid: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  void: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  // Campaign and cart lifecycle. Without these, a sent campaign and a draft\n  // rendered in the same grey, which is the one distinction that page is for.\n  sent: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  // The provider confirming it landed, which is not the same fact as `sent`\n  // and is the one a merchant is actually asking about.\n  delivered: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  /**\n   * Hardware on its way, and hardware asked for.\n   *\n   * `shipped` takes the info blue rather than amber: a box on a van is\n   * progress, not a thing needing the merchant. `requested` takes the muted\n   * grey for the same reason `draft` does — it is waiting on us, and a colour\n   * on it would be asking somebody to act on a state they cannot move.\n   *\n   * Both were painted by a hardware order before they were in here, which is\n   * the drift this file exists to stop.\n   */\n  shipped: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  requested: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  scheduled: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  recovered: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  // Tab lifecycle\n  open: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  /**\n   * Dispute lifecycle. `awaiting_merchant` is amber because it is the most\n   * literal case of \"this needs you\" in the product: doing nothing loses the\n   * money. `awaiting_provider` is grey — answered, nothing left to do.\n   */\n  awaiting_merchant: {\n    bg: 'bg-[var(--warning-bg)]',\n    text: 'text-[var(--warning)]',\n  },\n  awaiting_provider: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  /**\n   * Support cases, sorted by the only question this file asks: does this need\n   * a human on the merchant's side?\n   *\n   * `waiting_on_tenant` does — we have asked them something and the case stops\n   * until they answer — so it takes amber, the same job `awaiting_merchant`\n   * has one block up. `waiting_on_potter` is grey: it is with us, and a colour\n   * there would ask them to act on a queue they cannot move. `resolved` is\n   * green because it is finished, and `closed` is grey because it is only\n   * over. `open` is deliberately absent — it already resolves, from the tab\n   * lifecycle above.\n   */\n  waiting_on_tenant: {\n    bg: 'bg-[var(--warning-bg)]',\n    text: 'text-[var(--warning)]',\n  },\n  waiting_on_potter: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  waiting_on_customer: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  resolved: {\n    bg: 'bg-[var(--success-bg)]',\n    text: 'text-[var(--success)]',\n  },\n  closed: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  won: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  lost: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  // The merchant chose this. The money is gone either way, but a decision is\n  // not a failure and should not read in the loss colour.\n  accepted: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  settled: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  /**\n   * Money held and not yet taken — a deposit, a pre-auth, a tap a terminal has\n   * captured and not had confirmed.\n   *\n   * Sorted the way everything here is: does it need a human? It does not. The\n   * customer is already committed and the provider is doing its job, so this is\n   * `confirmed`'s sibling — agreed and not yet due — and takes info rather than\n   * the amber this file reserves for something going wrong. It matters that it\n   * is not green: nothing has actually been collected yet, and painting it as\n   * success is how held money gets counted as revenue.\n   */\n  authorized: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  voided: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  paused: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-secondary)]' },\n  /**\n   * Priority, which is the one axis colour is unambiguously for.\n   *\n   * \"Colour marks attention, not state\" cuts both ways: a status column of\n   * ordinary lifecycle words goes neutral, and a column that exists ONLY to say\n   * how badly something needs a human keeps its colour. The waitlist held these\n   * two privately; they belong with every other colour decision.\n   */\n  /**\n   * TEAM PRESENCE — a person's standing on the roster, sorted by the same\n   * question this file asks of everything: does it need a human?\n   *\n   * It does for an invite that has lapsed, and for one about to: somebody\n   * believes they were added and cannot sign in, and only the manager can fix\n   * it. That is amber's actual job here.\n   *\n   * It does not for the rest. `here` is green because it is the one live fact\n   * on the page — that person is at the counter right now — and everything else\n   * is ordinary: signed in earlier, signed in a while ago, invited and still\n   * within the window, never came back, gone. Those are the roster's normal\n   * weather and they read grey rather than ranking each other by hue.\n   *\n   * Hyphenated keys because `MemberPresence` spells them that way; the label\n   * is written by `readPresence` and passed as an override, so these decide\n   * colour only.\n   */\n  here: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  today: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-secondary)]' },\n  away: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-secondary)]' },\n  never: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  invited: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-secondary)]' },\n  'invite-expiring': {\n    bg: 'bg-[var(--warning-bg)]',\n    text: 'text-[var(--warning)]',\n  },\n  'invite-expired': {\n    bg: 'bg-[var(--warning-bg)]',\n    text: 'text-[var(--warning)]',\n  },\n  removed: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  urgent: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  high: { bg: 'bg-[var(--warning-bg)]', text: 'text-[var(--warning)]' },\n  expired: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  /**\n   * Integration lifecycle. Calendar-sync kept a private five-arm switch for\n   * these purely because `connected` and `error` were missing here and would\n   * have resolved to the default grey — a disconnected calendar and a working\n   * one rendered identically, which is the single distinction that page is for.\n   *\n   * `syncing` and `disconnected` are deliberately NOT added: they fall through\n   * to the default grey, which is what the map already decided for `pending`\n   * and `processing`. Nothing is wrong while a calendar is syncing, so it does\n   * not get a colour. The fork painted it brand-500 and spent an accent on the\n   * most ordinary state.\n   */\n  connected: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n  error: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  /**\n   * Booking lifecycle, which had TWO private copies — one in the list's\n   * constants file and one in the detail hook — and the detail copy is the\n   * drift this file's `pending` comment is about: it painted a pending booking\n   * amber. It also painted `waitlist` amber and `cancelled` grey, so a booking\n   * nobody had cancelled shouted and a cancelled one whispered, which is the\n   * ranking exactly backwards.\n   *\n   * Sorted the same way everything else here is: does it need a human?\n   *  - `confirmed` is agreed and not yet due, like `scheduled`: info.\n   *  - `checked_in` is a milestone reached, not a task: info.\n   *  - `in_progress` and `waitlist` are the booking equivalents of\n   *    `processing` and `pending` — nothing is wrong, it has not finished —\n   *    so they take the same quiet grey rather than an accent.\n   *  - `no_show` costs the merchant the slot and the money: error.\n   *  - `unpaid` is money owed, which is the most literal \"this needs you\"\n   *    there is after a dispute: warning.\n   */\n  confirmed: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  checked_in: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  in_progress: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  waitlist: {\n    bg: 'bg-[var(--bg-muted)]',\n    text: 'text-[var(--text-secondary)]',\n  },\n  no_show: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  unpaid: { bg: 'bg-[var(--warning-bg)]', text: 'text-[var(--warning)]' },\n  /**\n   * On / off / put away. Five screens spelled the off state three ways —\n   * `--text-muted`, `--text-tertiary`, `--text-secondary` on the same grey —\n   * because each wrote its own ternary rather than looking one up.\n   *\n   * `suspended` is the only one with a colour: it is a state a human put the\n   * record into and a human has to take it out of. `inactive` and `archived`\n   * are resting states, and nothing resting needs a hue.\n   */\n  /**\n   * What a live address is doing, from the four-hourly watch.\n   *\n   * Sorted by the rule this file argues elsewhere — amber is \"this needs you\",\n   * red is \"this is broken now\". A store that cannot be reached and a store\n   * serving an error page are both costing the merchant customers this minute,\n   * so both are red. A missing certificate is amber: the store still loads, the\n   * visitor is just warned on the way in, and it usually clears itself.\n   */\n  dns_broken: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  not_responding: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  serving_errors: { bg: 'bg-[var(--error-bg)]', text: 'text-[var(--error)]' },\n  no_certificate: {\n    bg: 'bg-[var(--warning-bg)]',\n    text: 'text-[var(--warning)]',\n  },\n  inactive: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  archived: { bg: 'bg-[var(--bg-muted)]', text: 'text-[var(--text-tertiary)]' },\n  suspended: { bg: 'bg-[var(--warning-bg)]', text: 'text-[var(--warning)]' },\n};\n\n/**\n * The same word asking a different question.\n *\n * `sent` on a campaign is finished work — it went out, nothing is owed, green\n * is right. `sent` on an invoice is money NOT yet in, and green said the\n * opposite of the truth on every unpaid invoice in the list. One map still, and\n * a scope for the handful of words two domains genuinely disagree about, rather\n * than a private copy per screen — which is what the invoice screens had.\n */\nexport const SCOPE_COLORS: Record<\n  string,\n  Record<string, (typeof STATUS_COLORS)[string]>\n> = {\n  invoice: {\n    sent: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  },\n  /**\n   * A bill the business owes, where `open` means the opposite of what it means\n   * everywhere else.\n   *\n   * The shared map paints `open` green, which is right for a dispute or a shift\n   * — the thing is live and healthy. A bill that is open is money not yet paid.\n   * Green there tells a merchant scanning a due list that the row is settled,\n   * which is the one thing it is not. Neutral: it is ordinary, it is not done,\n   * and it is not late. Late is `overdue`, which the shared map already reads\n   * red, and that is the row that should pull the eye.\n   */\n  bill: {\n    open: { bg: 'bg-[var(--bg-subtle)]', text: 'text-[var(--text-secondary)]' },\n  },\n  /**\n   * Connect: a managed connection, and the life of one command.\n   *\n   * Sorted on the question the operator is actually asking, which is \"does\n   * this need a human?\" — so amber is spent only where the answer is yes.\n   *\n   * `reconciling` is the one that earns it. It means the provider may have\n   * acted and did not say so clearly: the invoice might exist, the message\n   * might have gone. Nothing is broken and nothing is finished, and retrying\n   * blindly is how a merchant gets billed twice. That is a person's decision,\n   * so it reads amber alongside `attention_required`, which is a connection\n   * whose credential is failing.\n   *\n   * `retry_scheduled` is deliberately NOT amber. The system knows what it is\n   * doing and will do it again shortly; colouring it the same as the case that\n   * needs a human would make the amber mean nothing by volume.\n   *\n   * `accepted` and `published` are grey against the global map's green. Work\n   * that is durably recorded has not happened yet, and green on a command the\n   * provider has never seen says it did.\n   *\n   * The availability words are the point of the whole surface. `pilot` is\n   * info; `sandbox_certified`, `fixture_certified`, `implemented` and\n   * `defined` stay grey no matter how much code exists behind them, because\n   * only `generally_available` may read as live. A green pill on a connector\n   * that has never carried production traffic is the lie this vocabulary was\n   * written to prevent.\n   */\n  connect: {\n    /**\n     * A managed sending identity's life.\n     *\n     * Sorted the same way as everything above it: amber only where a person\n     * has to do something. `action_required` is the literal case — a DNS\n     * record nobody added — and `expiring` earns it for the reason this state\n     * exists at all: a renewal that lapses is indistinguishable from a working\n     * identity right up until the morning delivery stops, so it has to shout\n     * while there is still time to act.\n     *\n     * `verifying` and `requested` stay grey. Box is waiting on a provider,\n     * nothing is wrong, and colouring them would say otherwise.\n     *\n     * `suspended` and `released` take the same tertiary grey as\n     * `disconnected`: stopped, and not by anything the merchant can undo from\n     * this screen. Amber on a state with no action attached is amber spent for\n     * nothing, and spends the colour the two rows above it need.\n     */\n    /**\n     * A route's health, which is not a connection's.\n     *\n     * `degraded` is amber because it needs a person to know, not to act —\n     * their work is slower and nothing is lost. `unavailable` is grey rather\n     * than red for the reason the panel says out loud: work waits instead of\n     * failing, so painting it as an error would tell a merchant they had lost\n     * something they had not.\n     */\n    degraded: {\n      bg: 'bg-[var(--warning-bg)]',\n      text: 'text-[var(--warning)]',\n    },\n    healthy: {\n      bg: 'bg-[var(--success-bg)]',\n      text: 'text-[var(--success)]',\n    },\n    requested: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-secondary)]',\n    },\n    verifying: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-secondary)]',\n    },\n    action_required: {\n      bg: 'bg-[var(--warning-bg)]',\n      text: 'text-[var(--warning)]',\n    },\n    expiring: {\n      bg: 'bg-[var(--warning-bg)]',\n      text: 'text-[var(--warning)]',\n    },\n    suspended: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    released: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    accepted: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-secondary)]',\n    },\n    published: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-secondary)]',\n    },\n    processing: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n    retry_scheduled: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n    reconciling: {\n      bg: 'bg-[var(--warning-bg)]',\n      text: 'text-[var(--warning)]',\n    },\n    succeeded: { bg: 'bg-[var(--success-bg)]', text: 'text-[var(--success)]' },\n    attention_required: {\n      bg: 'bg-[var(--warning-bg)]',\n      text: 'text-[var(--warning)]',\n    },\n    disconnected: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    unavailable: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    revoked: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    generally_available: {\n      bg: 'bg-[var(--success-bg)]',\n      text: 'text-[var(--success)]',\n    },\n    pilot: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n    sandbox_certified: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-secondary)]',\n    },\n    fixture_certified: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-secondary)]',\n    },\n    implemented: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    defined: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    retired: {\n      bg: 'bg-[var(--bg-muted)]',\n      text: 'text-[var(--text-tertiary)]',\n    },\n    // A sync's own states. `needs_repair` is amber for the same reason\n    // `reconciling` is: it has lost its place and cannot recover without\n    // somebody deciding. `rate_limited` and `running` are not, because the\n    // system knows what it is doing and will carry on.\n    running: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n    needs_repair: {\n      bg: 'bg-[var(--warning-bg)]',\n      text: 'text-[var(--warning)]',\n    },\n    rate_limited: { bg: 'bg-[var(--info-bg)]', text: 'text-[var(--info)]' },\n  },\n};\n\n/**\n * The quiet badge, and the hairline is not decoration.\n *\n * `--bg-muted` is rgb(32,32,35). A hovered table row is `#ffffff09` over the\n * card, which lands on rgb(33,33,36) — one value away — so the pill dissolved\n * into the row exactly when you were pointing at it. A fill can collide with a\n * background; an edge cannot, because it is a boundary rather than a tone.\n *\n * `--border-subtle` is the same hairline every card and row already uses, so\n * this adds an edge without adding a colour.\n */\nexport const DEFAULT_COLOR = {\n  bg: 'bg-[var(--bg-muted)] ring-1 ring-inset ring-[var(--border-subtle)]',\n  text: 'text-[var(--text-secondary)]',\n};\n"],"mappings":"AAWO,MAAM,gBAA8D;AAAA,EACzE,QAAQ,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACtE,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACzE,MAAM,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACpE,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACzE,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAQzE,SAAS,EAAE,IAAI,wBAAwB,MAAM,+BAA+B;AAAA,EAC5E,YAAY;AAAA,IACV,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,OAAO,EAAE,IAAI,wBAAwB,MAAM,+BAA+B;AAAA;AAAA;AAAA,EAG1E,UAAU,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACxE,WAAW,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAWrE,SAAS,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACvE,oBAAoB;AAAA,IAClB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,UAAU;AAAA,IACR,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,QAAQ,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EAClE,SAAS,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EACnE,UAAU;AAAA,IACR,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,SAAS,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAYjE,QAAQ,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EAChE,gBAAgB,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACxE,MAAM,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA;AAAA;AAAA,EAGxE,MAAM,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA;AAAA;AAAA,EAGpE,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAYzE,SAAS,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACjE,WAAW;AAAA,IACT,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,WAAW,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACnE,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA;AAAA,EAEzE,MAAM,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAMpE,mBAAmB;AAAA,IACjB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,mBAAmB;AAAA,IACjB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAaA,mBAAmB;AAAA,IACjB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,mBAAmB;AAAA,IACjB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,qBAAqB;AAAA,IACnB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,UAAU;AAAA,IACR,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,QAAQ;AAAA,IACN,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,KAAK,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACnE,MAAM,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA;AAAA;AAAA,EAGhE,UAAU;AAAA,IACR,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,SAAS,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAYjE,YAAY,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACpE,QAAQ,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA,EAC1E,QAAQ,EAAE,IAAI,wBAAwB,MAAM,+BAA+B;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,EA2B3E,MAAM,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACpE,OAAO,EAAE,IAAI,wBAAwB,MAAM,+BAA+B;AAAA,EAC1E,MAAM,EAAE,IAAI,wBAAwB,MAAM,+BAA+B;AAAA,EACzE,OAAO,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA,EACzE,SAAS,EAAE,IAAI,wBAAwB,MAAM,+BAA+B;AAAA,EAC5E,mBAAmB;AAAA,IACjB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,kBAAkB;AAAA,IAChB,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,SAAS,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA,EAC3E,QAAQ,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EAClE,MAAM,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACpE,SAAS,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAa3E,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,EACzE,OAAO,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAmBjE,WAAW,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACnE,YAAY,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACpE,aAAa;AAAA,IACX,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,UAAU;AAAA,IACR,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,SAAS,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EACnE,QAAQ,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAmBtE,YAAY,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EACtE,gBAAgB,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EAC1E,gBAAgB,EAAE,IAAI,wBAAwB,MAAM,sBAAsB;AAAA,EAC1E,gBAAgB;AAAA,IACd,IAAI;AAAA,IACJ,MAAM;AAAA,EACR;AAAA,EACA,UAAU,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA,EAC5E,UAAU,EAAE,IAAI,wBAAwB,MAAM,8BAA8B;AAAA,EAC5E,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAC3E;AAWO,MAAM,eAGT;AAAA,EACF,SAAS;AAAA,IACP,MAAM,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EAChE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAYA,MAAM;AAAA,IACJ,MAAM,EAAE,IAAI,yBAAyB,MAAM,+BAA+B;AAAA,EAC5E;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,EA6BA,SAAS;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,IA4BP,UAAU;AAAA,MACR,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,SAAS;AAAA,MACP,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,WAAW;AAAA,MACT,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,WAAW;AAAA,MACT,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,iBAAiB;AAAA,MACf,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,UAAU;AAAA,MACR,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,WAAW;AAAA,MACT,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,UAAU;AAAA,MACR,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,UAAU;AAAA,MACR,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,WAAW;AAAA,MACT,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,YAAY,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,IACpE,iBAAiB,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,IACzE,aAAa;AAAA,MACX,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,WAAW,EAAE,IAAI,0BAA0B,MAAM,wBAAwB;AAAA,IACzE,oBAAoB;AAAA,MAClB,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,cAAc;AAAA,MACZ,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,aAAa;AAAA,MACX,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,SAAS;AAAA,MACP,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,qBAAqB;AAAA,MACnB,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,OAAO,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,IAC/D,mBAAmB;AAAA,MACjB,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,mBAAmB;AAAA,MACjB,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,aAAa;AAAA,MACX,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,SAAS;AAAA,MACP,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,SAAS;AAAA,MACP,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA;AAAA;AAAA;AAAA;AAAA,IAKA,SAAS,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,IACjE,cAAc;AAAA,MACZ,IAAI;AAAA,MACJ,MAAM;AAAA,IACR;AAAA,IACA,cAAc,EAAE,IAAI,uBAAuB,MAAM,qBAAqB;AAAA,EACxE;AACF;AAaO,MAAM,gBAAgB;AAAA,EAC3B,IAAI;AAAA,EACJ,MAAM;AACR;","names":[]}