@volter/twin-cloudflare

Cloudflare

Version

volter-aiVolter maintainedSelected defaultv3.0.11

Local Cloudflare DNS, R2 and Worker deployment configuration. Worker programs are not executed; static asset behavior and API limits are documented in the README.

Use Cloudflare in a World

Keep your app’s real SDK. The World routes this vendor’s configured calls to the selected twin.

Read workflows and limitations Run this twin in your app

Release measurements

HTTP operations served: 80 / 36933613 declared gaps
HTTP operations exercised: 74 / 3693API journey coverage
Installed first use: Not measuredExact release journey

Measurements describe this release’s recorded scope. Open Evidence for replay, browser results and unexercised operations.

Set up this release

Use Node 22.6 or newer. Install the CLI, then the exact packages shown alongside:

npm install -g @volter/world@3.0.108

In your app’s folder, initialize a World with this implementation:

volter world init --name my-app --twins cloudflare --source cloudflare=@volter/twin-cloudflare

Review the detected vendor and retain the generated bindings. The cloudflare service’s source must select this version:

{
  "source": {
    "package": "@volter/twin-cloudflare",
    "version": "3.0.11"
  }
}

This is the source field, not a complete config. Keep the installed version, lockfile and generated service source in agreement. Use the release README for throwaway SDK credentials, seeds and limits.

Run your app’s own test command inside the World:

volter world up
volter world run -- npm test
volter world log
volter world down

down stops compute and retains state.

Bring an existing app Recover a failed call Trial an update

Versions and implementations

Package / version	Publisher	Status	First use
@volter/twin-cloudflare3.0.11	volter-ai	Selected default	Not measured

Evidence for 3.0.11

Installed first use · Not measured

Installed first use was not measured for this release. HTTP coverage and publisher trust do not establish this result.

API coverage, replay and browser measurements

Counts describe the declared HTTP surface, not separate command tables or other protocols. Consult the release README for those workflows.

Assessment scope: packaged-customer-journey; in-process
Declared HTTP surface: 80 served · 3613 gaps · 3693 declared operations
Exercised HTTP operation coverage: 74 / 3693 declared operations (2%)
Journey steps: 268 answered / 292 steps
Replay: Equal across 2 runs
Journey failures: 0
Browser target: HTTP customer journey replay through Chromium at each request origin; authored HTTP headers and observed wire responses 153.0.8010.12
HTTP operations exercised through Chromium: 74 / 3693 declared operations (2%)
Chromium journey replay: Equal across 2 runs
Browser response observation: Transport observes status, headers and body, including redirects and Set-Cookie; these are not JavaScript-visible response claims
Application-origin CORS coverage: Not measured
Native cookie-jar coverage: Not measured
DOM coverage: Not measured
Source code coverage: Not measured
State transition coverage: Not measured

Operations not exercised

Conformance results

decided: 0 failures · every served operation is decided with its demand; every demanded and every refreshed operation is served
published: 0 failures · what a release publishes holds every unit: its manifest, its spec and its journeys
cited: 0 failures · every vendor fact cited is recorded as a page that answered, each quote found on it
refresh: 0 failures · every stored resource of a vendor-backed unit declares how it is read back, and a unit that sends events ingests the vendor's
registered: 0 failures · a vendor-backed unit, lane or not, reaches the registered pack's state system
allowance: 0 failures · a rate budget above the fallback rests on the vendor's documented allowance, cited in its manifest
client: 0 failures · driven by the vendor's own client (its official SDK), served as a World runs it, the vendor's documented behaviour holds · 3 case(s) through the vendor's client
life: 0 failures · the life walked over HTTP against the pack served as a World runs it, with its scenario: every check held
standalone: 0 failures · served by its server.ts as a World runs it, the pack answers HTTP and the boot probe, and each declared socket upgrades

Publisher, admission and provenance

Publisher: volter-ai/twin-packs-open
Source commit: ef7378d7523ac2c449ccecff170e7ee79aa9234e
Catalog record commit: 5a79cd1c2f34cba223f6b629d546c0c940215752
Package integrity: sha512-8JrSDMxmxzNy4Qkf4dLeaAU24tGDcW98vcjswh2XZLaGOjqWpxScT8IISWieaKz28wY4Om/xARADJZUrRlSdFg==
Admission mode: Trusted internal publisher · maintainer merge
Catalog assessment: Bundled report checksum verified
Assessed at: Not recorded
Assessment input head: 60192bada89306dd4a304b73f687f78aa6b4ba6c
Evidence: Assessment and admission

Read the catalog snapshot

Install this version

npm install --save-dev --save-exact \
  @volter/world-core@3.0.108 \
  @volter/twin-cloudflare@3.0.11

In your app’s folder. Full setup guide

License: Apache-2.0
Node: >=22.3
World kernel: ^3.0.68