@drawbridge/drawbridge-utils 0.0.161 → 0.0.163

package/dist/connections/index.js

@@ -558,10 +558,15 @@ var attentive_default2 = {
       "Attentive accepts these updates and applies them in the background, so a contact appears in your segment shortly after the sync rather than the instant it runs."
     ],
     excerpt: "Sync your Drawbridge contacts into an Attentive segment.",
+    // NAMES THE SEGMENT STEP, because `status` below gates on it: a grant with
+    // no segment chosen sits at Pending, and a guide that stops at the consent
+    // leaves a merchant looking at a connection they think is broken. Same
+    // omission Klaviyo's guide already carries a note about.
     guide: [
       "Press Connect. Drawbridge sends you to Attentive to approve access.",
       "Sign in to Attentive if you are not already, and authorize the permissions listed.",
-      "You are returned here \u2014 choose which Attentive segment your contacts should sync into."
+      "You come back here to choose which Attentive segment your contacts should sync into.",
+      "The connection shows Pending until you choose a segment, then Active."
     ]
   },
   // A contact destination, like Klaviyo and Mailchimp — a merchant could
@@ -824,6 +829,9 @@ var attentive_default2 = {
         // merchant would recognise in a builder label.
         key: "Sync contact to Attentive",
         queue: "connection",
+        // Attentive applies the update in the background and returns no id we
+        // could hand on, so there is nothing for a later step to interpolate.
+        returns: [],
         // Nothing for a merchant to configure on the step itself — the segment
         // is chosen once on the connection. Declared empty rather than omitted,
         // so "this step takes no settings" and "nobody thought about settings"
@@ -2051,13 +2059,18 @@ var drawbridge_default2 = {
           request: request2,
           response: { count, notified: recipients.length },
           writes: recipients.map((member) => {
-            var _a2, _b2;
+            var _a2, _b2, _c2;
             return queueNotification({
               audience: "member",
               message: interpolate((_a2 = step.settings) == null ? void 0 : _a2.message, values),
               organization: workflow.organization,
               send: { type: "email", email: member.email },
-              title: interpolate((_b2 = step.settings) == null ? void 0 : _b2.subject, values),
+              // The editor's plain rendering, interpolated the same way so
+              // {{count}} resolves in the text part too. Spread rather than
+              // written as null: a step saved before `text` existed has none,
+              // and the send path strips the markup itself for those.
+              ...((_b2 = step.settings) == null ? void 0 : _b2.text) && { text: interpolate(step.settings.text, values) },
+              title: interpolate((_c2 = step.settings) == null ? void 0 : _c2.subject, values),
               workflow: workflow.id
             });
           })
@@ -2126,7 +2139,7 @@ var drawbridge_default2 = {
       // unsubscribe token and the CAN-SPAM footer. The step's job is to say who
       // and what, correctly, and to refuse early when it must not send at all.
       send: async ({ context, step, workflow }, { canSend, read } = {}) => {
-        var _a, _b;
+        var _a, _b, _c;
         const to = context == null ? void 0 : context.email;
         if (!to) throw new Error("No email address on context (context.email is required)");
         const request2 = { to };
@@ -2163,7 +2176,11 @@ var drawbridge_default2 = {
               message: interpolate((_a = step.settings) == null ? void 0 : _a.message, context),
               organization: workflow.organization,
               send: { type: "email", email: to },
-              title: interpolate((_b = step.settings) == null ? void 0 : _b.subject, context),
+              // The editor's plain rendering, so the text/plain part of this
+              // email is what the merchant wrote rather than a regex's guess at
+              // it. See the digest above for why it is spread, not nulled.
+              ...((_b = step.settings) == null ? void 0 : _b.text) && { text: interpolate(step.settings.text, context) },
+              title: interpolate((_c = step.settings) == null ? void 0 : _c.subject, context),
               workflow: workflow.id
             })
           ]
@@ -2583,6 +2600,11 @@ var drawbridge_default2 = {
         hook: "email.digest",
         key: "Email \u2014 Digest",
         queue: "notification",
+        // Nothing for a later step to interpolate. Declared empty rather than
+        // omitted, so "this step leaves nothing behind" and "nobody thought
+        // about it" stay different statements — the second is what emptied the
+        // builder's Variables menu for every step in the product.
+        returns: [],
         settings: {
           // The organization OWNER is always a recipient, resolved by the
           // hook, so this is additional recipients rather than the list. It
@@ -2591,7 +2613,22 @@ var drawbridge_default2 = {
           // pick and could never save the step.
           members: { of: "string", type: "array" },
           message: { max: 2e3, required: true, type: "string" },
-          subject: { max: 150, required: true, type: "string" }
+          // THE LAST SPAM CHECK, stored beside the copy it measured. Shape is
+          // pinned no further than the pair that proves the match, which is the
+          // only part the api reads; the rest is SpamAssassin's own output and
+          // is stored as it arrives. Same declaration the campaign's draw
+          // notification validates against.
+          //
+          // Undeclared, this was silently dropped at submit — the settings
+          // validator is noUnknown().strict(), so the dashboard's step form
+          // mapped the key away rather than 400 — and every open of a workflow
+          // step re-ran a check against a free service to be told what the last
+          // open had already been told.
+          score: { shape: { message: { type: "string" }, subject: { type: "string" } }, type: "object" },
+          subject: { max: 150, required: true, type: "string" },
+          // The editor's plain rendering of `message`, written beside it rather
+          // than reconstructed by running a regex over the markup at send time.
+          text: { max: 2e3, type: "string" }
         },
         triggers: ["schedule.day", "schedule.week", "schedule.month"],
         usage: { actions: 0 }
@@ -2612,6 +2649,7 @@ var drawbridge_default2 = {
         hook: "email.notify",
         key: "Email \u2014 Notification",
         queue: "notification",
+        returns: [],
         settings: {
           members: { of: "string", type: "array" },
           message: { max: 2e3, type: "string" },
@@ -2628,9 +2666,14 @@ var drawbridge_default2 = {
         hook: "email.send",
         key: "Email \u2014 Send email",
         queue: "notification",
+        returns: [],
         settings: {
           message: { max: 2e3, required: true, type: "string" },
-          subject: { max: 150, required: true, type: "string" }
+          // See email.digest above — the last spam check, and the editor's
+          // plain rendering of the message.
+          score: { shape: { message: { type: "string" }, subject: { type: "string" } }, type: "object" },
+          subject: { max: 150, required: true, type: "string" },
+          text: { max: 2e3, type: "string" }
         },
         triggers: ["lead.insert"],
         // ONE SOURCE FOR THE PRICE. lib/pricing.js is the index of every
@@ -3229,6 +3272,13 @@ var klaviyo_default2 = {
           // than a label that could be any of their Klaviyo accounts.
           key: "Sync contact to " + (((_a = data2 == null ? void 0 : data2.settings) == null ? void 0 : _a.account) || "Klaviyo"),
           queue: "connection",
+          // The key the hook puts in `context`, which the runner merges into the
+          // run so a later step can interpolate {{klaviyoProfileId}}. Declared
+          // beside the hook that writes it — see the note on Shopify's
+          // commerce.code, which is where this came back from.
+          returns: [
+            { key: "klaviyoProfileId", label: "Klaviyo Profile ID" }
+          ],
           // Nothing for a merchant to configure on the step itself — the list
           // is chosen once on the connection. Declared empty rather than
           // omitted, so "this step takes no settings" and "nobody thought about
@@ -3344,10 +3394,15 @@ var mailchimp_default2 = {
       "Someone who unsubscribed inside Mailchimp keeps that choice: a resync only sets the status of a subscriber Mailchimp has never seen before."
     ],
     excerpt: "Sync your Drawbridge contacts into a Mailchimp audience.",
+    // NAMES THE AUDIENCE STEP, because `status` below gates on it: a grant with
+    // no audience chosen sits at Pending, and a guide that stops at the consent
+    // leaves a merchant looking at a connection they think is broken.
     guide: [
       "Press Connect. Drawbridge sends you to Mailchimp to approve access.",
       "Sign in to Mailchimp if you are not already, and choose the account to connect.",
-      "You come back here to pick the audience your contacts should sync into."
+      "You come back here to pick the audience your contacts should sync into.",
+      "The connection shows Pending until you pick an audience, then Active.",
+      "You can remove Drawbridge at any time from the Authorized Apps page in your Mailchimp account."
     ]
   },
   // Mailchimp and SendGrid shared a group while they were SENDERS, where an org
@@ -3589,6 +3644,11 @@ var mailchimp_default2 = {
         // than showing a string like a1b2c3d4e5.
         key: "Sync contact to Mailchimp",
         queue: "connection",
+        // The key the hook puts in `context`, for a later step to interpolate
+        // as {{mailchimpMemberId}}. Same reasoning as Klaviyo's.
+        returns: [
+          { key: "mailchimpMemberId", label: "Mailchimp Member ID" }
+        ],
         // Nothing for a merchant to configure on the step itself — the audience
         // is chosen once on the connection. Declared empty rather than omitted,
         // so "this step takes no settings" and "nobody thought about settings"
@@ -4850,6 +4910,24 @@ var shopify_default2 = {
           hook: "commerce.code",
           key: "Issue a discount code",
           queue: "connection",
+          // WHAT THIS STEP LEAVES BEHIND FOR THE ONES AFTER IT, and the only
+          // reason the builder can offer a Variables menu.
+          //
+          // These are the exact keys the hook puts in `context` — the runner
+          // merges that into the run's context, and a later step interpolates
+          // {{shopifyDiscountCode}} out of it. Declared beside the hook that
+          // writes them so the two cannot drift; there is nowhere else that
+          // knows both.
+          //
+          // They existed as a hand-written list in the api's workflow catalog
+          // until it was derived from these manifests, and the derivation
+          // hardcoded `returns : []` for every step. Nothing has offered a
+          // variable since — an email step after a discount step had no way to
+          // name the code it was supposed to send.
+          returns: [
+            { key: "shopifyDiscountCode", label: "Shopify Discount Code" },
+            { key: "shopifyDiscountId", label: "Shopify Discount ID" }
+          ],
           settings: {
             discount: {
               required: true,
@@ -4868,6 +4946,12 @@ var shopify_default2 = {
           hook: "commerce.customer",
           key: "Create customer",
           queue: "connection",
+          // Written on every path the hook can take — created, reused from an
+          // earlier step, or reused from the lead — so a later step can rely on
+          // it being there whenever this one succeeded.
+          returns: [
+            { key: "shopifyCustomerId", label: "Shopify Customer ID" }
+          ],
           settings: {},
           triggers: ["lead.insert"],
           usage: { actions: 1 }
@@ -5265,6 +5349,13 @@ var webhook_default = {
         hook: "webhook.send",
         key: "Send webhook",
         queue: "webhook",
+        // The receiver's response is buffered, not merged into the run — a
+        // receiver owes us a status, not a document — so there is nothing here
+        // for a later step to interpolate. Declared empty rather than omitted:
+        // "leaves nothing behind" and "nobody thought about it" are different
+        // statements, and the second one is what emptied the builder's
+        // Variables menu for every step in the product.
+        returns: [],
         settings: {
           url: { format: "url", required: true, type: "string" }
         },

package/dist/html.cjs

@@ -19,11 +19,14 @@ var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: tru
 // lib/html.js
 var html_exports = {};
 __export(html_exports, {
-  escapeHtml: () => escapeHtml
+  escapeHtml: () => escapeHtml,
+  plainText: () => plainText
 });
 module.exports = __toCommonJS(html_exports);
 var escapeHtml = (value) => String(value ?? "").replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;").replace(/"/g, "&quot;").replace(/'/g, "&#39;");
+var plainText = (value) => String(value ?? "").replace(/<[^>]+>/g, "").trim();
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {
-  escapeHtml
+  escapeHtml,
+  plainText
 });

package/dist/html.d.cts

@@ -29,4 +29,23 @@ const escapeHtml = ( value ) => String( value ?? '' )
 	.replace( /"/g, '"' )
 	.replace( /'/g, ''' );
 
-export { escapeHtml };
+// THE OTHER DIRECTION: markup out, words kept. For the places that need a plain
+// rendering of editor output and were not handed one — the spam check scoring a
+// message as text/plain, and the send paths' fallback for notifications written
+// before `text` was stored beside `message`.
+//
+// A REGEX, AND KNOWINGLY A GUESS. It drops tags and nothing else: entities stay
+// as typed and block boundaries collapse to nothing, so "<p>Hi</p><p>there</p>"
+// reads "Hithere". Tiptap's getText() is the answer where an editor is in hand,
+// which is why the dashboard stores what the editor says rather than calling
+// this at send time. This is for the copies that exist without it.
+//
+// Same three-copy story as escapeHtml above: scripts.js, the draw route and the
+// spam check route each carried this line inline. The spam check's was missing
+// entirely — it scored the raw markup as text/plain, so a merchant's <p> tags
+// were measured as words while the migration scored the same copy stripped.
+const plainText = ( value ) => String( value ?? '' )
+	.replace( /<[^>]+>/g, '' )
+	.trim();
+
+export { escapeHtml, plainText };

package/dist/html.d.ts

@@ -29,4 +29,23 @@ const escapeHtml = ( value ) => String( value ?? '' )
 	.replace( /"/g, '"' )
 	.replace( /'/g, ''' );
 
-export { escapeHtml };
+// THE OTHER DIRECTION: markup out, words kept. For the places that need a plain
+// rendering of editor output and were not handed one — the spam check scoring a
+// message as text/plain, and the send paths' fallback for notifications written
+// before `text` was stored beside `message`.
+//
+// A REGEX, AND KNOWINGLY A GUESS. It drops tags and nothing else: entities stay
+// as typed and block boundaries collapse to nothing, so "<p>Hi</p><p>there</p>"
+// reads "Hithere". Tiptap's getText() is the answer where an editor is in hand,
+// which is why the dashboard stores what the editor says rather than calling
+// this at send time. This is for the copies that exist without it.
+//
+// Same three-copy story as escapeHtml above: scripts.js, the draw route and the
+// spam check route each carried this line inline. The spam check's was missing
+// entirely — it scored the raw markup as text/plain, so a merchant's <p> tags
+// were measured as words while the migration scored the same copy stripped.
+const plainText = ( value ) => String( value ?? '' )
+	.replace( /<[^>]+>/g, '' )
+	.trim();
+
+export { escapeHtml, plainText };

package/dist/html.js

@@ -1,5 +1,7 @@
 // lib/html.js
 var escapeHtml = (value) => String(value ?? "").replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;").replace(/"/g, "&quot;").replace(/'/g, "&#39;");
+var plainText = (value) => String(value ?? "").replace(/<[^>]+>/g, "").trim();
 export {
-  escapeHtml
+  escapeHtml,
+  plainText
 };

package/dist/index.cjs

@@ -160,7 +160,40 @@ var constants_default = {
     notifications: {
       draw: {
         subject: "Your prize is ready to claim",
-        message: "You were selected in our giveaway. Follow the link to confirm your details and claim your prize."
+        message: "You were selected in our giveaway. Follow the link to confirm your details and claim your prize.",
+        // THE DEFAULT COPY'S SPAM SCORE, SHIPPED WITH THE COPY.
+        //
+        // A campaign is seeded from this object, so a score written here is a
+        // score every new campaign has from the moment it exists — which is
+        // what lets the dashboard's card open with an answer and ask the
+        // checker only when a merchant changes the words. Without it the copy
+        // arrived unmeasured and the panel had to go and find out, spending a
+        // request on a free service to be told what is measured right here.
+        //
+        // Verbatim what the checker returned for these two strings on
+        // 2026-09-10, so a campaign created today and one moved by
+        // backfillDrawNotifications carry the same object rather than two
+        // shapes of the same fact.
+        //
+        // The 0.5 is OURS, not the copy's: SpamAssassin charges the sending
+        // domain for its missing vowels on every message it will ever score.
+        // That is why `subtotal` — the merchant's own share — is what the
+        // dashboard reads and what it scores out of five.
+        score: {
+          rules: [
+            { description: "From: domain has series of non-vowel letters", score: 0.5 },
+            { description: "Informational: message was not relayed via SMTP", score: 0 },
+            { description: "Informational: message has no Received headers", score: 0 }
+          ],
+          subtotal: 0,
+          threshold: 5,
+          total: 0.5
+        },
+        // The plain rendering that rides alongside `message`. Identical to it
+        // here because the default carries no markup, and stored rather than
+        // derived because the draw notification leaves as email OR as SMS and
+        // twilio.sms drops its body in verbatim.
+        text: "You were selected in our giveaway. Follow the link to confirm your details and claim your prize."
       }
     },
     settings: {

package/dist/index.d.cts

@@ -85,7 +85,40 @@ var constantsData = {
 		notifications : {
 			draw : {
 				subject : 'Your prize is ready to claim',
-				message : 'You were selected in our giveaway. Follow the link to confirm your details and claim your prize.'
+				message : 'You were selected in our giveaway. Follow the link to confirm your details and claim your prize.',
+				// THE DEFAULT COPY'S SPAM SCORE, SHIPPED WITH THE COPY.
+				//
+				// A campaign is seeded from this object, so a score written here is a
+				// score every new campaign has from the moment it exists — which is
+				// what lets the dashboard's card open with an answer and ask the
+				// checker only when a merchant changes the words. Without it the copy
+				// arrived unmeasured and the panel had to go and find out, spending a
+				// request on a free service to be told what is measured right here.
+				//
+				// Verbatim what the checker returned for these two strings on
+				// 2026-09-10, so a campaign created today and one moved by
+				// backfillDrawNotifications carry the same object rather than two
+				// shapes of the same fact.
+				//
+				// The 0.5 is OURS, not the copy's: SpamAssassin charges the sending
+				// domain for its missing vowels on every message it will ever score.
+				// That is why `subtotal` — the merchant's own share — is what the
+				// dashboard reads and what it scores out of five.
+				score : {
+					rules : [
+						{ description : 'From: domain has series of non-vowel letters', score : 0.5 },
+						{ description : 'Informational: message was not relayed via SMTP', score : 0 },
+						{ description : 'Informational: message has no Received headers', score : 0 }
+					],
+					subtotal : 0,
+					threshold : 5,
+					total : 0.5
+				},
+				// The plain rendering that rides alongside `message`. Identical to it
+				// here because the default carries no markup, and stored rather than
+				// derived because the draw notification leaves as email OR as SMS and
+				// twilio.sms drops its body in verbatim.
+				text : 'You were selected in our giveaway. Follow the link to confirm your details and claim your prize.'
 			}
 		},
 		settings : {

package/dist/index.d.ts

@@ -85,7 +85,40 @@ var constantsData = {
 		notifications : {
 			draw : {
 				subject : 'Your prize is ready to claim',
-				message : 'You were selected in our giveaway. Follow the link to confirm your details and claim your prize.'
+				message : 'You were selected in our giveaway. Follow the link to confirm your details and claim your prize.',
+				// THE DEFAULT COPY'S SPAM SCORE, SHIPPED WITH THE COPY.
+				//
+				// A campaign is seeded from this object, so a score written here is a
+				// score every new campaign has from the moment it exists — which is
+				// what lets the dashboard's card open with an answer and ask the
+				// checker only when a merchant changes the words. Without it the copy
+				// arrived unmeasured and the panel had to go and find out, spending a
+				// request on a free service to be told what is measured right here.
+				//
+				// Verbatim what the checker returned for these two strings on
+				// 2026-09-10, so a campaign created today and one moved by
+				// backfillDrawNotifications carry the same object rather than two
+				// shapes of the same fact.
+				//
+				// The 0.5 is OURS, not the copy's: SpamAssassin charges the sending
+				// domain for its missing vowels on every message it will ever score.
+				// That is why `subtotal` — the merchant's own share — is what the
+				// dashboard reads and what it scores out of five.
+				score : {
+					rules : [
+						{ description : 'From: domain has series of non-vowel letters', score : 0.5 },
+						{ description : 'Informational: message was not relayed via SMTP', score : 0 },
+						{ description : 'Informational: message has no Received headers', score : 0 }
+					],
+					subtotal : 0,
+					threshold : 5,
+					total : 0.5
+				},
+				// The plain rendering that rides alongside `message`. Identical to it
+				// here because the default carries no markup, and stored rather than
+				// derived because the draw notification leaves as email OR as SMS and
+				// twilio.sms drops its body in verbatim.
+				text : 'You were selected in our giveaway. Follow the link to confirm your details and claim your prize.'
 			}
 		},
 		settings : {

package/dist/index.js

@@ -105,7 +105,40 @@ var constants_default = {
     notifications: {
       draw: {
         subject: "Your prize is ready to claim",
-        message: "You were selected in our giveaway. Follow the link to confirm your details and claim your prize."
+        message: "You were selected in our giveaway. Follow the link to confirm your details and claim your prize.",
+        // THE DEFAULT COPY'S SPAM SCORE, SHIPPED WITH THE COPY.
+        //
+        // A campaign is seeded from this object, so a score written here is a
+        // score every new campaign has from the moment it exists — which is
+        // what lets the dashboard's card open with an answer and ask the
+        // checker only when a merchant changes the words. Without it the copy
+        // arrived unmeasured and the panel had to go and find out, spending a
+        // request on a free service to be told what is measured right here.
+        //
+        // Verbatim what the checker returned for these two strings on
+        // 2026-09-10, so a campaign created today and one moved by
+        // backfillDrawNotifications carry the same object rather than two
+        // shapes of the same fact.
+        //
+        // The 0.5 is OURS, not the copy's: SpamAssassin charges the sending
+        // domain for its missing vowels on every message it will ever score.
+        // That is why `subtotal` — the merchant's own share — is what the
+        // dashboard reads and what it scores out of five.
+        score: {
+          rules: [
+            { description: "From: domain has series of non-vowel letters", score: 0.5 },
+            { description: "Informational: message was not relayed via SMTP", score: 0 },
+            { description: "Informational: message has no Received headers", score: 0 }
+          ],
+          subtotal: 0,
+          threshold: 5,
+          total: 0.5
+        },
+        // The plain rendering that rides alongside `message`. Identical to it
+        // here because the default carries no markup, and stored rather than
+        // derived because the draw notification leaves as email OR as SMS and
+        // twilio.sms drops its body in verbatim.
+        text: "You were selected in our giveaway. Follow the link to confirm your details and claim your prize."
       }
     },
     settings: {

package/dist/notification.cjs

@@ -77,16 +77,12 @@ var messageWarnings = ({ message }) => {
 };
 var notificationWarnings = ({
   brand,
-  channel = "email",
   message,
   subject
-} = {}) => {
-  if (channel !== "email") return { message: [], subject: [] };
-  return {
-    message: messageWarnings({ message }),
-    subject: subjectWarnings({ brand, subject })
-  };
-};
+} = {}) => ({
+  message: messageWarnings({ message }),
+  subject: subjectWarnings({ brand, subject })
+});
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {
   notificationWarnings

package/dist/notification.d.cts

@@ -131,25 +131,32 @@ const messageWarnings = ({ message }) => {
 // ONE ENTRY POINT, answering per field so each warning renders against the
 // input it is about rather than as a pile at the bottom of the form.
 //
-// `channel` is accepted and only 'email' is implemented. SMS is a genuinely
-// different problem — carriers filter on SHAFT categories, link shorteners and
-// opt-out wording, none of which these rules look at — and returning email
-// advice for an SMS would be confidently wrong. It returns nothing instead,
-// until someone writes the carrier rules properly.
+// NO CHANNEL ARGUMENT, deliberately, and it is worth saying why since one was
+// tried twice.
+//
+// First it gated SMS to silence, on the grounds that carriers filter on things
+// these rules do not look at. That much is true, and it does not follow:
+// shouting, repeated punctuation, currency amounts and scam-shaped phrasing
+// matter at least as much on a phone, and an unbranded text is the exact shape
+// of a smishing attempt. Then a hedge value was added for copy that could go
+// either way, a caller passed it to a build that did not have it, and a whole
+// form went quiet with nothing to show for the caution.
+//
+// Every rule here is one a person would want to hear wherever the words end up.
+// Sorting them by channel bought accuracy on a single warning — the subject
+// display limit, which is really an email idea — and cost the other six.
+//
+// SMS still has no rules of its OWN: SHAFT categories, link shorteners, opt-out
+// wording, and the segment mechanics where one emoji drops the limit from 160
+// characters to 70. Those belong with the SMS connection work rather than here,
+// and their absence is a reason to write them, not to stay quiet meanwhile.
 const notificationWarnings = ({
 	brand,
-	channel = 'email',
 	message,
 	subject
-} = {}) => {
-
-	if( channel !== 'email' ) return { message : [], subject : [] };
-
-	return {
-		message : messageWarnings({ message }),
-		subject : subjectWarnings({ brand, subject })
-	};
-
-};
+} = {}) => ({
+	message : messageWarnings({ message }),
+	subject : subjectWarnings({ brand, subject })
+});
 
 export { notificationWarnings };

package/dist/notification.d.ts

@@ -131,25 +131,32 @@ const messageWarnings = ({ message }) => {
 // ONE ENTRY POINT, answering per field so each warning renders against the
 // input it is about rather than as a pile at the bottom of the form.
 //
-// `channel` is accepted and only 'email' is implemented. SMS is a genuinely
-// different problem — carriers filter on SHAFT categories, link shorteners and
-// opt-out wording, none of which these rules look at — and returning email
-// advice for an SMS would be confidently wrong. It returns nothing instead,
-// until someone writes the carrier rules properly.
+// NO CHANNEL ARGUMENT, deliberately, and it is worth saying why since one was
+// tried twice.
+//
+// First it gated SMS to silence, on the grounds that carriers filter on things
+// these rules do not look at. That much is true, and it does not follow:
+// shouting, repeated punctuation, currency amounts and scam-shaped phrasing
+// matter at least as much on a phone, and an unbranded text is the exact shape
+// of a smishing attempt. Then a hedge value was added for copy that could go
+// either way, a caller passed it to a build that did not have it, and a whole
+// form went quiet with nothing to show for the caution.
+//
+// Every rule here is one a person would want to hear wherever the words end up.
+// Sorting them by channel bought accuracy on a single warning — the subject
+// display limit, which is really an email idea — and cost the other six.
+//
+// SMS still has no rules of its OWN: SHAFT categories, link shorteners, opt-out
+// wording, and the segment mechanics where one emoji drops the limit from 160
+// characters to 70. Those belong with the SMS connection work rather than here,
+// and their absence is a reason to write them, not to stay quiet meanwhile.
 const notificationWarnings = ({
 	brand,
-	channel = 'email',
 	message,
 	subject
-} = {}) => {
-
-	if( channel !== 'email' ) return { message : [], subject : [] };
-
-	return {
-		message : messageWarnings({ message }),
-		subject : subjectWarnings({ brand, subject })
-	};
-
-};
+} = {}) => ({
+	message : messageWarnings({ message }),
+	subject : subjectWarnings({ brand, subject })
+});
 
 export { notificationWarnings };

package/dist/notification.js

@@ -54,16 +54,12 @@ var messageWarnings = ({ message }) => {
 };
 var notificationWarnings = ({
   brand,
-  channel = "email",
   message,
   subject
-} = {}) => {
-  if (channel !== "email") return { message: [], subject: [] };
-  return {
-    message: messageWarnings({ message }),
-    subject: subjectWarnings({ brand, subject })
-  };
-};
+} = {}) => ({
+  message: messageWarnings({ message }),
+  subject: subjectWarnings({ brand, subject })
+});
 export {
   notificationWarnings
 };