@volter/twin-cloudflare 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,223 @@
+# @volter/twin-cloudflare
+
+Local, deterministic Cloudflare API v4 **control-plane** twin for generic account/zone discovery,
+remotely managed Cloudflare Tunnel provisioning, tunnel configuration/token retrieval, a bounded
+zone DNS-record control-plane slice, and the **Workers provisioning plane** a wrangler-shaped or
+raw-API deploy script drives: Worker script upload (metadata + bindings recorded, content
+fingerprinted, never executed), static-assets upload sessions (hashes and sizes recorded, bytes
+never kept), versions and deployments, script settings, cron triggers, workers.dev subdomains,
+zone routes, custom domains, Durable Object namespace records, R2 bucket control plane,
+Hyperdrive configuration records, and Queues with consumers. An unmodified `wrangler deploy` —
+first deploy and redeploy — completes against it. State is persisted through the shared `@volter/world-core` kernel.
+The pack never opens a real tunnel, publishes DNS, executes a Worker, stores an object, dials an
+origin, contacts Cloudflare, or embeds an application-specific workflow.
+
+```bash
+bun packages/twin/cloudflare/src/cli.ts serve
+```
+
+Point the official `cloudflare` TypeScript SDK at the printed loopback URL with any non-empty local
+token and `maxRetries: 0`. The integration test uses the SDK unchanged; only its public `baseURL`
+option is set.
+
+## Modeled surface
+
+Cloudflare accounts and zones normally pre-exist the workflow under certification. Seed them using
+the disclosed twin-only endpoint:
+
+```http
+POST /twin/bootstrap
+Authorization: Bearer local
+Content-Type: application/json
+
+{
+  "accounts": [{ "id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "name": "Acme" }],
+  "zones": [{ "id": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", "account_id": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "name": "example.test" }]
+}
+```
+
+The vendor-shaped endpoints are:
+
+- accounts: list/get;
+- zones: list/get, including `name` and `account.id` filters;
+- `/accounts/{account_id}/cfd_tunnel`: list/create/get/edit/delete;
+- tunnel configuration: get plus a locally useful put slice and tunnel token retrieval. The
+  official PUT includes broad nested `originRequest` schemas that are not fully validated here,
+  so that whole OpenAPI operation remains a manifest todo;
+- `/zones/{zone_id}/dns_records`: list/get/delete plus locally useful create/put/patch support for
+  CNAME, address, text, and structured CAA-shaped certification records. Because Cloudflare's three
+  write operations are discriminated unions spanning many more record schemas, those whole OpenAPI
+  operations remain manifest todos; the pack does not claim complete union fidelity;
+- **Workers scripts**: `/accounts/{account_id}/workers/scripts` list, script download, delete
+  (honoring the pinned OpenAPI `force` contract: without `force=true` a delete is stopped by
+  associated Durable Object namespaces or service bindings), plus the `PUT` module upload itself.
+  The upload accepts all three wire forms an unmodified client actually produces: raw
+  multipart/form-data with a JSON `metadata` part (wrangler / raw API), the official SDK's
+  FormData serialization (bracket-notation `metadata[...]` parts under the operation's
+  `application/javascript` content type — measured against `cloudflare@7.1.0`), and a raw
+  service-worker-syntax script body. Module content is recorded and SHA-256-fingerprinted into
+  the `etag`, never executed, parsed, or run. Because the full multipart metadata union (38
+  binding kinds, assets, placement, limits, observability) is far broader than the implemented
+  deploy slice, the whole `PUT` operation honestly remains a manifest todo (the same rule as the
+  DNS write unions) even though every worker-seeding verify drives it. The implemented binding
+  slice validates the closed binding-kind union and the deploy-critical kinds
+  (`plain_text`/`secret_text`/`json`/`kv_namespace`/`service`/`r2_bucket`/`queue`/`hyperdrive`/
+  `durable_object_namespace`), including referential checks against this twin's own R2 buckets,
+  queues, and Hyperdrive configs; other known kinds are recorded as configuration without deep
+  validation. Durable Object `migrations` (new/new_sqlite/deleted/renamed classes, old/new tag
+  matching, multi-step `steps`) materialize namespace records; `transferred_classes` fails loudly
+  as unmodeled;
+- **what `wrangler deploy` drives around the upload**:
+  `GET /accounts/{account_id}/workers/services/{service_name}` — the Worker-as-service view
+  wrangler reads first (`default_environment.script.{tag,tags,migration_tag,last_deployed_from}`),
+  answering `10007` for a Worker that does not exist yet. That path is **not in the pinned
+  OpenAPI**, so it is served but carries no manifest capability; its shape is grounded in what
+  Cloudflare's own client (wrangler's deploy helpers) reads from it. `last_deployed_from` is
+  `wrangler` when the upload's User-Agent is wrangler's, `api` otherwise. A missing account
+  workers.dev subdomain answers `10007`, the code wrangler's register-or-fail branch keys on — so
+  a deploy that wants `workers.dev` needs the account subdomain registered first (`PUT
+  /accounts/{account_id}/workers/subdomain`), exactly as on a real account;
+- **static assets**: `POST …/scripts/{script_name}/assets-upload-session` answers `{jwt, buckets}`
+  naming only the hashes the account does not already hold (at most 10 per bucket — a twin
+  convention; the spec does not pin the partition); `POST …/workers/assets/upload?base64=true`,
+  authenticated by that session token rather than the API token, checks each part's decoded
+  size against the manifest, records the asset's hash, size and content type — **never its
+  bytes**, since no vendor read endpoint returns them — and returns the completion token once
+  every hash is held. The manifest hash is wrangler's blake3 over base64 content plus extension;
+  the twin does not recompute blake3 and trusts the declared hash. The script upload redeems
+  `metadata.assets.jwt` (issued for this account and Worker, every hash uploaded), records the
+  manifest and the assets config (`run_worker_first`, `html_handling`, …) as configuration,
+  honours `keep_assets`, and refuses an `assets` binding with no assets. The single-file
+  Edge-KV upload path (`…/assets/upload/{hash}`) is not served: the twin's tokens never enable it;
+- **versions and deployments**: every script `PUT` is a new version deployed at 100% and answers
+  `deployment_id` (the version id wrangler prints as "Current Version ID"). A redeploy with no
+  pending migration takes wrangler's versions path: `POST …/versions` uploads a version without
+  deploying it (Durable Object migrations refused — Cloudflare migrates only on deploy; `inherit`
+  bindings resolved from the deployed version, refused under `bindings_inherit=strict` when there
+  is nothing to inherit), `POST …/deployments` records a one- or two-version percentage split and
+  makes the larger share the live content (the split is recorded, never routed), and
+  `PATCH …/script-settings` records logpush, tags, tail consumers and observability. `GET
+  …/deployments`, `GET …/versions` and `…/versions/{version_id}`, `GET …/settings` (the deployed
+  bindings and runtime), `GET …/script-settings`, and `GET …/secrets` / `…/secrets/{secret_name}`
+  read it back; secret values are write-only and never echoed. `POST …/versions` carries the same
+  multipart metadata union as the script `PUT` and stays a manifest todo for the same reason;
+  `worker_loader` bindings are recorded as configuration like the other non-deploy-critical kinds;
+- **cron triggers / subdomains / routes / domains**: script `schedules` get/put (5-field cron
+  validation), per-script workers.dev subdomain get/post/delete, the account-level Workers
+  subdomain get/put/delete (204), zone `workers/routes` CRUD, and `workers/domains`
+  attach/list/get/detach — domain attach resolves the hostname against this twin's zones and
+  requires the referenced Worker to exist, composing with the existing zone and DNS slices;
+- **Durable Object namespaces**: `/accounts/{account_id}/workers/durable_objects/namespaces`
+  list, populated exclusively by script-upload migrations (Cloudflare has no direct
+  namespace-create endpoint);
+- **R2 buckets** (control plane ONLY): create/list/get/delete with the vendor's documented name
+  pattern, `locationHint`/`storageClass` enums, and the `cf-r2-jurisdiction` header recorded.
+  The **object data plane is explicitly out of scope**: no object upload/get/list, no
+  presigned URLs, no CORS/lifecycle/sippy — a bucket here is a provisioning record, not storage;
+- **Hyperdrive configs**: create/list/get/put/patch/delete over the three official origin shapes
+  (public database, Access-protected, Workers VPC). The origin connection is **recorded as
+  configuration and never dialed**; `password`/`access_client_secret` are writeOnly per the
+  vendor schema and are never echoed back;
+- **Queues**: queue create/list/get/delete and consumer create/list/get/put/delete over the
+  official worker/http_pull consumer union with per-type settings validation. A queue's
+  `producers` list is computed from Worker uploads whose bindings declare `type:"queue"` —
+  producer bindings are configuration, not message flow. Queue messages, purge, metrics, and
+  subscriptions stay manifest todos (data plane).
+
+Responses use Cloudflare's API v4 `{success, errors, messages, result, result_info?}` envelope.
+Writes honor the kernel's read-only mode. Deletes are projected as tombstones, and deterministic ID
+allocation scans tombstones so delete/recreate cannot resurrect stale state.
+
+## Control plane, not infrastructure
+
+The tunnel object, ingress configuration, token, DNS record, Worker script record, bucket,
+Hyperdrive config, and queue are local control-plane data. The twin does **not** run
+`cloudflared`, connect to Cloudflare's edge, resolve DNS, propagate records, issue certificates,
+provide a publicly reachable hostname, **execute a Worker, evaluate a cron trigger, serve a
+route, store or serve an R2 object, dial a Hyperdrive origin, or move a queue message**. Those
+are intentionally real-world certification steps and never manifest capabilities — a twin is a
+deterministic, offline model of the API contract, and the tunnel/DNS infrastructure legs are what
+the real root does. The provisioning slice's data planes (R2 objects, queue messages) are todos.
+
+Cloudflare is API-first for this use case. Its dashboard is incidental administration UI, so this
+pack has no mirror and no UI capability claims.
+
+## Connector and budget
+
+All optional real I/O crosses the injected `CloudflareExecute` function. Pull walks every
+`result_info.total_pages` page for accounts and zones, then every tunnel page per observed account,
+one configuration read per remotely managed tunnel, and every DNS-record page per observed zone.
+It validates required vendor fields before folding all five resource types through the kernel observation path,
+tombstones previously vendor-observed resources absent from a later inventory only when pagination
+metadata proves that inventory complete (metadata-free observations never delete state), rejects anything
+other than a `success:true` envelope, and is idempotent for identical observations. Push translates
+only the modeled local actions, preserves PUT-versus-PATCH replacement semantics and
+Cloudflare-returned tunnel/DNS IDs across dependent
+actions and retries, and confirms each only after a successful response with the required result
+identity; unknown actions fail loudly.
+
+The only live executor, `liveCloudflareExecute`, checks a persistent `CloudflareBudget` before every
+fetch. Cloudflare documents a global 1,200 requests per five minutes per user/account token. This
+pack deliberately uses a tighter fallback-sized ceiling of 60 weighted units per minute: reads cost
+2 (30/minute), mutations cost 3 (20/minute), and `429 Retry-After` establishes a persistent
+cooldown. No live call is made by the tests or capability probes.
+
+## Error-code provenance for the provisioning slice
+
+The pinned OpenAPI declares only a **generic 4XX error envelope** for the Workers/R2/Hyperdrive/
+Queues operations, so specific numeric error codes are not pinned by it. This pack uses
+Cloudflare's widely observed codes where they are well known — `10007` (script not found, and a
+missing account workers.dev subdomain — the code wrangler branches on for both),
+`10006` (R2 bucket does not exist), `10004` (R2 bucket already exists) — and the pack's generic
+conventions (`1004` validation, `1001` not found, `1003` conflict) everywhere else. Statuses and
+envelopes are spec-grounded; the numeric codes outside the three above are conventions, stated
+here rather than dressed up as vendor facts.
+
+## Coverage denominator
+
+The vendor denominator is the exact **3,334 HTTP operations across 2,077 paths** in the pinned
+first-party OpenAPI document: one manifest entry per method + path, with no namespace sentinels or
+mixed granularity. The committed census is mechanically generated by
+`scripts/generate-operation-census.ts`; the manifest separately records fourteen connector
+capabilities. The Workers provisioning slice proves 51
+additional operations done (Workers scripts/schedules/subdomains/routes/domains, static-assets
+upload session and upload, versions and deployments, script settings and secrets listing,
+Durable Object namespace listing, R2 bucket control plane, Hyperdrive configs, Queues +
+consumers), each with a
+failable fresh-root verify asserting response values from a fresh root, and driving the negative
+4xx or not-found path its title implies wherever the operation has a reachable one. The official SDK's **121** top-level resource
+namespaces remain a separately asserted cross-check, never a substitute for the operation
+denominator. This intentionally produces about 1% initial coverage rather than letting the
+implementation define its own denominator.
+
+See `src/cloudflare-capabilities.ts` for the complete manifest and generated repository docs for
+the measured counts.
+
+## Official grounding
+
+Grounding was inspected on 2026-08-21 (provisioning slice re-read 2026-08-23 from the same
+pinned commits) from only Cloudflare-maintained sources:
+
+- `cloudflare/api-schemas`, OpenAPI 4.0.0 at commit
+  `2ac8369e9b63dccacee1a2284e95bb819f05b307`;
+- `cloudflare/cloudflare-typescript` at commit
+  `faaaf89ed8064a9fb54de538ec3e89487f1302b0` and npm `cloudflare@7.1.0`;
+- Cloudflare's official API rate-limit reference:
+  <https://developers.cloudflare.com/fundamentals/api/reference/limits/>.
+
+The OpenAPI supplied the complete 3,334-operation census plus the account, zone, `cfd_tunnel`,
+tunnel configuration/token, DNS-record, Workers, R2, Hyperdrive, Queues, and Durable Object
+paths and request schemas (including the script-name and bucket-name patterns and the script
+delete `force` contract). The official SDK supplied the namespace census, structured DNS unions
+(including `data`-shaped CAA records), PUT-versus-PATCH semantics, tunnel filter/secret
+contracts, the Workers binding-kind and queue-consumer unions, the response shapes for the
+provisioning slice, the SDK's actual multipart serialization for script uploads (measured on the
+wire during this build), and the unchanged loopback client contract. No third-party Cloudflare
+wrappers or application code were used as behavioral truth.
+
+**No live probe was possible for any slice of this pack — there is no Cloudflare account to
+probe.** The pinned first-party OpenAPI document plus the pinned official SDK are the honest
+grounding ceiling: paths, envelopes, request schemas, pagination, and closed enums/unions are
+spec-grounded; behavior the spec leaves open (specific 4xx codes, uniqueness-conflict statuses,
+cross-resource referential checks on bindings/domains/consumers) is a documented convention of
+this twin, not a verified vendor observation.

