Agent Composer v1.2.4 – Fixed rendered preview assets

SmartCloud Agent Composer 1.2.4

Rendered previews

• Return sanitized rendered frontend HTML without Gutenberg serialization comments.
• Recreate the frontend body and WordPress content wrappers inside the isolated preview.
• Preserve approved Gutenberg inline styles and prioritize explicitly selected theme stylesheets.
• Keep long pages and warning lists inside bounded scrolling areas.

Private preview assets

• Flatten bounded local CSS imports.
• Deliver approved local stylesheet images and WOFF/WOFF2 fonts through private, revision-bound MCP resources.
• Enforce path, MIME type, file signature, size, import-depth, cycle, and total asset-count limits.
• Omit external, unsupported, or unsafe resource-loading constructs.
• Keep exact revision-bound assets readable after proposal submission or closure.

Performance and compatibility

• Cache authorized revision-bound asset maps for 30 minutes.
• Deduplicate repeated preview deliveries and limit concurrent private asset calls.
• Deliver ordered preview CSS through a single private resource.
• Publish the current viewer under the v5 resource URI while retaining v1-v4 compatibility aliases.

Proposal safety

• Proposal submission now requires the exact short-lived token returned by the final rendered-preview operation.
• The token is bound to the agent, proposal, and exact revision.
• Human merge and rejection operations remain separate and do not use the agent preview token.

Blueprints

• Enabled governed update proposals for the homepage and product pages.
• Added the published homepage Playground CTA to the approved pattern sequence.

Dependencies

• Updated Agent Composer Core to 1.2.2.
• Bundled WP Suite Hub 2.5.15 with corrected Amplify preview.3 translations.
• Included WebCrypto 1.1.8 support for protected configuration on local HTTP development sites.

Upgrade notes

1. Restart the MCP runtime after upgrading.
2. Refresh the MCP client tool and resource catalogue so the current rendered-preview resource and submission-token schema are loaded.
3. Import, validate, and explicitly activate the updated WP Suite Config Set if homepage or product-page update proposals are needed.

Existing active Config Sets are not overwritten automatically.