Generated-site replay blueprints should contain the portable site artifact, not generation runtime activation

[chubes4]

Problem

The blueprint.after.json emitted by WP Codebox during Studio Web Workflow Bench proof run studio-web-data-machine-diagnostic-20260613-viewer-proof-r25 was fetchable as JSON, but it only contained runtime/plugin activation state:

• setSiteOptions.active_plugins for generation-time plugins like agents-api, data-machine, wp-codebox, frontend-agent-chat, ai-provider-for-openai, and studio-web
• login

It did not include the generated website content/state needed to open the generated result in WordPress Playground.

For reviewer-facing generated-site previews, the artifact should be a portable replay of the generated WordPress site, not a snapshot of the agentic runtime stack that produced it.

Expected behavior

WP Codebox should emit a blueprint.after.json or blueprint.zip that can be passed to:

https://playground.wordpress.net/?blueprint-url=<public blueprint artifact URL>

and open directly to the generated WordPress site.

Acceptance criteria

• Generated-site replay includes the site content/state needed to view the generated result in Playground.
• The replay artifact excludes generation-time-only plugins unless required to render the result.
• If additional files are required, emit a blueprint.zip or equivalent archive that Playground can fetch and apply.
• The artifact contract distinguishes runtime snapshot/diagnostic blueprints from reviewer-facing generated-site replay blueprints.
• Add a smoke test that fetches the emitted blueprint through a public URL and verifies Playground-compatible content/state is present.

Evidence

The observed blueprint only activated runtime plugins and logged in; opening it in Playground would not show the generated Data Machine landing page produced by the Studio Web run.