@withpotter/components 0.13.0-next.101

package/dist/plan-editor/use-plan-groups.d.ts

@@ -0,0 +1,19 @@
+export interface PlanGroup {
+    id: string;
+    label: string;
+    /** How many plans already sit in it, so the picker can say so. */
+    count: number;
+}
+/** A group id a merchant will never have to type, minted from what they did. */
+export declare function slugifyGroup(label: string): string;
+/**
+ * The groups this workspace already has.
+ *
+ * The group fields used to be two free-text boxes: a merchant was asked to
+ * invent a stable key, type it identically on the second plan, and only then
+ * did the two show up together on the storefront. One typo and the pair
+ * silently stopped being a pair. The groups are derivable — every plan that
+ * has one carries its id and label — so the second plan picks the first one's
+ * group from a list instead.
+ */
+export declare function usePlanGroups(tenantSlug: string | undefined): PlanGroup[];

package/dist/plan-editor/use-plan-groups.js

@@ -0,0 +1,40 @@
+"use client";
+import { useEffect, useState } from "react";
+import { merchantSubscriptionsApi } from "@withpotter/lib/api/merchant-subscriptions";
+function slugifyGroup(label) {
+  return label.toLowerCase().trim().replace(/[^a-z0-9]+/g, "-").replace(/^-|-$/g, "");
+}
+function usePlanGroups(tenantSlug) {
+  const [groups, setGroups] = useState([]);
+  useEffect(() => {
+    if (!tenantSlug) return;
+    let cancelled = false;
+    merchantSubscriptionsApi.listPlans(tenantSlug, { limit: 100 }).then((res) => {
+      if (cancelled) return;
+      const byId = /* @__PURE__ */ new Map();
+      for (const plan of res.plans ?? []) {
+        if (!plan.groupId) continue;
+        const existing = byId.get(plan.groupId);
+        byId.set(plan.groupId, {
+          id: plan.groupId,
+          label: existing?.label || plan.groupLabel || plan.groupId,
+          count: (existing?.count ?? 0) + 1
+        });
+      }
+      setGroups(
+        [...byId.values()].sort((a, b) => a.label.localeCompare(b.label))
+      );
+    }).catch(() => {
+      if (!cancelled) setGroups([]);
+    });
+    return () => {
+      cancelled = true;
+    };
+  }, [tenantSlug]);
+  return groups;
+}
+export {
+  slugifyGroup,
+  usePlanGroups
+};
+//# sourceMappingURL=use-plan-groups.js.map