package/dist/r2/src/endpoint.d.ts

@@ -0,0 +1,14 @@
+/** The jurisdictions an endpoint may name (Data location, "Available jurisdictions": eu, fedramp, us). */
+export declare const JURISDICTIONS: Set<string>;
+/** The account, the jurisdiction and, for a virtual-hosted request, the bucket an S3 endpoint host names:
+ *  `<ACCOUNT_ID>.r2.cloudflarestorage.com`, `<ACCOUNT_ID>.<JURISDICTION>.r2.cloudflarestorage.com` ("you must specify the
+ *  jurisdiction in your S3 endpoint", https://developers.cloudflare.com/r2/reference/data-location/), each with a bucket in
+ *  front for the virtual-hosted form R2's presigned-URL page shows its SDKs producing. */
+export declare function endpointOf(host: string): {
+    account: string;
+    jurisdiction: string;
+    bucket?: string;
+} | undefined;
+/** A request URL in path-style form: a virtual-hosted one (`https://<bucket>.<ACCOUNT_ID>[.<JURISDICTION>].r2.cloudflarestorage.com/<key>`)
+ *  becomes `https://<ACCOUNT_ID>[.<JURISDICTION>].r2.cloudflarestorage.com/<bucket>/<key>`; any other URL is unchanged. */
+export declare function pathStyle(url: string): string;

