@odla-ai/chapter 0.54.1 → 0.55.0

package/README.md

@@ -1520,7 +1520,7 @@ These bite silently — a smoke test won't catch them:
   | `submitConfirmation` | `POST /api/applications` (submit) — a free tier always; a paid tier only when `paymentConfirmation` is disabled, so a paid applicant is confirmed once | template `enabled` flag |
   | `prepEmail` | `POST /api/schedule/book` — once per application; a reschedule sends no second one | template `enabled` flag |
   | `paymentConfirmation` | Stripe webhook, first successful invoice | template `enabled` flag |
-  | `seatAccepted` | `POST /api/named-seat/accept` — to the seat's purchaser, once per seat, naming the recipient and tier | template `enabled` flag; the seeded default copy applies until the group row carries its own `emailTemplates.seatAccepted` |
+  | `seatAccepted` | `POST /api/named-seat/accept` — to the seat's purchaser, once per seat, naming the recipient and tier | explicit `enabled: true` on a stored `emailTemplates.seatAccepted`; missing copy blocks delivery |
 
   ```ts
   defineChapter({ /* … */ sends: { adminNotification: "payment" } });
@@ -1528,8 +1528,19 @@ These bite silently — a smoke test won't catch them:
 
   **Template variables.** Every value comes from stored data — the frozen
   checkout the applicant consented to, the tier catalog, the booked meeting,
-  the request origin — never from a price or a name written into code. An
-  unknown placeholder renders empty, so copy can use any subset.
+  the request origin — never from a price or a name written into code. Sends
+  reject unknown placeholders, missing required values, internal draft notes,
+  incomplete copy, and unresolved tier display names. Optional blanks must be
+  declared by the event (for example, a free tier’s payment amount suffix).
+
+  **Readiness on page open.** The Email page checks every built-in and host event
+  against saved templates and current tier names. Missing templates and invalid
+  values appear with the event’s trigger and recipient. Explicitly disabled
+  emails stay off. `emails.events` declares custom reminder contracts; pass the
+  same event to `sendTemplated`. Gift invitations and acceptance notices require
+  stored copy; delivery never supplies a hidden fallback. Hub mode uses the
+  site’s actual CRM template registry and CRM settings. All automatic sends
+  require explicit `enabled: true`; validation never enables a template.
 
   | Variable | Templates | Value |
   |---|---|---|
@@ -1734,6 +1745,38 @@ These bite silently — a smoke test won't catch them:
   durable, unfinished local approval work without starving later applicants.
   Neither helper installs a cron or provisions infrastructure by itself.
 
+  Starting with Chapter 0.55.0, a named-seat-enabled `JoinIsland` also offers the
+  additional member in the initial payment step. Both journeys read
+  `seatPriceCents` from the selected SKU's frozen offering: a positive amount is
+  the additional-member rate, and zero means included. No tier names or prices
+  are hardcoded. A host form may pass `payment.initialNamedSeat` with
+  `{ recipientName, recipientEmail }`; Chapter validates that selection and
+  shows a fresh total before consent. Custom `payment.renderPriceLines` slots
+  receive `namedSeatCents` (including zero); `dueTodayCents` already includes it.
+
+  `POST /api/payments/quote?application=<id>` accepts
+  `{ namedSeat: { recipientName, recipientEmail } }` or `{ namedSeat: null }`
+  before checkout starts. The response binds the selection, configured amount,
+  and combined renewal total into its digest. The subscription request requires
+  `seatTermsAck: true` for a selected seat, alongside the quote digest and refund
+  consent. After that, the selection is immutable. The
+  `x-chapter-checkout-started` response header tells a resumed UI to lock edits.
+  There is one subscription and one initial payment. A priced seat has a
+  separate, co-terminating recurring item; membership discounts are restricted
+  to the primary product. An included seat has no provider item or extra charge.
+  Independent invoice evidence commits the primary purchase and named seat
+  together. A seat-only refund returns only its allocation and removes only its
+  renewal item; a full membership refund covers both without a second refund.
+
+  Upgrade and provision the network owner's authority integration before
+  deploying the follower on 0.55.0. The added checkout `namedSeat` and seat
+  `combinedInvoice`/`purchaserEmailNormalized` fields are optional; a signup
+  purchaser need not have a user account yet, so `purchaserUserId` is optional.
+  The existing authority peer's configured `seatPriceId` is still server-owned
+  and must match a positive offering seat price on a separate Stripe product.
+  In-process users of `bindMembershipCheckout` pass that configured Price as
+  its fourth argument when binding a selected seat.
+
   The member area exposes the authenticated purchaser's named-seat checkout
   only when configured, and as soon as the membership is paid: `/api/me`
   reports `namedSeatsEnabled` for a paid application whose interview is still