@aglyn/plugins-email 1.0.0-beta.143

package/src/lib/components/suppressions-card.d.ts

@@ -0,0 +1,49 @@
+export interface SuppressionsCardProps {
+    hostId: string;
+}
+/**
+ * Suppressions (AGL-2410): who is not being emailed, and why.
+ *
+ * ## What was missing
+ *
+ * `hosts/{hostId}/suppressions` was written by two paths — the unsubscribe
+ * handler and, since AGL-1918, the Resend webhook on a permanent bounce or a
+ * complaint — and read by exactly one: `campaign-send.ts`, to filter an
+ * audience. Nothing in the console displayed it. So a merchant could not
+ * answer any of:
+ *
+ *  - *"My campaign says 500 recipients and 480 sent — who were the other
+ *    20?"* The send returns `{recipients, sent}` and the difference was
+ *    unexplained.
+ *  - *"Is my list going stale?"* A bounce rate is the single most useful
+ *    number about a list and there was nowhere to see it.
+ *  - *"This address was suppressed by mistake."* There was no way to remove
+ *    an entry — and a link prescanner unsubscribing someone (AGL-2408 §2) was
+ *    therefore unrecoverable from inside the product.
+ *
+ * ## Why a surface and not another counter
+ *
+ * AGL-1918 deliberately did NOT write a `stats.bounces` counter alongside its
+ * fix, because a number with no screen to show it is the written-but-never-
+ * read shape this issue is about, one level up. So the fix is the READER, and
+ * the breakdown here is derived from the rows on screen rather than from a
+ * second stored figure that could disagree with them.
+ *
+ * ## Removing an entry
+ *
+ * A plain client `deleteDoc`, and that is a decision. The list belongs to the
+ * merchant, host admins already read it through the same rules, and removing
+ * a row does nothing except make an address targetable again — there is no
+ * counter to launder and no money attached, which is the AGL-1367 test for
+ * whether a write has to move server-side.
+ *
+ * The confirmation is not decoration either: for a `bounce` the address very
+ * likely does not exist, and mailing it again is what a provider scores the
+ * sending domain on. So the dialog says which reason is being overridden
+ * rather than asking a generic "are you sure".
+ */
+export declare function SuppressionsCard(props: SuppressionsCardProps): import("react").JSX.Element;
+export declare namespace SuppressionsCard {
+    var displayName: string;
+}
+export default SuppressionsCard;