Prove WP Build and Studio artifacts through remote site provisioning

[chubes4]

Parent: #1970

Goal

Prove real producer artifacts from WP Build and Studio draft Automattic/studio#3952 can remotely create accepted Cloudflare WordPress sites through the public provisioning contract.

Scope

• lock one canonical portable artifact schema and encoding contract across producers/consumer
• submit representative multipage WP Build output through POST /v1/sites
• submit Studio create --from artifact output through the same API
• verify block editability, theme/assets, cold restart, publication, and subsequent edits
• produce reviewer-resolvable import reports and visual comparison artifacts
• document public URL limitations: one fetched HTML document, no implicit asset crawl

Acceptance

Both producers create isolated ready sites without adapter-specific payloads. SSI reports zero fallback blocks and visual evidence proves exact parity on desktop and mobile. All evidence links back to this tracker and the originating producer changes.

[chubes4]

Cross-repo producer contract repair is now reviewable:

• WP Build canonical SSI export: https://github.a8c.com/chubes4/wp-build/pull/1271
• WP Codebox authenticated immutable artifact staging: Add authenticated provisioning artifact staging #2002
• Studio producer/import draft CI follow-up: Route studio create --from URLs through Data Liberation studio#3952 (comment)

Verified locally:

• WP Build project export smoke passes all 34 assertions against a multipage fixture while preserving the existing WP Build round-trip contract.
• WP Codebox full Cloudflare runtime suite and TypeScript pass, including authenticated staging auth, canonical-contract rejection, digest mismatch, convergent replay, and conditional R2 race behavior.
• Both DO and D1 Worker bundle dry runs pass.
• Studio filtered Unit suite passes; focused serialized lifecycle E2E passes.

No deployment was performed. Live WP Build and Studio producer submissions, zero-fallback receipts, desktop/mobile parity, cold restart, publication, and subsequent-edit proof remain gated on explicit deployment authorization and the review/merge state of these PRs.

[chubes4]

Producer fixture progress after SSI dependency fix

The validation-runtime dependency blocker is fixed in Static Site Importer PR #709, commit 9414dc69ec8e44cf42e34a37c4db59c5b14a5331.

Exact blocker regression

Homeboy Lab run 60f5d4b3-7e9d-4bf2-9ff0-8ec339d92ec4 ran 8-local-service-business against SSI 9414dc69 and Blocks Engine 8ad978fb. The prior static_site_importer_required_runtime_dependency_missing failure is absent, and materialization advances to the later SVG-font evidence gate. That new gap is tracked in Blocks Engine #687: three generated SVG text assets require planned fonts, but none carry a self-contained font payload.

Independent canonical materialization proof

Homeboy Lab run 4d21cd30-b349-493c-bbc4-3bb8f6947b30 ran 29-multilingual-i18n against SSI 9414dc69 and fresh Blocks Engine 2adb310a6094949d206eaaaeebe43bb08d42c559.

Observed canonical receipt:

• schema: static-site-importer/materialization-receipt/v1
• status: completed
• plan hash: 89edeb63f39eab67ddc4867cee8e5e1bbb103c44b68255c1dbb857a43c930f42
• pages: 10
• files: 22
• operations: 2
• block composition: 213/213 native blocks, 0 core/html blocks

The fixture is not acceptance-complete: browser/editor/visual capture did not run because the importer quality result failed on 24 Blocks Engine preserved_runtime_island findings for navigation and forms. There is no visual-parity claim from this run. One initial Playground startup failed fetching WordPress release metadata and recovered in the isolated retry sandbox.

No Cloudflare Worker deployment was performed. Live staging/provisioning proof still requires deployment authorization for WP Codebox PR #2002.