package/dist/r2/src/endpoint.js

@@ -0,0 +1,30 @@
+// Where an S3 request to R2 is addressed: the account, the jurisdiction and, for a virtual-hosted request, the bucket its
+// host names, and the same request in path-style form. The lane's router (fetch.ts) and the tools that read its answers
+// (SHAPE, the example replay: manifest.ts exports pathStyle) share this one rule.
+import { R2_ENDPOINT_SUFFIX } from "../../src/cloudflare-r2.js";
+/** The jurisdictions an endpoint may name (Data location, "Available jurisdictions": eu, fedramp, us). */
+export const JURISDICTIONS = new Set(['eu', 'fedramp', 'us']);
+/** The account, the jurisdiction and, for a virtual-hosted request, the bucket an S3 endpoint host names:
+ *  `<ACCOUNT_ID>.r2.cloudflarestorage.com`, `<ACCOUNT_ID>.<JURISDICTION>.r2.cloudflarestorage.com` ("you must specify the
+ *  jurisdiction in your S3 endpoint", https://developers.cloudflare.com/r2/reference/data-location/), each with a bucket in
+ *  front for the virtual-hosted form R2's presigned-URL page shows its SDKs producing. */
+export function endpointOf(host) {
+    if (!host.endsWith(R2_ENDPOINT_SUFFIX))
+        return undefined;
+    const labels = host.slice(0, -R2_ENDPOINT_SUFFIX.length).split('.');
+    const jurisdiction = labels.length >= 2 && JURISDICTIONS.has(labels.at(-1)) ? labels.pop() : 'default';
+    const account = labels.at(-1);
+    if (!/^[0-9a-f]{32}$/.test(account))
+        return undefined;
+    return labels.length === 2 ? { account, jurisdiction, bucket: labels[0] } : labels.length === 1 ? { account, jurisdiction } : undefined;
+}
+/** A request URL in path-style form: a virtual-hosted one (`https://<bucket>.<ACCOUNT_ID>[.<JURISDICTION>].r2.cloudflarestorage.com/<key>`)
+ *  becomes `https://<ACCOUNT_ID>[.<JURISDICTION>].r2.cloudflarestorage.com/<bucket>/<key>`; any other URL is unchanged. */
+export function pathStyle(url) {
+    const u = new URL(url);
+    const endpoint = endpointOf(u.hostname.toLowerCase());
+    if (!endpoint?.bucket)
+        return url;
+    const host = `${endpoint.account}${endpoint.jurisdiction === 'default' ? '' : `.${endpoint.jurisdiction}`}${R2_ENDPOINT_SUFFIX}`;
+    return `${u.protocol}//${host}${u.port ? `:${u.port}` : ''}/${endpoint.bucket}${u.pathname === '/' ? '' : u.pathname}${u.search}`;
+}

package/dist/r2/src/fetch.d.ts

@@ -0,0 +1,7 @@
+import { type DerivedFetch } from '@volter/world-core';
+export type R2LaneOptions = {
+    root?: string;
+    readOnly?: boolean;
+    clock?: () => string;
+};
+export declare function createR2LaneFetch(options?: R2LaneOptions): DerivedFetch;