Import a pinned static website artifact into the Cloudflare runtime

[chubes4]

Parent: #1970

Goal

Prove one canonical SSI/WP Build website artifact can be remotely materialized into the existing default Cloudflare WordPress site as editable content through the canonical lease/MDI/R2 transaction.

Scope

• package a pinned, digest-verified Static Site Importer runtime and required dependencies
• add an authenticated bounded artifact-import operation accepting an R2 reference plus SHA-256
• invoke static-site-importer/import-website-artifact inside the existing coordinator lease
• persist MDI changes, uploads, generated theme files, options, and import provenance
• commit one canonical revision and publish affected routes
• return a structured SSI report and canonical receipt

Acceptance

A representative multipage artifact imports with zero fallback blocks and exact visual parity, remains editable in Gutenberg, survives cold restart, serves assets from R2, publishes routes, rejects malformed/oversized/digest-mismatched inputs, and preserves idempotency and lease conflict behavior.

[chubes4]

Upstream root cause is confirmed and dispatched. SSI 1.3.3 bundles Blocks Engine PHP transformer 0.4.5, which emits duplicate slug: index values for wrapper-root nested index documents. The SSI receipt creates two posts, but MDI correctly projects both into the same page/index/index.md identity; publication routes /index/ and /index/index/ are consequences of the defective site plan.

Tracking and repair:

• Blocks Engine root cause: Align WordPress site-plan page slugs with nested index routes blocks-engine#681
• Blocks Engine fix: Align nested index page slugs with canonical routes blocks-engine#682
• SSI release handoff: Ship canonical nested-index page identity from Blocks Engine static-site-importer#702

The #1975 branch remains intentionally uncommitted/unpublished until a public pinned SSI artifact contains the upstream route+slug contract and the DO/D1 multipage gates pass against it.

[chubes4]

Upstream route identity repair Automattic/blocks-engine#682 is merged at 6709ac7f911207f222b40b8cb01c73d505aa7fb8; all CI and solved-site promotion gates passed.

#1975 now waits on the tracked package handoff in Automattic/static-site-importer#702: publish a Blocks Engine PHP transformer release containing #680/#682, consume it in SSI with WordPress materializer coverage, then publish the immutable SSI archive that this Cloudflare branch can pin and verify through DO/D1 multipage gates.

[chubes4]

Implementation PR: #1980

The upstream-to-downstream chain is now complete:

• Blocks Engine nested-index identity fix Emit generic agent fanout progress events #682, released as PHP Transformer 0.4.6
• SSI dependency/materializer proof Expose generic host delegation seam for server-side workspace offload #703, released as SSI 1.3.4
• WP Codebox import transaction and static-front-page publication reconciliation Import static artifacts into Cloudflare WordPress #1980

Verification on 7b3781b6:

• npm run test:cloudflare-runtime passes 25/25 plus TypeScript checking.
• npm run cloudflare:local-gate passes the complete multipage import/publication/restart proof with Durable Object coordination.
• npm run cloudflare:local-gate:d1 passes the identical proof with D1 coordination.

Both page IDs survive canonical reconstruction and remain editable; quality counts are all zero; / and /about/ promote to coordinator-free R2 publication; replay/conflict and broader authenticated runtime workflows pass.

[chubes4]

Production deployment evidence on 2026-07-24:

• Deployed merged main revision 6552a47c3d00c4d9d380efc81e682b81d5806b92 through Homeboy as Worker version aa0c5b5c-db2c-4859-9d8a-8fcf858fc26a; health, D1 state, existing publication, and exact R2 runtime-artifact gates passed.
• Staged a 27,477-byte, five-page blocks-engine/php-transformer/site-artifact/v1 learner corpus at SHA-256 9c533f8a78630d830be70e8898cb46b42eba6a37b21c7c4151e7fd49d813addf.
• The identical artifact imports locally through SSI 1.3.4 with five editable pages and zero fallback, core HTML, freeform, or invalid blocks.
• Production operation ccea2c23-8f80-4bc4-a37a-dcb5a21049a9 reaches booting-runtime (20%) and is terminated by Cloudflare with outcome: exceededMemory before SSI executes. Three claims reproduce the same result; no canonical commit or publication occurred.

This is now the remaining owning-layer blocker for #1975: reduce the dedicated SSI runtime boot below the 128 MB isolate limit while preserving content-addressed verification and complete plugin behavior. The existing public site remains intact.

[chubes4]

Production recovery update:

• Deployed exact WP Codebox revision 7eab0401b72434141d2b1529c27016024687fcfb through Homeboy as Worker version 2dc9d0ba-9a24-4534-afe6-40b254fcaa2d. Health, D1 state, and existing-publication gates passed.
• Operation ccea2c23-8f80-4bc4-a37a-dcb5a21049a9 reached succeeded/100%. Publication revision 9c712153-bc56-4cd3-ba1c-8f484a8a95c8 is active from R2. This proves both the SSI memory repair and permanent-redirect publication recovery in production.
• The learner is not exact acceptance evidence yet: / serves the API document and nested pages redirect under /index/website/. Direct php-transformer reproduction shows every nested */index.html was inferred as an entrypoint and routed to /. The owning-layer defect is tracked at Nested index pages are all promoted to artifact entrypoints blocks-engine#691.
• WP Codebox repair PR: Reduce Cloudflare SSI runtime memory #2013

I am keeping #1975 open until the upstream entrypoint repair is shipped into SSI/WP Codebox and all five intended public routes verify from immutable publication storage.