Provision editable Cloudflare WordPress sites from static artifacts

[chubes4]

Goal

Expose a remote API that accepts a bounded static website artifact, provisions an isolated Cloudflare WordPress site, materializes it as editable Gutenberg content through Static Site Importer, persists canonical state through MDI/D1/R2, publishes immutable routes, and returns a durable operation receipt plus site URL.

Architecture

• one shared Worker with hostname-derived site identity
• shared D1 registry/coordinator with strict site_id isolation
• shared R2 bucket with sites/{siteId}/... namespaces
• Static Site Importer owns artifact validation, Blocks Engine compilation, WordPress site-plan materialization, and import reports
• WP Codebox owns authentication, bounded artifact transport, coordinator leases, canonical persistence, publication, and lifecycle receipts

Tracked slices

• Fence Cloudflare mutations for lossless D1 cutover #1976
• Import a pinned static website artifact into the Cloudflare runtime #1975
• Scope Cloudflare WordPress state by site identity #1972
• Add a durable Cloudflare site registry and operation lifecycle #1973
• Expose an authenticated idempotent Cloudflare site provisioning API #1971
• Prove WP Build and Studio artifacts through remote site provisioning #1974

Dependency order

1. Finish lossless D1 activation (Fence Cloudflare mutations for lossless D1 cutover #1976).
2. Prove SSI import in the existing single-site transaction (Import a pinned static website artifact into the Cloudflare runtime #1975).
3. Generalize all state and caches by site identity (Scope Cloudflare WordPress state by site identity #1972).
4. Add durable resumable lifecycle records (Add a durable Cloudflare site registry and operation lifecycle #1973).
5. Expose the authenticated provisioning API (Expose an authenticated idempotent Cloudflare site provisioning API #1971).
6. Prove producer interoperability and acceptance (Prove WP Build and Studio artifacts through remote site provisioning #1974).

Acceptance

A remote POST /v1/sites with a digest-verified WP Build/SSI website artifact returns 202, progresses through a durable operation, and produces an isolated hostname whose pages are editable Gutenberg blocks, survive cold restart, publish through R2, and support subsequent canonical N+1 edits. Repeated idempotency keys create nothing twice; concurrent sites cannot read or mutate one another. Generated-site acceptance requires zero fallback blocks and exact visual parity.

Existing foundations

• Persist Worker WordPress state with MDI, R2, and Durable Objects #1863 canonical MDI/R2/Worker state
• Adopt exact coordinator state for Durable Object and D1 cutovers #1968 exact coordinator-state adoption
• Static Site Importer artifact and blocks-engine/wordpress-site-plan/v2 contracts
• Studio draft Experiment: create Studio sites from static artifacts studio#3952

This parent issue tracks the complete program; implementation remains split into independently reviewable child issues.

[chubes4]

Static artifact import slice #1975 is implemented in PR #1980 after upstream fixes/releases in Automattic/blocks-engine#682 (PHP Transformer 0.4.6) and Automattic/static-site-importer#703 (SSI 1.3.4). Production-shaped Durable Object and D1 multipage gates both pass, including canonical reconstruction, Gutenberg editability, and R2 publication.

[chubes4]

Foundation update:

• Static artifact import PR Import static artifacts into Cloudflare WordPress #1980 merged at 0a4ffd6152a3d577f51ccaeb78f242037ce3c96d.
• Lossless cutover fence PR Fence Cloudflare coordinator cutovers #1977 merged at 5ef860bac743cc718051498ee58d0b6f1ca697a7.
• Their combined main composition passed the 25-contract runtime/type suite and complete Durable Object + D1 local gates, including active-fence conflicts, anonymous R2 reads, SSI 1.3.4 multipage import, canonical reconstruction, Gutenberg editability, and / + /about/ publication.

No production deployment or D1 cutover has occurred. #1975 remains open for its explicit visual-parity acceptance evidence; #1976 remains open for provision/deploy/adopt/N+1/rollback operator evidence.