package/dist/plan-editor/use-plan-groups.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/plan-editor/use-plan-groups.ts"],"sourcesContent":["'use client';\n\nimport { useEffect, useState } from 'react';\nimport { merchantSubscriptionsApi } from '@withpotter/lib/api/merchant-subscriptions';\n\nexport interface PlanGroup {\n  id: string;\n  label: string;\n  /** How many plans already sit in it, so the picker can say so. */\n  count: number;\n}\n\n/** A group id a merchant will never have to type, minted from what they did. */\nexport function slugifyGroup(label: string) {\n  return label\n    .toLowerCase()\n    .trim()\n    .replace(/[^a-z0-9]+/g, '-')\n    .replace(/^-|-$/g, '');\n}\n\n/**\n * The groups this workspace already has.\n *\n * The group fields used to be two free-text boxes: a merchant was asked to\n * invent a stable key, type it identically on the second plan, and only then\n * did the two show up together on the storefront. One typo and the pair\n * silently stopped being a pair. The groups are derivable — every plan that\n * has one carries its id and label — so the second plan picks the first one's\n * group from a list instead.\n */\nexport function usePlanGroups(tenantSlug: string | undefined) {\n  const [groups, setGroups] = useState<PlanGroup[]>([]);\n\n  useEffect(() => {\n    if (!tenantSlug) return;\n    let cancelled = false;\n    merchantSubscriptionsApi\n      .listPlans(tenantSlug, { limit: 100 })\n      .then((res) => {\n        if (cancelled) return;\n        const byId = new Map<string, PlanGroup>();\n        for (const plan of res.plans ?? []) {\n          if (!plan.groupId) continue;\n          const existing = byId.get(plan.groupId);\n          byId.set(plan.groupId, {\n            id: plan.groupId,\n            label: existing?.label || plan.groupLabel || plan.groupId,\n            count: (existing?.count ?? 0) + 1,\n          });\n        }\n        setGroups(\n          [...byId.values()].sort((a, b) => a.label.localeCompare(b.label)),\n        );\n      })\n      .catch(() => {\n        // A picker that cannot list is a picker with one option, \"New group\",\n        // which is still the whole job for a workspace's first plan.\n        if (!cancelled) setGroups([]);\n      });\n    return () => {\n      cancelled = true;\n    };\n  }, [tenantSlug]);\n\n  return groups;\n}\n"],"mappings":";AAEA,SAAS,WAAW,gBAAgB;AACpC,SAAS,gCAAgC;AAUlC,SAAS,aAAa,OAAe;AAC1C,SAAO,MACJ,YAAY,EACZ,KAAK,EACL,QAAQ,eAAe,GAAG,EAC1B,QAAQ,UAAU,EAAE;AACzB;AAYO,SAAS,cAAc,YAAgC;AAC5D,QAAM,CAAC,QAAQ,SAAS,IAAI,SAAsB,CAAC,CAAC;AAEpD,YAAU,MAAM;AACd,QAAI,CAAC,WAAY;AACjB,QAAI,YAAY;AAChB,6BACG,UAAU,YAAY,EAAE,OAAO,IAAI,CAAC,EACpC,KAAK,CAAC,QAAQ;AACb,UAAI,UAAW;AACf,YAAM,OAAO,oBAAI,IAAuB;AACxC,iBAAW,QAAQ,IAAI,SAAS,CAAC,GAAG;AAClC,YAAI,CAAC,KAAK,QAAS;AACnB,cAAM,WAAW,KAAK,IAAI,KAAK,OAAO;AACtC,aAAK,IAAI,KAAK,SAAS;AAAA,UACrB,IAAI,KAAK;AAAA,UACT,OAAO,UAAU,SAAS,KAAK,cAAc,KAAK;AAAA,UAClD,QAAQ,UAAU,SAAS,KAAK;AAAA,QAClC,CAAC;AAAA,MACH;AACA;AAAA,QACE,CAAC,GAAG,KAAK,OAAO,CAAC,EAAE,KAAK,CAAC,GAAG,MAAM,EAAE,MAAM,cAAc,EAAE,KAAK,CAAC;AAAA,MAClE;AAAA,IACF,CAAC,EACA,MAAM,MAAM;AAGX,UAAI,CAAC,UAAW,WAAU,CAAC,CAAC;AAAA,IAC9B,CAAC;AACH,WAAO,MAAM;AACX,kBAAY;AAAA,IACd;AAAA,EACF,GAAG,CAAC,UAAU,CAAC;AAEf,SAAO;AACT;","names":[]}

package/dist/plan-editor/use-plan-products.d.ts

@@ -0,0 +1,17 @@
+import type { ContentItem } from '@withpotter/lib/api/types';
+export declare function usePlanProducts(opts: {
+    enabled: boolean;
+    tenantSlug: string | undefined;
+    selectedIds: string[];
+    discountPercent: string;
+}): {
+    products: ContentItem[];
+    loading: boolean;
+    search: string;
+    setSearch: import("react").Dispatch<import("react").SetStateAction<string>>;
+    filtered: ContentItem[];
+    selected: ContentItem[];
+    subtotal: number;
+    discountPct: number;
+    estCycle: number;
+};

package/dist/plan-editor/use-plan-products.js

@@ -0,0 +1,49 @@
+"use client";
+import { useEffect, useMemo, useState } from "react";
+import { contentApi } from "@withpotter/lib/api/content";
+function usePlanProducts(opts) {
+  const { enabled, tenantSlug, selectedIds, discountPercent } = opts;
+  const [products, setProducts] = useState([]);
+  const [loading, setLoading] = useState(false);
+  const [search, setSearch] = useState("");
+  useEffect(() => {
+    if (!enabled || !tenantSlug) return;
+    let cancelled = false;
+    setLoading(true);
+    contentApi.list(tenantSlug, "products", { limit: 100 }).then((res) => {
+      if (!cancelled) setProducts(res.data || []);
+    }).catch(() => {
+      if (!cancelled) setProducts([]);
+    }).finally(() => {
+      if (!cancelled) setLoading(false);
+    });
+    return () => {
+      cancelled = true;
+    };
+  }, [enabled, tenantSlug]);
+  const filtered = useMemo(
+    () => search ? products.filter(
+      (p) => p.title.toLowerCase().includes(search.toLowerCase())
+    ) : products,
+    [search, products]
+  );
+  const selected = products.filter((p) => selectedIds.includes(p.id));
+  const subtotal = selected.reduce((acc, p) => acc + (p.price ?? 0), 0);
+  const discountPct = Number(discountPercent) || 0;
+  const estCycle = subtotal * (1 - discountPct / 100);
+  return {
+    products,
+    loading,
+    search,
+    setSearch,
+    filtered,
+    selected,
+    subtotal,
+    discountPct,
+    estCycle
+  };
+}
+export {
+  usePlanProducts
+};
+//# sourceMappingURL=use-plan-products.js.map

package/dist/plan-editor/use-plan-products.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/plan-editor/use-plan-products.ts"],"sourcesContent":["'use client';\n\nimport { useEffect, useMemo, useState } from 'react';\nimport { contentApi } from '@withpotter/lib/api/content';\nimport type { ContentItem } from '@withpotter/lib/api/types';\n\nexport function usePlanProducts(opts: {\n  enabled: boolean;\n  tenantSlug: string | undefined;\n  selectedIds: string[];\n  discountPercent: string;\n}) {\n  const { enabled, tenantSlug, selectedIds, discountPercent } = opts;\n  const [products, setProducts] = useState<ContentItem[]>([]);\n  const [loading, setLoading] = useState(false);\n  const [search, setSearch] = useState('');\n\n  useEffect(() => {\n    if (!enabled || !tenantSlug) return;\n    let cancelled = false;\n    setLoading(true);\n    contentApi\n      .list(tenantSlug, 'products', { limit: 100 })\n      .then((res) => {\n        if (!cancelled) setProducts(res.data || []);\n      })\n      .catch(() => {\n        if (!cancelled) setProducts([]);\n      })\n      .finally(() => {\n        if (!cancelled) setLoading(false);\n      });\n    return () => {\n      cancelled = true;\n    };\n  }, [enabled, tenantSlug]);\n\n  const filtered = useMemo(\n    () =>\n      search\n        ? products.filter((p) =>\n            p.title.toLowerCase().includes(search.toLowerCase()),\n          )\n        : products,\n    [search, products],\n  );\n\n  const selected = products.filter((p) => selectedIds.includes(p.id));\n  const subtotal = selected.reduce((acc, p) => acc + (p.price ?? 0), 0);\n  const discountPct = Number(discountPercent) || 0;\n  const estCycle = subtotal * (1 - discountPct / 100);\n\n  return {\n    products,\n    loading,\n    search,\n    setSearch,\n    filtered,\n    selected,\n    subtotal,\n    discountPct,\n    estCycle,\n  };\n}\n"],"mappings":";AAEA,SAAS,WAAW,SAAS,gBAAgB;AAC7C,SAAS,kBAAkB;AAGpB,SAAS,gBAAgB,MAK7B;AACD,QAAM,EAAE,SAAS,YAAY,aAAa,gBAAgB,IAAI;AAC9D,QAAM,CAAC,UAAU,WAAW,IAAI,SAAwB,CAAC,CAAC;AAC1D,QAAM,CAAC,SAAS,UAAU,IAAI,SAAS,KAAK;AAC5C,QAAM,CAAC,QAAQ,SAAS,IAAI,SAAS,EAAE;AAEvC,YAAU,MAAM;AACd,QAAI,CAAC,WAAW,CAAC,WAAY;AAC7B,QAAI,YAAY;AAChB,eAAW,IAAI;AACf,eACG,KAAK,YAAY,YAAY,EAAE,OAAO,IAAI,CAAC,EAC3C,KAAK,CAAC,QAAQ;AACb,UAAI,CAAC,UAAW,aAAY,IAAI,QAAQ,CAAC,CAAC;AAAA,IAC5C,CAAC,EACA,MAAM,MAAM;AACX,UAAI,CAAC,UAAW,aAAY,CAAC,CAAC;AAAA,IAChC,CAAC,EACA,QAAQ,MAAM;AACb,UAAI,CAAC,UAAW,YAAW,KAAK;AAAA,IAClC,CAAC;AACH,WAAO,MAAM;AACX,kBAAY;AAAA,IACd;AAAA,EACF,GAAG,CAAC,SAAS,UAAU,CAAC;AAExB,QAAM,WAAW;AAAA,IACf,MACE,SACI,SAAS;AAAA,MAAO,CAAC,MACf,EAAE,MAAM,YAAY,EAAE,SAAS,OAAO,YAAY,CAAC;AAAA,IACrD,IACA;AAAA,IACN,CAAC,QAAQ,QAAQ;AAAA,EACnB;AAEA,QAAM,WAAW,SAAS,OAAO,CAAC,MAAM,YAAY,SAAS,EAAE,EAAE,CAAC;AAClE,QAAM,WAAW,SAAS,OAAO,CAAC,KAAK,MAAM,OAAO,EAAE,SAAS,IAAI,CAAC;AACpE,QAAM,cAAc,OAAO,eAAe,KAAK;AAC/C,QAAM,WAAW,YAAY,IAAI,cAAc;AAE/C,SAAO;AAAA,IACL;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,EACF;AACF;","names":[]}

package/dist/plan-editor.d.ts

@@ -0,0 +1 @@
+export * from './plan-editor/index';

package/dist/plan-editor.js

@@ -0,0 +1 @@
+export * from './plan-editor/index.js';

package/dist/potter/index.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Only what the dashboard shell mounts.
+ *
+ * The surface, the ask hook and the context are imported from their own files
+ * by the home's ask bar, deliberately: pulling them through here would drag
+ * `PotterLauncher` — a fixed-position button, a panel and a scrim — into the
+ * module graph of a page that renders none of them. A barrel is for the
+ * boundary, not for every internal that happens to be exported.
+ */
+export { PotterProvider } from './potter-context';
+export { PotterLauncher } from './potter-launcher';

package/dist/potter/index.js

@@ -0,0 +1,7 @@
+import { PotterProvider } from "./potter-context";
+import { PotterLauncher } from "./potter-launcher";
+export {
+  PotterLauncher,
+  PotterProvider
+};
+//# sourceMappingURL=index.js.map

package/dist/potter/index.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/potter/index.ts"],"sourcesContent":["/**\n * Only what the dashboard shell mounts.\n *\n * The surface, the ask hook and the context are imported from their own files\n * by the home's ask bar, deliberately: pulling them through here would drag\n * `PotterLauncher` — a fixed-position button, a panel and a scrim — into the\n * module graph of a page that renders none of them. A barrel is for the\n * boundary, not for every internal that happens to be exported.\n */\nexport { PotterProvider } from './potter-context';\nexport { PotterLauncher } from './potter-launcher';\n"],"mappings":"AASA,SAAS,sBAAsB;AAC/B,SAAS,sBAAsB;","names":[]}

package/dist/potter/potter-answer.d.ts

@@ -0,0 +1,96 @@
+import type { HelpTopic } from '@withpotter/lib/help-topics';
+/**
+ * What Box decides to do with a sentence.
+ *
+ * THIS IS A ROUTER, NOT A MODEL, and the distinction is the whole design. There
+ * is no general answering endpoint behind the dashboard today: what exists is a
+ * help corpus, a search index over the merchant's own records, and a setup
+ * proposal engine. A panel that opened a chat and improvised over those three
+ * would be a demo. So every reply Box gives lands on one of them, and the
+ * fourth case says so plainly rather than guessing.
+ *
+ * The order below is deliberate and it is the part that would rot first if
+ * someone reshuffled it:
+ *
+ *   setup BEFORE help — "how do I set up delivery" matches a help topic AND
+ *   reads as an instruction. The help topic is the better answer; the setup
+ *   engine should only take sentences that describe a BUSINESS, not a task.
+ *   Hence the patterns below are about what you sell, not about doing a thing.
+ *
+ *   help BEFORE find — "where do refunds go" is a question with an answer, not
+ *   a record to look up. Falling to search first would hand back an empty
+ *   result list for a question the corpus answers.
+ *
+ *   find LAST of the three, because it is the widest net: almost any noun is
+ *   plausibly a customer name. It has to be the fallback of the confident
+ *   branches, never the first guess.
+ */
+export type PotterReply = {
+    kind: 'help';
+    topics: HelpTopic[];
+} | {
+    kind: 'find';
+    query: string;
+} | {
+    kind: 'setup';
+    intent: string;
+} | {
+    kind: 'unsure';
+    query: string;
+}
+/**
+ * A spreadsheet Box has read and can hand to the catalogue's importer.
+ *
+ * Never produced by `routeQuestion` — nothing anybody TYPES lands here. It is
+ * pushed directly by the attach control, which is why this union is now the
+ * shape of "what a Box turn can be" rather than "what the router returns".
+ */
+ | {
+    kind: 'sheet';
+    rows: number;
+    usable: boolean;
+}
+/**
+ * A picture Box cannot read, with the one thing it can do about it.
+ *
+ * Same rule as `sheet`: never produced by `routeQuestion`, because nothing
+ * anybody types lands here. It is pushed by the attach control.
+ */
+ | {
+    kind: 'photo';
+    count: number;
+};
+/**
+ * Route one question.
+ *
+ * `topics` is the merchant's own resolved corpus, not the full one — a business
+ * that takes no bookings must not be answered with a bookings topic, which is
+ * the same gate the help page and the nav already apply.
+ */
+export declare function routeQuestion(query: string, topics: HelpTopic[]): PotterReply;
+/**
+ * What Box says out loud before the affordances under it.
+ *
+ * Kept beside the router rather than in the component: the sentence and the
+ * branch that produced it have to agree, and they drift the moment they live in
+ * two files.
+ */
+/**
+ * THE ANSWER FIRST, NOT A CAPTION OVER IT.
+ *
+ * This returned "Here is what I have on that." for every help match, and then
+ * the topics were printed underneath in full — so the largest text in the
+ * reply said nothing and the actual answer arrived as a heading plus two
+ * paragraphs plus a numbered list, twice over when two topics matched. That is
+ * a search results page wearing a conversation's clothes.
+ *
+ * The order every good answer surface uses — Perplexity's, Fin's — is: the
+ * answer, then where it came from, then what to do about it. `replySpoken`
+ * already worked this way, because a voice reading a caption aloud answers
+ * nothing and the problem was impossible to miss there. It was just as true on
+ * screen and easy to miss.
+ *
+ * The topics still render under this as sources; see `potter-thread`.
+ */
+export declare function replyLead(reply: PotterReply): string;
+export declare function replySpoken(reply: PotterReply): string;

package/dist/potter/potter-answer.js

@@ -0,0 +1,64 @@
+import { searchHelpTopics } from "@withpotter/lib/help-topics";
+import { isServiceOperationsEnabled } from "@withpotter/lib/service-operations-api";
+const SETUP = [
+  /\b(i|we)\s+(sell|make|rent|run|host|serve|offer|do)\b/i,
+  /\bmy\s+(shop|store|business|studio|kitchen|salon|club|brand)\b/i,
+  /\bset\s*up\s+(my|our|the)?\s*(shop|store|business|site|catalog|catalogue)\b/i,
+  /\b(build|create|launch)\s+(me\s+)?(a|my|our)\s+(shop|store|site|website|business)\b/i
+];
+const FIND = [
+  /\b(find|show|open|search|look\s*up|pull\s*up|go\s*to|jump\s*to|where\s+is)\b/i,
+  /#\s*\d+/,
+  /\b(order|invoice|customer|product|item|booking|receipt)s?\b/i
+];
+const hits = (patterns, q) => patterns.some((p) => p.test(q));
+function routeQuestion(query, topics) {
+  const q = query.trim();
+  if (!q) return { kind: "unsure", query: q };
+  if (hits(SETUP, q)) return { kind: "setup", intent: q };
+  const found = searchHelpTopics(topics, q).slice(0, 3);
+  if (found.length) return { kind: "help", topics: found };
+  if (hits(FIND, q)) return { kind: "find", query: q };
+  return { kind: "unsure", query: q };
+}
+function replyLead(reply) {
+  switch (reply.kind) {
+    case "help": {
+      const top = reply.topics[0];
+      return top ? top.answer : "I have nothing on that one yet.";
+    }
+    case "find":
+      return "I can look through your orders, invoices, customers and products for that.";
+    case "setup":
+      return "I can turn that into a setup plan for you to review before anything changes.";
+    /* A sheet's sentence is written by `describeSheet`, which has the row count
+       and the columns; there is nothing generic to say about a file. The turn
+       carries its own text and this is never consulted — but the switch is
+       exhaustive and a missing arm is a compile error rather than a bug. */
+    case "sheet":
+    case "photo":
+      return "";
+    /* The second half names the door that is actually under it. Where cases
+       exist the control says "Start a case", and a sentence still offering to
+       "put it to the team" describes a button that is no longer there. */
+    case "unsure":
+      return isServiceOperationsEnabled() ? "I can't answer that one yet. Here is what I can do today, or you can open a case and a person will take it." : "I can't answer that one yet. Here is what I can do today, or you can put it to the team.";
+  }
+}
+const SPOKEN_ANSWER_MAX = 320;
+function replySpoken(reply) {
+  if (reply.kind !== "help") return replyLead(reply);
+  const top = reply.topics[0];
+  if (!top) return replyLead(reply);
+  if (top.answer.length <= SPOKEN_ANSWER_MAX) return top.answer;
+  const clipped = top.answer.slice(0, SPOKEN_ANSWER_MAX);
+  const end = Math.max(clipped.lastIndexOf(". "), clipped.lastIndexOf("? "));
+  const said = end > 80 ? clipped.slice(0, end + 1) : `${clipped.trimEnd()}\u2026`;
+  return `${said} The rest is on screen.`;
+}
+export {
+  replyLead,
+  replySpoken,
+  routeQuestion
+};
+//# sourceMappingURL=potter-answer.js.map

package/dist/potter/potter-answer.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/potter/potter-answer.ts"],"sourcesContent":["import type { HelpTopic } from '@withpotter/lib/help-topics';\nimport { searchHelpTopics } from '@withpotter/lib/help-topics';\nimport { isServiceOperationsEnabled } from '@withpotter/lib/service-operations-api';\n\n/**\n * What Box decides to do with a sentence.\n *\n * THIS IS A ROUTER, NOT A MODEL, and the distinction is the whole design. There\n * is no general answering endpoint behind the dashboard today: what exists is a\n * help corpus, a search index over the merchant's own records, and a setup\n * proposal engine. A panel that opened a chat and improvised over those three\n * would be a demo. So every reply Box gives lands on one of them, and the\n * fourth case says so plainly rather than guessing.\n *\n * The order below is deliberate and it is the part that would rot first if\n * someone reshuffled it:\n *\n *   setup BEFORE help — \"how do I set up delivery\" matches a help topic AND\n *   reads as an instruction. The help topic is the better answer; the setup\n *   engine should only take sentences that describe a BUSINESS, not a task.\n *   Hence the patterns below are about what you sell, not about doing a thing.\n *\n *   help BEFORE find — \"where do refunds go\" is a question with an answer, not\n *   a record to look up. Falling to search first would hand back an empty\n *   result list for a question the corpus answers.\n *\n *   find LAST of the three, because it is the widest net: almost any noun is\n *   plausibly a customer name. It has to be the fallback of the confident\n *   branches, never the first guess.\n */\nexport type PotterReply =\n  | { kind: 'help'; topics: HelpTopic[] }\n  | { kind: 'find'; query: string }\n  | { kind: 'setup'; intent: string }\n  | { kind: 'unsure'; query: string }\n  /**\n   * A spreadsheet Box has read and can hand to the catalogue's importer.\n   *\n   * Never produced by `routeQuestion` — nothing anybody TYPES lands here. It is\n   * pushed directly by the attach control, which is why this union is now the\n   * shape of \"what a Box turn can be\" rather than \"what the router returns\".\n   */\n  | { kind: 'sheet'; rows: number; usable: boolean }\n  /**\n   * A picture Box cannot read, with the one thing it can do about it.\n   *\n   * Same rule as `sheet`: never produced by `routeQuestion`, because nothing\n   * anybody types lands here. It is pushed by the attach control.\n   */\n  | { kind: 'photo'; count: number };\n\n/**\n * Sentences that describe a business rather than ask about the software.\n *\n * \"I sell\", \"we run\", \"my shop\" — first person and present tense, which is how\n * someone answers \"what is your business\" and not how they ask a question. The\n * imperative forms (\"set up my store\") are here too because they are the ones\n * the home launcher's own placeholder invites.\n */\nconst SETUP = [\n  /\\b(i|we)\\s+(sell|make|rent|run|host|serve|offer|do)\\b/i,\n  /\\bmy\\s+(shop|store|business|studio|kitchen|salon|club|brand)\\b/i,\n  /\\bset\\s*up\\s+(my|our|the)?\\s*(shop|store|business|site|catalog|catalogue)\\b/i,\n  /\\b(build|create|launch)\\s+(me\\s+)?(a|my|our)\\s+(shop|store|site|website|business)\\b/i,\n];\n\n/**\n * Sentences reaching for a record. Note `#\\d` and the bare noun list: \"order\n * 1042\" and \"invoice for Ada\" are the two shapes merchants actually type, and\n * neither contains a verb.\n */\nconst FIND = [\n  /\\b(find|show|open|search|look\\s*up|pull\\s*up|go\\s*to|jump\\s*to|where\\s+is)\\b/i,\n  /#\\s*\\d+/,\n  /\\b(order|invoice|customer|product|item|booking|receipt)s?\\b/i,\n];\n\n/** True when any pattern in the set matches. */\nconst hits = (patterns: RegExp[], q: string) => patterns.some((p) => p.test(q));\n\n/**\n * Route one question.\n *\n * `topics` is the merchant's own resolved corpus, not the full one — a business\n * that takes no bookings must not be answered with a bookings topic, which is\n * the same gate the help page and the nav already apply.\n */\nexport function routeQuestion(query: string, topics: HelpTopic[]): PotterReply {\n  const q = query.trim();\n  if (!q) return { kind: 'unsure', query: q };\n\n  if (hits(SETUP, q)) return { kind: 'setup', intent: q };\n\n  // Two, not one. A single weak hit on a seventeen-topic corpus is as often\n  // \"we don't have your words\" as it is an answer — the help page makes the\n  // same call and keeps a human on screen for exactly this reason.\n  const found = searchHelpTopics(topics, q).slice(0, 3);\n  if (found.length) return { kind: 'help', topics: found };\n\n  if (hits(FIND, q)) return { kind: 'find', query: q };\n\n  return { kind: 'unsure', query: q };\n}\n\n/**\n * What Box says out loud before the affordances under it.\n *\n * Kept beside the router rather than in the component: the sentence and the\n * branch that produced it have to agree, and they drift the moment they live in\n * two files.\n */\n/**\n * THE ANSWER FIRST, NOT A CAPTION OVER IT.\n *\n * This returned \"Here is what I have on that.\" for every help match, and then\n * the topics were printed underneath in full — so the largest text in the\n * reply said nothing and the actual answer arrived as a heading plus two\n * paragraphs plus a numbered list, twice over when two topics matched. That is\n * a search results page wearing a conversation's clothes.\n *\n * The order every good answer surface uses — Perplexity's, Fin's — is: the\n * answer, then where it came from, then what to do about it. `replySpoken`\n * already worked this way, because a voice reading a caption aloud answers\n * nothing and the problem was impossible to miss there. It was just as true on\n * screen and easy to miss.\n *\n * The topics still render under this as sources; see `potter-thread`.\n */\nexport function replyLead(reply: PotterReply): string {\n  switch (reply.kind) {\n    case 'help': {\n      const top = reply.topics[0];\n      return top ? top.answer : 'I have nothing on that one yet.';\n    }\n    case 'find':\n      return 'I can look through your orders, invoices, customers and products for that.';\n    case 'setup':\n      return 'I can turn that into a setup plan for you to review before anything changes.';\n    /* A sheet's sentence is written by `describeSheet`, which has the row count\n       and the columns; there is nothing generic to say about a file. The turn\n       carries its own text and this is never consulted — but the switch is\n       exhaustive and a missing arm is a compile error rather than a bug. */\n    case 'sheet':\n    case 'photo':\n      return '';\n    /* The second half names the door that is actually under it. Where cases\n       exist the control says \"Start a case\", and a sentence still offering to\n       \"put it to the team\" describes a button that is no longer there. */\n    case 'unsure':\n      return isServiceOperationsEnabled()\n        ? \"I can't answer that one yet. Here is what I can do today, or you can open a case and a person will take it.\"\n        : \"I can't answer that one yet. Here is what I can do today, or you can put it to the team.\";\n  }\n}\n\n/**\n * The same reply, for a voice that has no screen.\n *\n * WHY IT IS NOT `replyLead`. On screen the lead is a caption over the thing that\n * answers — the help topic underneath it, the result list, the proposal button.\n * Read aloud with nothing under it, \"Here is what I have on that\" answers\n * nothing at all, and a voice mode whose every turn is a caption for an unread\n * screen is worse than silence: it sounds like an assistant that heard you and\n * had no reply.\n *\n * So a spoken `help` turn carries the actual answer. The other three do not\n * grow, and that is not laziness — a `find` turn's answer IS the list of\n * records, which belongs on screen and cannot be recited without turning a\n * glance into a minute; `setup` waits on a button the merchant has to press;\n * `unsure` is already the whole sentence.\n *\n * THE CEILING IS DELIBERATE. Speech runs at roughly fifteen characters a\n * second, so an unbounded answer is a merchant standing at a counter listening\n * to a paragraph they cannot skim. Past the cut the voice hands back to the\n * screen rather than reading on, which is also what stops this from drifting\n * into a text-to-speech reader for the help centre.\n */\nconst SPOKEN_ANSWER_MAX = 320;\n\nexport function replySpoken(reply: PotterReply): string {\n  if (reply.kind !== 'help') return replyLead(reply);\n  const top = reply.topics[0];\n  if (!top) return replyLead(reply);\n  if (top.answer.length <= SPOKEN_ANSWER_MAX) return top.answer;\n  // Cut on a sentence rather than mid-word, and say that there is more. A\n  // spoken answer that stops dead sounds like the connection dropped.\n  const clipped = top.answer.slice(0, SPOKEN_ANSWER_MAX);\n  const end = Math.max(clipped.lastIndexOf('. '), clipped.lastIndexOf('? '));\n  const said = end > 80 ? clipped.slice(0, end + 1) : `${clipped.trimEnd()}…`;\n  return `${said} The rest is on screen.`;\n}\n"],"mappings":"AACA,SAAS,wBAAwB;AACjC,SAAS,kCAAkC;AAyD3C,MAAM,QAAQ;AAAA,EACZ;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF;AAOA,MAAM,OAAO;AAAA,EACX;AAAA,EACA;AAAA,EACA;AACF;AAGA,MAAM,OAAO,CAAC,UAAoB,MAAc,SAAS,KAAK,CAAC,MAAM,EAAE,KAAK,CAAC,CAAC;AASvE,SAAS,cAAc,OAAe,QAAkC;AAC7E,QAAM,IAAI,MAAM,KAAK;AACrB,MAAI,CAAC,EAAG,QAAO,EAAE,MAAM,UAAU,OAAO,EAAE;AAE1C,MAAI,KAAK,OAAO,CAAC,EAAG,QAAO,EAAE,MAAM,SAAS,QAAQ,EAAE;AAKtD,QAAM,QAAQ,iBAAiB,QAAQ,CAAC,EAAE,MAAM,GAAG,CAAC;AACpD,MAAI,MAAM,OAAQ,QAAO,EAAE,MAAM,QAAQ,QAAQ,MAAM;AAEvD,MAAI,KAAK,MAAM,CAAC,EAAG,QAAO,EAAE,MAAM,QAAQ,OAAO,EAAE;AAEnD,SAAO,EAAE,MAAM,UAAU,OAAO,EAAE;AACpC;AA0BO,SAAS,UAAU,OAA4B;AACpD,UAAQ,MAAM,MAAM;AAAA,IAClB,KAAK,QAAQ;AACX,YAAM,MAAM,MAAM,OAAO,CAAC;AAC1B,aAAO,MAAM,IAAI,SAAS;AAAA,IAC5B;AAAA,IACA,KAAK;AACH,aAAO;AAAA,IACT,KAAK;AACH,aAAO;AAAA;AAAA;AAAA;AAAA;AAAA,IAKT,KAAK;AAAA,IACL,KAAK;AACH,aAAO;AAAA;AAAA;AAAA;AAAA,IAIT,KAAK;AACH,aAAO,2BAA2B,IAC9B,gHACA;AAAA,EACR;AACF;AAwBA,MAAM,oBAAoB;AAEnB,SAAS,YAAY,OAA4B;AACtD,MAAI,MAAM,SAAS,OAAQ,QAAO,UAAU,KAAK;AACjD,QAAM,MAAM,MAAM,OAAO,CAAC;AAC1B,MAAI,CAAC,IAAK,QAAO,UAAU,KAAK;AAChC,MAAI,IAAI,OAAO,UAAU,kBAAmB,QAAO,IAAI;AAGvD,QAAM,UAAU,IAAI,OAAO,MAAM,GAAG,iBAAiB;AACrD,QAAM,MAAM,KAAK,IAAI,QAAQ,YAAY,IAAI,GAAG,QAAQ,YAAY,IAAI,CAAC;AACzE,QAAM,OAAO,MAAM,KAAK,QAAQ,MAAM,GAAG,MAAM,CAAC,IAAI,GAAG,QAAQ,QAAQ,CAAC;AACxE,SAAO,GAAG,IAAI;AAChB;","names":[]}

package/dist/potter/potter-attach.d.ts

@@ -0,0 +1,107 @@
+import { type ImportField } from '@withpotter/pages-commerce/dashboard/(commerce)/catalog/_hooks/use-csv-import';
+/**
+ * What Box can honestly say about a file you hand it, with no model.
+ *
+ * WHY THIS IS NOT A CHAT ATTACHMENT. Every other assistant's paperclip puts a
+ * file in a message and waits for a model to look at it. We have no model, so
+ * that control would be the exact lie this surface refuses to tell — a
+ * capability drawn rather than built.
+ *
+ * A spreadsheet is different, and it is the one file a Nigerian merchant
+ * actually arrives with. Reading a CSV needs no intelligence: `parseCsv` splits
+ * it, `guessMapping` recognises the columns by name — the same function the
+ * catalogue's own importer uses to guess them — and the row count is arithmetic.
+ * So Box can tell you what is in the file, correctly, and hand it to the
+ * thing that puts it in your catalogue. That is a real capability with real
+ * code behind it, today.
+ *
+ * WHAT IT REFUSES TO CLAIM. An image of a supplier invoice is exactly the thing
+ * worth reading and exactly the thing that needs a model to read. The picker
+ * takes `.csv` only, so nobody is invited to photograph a receipt and then told
+ * the software cannot see it. It opens up when the answering route lands — see
+ * the ladder in the research brief.
+ */
+export interface AttachedSheet {
+    name: string;
+    /** Data rows, header excluded. */
+    rows: number;
+    /** The header row, verbatim. */
+    headers: string[];
+    /** Which catalogue fields the headers were recognised as. */
+    recognised: ImportField[];
+    /** Set when the file cannot be used, in the words the merchant needs. */
+    problem?: string;
+}
+export declare function readSheet(file: File): Promise<AttachedSheet>;
+/**
+ * What Box says back, in the merchant's own nouns.
+ *
+ * It names the columns it RECOGNISED rather than all of them, because that is
+ * the part that decides whether the import will work — a file whose price
+ * column is called "cost" imports fine, and one with no title column does not
+ * import at all. Saying so here means the merchant learns it before the
+ * importer opens rather than inside it.
+ */
+export declare function describeSheet(sheet: AttachedSheet, itemPlural: string): string;
+/**
+ * A file waiting in the composer.
+ *
+ * TWO KINDS, AND POTTER CAN ONLY READ ONE OF THEM. That asymmetry is the whole
+ * design problem here, and pretending it away is the failure: a paperclip that
+ * takes anything and a model that reads nothing is the dead control this
+ * surface keeps refusing to draw.
+ *
+ * So each kind carries what can honestly be said about it. A sheet knows its
+ * rows and its recognised columns, because parsing needs no intelligence. A
+ * photograph knows only that it is a photograph — and gets somewhere real to
+ * go anyway, because `uploadImage` puts it with the business's own pictures.
+ */
+export type PotterAttachment = {
+    kind: 'sheet';
+    file: File;
+    sheet: AttachedSheet;
+} | {
+    kind: 'image';
+    file: File;
+    /** An object URL for the thumbnail. The holder revokes it. */
+    url: string;
+    width?: number;
+    height?: number;
+};
+/** What the picker takes. Nothing here is accepted that has nowhere to go. */
+export declare const ATTACH_ACCEPT = ".csv,text/csv,image/png,image/jpeg";
+/**
+ * How many files may wait in the composer at once. John's number.
+ *
+ * A cap rather than none, because the row of thumbnails is the point: five
+ * squares read as a set you can check at a glance, and twenty read as a
+ * problem. It is also the honest ceiling on what happens next — every one of
+ * these is uploaded in sequence when the turn is answered.
+ */
+export declare const MAX_ATTACHMENTS = 5;
+/**
+ * Read whatever was chosen, far enough to describe it.
+ *
+ * Returns `null` for a type we do not take, which the picker's `accept` should
+ * already have prevented — a merchant can still drag one in, and silently doing
+ * nothing is worse than saying so.
+ */
+export declare function readAttachment(file: File): Promise<PotterAttachment | null>;
+/**
+ * What Box says when a photograph arrives.
+ *
+ * IT ADMITS THE LIMIT FIRST. There is no vision behind this and there is no
+ * pretending otherwise — but "I cannot read that" as a whole answer is a dead
+ * end, so it is followed by the one true thing it can do with a picture.
+ */
+export declare function describeImage(name: string): string;
+/**
+ * The same admission, for a handful of them.
+ *
+ * It does NOT list the filenames. They are `IMG_4821.jpg` and
+ * `_designerbabe_1718527507_3391577010625190628_15287514660.jpg`, which is the
+ * exact string John pointed at — a name that tells a merchant nothing, wrapped
+ * over two lines of an answer. The pictures are visible in the turn above; the
+ * count is the only part of this that is information.
+ */
+export declare function describeImages(count: number): string;

package/dist/potter/potter-attach.js

@@ -0,0 +1,99 @@
+import { parseCsv } from "@withpotter/lib/csv";
+import {
+  guessMapping,
+  IMPORT_FIELDS
+} from "@withpotter/pages-commerce/dashboard/(commerce)/catalog/_hooks/use-csv-import";
+const MAX_BYTES = 5 * 1024 * 1024;
+async function readSheet(file) {
+  const base = {
+    name: file.name,
+    rows: 0,
+    headers: [],
+    recognised: []
+  };
+  if (file.size > MAX_BYTES) {
+    return {
+      ...base,
+      problem: "That file is over 5MB. Split it and bring it in parts."
+    };
+  }
+  let parsed;
+  try {
+    parsed = parseCsv(await file.text());
+  } catch {
+    return { ...base, problem: "I could not read that file." };
+  }
+  if (parsed.length === 0) return { ...base, problem: "That file is empty." };
+  if (parsed.length === 1) {
+    return {
+      ...base,
+      problem: "That file has a header row and nothing under it."
+    };
+  }
+  const [headers, ...body] = parsed;
+  const mapping = guessMapping(headers);
+  const recognised = IMPORT_FIELDS.map((f) => f.key).filter(
+    (key) => mapping[key] >= 0
+  );
+  return { ...base, rows: body.length, headers, recognised };
+}
+function describeSheet(sheet, itemPlural) {
+  if (sheet.problem) return sheet.problem;
+  const names = IMPORT_FIELDS.filter((f) => sheet.recognised.includes(f.key)).map((f) => f.label.toLowerCase()).slice(0, 4);
+  if (!sheet.recognised.includes("title")) {
+    return `That is ${sheet.rows} rows, but I cannot see a name column \u2014 ${itemPlural} need one. Rename it to "Title" and bring it back.`;
+  }
+  const columns = names.length > 1 ? `${names.slice(0, -1).join(", ")} and ${names[names.length - 1]}` : names[0];
+  return `That is ${sheet.rows} rows with ${columns}. I can put them in your ${itemPlural}.`;
+}
+const ATTACH_ACCEPT = ".csv,text/csv,image/png,image/jpeg";
+const MAX_ATTACHMENTS = 5;
+const IMAGE_TYPES = ["image/png", "image/jpeg"];
+const MAX_IMAGE_BYTES = 10 * 1024 * 1024;
+async function readAttachment(file) {
+  if (IMAGE_TYPES.includes(file.type)) {
+    if (file.size > MAX_IMAGE_BYTES) {
+      return {
+        kind: "sheet",
+        file,
+        sheet: {
+          name: file.name,
+          rows: 0,
+          headers: [],
+          recognised: [],
+          problem: "That picture is over 10MB. A smaller one will go through."
+        }
+      };
+    }
+    const url = URL.createObjectURL(file);
+    const size = await new Promise(
+      (done) => {
+        const img = new Image();
+        img.onload = () => done({ width: img.width, height: img.height });
+        img.onerror = () => done(null);
+        img.src = url;
+      }
+    );
+    return { kind: "image", file, url, ...size ?? {} };
+  }
+  const isCsv = file.type === "text/csv" || file.name.toLowerCase().endsWith(".csv");
+  if (!isCsv) return null;
+  return { kind: "sheet", file, sheet: await readSheet(file) };
+}
+function describeImage(name) {
+  return `I cannot read pictures yet, so I do not know what is in ${name}. I can keep it with your photographs, though.`;
+}
+function describeImages(count) {
+  if (count === 1) return describeImage("that one");
+  return `I cannot read pictures yet, so I do not know what is in those ${count}. I can keep them with your photographs, though.`;
+}
+export {
+  ATTACH_ACCEPT,
+  MAX_ATTACHMENTS,
+  describeImage,
+  describeImages,
+  describeSheet,
+  readAttachment,
+  readSheet
+};
+//# sourceMappingURL=potter-attach.js.map

package/dist/potter/potter-attach.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/potter/potter-attach.ts"],"sourcesContent":["import { parseCsv } from '@withpotter/lib/csv';\nimport {\n  guessMapping,\n  IMPORT_FIELDS,\n  type ImportField,\n} from '@withpotter/pages-commerce/dashboard/(commerce)/catalog/_hooks/use-csv-import';\n\n/**\n * What Box can honestly say about a file you hand it, with no model.\n *\n * WHY THIS IS NOT A CHAT ATTACHMENT. Every other assistant's paperclip puts a\n * file in a message and waits for a model to look at it. We have no model, so\n * that control would be the exact lie this surface refuses to tell — a\n * capability drawn rather than built.\n *\n * A spreadsheet is different, and it is the one file a Nigerian merchant\n * actually arrives with. Reading a CSV needs no intelligence: `parseCsv` splits\n * it, `guessMapping` recognises the columns by name — the same function the\n * catalogue's own importer uses to guess them — and the row count is arithmetic.\n * So Box can tell you what is in the file, correctly, and hand it to the\n * thing that puts it in your catalogue. That is a real capability with real\n * code behind it, today.\n *\n * WHAT IT REFUSES TO CLAIM. An image of a supplier invoice is exactly the thing\n * worth reading and exactly the thing that needs a model to read. The picker\n * takes `.csv` only, so nobody is invited to photograph a receipt and then told\n * the software cannot see it. It opens up when the answering route lands — see\n * the ladder in the research brief.\n */\n\nexport interface AttachedSheet {\n  name: string;\n  /** Data rows, header excluded. */\n  rows: number;\n  /** The header row, verbatim. */\n  headers: string[];\n  /** Which catalogue fields the headers were recognised as. */\n  recognised: ImportField[];\n  /** Set when the file cannot be used, in the words the merchant needs. */\n  problem?: string;\n}\n\n/** The same 5MB ceiling the catalogue importer enforces, for the same reason. */\nconst MAX_BYTES = 5 * 1024 * 1024;\n\nexport async function readSheet(file: File): Promise<AttachedSheet> {\n  const base: AttachedSheet = {\n    name: file.name,\n    rows: 0,\n    headers: [],\n    recognised: [],\n  };\n\n  if (file.size > MAX_BYTES) {\n    return {\n      ...base,\n      problem: 'That file is over 5MB. Split it and bring it in parts.',\n    };\n  }\n\n  let parsed: string[][];\n  try {\n    parsed = parseCsv(await file.text());\n  } catch {\n    return { ...base, problem: 'I could not read that file.' };\n  }\n\n  if (parsed.length === 0) return { ...base, problem: 'That file is empty.' };\n  if (parsed.length === 1) {\n    return {\n      ...base,\n      problem: 'That file has a header row and nothing under it.',\n    };\n  }\n\n  const [headers, ...body] = parsed;\n  const mapping = guessMapping(headers);\n  const recognised = IMPORT_FIELDS.map((f) => f.key).filter(\n    (key) => mapping[key] >= 0,\n  );\n\n  return { ...base, rows: body.length, headers, recognised };\n}\n\n/**\n * What Box says back, in the merchant's own nouns.\n *\n * It names the columns it RECOGNISED rather than all of them, because that is\n * the part that decides whether the import will work — a file whose price\n * column is called \"cost\" imports fine, and one with no title column does not\n * import at all. Saying so here means the merchant learns it before the\n * importer opens rather than inside it.\n */\nexport function describeSheet(\n  sheet: AttachedSheet,\n  itemPlural: string,\n): string {\n  if (sheet.problem) return sheet.problem;\n\n  const names = IMPORT_FIELDS.filter((f) => sheet.recognised.includes(f.key))\n    .map((f) => f.label.toLowerCase())\n    .slice(0, 4);\n\n  if (!sheet.recognised.includes('title')) {\n    return `That is ${sheet.rows} rows, but I cannot see a name column — ${itemPlural} need one. Rename it to \"Title\" and bring it back.`;\n  }\n\n  const columns =\n    names.length > 1\n      ? `${names.slice(0, -1).join(', ')} and ${names[names.length - 1]}`\n      : names[0];\n\n  return `That is ${sheet.rows} rows with ${columns}. I can put them in your ${itemPlural}.`;\n}\n\n/* ---------------------------------------------------------------------------\n   Attachments, of which a spreadsheet is one kind.\n   --------------------------------------------------------------------------- */\n\n/**\n * A file waiting in the composer.\n *\n * TWO KINDS, AND POTTER CAN ONLY READ ONE OF THEM. That asymmetry is the whole\n * design problem here, and pretending it away is the failure: a paperclip that\n * takes anything and a model that reads nothing is the dead control this\n * surface keeps refusing to draw.\n *\n * So each kind carries what can honestly be said about it. A sheet knows its\n * rows and its recognised columns, because parsing needs no intelligence. A\n * photograph knows only that it is a photograph — and gets somewhere real to\n * go anyway, because `uploadImage` puts it with the business's own pictures.\n */\nexport type PotterAttachment =\n  | { kind: 'sheet'; file: File; sheet: AttachedSheet }\n  | {\n      kind: 'image';\n      file: File;\n      /** An object URL for the thumbnail. The holder revokes it. */\n      url: string;\n      width?: number;\n      height?: number;\n    };\n\n/** What the picker takes. Nothing here is accepted that has nowhere to go. */\nexport const ATTACH_ACCEPT = '.csv,text/csv,image/png,image/jpeg';\n\n/**\n * How many files may wait in the composer at once. John's number.\n *\n * A cap rather than none, because the row of thumbnails is the point: five\n * squares read as a set you can check at a glance, and twenty read as a\n * problem. It is also the honest ceiling on what happens next — every one of\n * these is uploaded in sequence when the turn is answered.\n */\nexport const MAX_ATTACHMENTS = 5;\n\nconst IMAGE_TYPES = ['image/png', 'image/jpeg'];\n/** Images go to the media library, which has its own ceiling. */\nconst MAX_IMAGE_BYTES = 10 * 1024 * 1024;\n\n/**\n * Read whatever was chosen, far enough to describe it.\n *\n * Returns `null` for a type we do not take, which the picker's `accept` should\n * already have prevented — a merchant can still drag one in, and silently doing\n * nothing is worse than saying so.\n */\nexport async function readAttachment(\n  file: File,\n): Promise<PotterAttachment | null> {\n  if (IMAGE_TYPES.includes(file.type)) {\n    if (file.size > MAX_IMAGE_BYTES) {\n      /* Surfaced as a sheet-shaped problem so one chip can show either. The\n         wording is the merchant's, not the limit's. */\n      return {\n        kind: 'sheet',\n        file,\n        sheet: {\n          name: file.name,\n          rows: 0,\n          headers: [],\n          recognised: [],\n          problem: 'That picture is over 10MB. A smaller one will go through.',\n        },\n      };\n    }\n\n    const url = URL.createObjectURL(file);\n    /* Measured so the thumbnail can crop rather than letterbox, and so a very\n       wide picture does not arrive as a sliver. Failure is not fatal: a\n       thumbnail without dimensions still renders, it just cannot be clever. */\n    const size = await new Promise<{ width: number; height: number } | null>(\n      (done) => {\n        const img = new Image();\n        img.onload = () => done({ width: img.width, height: img.height });\n        img.onerror = () => done(null);\n        img.src = url;\n      },\n    );\n\n    return { kind: 'image', file, url, ...(size ?? {}) };\n  }\n\n  const isCsv =\n    file.type === 'text/csv' || file.name.toLowerCase().endsWith('.csv');\n  if (!isCsv) return null;\n\n  return { kind: 'sheet', file, sheet: await readSheet(file) };\n}\n\n/**\n * What Box says when a photograph arrives.\n *\n * IT ADMITS THE LIMIT FIRST. There is no vision behind this and there is no\n * pretending otherwise — but \"I cannot read that\" as a whole answer is a dead\n * end, so it is followed by the one true thing it can do with a picture.\n */\nexport function describeImage(name: string): string {\n  return `I cannot read pictures yet, so I do not know what is in ${name}. I can keep it with your photographs, though.`;\n}\n\n/**\n * The same admission, for a handful of them.\n *\n * It does NOT list the filenames. They are `IMG_4821.jpg` and\n * `_designerbabe_1718527507_3391577010625190628_15287514660.jpg`, which is the\n * exact string John pointed at — a name that tells a merchant nothing, wrapped\n * over two lines of an answer. The pictures are visible in the turn above; the\n * count is the only part of this that is information.\n */\nexport function describeImages(count: number): string {\n  if (count === 1) return describeImage('that one');\n  return `I cannot read pictures yet, so I do not know what is in those ${count}. I can keep them with your photographs, though.`;\n}\n"],"mappings":"AAAA,SAAS,gBAAgB;AACzB;AAAA,EACE;AAAA,EACA;AAAA,OAEK;AAsCP,MAAM,YAAY,IAAI,OAAO;AAE7B,eAAsB,UAAU,MAAoC;AAClE,QAAM,OAAsB;AAAA,IAC1B,MAAM,KAAK;AAAA,IACX,MAAM;AAAA,IACN,SAAS,CAAC;AAAA,IACV,YAAY,CAAC;AAAA,EACf;AAEA,MAAI,KAAK,OAAO,WAAW;AACzB,WAAO;AAAA,MACL,GAAG;AAAA,MACH,SAAS;AAAA,IACX;AAAA,EACF;AAEA,MAAI;AACJ,MAAI;AACF,aAAS,SAAS,MAAM,KAAK,KAAK,CAAC;AAAA,EACrC,QAAQ;AACN,WAAO,EAAE,GAAG,MAAM,SAAS,8BAA8B;AAAA,EAC3D;AAEA,MAAI,OAAO,WAAW,EAAG,QAAO,EAAE,GAAG,MAAM,SAAS,sBAAsB;AAC1E,MAAI,OAAO,WAAW,GAAG;AACvB,WAAO;AAAA,MACL,GAAG;AAAA,MACH,SAAS;AAAA,IACX;AAAA,EACF;AAEA,QAAM,CAAC,SAAS,GAAG,IAAI,IAAI;AAC3B,QAAM,UAAU,aAAa,OAAO;AACpC,QAAM,aAAa,cAAc,IAAI,CAAC,MAAM,EAAE,GAAG,EAAE;AAAA,IACjD,CAAC,QAAQ,QAAQ,GAAG,KAAK;AAAA,EAC3B;AAEA,SAAO,EAAE,GAAG,MAAM,MAAM,KAAK,QAAQ,SAAS,WAAW;AAC3D;AAWO,SAAS,cACd,OACA,YACQ;AACR,MAAI,MAAM,QAAS,QAAO,MAAM;AAEhC,QAAM,QAAQ,cAAc,OAAO,CAAC,MAAM,MAAM,WAAW,SAAS,EAAE,GAAG,CAAC,EACvE,IAAI,CAAC,MAAM,EAAE,MAAM,YAAY,CAAC,EAChC,MAAM,GAAG,CAAC;AAEb,MAAI,CAAC,MAAM,WAAW,SAAS,OAAO,GAAG;AACvC,WAAO,WAAW,MAAM,IAAI,gDAA2C,UAAU;AAAA,EACnF;AAEA,QAAM,UACJ,MAAM,SAAS,IACX,GAAG,MAAM,MAAM,GAAG,EAAE,EAAE,KAAK,IAAI,CAAC,QAAQ,MAAM,MAAM,SAAS,CAAC,CAAC,KAC/D,MAAM,CAAC;AAEb,SAAO,WAAW,MAAM,IAAI,cAAc,OAAO,4BAA4B,UAAU;AACzF;AA+BO,MAAM,gBAAgB;AAUtB,MAAM,kBAAkB;AAE/B,MAAM,cAAc,CAAC,aAAa,YAAY;AAE9C,MAAM,kBAAkB,KAAK,OAAO;AASpC,eAAsB,eACpB,MACkC;AAClC,MAAI,YAAY,SAAS,KAAK,IAAI,GAAG;AACnC,QAAI,KAAK,OAAO,iBAAiB;AAG/B,aAAO;AAAA,QACL,MAAM;AAAA,QACN;AAAA,QACA,OAAO;AAAA,UACL,MAAM,KAAK;AAAA,UACX,MAAM;AAAA,UACN,SAAS,CAAC;AAAA,UACV,YAAY,CAAC;AAAA,UACb,SAAS;AAAA,QACX;AAAA,MACF;AAAA,IACF;AAEA,UAAM,MAAM,IAAI,gBAAgB,IAAI;AAIpC,UAAM,OAAO,MAAM,IAAI;AAAA,MACrB,CAAC,SAAS;AACR,cAAM,MAAM,IAAI,MAAM;AACtB,YAAI,SAAS,MAAM,KAAK,EAAE,OAAO,IAAI,OAAO,QAAQ,IAAI,OAAO,CAAC;AAChE,YAAI,UAAU,MAAM,KAAK,IAAI;AAC7B,YAAI,MAAM;AAAA,MACZ;AAAA,IACF;AAEA,WAAO,EAAE,MAAM,SAAS,MAAM,KAAK,GAAI,QAAQ,CAAC,EAAG;AAAA,EACrD;AAEA,QAAM,QACJ,KAAK,SAAS,cAAc,KAAK,KAAK,YAAY,EAAE,SAAS,MAAM;AACrE,MAAI,CAAC,MAAO,QAAO;AAEnB,SAAO,EAAE,MAAM,SAAS,MAAM,OAAO,MAAM,UAAU,IAAI,EAAE;AAC7D;AASO,SAAS,cAAc,MAAsB;AAClD,SAAO,2DAA2D,IAAI;AACxE;AAWO,SAAS,eAAe,OAAuB;AACpD,MAAI,UAAU,EAAG,QAAO,cAAc,UAAU;AAChD,SAAO,iEAAiE,KAAK;AAC/E;","names":[]}

package/dist/potter/potter-attachment-chip.d.ts

@@ -0,0 +1,35 @@
+import type { PotterAttachment } from './potter-attach';
+/**
+ * An attachment waiting in the composer, with something to look at.
+ *
+ * JOHN: *"there shudl be an imagery for every attachment"*. He is right, and
+ * the first version had none — a filename and a line of text, which is what a
+ * settings row looks like. A thing you picked and can still remove should look
+ * like a thing.
+ *
+ * BUT NOT THE SAME IMAGERY, because the two kinds do not have the same answer
+ * to "is this the right file".
+ *
+ *   A PHOTOGRAPH IS ITS OWN THUMBNAIL. Nothing else identifies it — the
+ *   filename is `IMG_4821.jpg` — so the picture is the only useful thing that
+ *   can go in that square, cropped rather than letterboxed so it fills it.
+ *
+ *   A SPREADSHEET HAS NO PICTURE, and the two usual substitutes are both
+ *   useless: a generic file glyph says nothing at all, and a filename says
+ *   almost nothing, because the file is called `export (3).csv`. What it HAS
+ *   is contents, and we have already parsed them. So its thumbnail is a few
+ *   real cells from the file — the same trick a file manager plays, and the
+ *   only version of "imagery" that answers the question a merchant is actually
+ *   asking before they press send.
+ *
+ * The line underneath is what decides whether it will work: for a sheet, the
+ * columns we RECOGNISED; for a picture, the plain admission that Box cannot
+ * read it. Both are said HERE, before sending, rather than after a wasted turn.
+ */
+export declare function PotterAttachmentChip({ attachment, onRemove, 
+/** Compact: inside a queued card, where there is one line to spend. */
+compact, }: {
+    attachment: PotterAttachment;
+    onRemove?: () => void;
+    compact?: boolean;
+}): import("react").JSX.Element;