@aglyn/plugins-email 1.0.0-beta.143

package/src/lib/components/emails-console-page.js

@@ -0,0 +1,229 @@
+/**
+ * @license
+ * Copyright 2026 Aglyn LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */ 'use client';
+import { _ as _extends } from "@swc/helpers/_/_extends";
+import { jsx as _jsx } from "react/jsx-runtime";
+import { consentGroupForHost } from "@aglyn/aglyn";
+import { useConsoleWidgetSlot } from "@aglyn/aglyn/app-utils/console-widget-slot-context";
+import { HubSections } from "@aglyn/shared-ui-next";
+import { useMemo } from "react";
+import EmailScreensCard from "./email-screens-card.js";
+import EmailTemplateDetail from "./email-template-detail.js";
+import EmailTopicDetail from "./email-topic-detail.js";
+import EmailTopicsCard from "./email-topics-card.js";
+import ListDetailCard from "./list-detail-card.js";
+import ListEditCard from "./list-edit-card.js";
+import ListsCard from "./lists-card.js";
+import SendingDomainDetail from "./sending-domain-detail.js";
+import SendingDomainsCard from "./sending-domains-card.js";
+import SuppressionsCard from "./suppressions-card.js";
+import { EMAIL_MESSAGES_ZONE } from "./email-zones.js";
+/**
+ * The Messages section: a zone, drawn by whichever plugin owns campaigns.
+ *
+ * Its own component because a zone's renderer comes from a hook and
+ * `sectionBody` is a plain function — and so that, like every other branch
+ * there, it is constructed only while Messages is the section being read.
+ */ function EmailMessagesSection(props) {
+    const Zone = useConsoleWidgetSlot();
+    return Zone ? /*#__PURE__*/ _jsx(Zone, _extends({
+        slot: EMAIL_MESSAGES_ZONE.id
+    }, props)) : null;
+}
+/**
+ * The body of one emails section, built only when that section is the one
+ * being read (AGL-2501).
+ *
+ * A function rather than a map of nodes on purpose: a `Record<id, ReactNode>`
+ * would CONSTRUCT every section on every render, and each card opens its
+ * Firestore listens on mount — which is the entire cost this page exists to
+ * stop paying. Only the returned branch is ever built.
+ */ function sectionBody(section, hostId, /**
+   * The section's OWN segments — `segments[1]` onward, already sliced by the
+   * caller. A section that owns deeper routes reads them here; one that does
+   * not simply ignores them.
+   */ detail, basePath, /**
+   * The controller the surface is being viewed as, resolved once by the page.
+   *
+   * Only the audience detail needs it today — it is what its membership table
+   * reads consent FOR — but it is resolved at the page because the answer is a
+   * property of the org and this is the one place holding the org document.
+   */ consentGroup) {
+    switch(section){
+        case 'messages':
+            /*
+       * `/emails/messages/{emailId}` is ONE MESSAGE — the thing that was or
+       * will be sent, as against the campaign that groups messages and the
+       * template they are built from. A ROUTE rather than an expanded row: it
+       * is linkable, which is what a merchant wants to paste into a message
+       * about last week's send, and its preview, link table and recipient
+       * list are reads the list above it must not pay for.
+       *
+       * The page links OUT to the campaign this message belongs to, which is
+       * a section of the Marketing console.
+       */ /*
+       * `…/{emailId}/edit` WRITES the email and `…/{emailId}` reports on
+       * it — two jobs with two shapes, and creating stays a drawer on the
+       * list. Which of the three is drawn is decided from `detail` by the
+       * widget, which builds only the one it is asked for: the composer's
+       * listens are not paid for by somebody reading a report.
+       */ return /*#__PURE__*/ _jsx(EmailMessagesSection, {
+                hostId: hostId,
+                basePath: basePath,
+                detail: detail
+            });
+        case 'templates':
+            /*
+       * `/emails/templates/{screenId}` is one TEMPLATE's page.
+       *
+       * A route for the same reasons a message's page is one: it is
+       * linkable, and the listing above it is a cheaper surface a reader who
+       * came for one template should not have to mount. The preview, the
+       * aggregate figures and the recipients table all hang off this branch,
+       * so none of them is constructed while the list is what is being read.
+       */ return detail[0] ? /*#__PURE__*/ _jsx(EmailTemplateDetail, {
+                hostId: hostId,
+                screenId: detail[0],
+                basePath: basePath
+            }) : /*#__PURE__*/ _jsx(EmailScreensCard, {
+                hostId: hostId,
+                basePath: basePath
+            });
+        case 'audiences':
+            /*
+       * A list is a resource with its own pages, on the same terms a message
+       * is: `/emails/audiences/{listId}` is one audience, and `…/edit` is its
+       * settings.
+       *
+       * The membership used to unfold inside the audiences table. That made a
+       * list unlinkable, put the back button one press from leaving the whole
+       * surface, and asked the reader of a list of lists to hold the table
+       * that lists them AND the table of one list's subscribers on the same
+       * screen. The subscribers are also the expensive read here — one PII
+       * document per person — so putting them behind a route is what stops
+       * them being paid for by somebody who came to see which audiences exist.
+       *
+       * Ternaries rather than a lookup: only the branch taken is CONSTRUCTED,
+       * which is the cost this whole function is shaped around.
+       */ return detail[0] ? detail[1] === 'edit' ? /*#__PURE__*/ _jsx(ListEditCard, {
+                hostId: hostId,
+                listId: detail[0],
+                basePath: basePath
+            }) : /*#__PURE__*/ _jsx(ListDetailCard, {
+                hostId: hostId,
+                consentGroup: consentGroup,
+                listId: detail[0],
+                basePath: basePath
+            }) : /*#__PURE__*/ _jsx(ListsCard, {
+                hostId: hostId,
+                basePath: basePath
+            });
+        case 'topics':
+            // Create is a drawer on the list; EDIT is the topic's own route, which
+            // is the section owning its own subtree exactly as `messages` does.
+            return detail[0] ? /*#__PURE__*/ _jsx(EmailTopicDetail, {
+                hostId: hostId,
+                topicId: detail[0],
+                basePath: basePath
+            }) : /*#__PURE__*/ _jsx(EmailTopicsCard, {
+                hostId: hostId,
+                basePath: basePath
+            });
+        case 'sending':
+            /*
+       * `/emails/sending/{domain}` is one domain's page, and it is a route
+       * for the reason every other detail here is: the DNS records, the DMARC
+       * read and the verification button are what somebody came for, and a
+       * link to them is what they paste to whoever actually edits the zone.
+       *
+       * The domain is the document id, so it is also the segment. It is
+       * decoded because a URL carries it encoded and the record is keyed on
+       * the bare name.
+       */ return detail[0] ? /*#__PURE__*/ _jsx(SendingDomainDetail, {
+                hostId: hostId,
+                domain: decodeURIComponent(detail[0]),
+                basePath: basePath
+            }) : /*#__PURE__*/ _jsx(SendingDomainsCard, {
+                hostId: hostId,
+                basePath: basePath
+            });
+        case 'suppressions':
+            return /*#__PURE__*/ _jsx(SuppressionsCard, {
+                hostId: hostId
+            });
+        default:
+            return null;
+    }
+}
+/**
+ * Emails page (AGL-395): the console surface owned by the email plugin,
+ * rendered by the shell's generic plugin route.
+ *
+ * Two of its sections are two different things a merchant calls "an email":
+ * an EMAIL is one message that was or will be sent, and a TEMPLATE is the
+ * reusable besigner document a message is built from. Keeping them apart is
+ * what lets each carry its own report — a message's own numbers, and a
+ * template's summed across every message sent from it. Audience lists, the
+ * topic catalog, the sending identities and the suppression list complete the
+ * surface.
+ *
+ * The CAMPAIGN that groups messages is not here. It is a container with a
+ * window of dates, a set of lists, a topic and revenue attribution — a
+ * marketing object that reaches people by email — so it is a section of the
+ * Marketing console, and a message's page links out to the campaign it
+ * belongs to.
+ *
+ * Sections are ROUTES (AGL-2501). `HubTabs lazy` already mounted one panel, so
+ * this is not a read saving — `emails-console-read-cost.spec.tsx` was written
+ * BEFORE the conversion precisely to hold that line, and reports the same
+ * counts after. What routing adds is that the URL names the section: it is
+ * linkable, the back button walks sections, the breadcrumb says where you are,
+ * and "mount only what is open" is structural rather than a `lazy` flag
+ * somebody has to remember on the next surface.
+ */ export function EmailsConsolePage(props) {
+    const { hostId, org, section, sections, basePath, segments } = props;
+    /*==========================================
+   * THE CONTROLLER THIS SURFACE IS BEING VIEWED AS.
+   *
+   * The declared group of sites that are one sender, or this site alone. Every
+   * consent question asked below is asked FOR a controller and not for a site:
+   * a grant is looked up under the asking site, a refusal is honored across
+   * the whole group, and a grant held by a site outside it belongs to somebody
+   * else. It is the same group `performCampaignSend` resolves, so the audience
+   * table and the send agree about the same document by construction.
+   *
+   * Pure, from the org document the shell already passed, so it costs no read.
+   * An absent org resolves to the group of one, which is the narrow answer.
+   *=========================================*/ const consentGroup = useMemo(()=>consentGroupForHost(org, hostId), [
+        org,
+        hostId
+    ]);
+    /*
+   * Nothing, deliberately, while the redirect is in flight. Rendering the
+   * default section here would issue its listens on a URL about to be
+   * replaced — on every arrival at `/emails`, which is every nav-tab click.
+   */ if (!section || !(sections == null ? void 0 : sections.length) || !basePath) return null;
+    return /*#__PURE__*/ _jsx(HubSections, {
+        sections: sections,
+        children: sectionBody(section, hostId, (// `segments[0]` IS the section — the shell resolved it into `section`
+        // already — so what a section owns is everything after it.
+        segments != null ? segments : []).slice(1), basePath, consentGroup)
+    });
+}
+EmailsConsolePage.displayName = 'EmailsConsolePage';
+export default EmailsConsolePage;
+
+//# sourceMappingURL=emails-console-page.js.map

