cloud

status → amber

ci → green (protected master run 29415119568: backend/UI tests, coverage ratchet, linux/amd64 image build, live container health, and staging/production Wrangler dry-runs all passed)

deploy → Cloudflare Worker + Container contract is dispatch-deployable for staging/production; production traffic remains gated on Cloudflare-native durable persistence

Closed: CLOUD-1

Cloud master 04f35ef replaces the GHCR placeholder with a typed Worker, Durable Object container binding, pinned Bun image, and real cloudflare/wrangler-action deployment workflow.

CI builds the runtime image on every push and pull request, starts it, and verifies GET /health before validating both Wrangler environments.

GitHub Packages remains the registry for @frauthy/* SDK artifacts. Cloudflare's integrated container registry owns runtime images.

The hosting decision is Cloudflare-only. Container-local DuckDB is explicitly ephemeral; the next deployment lane migrates control-plane and APM persistence to Cloudflare-hosted durable services before production traffic.

Program-wide

Runtime hosting decisions are now standardized on Cloudflare. Provider-specific deployment and persistence requirements should use Cloudflare primitives; prior Kubernetes/AWS/provider-selection placeholders are no longer authoritative.