@odla-ai/chapter 0.26.0 → 0.26.1

package/README.md

@@ -373,6 +373,7 @@ export const chapter = defineChapter({
       id: "example-chapter",
       name: "Example Chapter",
       url: "https://chapter.example.com",
+      binding: "EXAMPLE_CHAPTER",
       fields: {
         person: ["name", "email", "firstName", "lastName", "phone", "linkedin"],
         company: ["name", "domain", "industry", "location", "linkedin"],
@@ -387,7 +388,7 @@ Treat the network as websites connected by explicit delivery edges:
 - each website is a node with its own `appId`, ODLA tenants/keys, CRM config,
   Clerk application, publishable keys, issuer, roles, and local users;
 - each `network.targets[]` entry is a directed edge from one leader to one
-  follower: `{ id, name, url, secretName?, fields }`;
+  follower: `{ id, name, url, binding?, secretName?, fields }`;
 - the payload is a versioned, allowlisted business record
   `{ version: 2, source: { siteId, recordId }, type, input }`, never an
   identity-provider session, another site's pipeline/account/billing state, or
@@ -406,6 +407,32 @@ payload against its own CRM config, and writes with its own server-side
 is never needed, the leader never receives the follower's database key, and
 sites do not share a Clerk application.
 
+When both sites are Cloudflare Workers, configure `binding` and add the matching
+service binding to the leader's Wrangler environment. Cloudflare does not
+reliably dispatch same-account `workers.dev` subrequests into the target
+Worker; Chapter therefore signs against `url` but sends through the bound
+Worker:
+
+```jsonc
+{
+  "env": {
+    "dev": {
+      "services": [{
+        "binding": "EXAMPLE_CHAPTER",
+        "service": "example-chapter-dev"
+      }]
+    }
+  }
+}
+```
+
+The example assumes the follower sets its development Worker `name` explicitly
+to `example-chapter-dev`. If it instead uses Cloudflare's named-environment
+addressing, declare the base `service` plus `"environment": "dev"`. The binding
+name is public configuration, not a credential. If a configured binding is
+missing at runtime, the target fails explicitly instead of falling back to a
+potentially misrouted public fetch.
+
 Vault the same random value as `network_share_secret` in the follower and as
 `network_share_example_chapter` in the leader (or set a different
 `secretName`). No secret is placed in source, browser data, or provisioning
@@ -531,9 +558,10 @@ data.
 
 Use distinct development tenants and follower origins for the first delivery:
 
-1. Confirm every target `id` exactly equals the follower's `chapter.id`. Vault
-   one random value as `network_share_secret` in the follower and under
-   the target's resolved `secretName` in the leader.
+1. Confirm every target `id` exactly equals the follower's `chapter.id`. For
+   Cloudflare Workers, confirm its `binding` exists in the leader's development
+   Wrangler environment. Vault one random value as `network_share_secret` in
+   the follower and under the target's resolved `secretName` in the leader.
 2. Confirm `GET /api/admin/network/targets` lists the development follower with
    the expected compatible record types.
 3. Share one test person and one test business from the leader's record drawer.

package/dist/{copy-context-CLvhJhrF.d.ts → copy-context-Vof2eTMt.d.ts}

@@ -65,6 +65,10 @@ interface ChapterNetworkTarget {
     name?: string;
     /** Absolute follower origin, e.g. `https://chapter.example.com`. */
     url: string;
+    /** Optional Cloudflare service-binding name for Worker-to-Worker delivery.
+     * The URL still defines the signed request origin; the binding only supplies
+     * the transport when a `workers.dev` subrequest cannot enter another Worker. */
+    binding?: string;
     /** Leader-vault key holding this follower's share secret. Defaults to
      * `network_share_<id-with-underscores>`. */
     secretName?: string;
@@ -107,6 +111,7 @@ interface ResolvedNetworkTarget {
     id: string;
     name: string;
     url: string;
+    binding?: string;
     secretName: string;
     fields?: Record<string, readonly string[]>;
 }

package/dist/index.cjs

@@ -997,6 +997,7 @@ function formationFields(crm, formation) {
 // src/config.ts
 var SLUG = /^[a-z0-9][a-z0-9-]{1,62}$/;
 var FIELD = /^[a-z][a-zA-Z0-9_]*$/;
+var BINDING = /^[A-Z][A-Z0-9_]{0,127}$/;
 function resolveNetwork(config, crm) {
   const seen = /* @__PURE__ */ new Set();
   const targets = [];
@@ -1042,10 +1043,17 @@ function resolveNetwork(config, crm) {
     if (!/^[a-zA-Z][a-zA-Z0-9_-]{1,127}$/.test(secretName)) {
       throw new Error(`defineChapter.network.targets.${target.id}.secretName: must be a vault-key identifier`);
     }
+    const binding = target.binding?.trim();
+    if (binding && !BINDING.test(binding)) {
+      throw new Error(
+        `defineChapter.network.targets.${target.id}.binding: must be an uppercase Worker binding identifier`
+      );
+    }
     targets.push({
       id: target.id,
       name: target.name?.trim() || target.id,
       url: url.origin,
+      ...binding ? { binding } : {},
       secretName,
       ...fields ? { fields } : {}
     });