@agent-os/deploy-cloudflare
Purpose
Section titled “Purpose”Cloudflare Worker deploy material and provider implementation for
@agent-os/deploy.
Invariant
Section titled “Invariant”Worker script/modules and Worker manifest live inside deployable artifact
material resolved from artifactRef. Staging facts keep only symbolic
artifactRef, routeRef, and digest; they do not grow Worker-specific
manifest fields. Cloudflare account IDs, route URLs, tokens, and provider
handles stay out of manifest refs and ledger-visible projections.
Minimal Usage
Section titled “Minimal Usage”Resolve a staged artifactRef to a CloudflareWorkerDeployBundle, validate
the bundle digest, and use makeCloudflareWorkerDeployCarrier to emit symbolic
deploy refs while raw Cloudflare material stays resolver-side.
Use makeCloudflareWorkerDeployResolverComposition to adapt a kernel
RefResolver into the provider-specific resolver contract: credentials,
Cloudflare resources, bindings, and production endpoints stay material refs;
artifact bundle lookup stays in the staging artifact resolver.
The stable Worker webapp route composes bounded workspace exec, staging
artifact publication, Cloudflare Worker resource material, deploy promotion,
readback, rollback, and UI endpoint lookup without adding trycf or background
session-process semantics. Deploy/promote orchestration relies on the a44
durable trigger claim-token/redrive substrate; the provider does not implement
its own retry ledger.
import { cloudflareWorkerDeployBundleDigest } from "@agent-os/deploy-cloudflare";Verification
Section titled “Verification”cd packages/providers/deploy-cloudflarevp test runLive Cloudflare deploy smoke is opt-in and must not commit provider material or raw URLs.