@odla-ai/chapter 0.54.2 → 0.55.0

package/README.md

@@ -1745,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