package/src/lib/components/emails-console-page.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../../libs/plugins/email/src/lib/components/emails-console-page.tsx"],"sourcesContent":["/**\n * @license\n * Copyright 2026 Aglyn LLC\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * you may not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n *   http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing, software\n * distributed under the License is distributed on an \"AS IS\" BASIS,\n * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n * See the License for the specific language governing permissions and\n * limitations under the License.\n */\n'use client'\n\nimport {\n  consentGroupForHost,\n  type ConsentGroup,\n  type ConsolePluginPageProps,\n} from '@aglyn/aglyn'\nimport { useConsoleWidgetSlot } from '@aglyn/aglyn/app-utils/console-widget-slot-context'\nimport { HubSections } from '@aglyn/shared-ui-next'\nimport { useMemo, type ReactNode } from 'react'\nimport EmailScreensCard from './email-screens-card'\nimport EmailTemplateDetail from './email-template-detail'\nimport EmailTopicDetail from './email-topic-detail'\nimport EmailTopicsCard from './email-topics-card'\nimport ListDetailCard from './list-detail-card'\nimport ListEditCard from './list-edit-card'\nimport ListsCard from './lists-card'\nimport SendingDomainDetail from './sending-domain-detail'\nimport SendingDomainsCard from './sending-domains-card'\nimport SuppressionsCard from './suppressions-card'\nimport type { EmailsConsoleSectionId } from './emails-console-sections'\nimport { EMAIL_MESSAGES_ZONE, type EmailMessagesZoneProps } from './email-zones'\n\n/**\n * The Messages section: a zone, drawn by whichever plugin owns campaigns.\n *\n * Its own component because a zone's renderer comes from a hook and\n * `sectionBody` is a plain function — and so that, like every other branch\n * there, it is constructed only while Messages is the section being read.\n */\nfunction EmailMessagesSection(props: EmailMessagesZoneProps) {\n  const Zone = useConsoleWidgetSlot()\n  return Zone ? <Zone slot={EMAIL_MESSAGES_ZONE.id} {...props} /> : null\n}\n\n/**\n * The body of one emails section, built only when that section is the one\n * being read (AGL-2501).\n *\n * A function rather than a map of nodes on purpose: a `Record<id, ReactNode>`\n * would CONSTRUCT every section on every render, and each card opens its\n * Firestore listens on mount — which is the entire cost this page exists to\n * stop paying. Only the returned branch is ever built.\n */\nfunction sectionBody(\n  section: EmailsConsoleSectionId,\n  hostId: string,\n  /**\n   * The section's OWN segments — `segments[1]` onward, already sliced by the\n   * caller. A section that owns deeper routes reads them here; one that does\n   * not simply ignores them.\n   */\n  detail: readonly string[],\n  basePath: string,\n  /**\n   * The controller the surface is being viewed as, resolved once by the page.\n   *\n   * Only the audience detail needs it today — it is what its membership table\n   * reads consent FOR — but it is resolved at the page because the answer is a\n   * property of the org and this is the one place holding the org document.\n   */\n  consentGroup: ConsentGroup,\n): ReactNode {\n  switch (section) {\n    case 'messages':\n      /*\n       * `/emails/messages/{emailId}` is ONE MESSAGE — the thing that was or\n       * will be sent, as against the campaign that groups messages and the\n       * template they are built from. A ROUTE rather than an expanded row: it\n       * is linkable, which is what a merchant wants to paste into a message\n       * about last week's send, and its preview, link table and recipient\n       * list are reads the list above it must not pay for.\n       *\n       * The page links OUT to the campaign this message belongs to, which is\n       * a section of the Marketing console.\n       */\n      /*\n       * `…/{emailId}/edit` WRITES the email and `…/{emailId}` reports on\n       * it — two jobs with two shapes, and creating stays a drawer on the\n       * list. Which of the three is drawn is decided from `detail` by the\n       * widget, which builds only the one it is asked for: the composer's\n       * listens are not paid for by somebody reading a report.\n       */\n      return (\n        <EmailMessagesSection\n          hostId={hostId}\n          basePath={basePath}\n          detail={detail}\n        />\n      )\n    case 'templates':\n      /*\n       * `/emails/templates/{screenId}` is one TEMPLATE's page.\n       *\n       * A route for the same reasons a message's page is one: it is\n       * linkable, and the listing above it is a cheaper surface a reader who\n       * came for one template should not have to mount. The preview, the\n       * aggregate figures and the recipients table all hang off this branch,\n       * so none of them is constructed while the list is what is being read.\n       */\n      return detail[0] ? (\n        <EmailTemplateDetail\n          hostId={hostId}\n          screenId={detail[0]}\n          basePath={basePath}\n        />\n      ) : (\n        <EmailScreensCard hostId={hostId} basePath={basePath} />\n      )\n    case 'audiences':\n      /*\n       * A list is a resource with its own pages, on the same terms a message\n       * is: `/emails/audiences/{listId}` is one audience, and `…/edit` is its\n       * settings.\n       *\n       * The membership used to unfold inside the audiences table. That made a\n       * list unlinkable, put the back button one press from leaving the whole\n       * surface, and asked the reader of a list of lists to hold the table\n       * that lists them AND the table of one list's subscribers on the same\n       * screen. The subscribers are also the expensive read here — one PII\n       * document per person — so putting them behind a route is what stops\n       * them being paid for by somebody who came to see which audiences exist.\n       *\n       * Ternaries rather than a lookup: only the branch taken is CONSTRUCTED,\n       * which is the cost this whole function is shaped around.\n       */\n      return detail[0] ? (\n        detail[1] === 'edit' ? (\n          <ListEditCard\n            hostId={hostId}\n            listId={detail[0]}\n            basePath={basePath}\n          />\n        ) : (\n          <ListDetailCard\n            hostId={hostId}\n            consentGroup={consentGroup}\n            listId={detail[0]}\n            basePath={basePath}\n          />\n        )\n      ) : (\n        <ListsCard hostId={hostId} basePath={basePath} />\n      )\n    case 'topics':\n      // Create is a drawer on the list; EDIT is the topic's own route, which\n      // is the section owning its own subtree exactly as `messages` does.\n      return detail[0] ? (\n        <EmailTopicDetail\n          hostId={hostId}\n          topicId={detail[0]}\n          basePath={basePath}\n        />\n      ) : (\n        <EmailTopicsCard hostId={hostId} basePath={basePath} />\n      )\n    case 'sending':\n      /*\n       * `/emails/sending/{domain}` is one domain's page, and it is a route\n       * for the reason every other detail here is: the DNS records, the DMARC\n       * read and the verification button are what somebody came for, and a\n       * link to them is what they paste to whoever actually edits the zone.\n       *\n       * The domain is the document id, so it is also the segment. It is\n       * decoded because a URL carries it encoded and the record is keyed on\n       * the bare name.\n       */\n      return detail[0] ? (\n        <SendingDomainDetail\n          hostId={hostId}\n          domain={decodeURIComponent(detail[0])}\n          basePath={basePath}\n        />\n      ) : (\n        <SendingDomainsCard hostId={hostId} basePath={basePath} />\n      )\n    case 'suppressions':\n      return <SuppressionsCard hostId={hostId} />\n    default:\n      return null\n  }\n}\n\n/**\n * Emails page (AGL-395): the console surface owned by the email plugin,\n * rendered by the shell's generic plugin route.\n *\n * Two of its sections are two different things a merchant calls \"an email\":\n * an EMAIL is one message that was or will be sent, and a TEMPLATE is the\n * reusable besigner document a message is built from. Keeping them apart is\n * what lets each carry its own report — a message's own numbers, and a\n * template's summed across every message sent from it. Audience lists, the\n * topic catalog, the sending identities and the suppression list complete the\n * surface.\n *\n * The CAMPAIGN that groups messages is not here. It is a container with a\n * window of dates, a set of lists, a topic and revenue attribution — a\n * marketing object that reaches people by email — so it is a section of the\n * Marketing console, and a message's page links out to the campaign it\n * belongs to.\n *\n * Sections are ROUTES (AGL-2501). `HubTabs lazy` already mounted one panel, so\n * this is not a read saving — `emails-console-read-cost.spec.tsx` was written\n * BEFORE the conversion precisely to hold that line, and reports the same\n * counts after. What routing adds is that the URL names the section: it is\n * linkable, the back button walks sections, the breadcrumb says where you are,\n * and \"mount only what is open\" is structural rather than a `lazy` flag\n * somebody has to remember on the next surface.\n */\nexport function EmailsConsolePage(props: ConsolePluginPageProps) {\n  const { hostId, org, section, sections, basePath, segments } = props\n\n  /*==========================================\n   * THE CONTROLLER THIS SURFACE IS BEING VIEWED AS.\n   *\n   * The declared group of sites that are one sender, or this site alone. Every\n   * consent question asked below is asked FOR a controller and not for a site:\n   * a grant is looked up under the asking site, a refusal is honored across\n   * the whole group, and a grant held by a site outside it belongs to somebody\n   * else. It is the same group `performCampaignSend` resolves, so the audience\n   * table and the send agree about the same document by construction.\n   *\n   * Pure, from the org document the shell already passed, so it costs no read.\n   * An absent org resolves to the group of one, which is the narrow answer.\n   *=========================================*/\n  const consentGroup = useMemo(\n    () => consentGroupForHost(org as Record<string, unknown>, hostId),\n    [org, hostId],\n  )\n\n  /*\n   * Nothing, deliberately, while the redirect is in flight. Rendering the\n   * default section here would issue its listens on a URL about to be\n   * replaced — on every arrival at `/emails`, which is every nav-tab click.\n   */\n  if (!section || !sections?.length || !basePath) return null\n\n  return (\n    <HubSections sections={sections}>\n      {sectionBody(\n        section as EmailsConsoleSectionId,\n        hostId,\n        // `segments[0]` IS the section — the shell resolved it into `section`\n        // already — so what a section owns is everything after it.\n        (segments ?? []).slice(1),\n        basePath,\n        consentGroup,\n      )}\n    </HubSections>\n  )\n}\nEmailsConsolePage.displayName = 'EmailsConsolePage'\n\nexport default EmailsConsolePage\n"],"names":["consentGroupForHost","useConsoleWidgetSlot","HubSections","useMemo","EmailScreensCard","EmailTemplateDetail","EmailTopicDetail","EmailTopicsCard","ListDetailCard","ListEditCard","ListsCard","SendingDomainDetail","SendingDomainsCard","SuppressionsCard","EMAIL_MESSAGES_ZONE","EmailMessagesSection","props","Zone","slot","id","sectionBody","section","hostId","detail","basePath","consentGroup","screenId","listId","topicId","domain","decodeURIComponent","EmailsConsolePage","org","sections","segments","length","slice","displayName"],"mappings":"AAAA;;;;;;;;;;;;;;;CAeC,GACD;;;AAEA,SACEA,mBAAmB,QAGd,eAAc;AACrB,SAASC,oBAAoB,QAAQ,qDAAoD;AACzF,SAASC,WAAW,QAAQ,wBAAuB;AACnD,SAASC,OAAO,QAAwB,QAAO;AAC/C,OAAOC,sBAAsB,0BAAsB;AACnD,OAAOC,yBAAyB,6BAAyB;AACzD,OAAOC,sBAAsB,0BAAsB;AACnD,OAAOC,qBAAqB,yBAAqB;AACjD,OAAOC,oBAAoB,wBAAoB;AAC/C,OAAOC,kBAAkB,sBAAkB;AAC3C,OAAOC,eAAe,kBAAc;AACpC,OAAOC,yBAAyB,6BAAyB;AACzD,OAAOC,wBAAwB,4BAAwB;AACvD,OAAOC,sBAAsB,yBAAqB;AAElD,SAASC,mBAAmB,QAAqC,mBAAe;AAEhF;;;;;;CAMC,GACD,SAASC,qBAAqBC,KAA6B;IACzD,MAAMC,OAAOhB;IACb,OAAOgB,qBAAO,KAACA;QAAKC,MAAMJ,oBAAoBK,EAAE;OAAMH,UAAY;AACpE;AAEA;;;;;;;;CAQC,GACD,SAASI,YACPC,OAA+B,EAC/BC,MAAc,EACd;;;;GAIC,GACDC,MAAyB,EACzBC,QAAgB,EAChB;;;;;;GAMC,GACDC,YAA0B;IAE1B,OAAQJ;QACN,KAAK;YACH;;;;;;;;;;OAUC,GACD;;;;;;OAMC,GACD,qBACE,KAACN;gBACCO,QAAQA;gBACRE,UAAUA;gBACVD,QAAQA;;QAGd,KAAK;YACH;;;;;;;;OAQC,GACD,OAAOA,MAAM,CAAC,EAAE,iBACd,KAAClB;gBACCiB,QAAQA;gBACRI,UAAUH,MAAM,CAAC,EAAE;gBACnBC,UAAUA;+BAGZ,KAACpB;gBAAiBkB,QAAQA;gBAAQE,UAAUA;;QAEhD,KAAK;YACH;;;;;;;;;;;;;;;OAeC,GACD,OAAOD,MAAM,CAAC,EAAE,GACdA,MAAM,CAAC,EAAE,KAAK,uBACZ,KAACd;gBACCa,QAAQA;gBACRK,QAAQJ,MAAM,CAAC,EAAE;gBACjBC,UAAUA;+BAGZ,KAAChB;gBACCc,QAAQA;gBACRG,cAAcA;gBACdE,QAAQJ,MAAM,CAAC,EAAE;gBACjBC,UAAUA;+BAId,KAACd;gBAAUY,QAAQA;gBAAQE,UAAUA;;QAEzC,KAAK;YACH,uEAAuE;YACvE,oEAAoE;YACpE,OAAOD,MAAM,CAAC,EAAE,iBACd,KAACjB;gBACCgB,QAAQA;gBACRM,SAASL,MAAM,CAAC,EAAE;gBAClBC,UAAUA;+BAGZ,KAACjB;gBAAgBe,QAAQA;gBAAQE,UAAUA;;QAE/C,KAAK;YACH;;;;;;;;;OASC,GACD,OAAOD,MAAM,CAAC,EAAE,iBACd,KAACZ;gBACCW,QAAQA;gBACRO,QAAQC,mBAAmBP,MAAM,CAAC,EAAE;gBACpCC,UAAUA;+BAGZ,KAACZ;gBAAmBU,QAAQA;gBAAQE,UAAUA;;QAElD,KAAK;YACH,qBAAO,KAACX;gBAAiBS,QAAQA;;QACnC;YACE,OAAO;IACX;AACF;AAEA;;;;;;;;;;;;;;;;;;;;;;;;;CAyBC,GACD,OAAO,SAASS,kBAAkBf,KAA6B;IAC7D,MAAM,EAAEM,MAAM,EAAEU,GAAG,EAAEX,OAAO,EAAEY,QAAQ,EAAET,QAAQ,EAAEU,QAAQ,EAAE,GAAGlB;IAE/D;;;;;;;;;;;;6CAY2C,GAC3C,MAAMS,eAAetB,QACnB,IAAMH,oBAAoBgC,KAAgCV,SAC1D;QAACU;QAAKV;KAAO;IAGf;;;;GAIC,GACD,IAAI,CAACD,WAAW,EAACY,4BAAAA,SAAUE,MAAM,KAAI,CAACX,UAAU,OAAO;IAEvD,qBACE,KAACtB;QAAY+B,UAAUA;kBACpBb,YACCC,SACAC,QAGA,CAFA,sEAAsE;QACtE,2DAA2D;QAC1DY,mBAAAA,WAAY,EAAE,EAAEE,KAAK,CAAC,IACvBZ,UACAC;;AAIR;AACAM,kBAAkBM,WAAW,GAAG;AAEhC,eAAeN,kBAAiB"}

package/src/lib/components/emails-console-sections.d.ts

@@ -0,0 +1,36 @@
+/**
+ * @license
+ * Copyright 2026 Aglyn LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+import type { ConsoleNavSection } from '@aglyn/aglyn';
+export type EmailsConsoleSectionId = 'messages' | 'templates' | 'audiences' | 'topics' | 'sending' | 'suppressions';
+/**
+ * The emails console's sections, in rail order (AGL-2501).
+ *
+ * One list, read twice and never copied: `plugin.ts` registers it on the nav
+ * item so the shell can route and gate each section, and the page switches its
+ * body on the id the shell resolves back.
+ *
+ * Ids appear in links people keep — treat them as persisted, and prefer
+ * renaming a LABEL over an id. Where the two have to move together, the old
+ * path is kept alive by a redirect rather than by an id that no longer says
+ * what the section is. `audiences` and `suppressions` are also the `?tab=`
+ * ids this page deep-linked by before its sections became routes, so a
+ * bookmark that named one of those tabs still names the same section.
+ *
+ * No `navTabId` on any of them: every section ships with the surface, so they
+ * inherit the Emails nav item's gate.
+ */
+export declare const EMAILS_CONSOLE_SECTIONS: readonly ConsoleNavSection[];

package/src/lib/components/emails-console-sections.js

@@ -0,0 +1,108 @@
+/**
+ * @license
+ * Copyright 2026 Aglyn LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */ /**
+ * The emails console's sections, in rail order (AGL-2501).
+ *
+ * One list, read twice and never copied: `plugin.ts` registers it on the nav
+ * item so the shell can route and gate each section, and the page switches its
+ * body on the id the shell resolves back.
+ *
+ * Ids appear in links people keep — treat them as persisted, and prefer
+ * renaming a LABEL over an id. Where the two have to move together, the old
+ * path is kept alive by a redirect rather than by an id that no longer says
+ * what the section is. `audiences` and `suppressions` are also the `?tab=`
+ * ids this page deep-linked by before its sections became routes, so a
+ * bookmark that named one of those tabs still names the same section.
+ *
+ * No `navTabId` on any of them: every section ships with the surface, so they
+ * inherit the Emails nav item's gate.
+ */ export const EMAILS_CONSOLE_SECTIONS = [
+    /*
+   * The individual messages: one row per email that was or will be sent, each
+   * with its own report.
+   *
+   * A message is what this surface is about, and this section is named for
+   * the record rather than for the surface holding it. The shell prints the
+   * surface and the section together — in the header, in the breadcrumb and
+   * in the browser tab — so a section whose name repeats its surface's says
+   * nothing about which of the six is open, which is the one job a section
+   * name has. `messages` is also the word the rest of this surface already
+   * uses for the record: a message's own page, a template's sends table and
+   * the campaign detail all call it that.
+   *
+   * `/emails/emails/{id}` is answered by a permanent redirect in the console's
+   * `next.config.js`, on the terms the Workflows → Automation move set: a URL
+   * somebody pasted keeps resolving, and it resolves to the one address the
+   * console generates.
+   *
+   * The CAMPAIGN that groups messages is a marketing object — a window of
+   * dates, a set of lists, a topic and revenue attribution, which happens to
+   * reach people by email — so it is a section of the Marketing console and a
+   * message's page links out to it.
+   */ {
+        id: 'messages',
+        label: 'Messages'
+    },
+    /*
+   * The reusable besigner documents a message is built from.
+   *
+   * Id and label say the same word on purpose: a template is the vocabulary
+   * everywhere else in this surface — an email names the template it renders,
+   * and the marketplace publishes them — so a URL saying anything else would
+   * be the one place the reader has to translate.
+   */ {
+        id: 'templates',
+        label: 'Templates'
+    },
+    {
+        id: 'audiences',
+        label: 'Audiences'
+    },
+    // Between the audiences and the suppressions, which is where a topic sits
+    // conceptually: an audience is who you may reach, a suppression is who you
+    // may not, and a topic is the stream a recipient can leave without becoming
+    // either.
+    {
+        id: 'topics',
+        label: 'Topics'
+    },
+    /*
+   * WHO THE MAIL COMES FROM, as against who it goes to.
+   *
+   * After the three audience sections and before Suppressions, which is where
+   * the question sits: everything above decides who is reached, and this one
+   * decides what they see in the `From:` line. It is also the section a
+   * merchant is sent to from the composer when a send is refused for an
+   * unverified identity, so it has to be a route of its own.
+   */ {
+        id: 'sending',
+        label: 'Sending'
+    },
+    // Beside the audiences rather than inside them (AGL-2410): a suppression is
+    // not a list you build, it is the reason a list you built did not all get
+    // mailed.
+    {
+        id: 'suppressions',
+        label: 'Suppressions'
+    }
+] /*
+ * Rail ORDER decides where `/emails` lands: the shell redirects a bare hub
+ * URL to the first section in this list the reader may open (AGL-2501). There
+ * is deliberately no separate default constant — a second place to say which
+ * section is first is a second place for it to disagree with the rail.
+ */ ;
+
+//# sourceMappingURL=emails-console-sections.js.map

package/src/lib/components/emails-console-sections.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../../../../../libs/plugins/email/src/lib/components/emails-console-sections.ts"],"sourcesContent":["/**\n * @license\n * Copyright 2026 Aglyn LLC\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * you may not use this file except in compliance with the License.\n * You may obtain a copy of the License at\n *\n *   http://www.apache.org/licenses/LICENSE-2.0\n *\n * Unless required by applicable law or agreed to in writing, software\n * distributed under the License is distributed on an \"AS IS\" BASIS,\n * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n * See the License for the specific language governing permissions and\n * limitations under the License.\n */\n\nimport type { ConsoleNavSection } from '@aglyn/aglyn'\n\nexport type EmailsConsoleSectionId =\n  | 'messages'\n  | 'templates'\n  | 'audiences'\n  | 'topics'\n  | 'sending'\n  | 'suppressions'\n\n/**\n * The emails console's sections, in rail order (AGL-2501).\n *\n * One list, read twice and never copied: `plugin.ts` registers it on the nav\n * item so the shell can route and gate each section, and the page switches its\n * body on the id the shell resolves back.\n *\n * Ids appear in links people keep — treat them as persisted, and prefer\n * renaming a LABEL over an id. Where the two have to move together, the old\n * path is kept alive by a redirect rather than by an id that no longer says\n * what the section is. `audiences` and `suppressions` are also the `?tab=`\n * ids this page deep-linked by before its sections became routes, so a\n * bookmark that named one of those tabs still names the same section.\n *\n * No `navTabId` on any of them: every section ships with the surface, so they\n * inherit the Emails nav item's gate.\n */\nexport const EMAILS_CONSOLE_SECTIONS: readonly ConsoleNavSection[] = [\n  /*\n   * The individual messages: one row per email that was or will be sent, each\n   * with its own report.\n   *\n   * A message is what this surface is about, and this section is named for\n   * the record rather than for the surface holding it. The shell prints the\n   * surface and the section together — in the header, in the breadcrumb and\n   * in the browser tab — so a section whose name repeats its surface's says\n   * nothing about which of the six is open, which is the one job a section\n   * name has. `messages` is also the word the rest of this surface already\n   * uses for the record: a message's own page, a template's sends table and\n   * the campaign detail all call it that.\n   *\n   * `/emails/emails/{id}` is answered by a permanent redirect in the console's\n   * `next.config.js`, on the terms the Workflows → Automation move set: a URL\n   * somebody pasted keeps resolving, and it resolves to the one address the\n   * console generates.\n   *\n   * The CAMPAIGN that groups messages is a marketing object — a window of\n   * dates, a set of lists, a topic and revenue attribution, which happens to\n   * reach people by email — so it is a section of the Marketing console and a\n   * message's page links out to it.\n   */\n  { id: 'messages', label: 'Messages' },\n  /*\n   * The reusable besigner documents a message is built from.\n   *\n   * Id and label say the same word on purpose: a template is the vocabulary\n   * everywhere else in this surface — an email names the template it renders,\n   * and the marketplace publishes them — so a URL saying anything else would\n   * be the one place the reader has to translate.\n   */\n  { id: 'templates', label: 'Templates' },\n  { id: 'audiences', label: 'Audiences' },\n  // Between the audiences and the suppressions, which is where a topic sits\n  // conceptually: an audience is who you may reach, a suppression is who you\n  // may not, and a topic is the stream a recipient can leave without becoming\n  // either.\n  { id: 'topics', label: 'Topics' },\n  /*\n   * WHO THE MAIL COMES FROM, as against who it goes to.\n   *\n   * After the three audience sections and before Suppressions, which is where\n   * the question sits: everything above decides who is reached, and this one\n   * decides what they see in the `From:` line. It is also the section a\n   * merchant is sent to from the composer when a send is refused for an\n   * unverified identity, so it has to be a route of its own.\n   */\n  { id: 'sending', label: 'Sending' },\n  // Beside the audiences rather than inside them (AGL-2410): a suppression is\n  // not a list you build, it is the reason a list you built did not all get\n  // mailed.\n  { id: 'suppressions', label: 'Suppressions' },\n]\n\n/*\n * Rail ORDER decides where `/emails` lands: the shell redirects a bare hub\n * URL to the first section in this list the reader may open (AGL-2501). There\n * is deliberately no separate default constant — a second place to say which\n * section is first is a second place for it to disagree with the rail.\n */\n"],"names":["EMAILS_CONSOLE_SECTIONS","id","label"],"mappings":"AAAA;;;;;;;;;;;;;;;CAeC,GAYD;;;;;;;;;;;;;;;;CAgBC,GACD,OAAO,MAAMA,0BAAwD;IACnE;;;;;;;;;;;;;;;;;;;;;;GAsBC,GACD;QAAEC,IAAI;QAAYC,OAAO;IAAW;IACpC;;;;;;;GAOC,GACD;QAAED,IAAI;QAAaC,OAAO;IAAY;IACtC;QAAED,IAAI;QAAaC,OAAO;IAAY;IACtC,0EAA0E;IAC1E,2EAA2E;IAC3E,4EAA4E;IAC5E,UAAU;IACV;QAAED,IAAI;QAAUC,OAAO;IAAS;IAChC;;;;;;;;GAQC,GACD;QAAED,IAAI;QAAWC,OAAO;IAAU;IAClC,4EAA4E;IAC5E,0EAA0E;IAC1E,UAAU;IACV;QAAED,IAAI;QAAgBC,OAAO;IAAe;CAC7C,CAED;;;;;CAKC,IAPA"}

package/src/lib/components/list-detail-card.d.ts

@@ -0,0 +1,47 @@
+/**
+ * ONE AUDIENCE: who it is, how it is built, and every person on it.
+ *
+ * ## Why a route rather than an expanded row
+ *
+ * The membership used to unfold inside the list table, which cost three
+ * things a merchant actually uses. A list was not linkable, so "check the
+ * Wholesale audience" could not be sent to anybody. The back button walked out
+ * of the whole surface rather than out of the list. And the list's own
+ * settings had to live under a table they were not about.
+ *
+ * ## What it reads
+ *
+ * The list document — one document, whatever the audience's size — plus one
+ * server aggregate for the subscriber total, plus the paged membership window
+ * the table below draws. The membership is PII and there is one document per
+ * subscriber, so it is read HERE, where somebody asked for it, and nowhere
+ * that merely lists audiences.
+ *
+ * ## The rule is stated, not just flagged
+ *
+ * A dynamic list is a claim about who is on it, and "Rule" as a chip is not
+ * that claim. The summary spells out every dimension the rule actually
+ * carries, so the answer to "why is this person not in the audience" is on the
+ * screen the question gets asked on.
+ */
+import { type ConsentGroup } from '@aglyn/aglyn';
+export interface ListDetailCardProps {
+    hostId: string;
+    /**
+     * The controller this audience is being read AS, resolved by the page from
+     * the org document it already holds.
+     *
+     * Passed through rather than resolved here: the group is a fact about the
+     * ORG, one lookup serves every section, and a card that resolved its own
+     * would be a second place for the answer to come from.
+     */
+    consentGroup: ConsentGroup;
+    listId: string;
+    /** The emails hub URL, for the way back to the audiences list. */
+    basePath: string;
+}
+export declare function ListDetailCard(props: ListDetailCardProps): import("react").JSX.Element;
+export declare namespace ListDetailCard {
+    var displayName: string;
+}
+export default ListDetailCard;