@odla-ai/chapter 0.39.2 → 0.40.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@odla-ai/chapter",
-  "version": "0.39.2",
+  "version": "0.40.0",
   "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/greenfield.md

@@ -748,10 +748,15 @@ deployed dev origin.
 ### Stripe test mode
 
 1. Create the approved recurring test product/price.
-2. Point a Stripe test webhook to
-   `https://<dev-origin>/api/webhooks/stripe`.
-3. Store `stripe_secret_key` and `stripe_webhook_secret` as named dev vault
-   secrets through write-only `odla-ai secrets set ... --stdin`.
+2. Store `stripe_secret_key` in the shared dev vault through write-only
+   `odla-ai secrets set stripe_secret_key --env dev --stdin`.
+3. For one Worker per developer on shared dev data, declare top-level
+   `runtimes.<name>` with `dataEnvironment: "dev"` and its stable origin, then
+   run `odla-ai environment reconcile --runtime <name>`. ODLA creates the
+   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.
 4. In the guarded `groups` row, set `stripePublishableKey` and `stripePriceId`.
 5. Read that exact Stripe Price from Stripe and compare its first charge,
    recurring amount, currency, and interval with the approved public contract.