Skip to content

Generate deterministic static registered-block source - #20

Open
noeltock wants to merge 1 commit into
mainfrom
foundry/3-generate-deterministic-static-registered-block-source
Open

Generate deterministic static registered-block source#20
noeltock wants to merge 1 commit into
mainfrom
foundry/3-generate-deterministic-static-registered-block-source

Conversation

@noeltock

@noeltock noeltock commented Sep 3, 2026

Copy link
Copy Markdown
Member

Problem

Block Runner currently produces post content. It has no artifact that WordPress can register as a reusable inserter block. Asking the model to write React, PHP, metadata, and CSS directly would recreate the invalid-markup problem at a larger and more dangerous source-code boundary. Closes #3.

Solution

Both original blockers are resolved. Parser loading now supports the package’s constructor shape, and styles are produced through a versioned declarative emitter.

Testing & verification

  • Local runnpm run typecheck → pass.
  • Local runnpm run test → pass.
  • Local runnpm run build → pass.

QA evidence

Captured 6 render checks after the CI gate — all green: scoreboard, hero-overlay, hero-split, pricing-table, testimonials, bento-grid.

All five layout comparisons are pixel-identical to main (this change alters generator source, not the recorded benchmark renders), so only the scoreboard is shown. The full set is retained on the factory host.

Benchmark scoreboard at PR head — 17 recorded runs

Risk / rollout

Small, targeted change — see the diff for the affected paths.


Built by 🪺 Rookery · flight #44 · 56m38s · 3 passes · gpt-5.6-terra·xhigh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Generate deterministic static registered-block source

1 participant