@odla-ai/chapter 0.59.0 → 0.60.0

package/README.md

@@ -1629,6 +1629,23 @@ These bite silently — a smoke test won't catch them:
   `Tori Horton <tori@…>` in an inbox — while the address stays the Worker's
   `EMAIL_FROM`. A group with no name sends the bare address exactly as before.
 
+  **Deliverability.** Every send carries the text part verbatim and an HTML
+  alternative rendered from it by `textToHtml` (paragraphs, line breaks, and
+  each https address as a link labelled with itself) — multipart like mail from
+  any mainstream sender, with nothing the text lacks. Recipient-facing events
+  (every audience except the administrator's) also carry a List-Unsubscribe
+  header pointing at the group's reply-to as a mailto link, so a reader who
+  wants out writes to you instead of reporting spam. Set the notify deps'
+  render hook to `false` for text-only mail, or pass your own renderer. The
+  Email page lists spam-filter signals beside each template — shouting or
+  over-punctuated subjects, trigger phrases, insecure or development-host
+  links, shorteners, link-only bodies — and beside the sender (a no-reply
+  From, a Reply-To on another domain); `emailSpamSignals` and
+  `emailSenderWarnings` are the same checks for a script, and the save route
+  returns them. Warnings never block a send. Authentication (SPF, DKIM, DMARC)
+  belongs to Cloudflare Email Service: onboard the sending domain in the
+  Cloudflare dashboard and it adds the records.
+
   **Re-check this on every chapter upgrade.** Wiring a send changes a site's
   outbound mail with no local diff — release notes call out send changes
   explicitly for that reason.
@@ -1835,8 +1852,20 @@ These bite silently — a smoke test won't catch them:
   `MembershipDisputes` from `@odla-ai/chapter/ui/admin`: re-charging collects
   the lost amount again on the member's saved card, off-session and only on the
   operator's confirmed click, with one idempotency key kept on the row until
-  Stripe answers so a lost response never charges twice. A seat's own charge or
-  another customer's never touches the primary membership.
+  Stripe answers so a lost response never charges twice. Another customer's
+  charge never touches the membership.
+
+  A named seat's own PaymentIntent is the seat's dispute (Chapter 0.59.1): the
+  same facts suspend only the `networkSeat` (`payment_disputed`, the prior
+  seat status remembered, recipient state `disputed`), so the recipient loses
+  access while the purchaser's membership stays as it was; won restores the
+  seat, lost waits for the operator. The disputes list tags each row with
+  `kind` (`membership` or `seat`, with the recipient's name), and a `seat_…`
+  id on the re-charge route collects the seat amount again on the purchaser's
+  saved card. A seat line billed on the primary subscription's invoice is the
+  primary's charge and follows the membership rules above. Re-provision the
+  authority schema: the seat row gains the same optional `dispute*` and
+  `recharge*` attributes.
 
   Starting with Chapter 0.55.0, a named-seat-enabled `JoinIsland` also offers the
   additional member in the initial payment step. Both journeys read

package/dist/{chunk-Y2H4VURI.js → chunk-D5UR5H6R.js}

@@ -2,7 +2,7 @@ import {
   DEFAULT_JOIN_COPY,
   formatChapterCopy,
   useChapterCopy
-} from "./chunk-GADLTNJF.js";
+} from "./chunk-QNP3UEIL.js";
 import {
   collectFormFields
 } from "./chunk-IVXVECKR.js";
@@ -1104,7 +1104,8 @@ var NAMED_SEAT_RECIPIENT_WORDS = {
   joined: "joined as a member",
   declined: "declined the seat",
   refunded: "seat refunded",
-  canceled: "seat canceled"
+  canceled: "seat canceled",
+  disputed: "seat payment disputed with the card issuer; their access is paused until it is resolved"
 };
 var day = (at) => new Date(at).toLocaleDateString("en-US", { timeZone: "UTC" });
 function NamedSeatRecipientLine({ seat }) {
@@ -2697,4 +2698,4 @@ export {
   membershipApplicationHref,
   MembershipCards
 };
-//# sourceMappingURL=chunk-Y2H4VURI.js.map
+//# sourceMappingURL=chunk-D5UR5H6R.js.map