@odla-ai/chapter 0.43.0 → 0.43.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/chapter",
-  "version": "0.43.0",
+  "version": "0.43.1",
   "description": "A leader/follower foundation for branded membership sites: shared CRM, admin, auth, payments, booking, and explicit record delivery from one defineChapter config.",
   "license": "MIT",
   "homepage": "https://odla.ai/docs/packages/chapter",

package/runbooks/adopt-existing.md

@@ -584,7 +584,12 @@ cancellation before switching the UI.
 For a shared Stripe account, preserve Chapter's closed partition metadata on
 every new customer, subscription, payment intent, and refund: app, chapter,
 environment, data environment, and stable runtime. Do not infer ownership from
-the Stripe account or Price alone. The signed webhook must apply an exact target
+the Stripe account or Price alone. A Worker with a named runtime prefers its
+`stripe_webhook_secret__<runtime>` endpoint secret. During an existing app's
+upgrade, Chapter falls back to the historical `stripe_webhook_secret` slot only
+when the scoped slot is absent; replace that compatibility path by reconciling a
+dedicated endpoint, without reading or manually copying either secret. The
+signed webhook must apply an exact target
 once, acknowledge a fully tagged sibling with zero local writes, quarantine an
 unmatched event for operators, and accept a metadata-free legacy object only
 when its Stripe customer, subscription, or gift id is already linked to this

package/runbooks/greenfield.md

@@ -762,7 +762,10 @@ deployed dev origin.
    endpoint, stores `stripe_webhook_secret__<name>` under write-only custody,
    and binds `ODLA_RUNTIME`; do not manually reuse one signing secret across
    endpoints. A legacy single-Worker app may still store
-   `stripe_webhook_secret` directly.
+   `stripe_webhook_secret` directly. An upgraded named-runtime Worker falls back
+   to that historical slot only while its scoped endpoint secret is absent;
+   reconcile the dedicated endpoint to end the compatibility period without
+   reading or copying either secret.
 4. In the guarded `groups` row, set `stripePublishableKey` and `stripePriceId`.
 5. Confirm `policy.merchantDisclosureText` names the merchant the customer will
    see on the charge or receipt, including the chapter relationship when the