Changelog

Updates to block registration, editing, and editor asset loading.

• Added an editor document registry to keep block previews aligned with the active Gutenberg canvas.
• Improved iframe-aware asset loading for WordPress editors that render inside an isolated document.
• Protected native InnerBlocks selection and focus, so editing nested paragraphs, headings, and buttons stays predictable.
• Hardened rich-text and script loading behavior for inline editing and live previews.

Updates to block rendering, context management, and response handling.

• Introduced a Bricks runtime adapter and render sessions to isolate shortcode state between blocks.
• Expanded render context management and block identity tracking for more reliable dynamic output.
• Added cache invalidation paths for templates and transient render results.
• Strengthened REST block responses and block-definition creation for the Gutenberg runtime.

Updates to CSS generation and editor preview layout.

• Moved global class CSS generation to the page footer so multiple blocks share one clean stylesheet.
• Included theme settings CSS in editor previews for variables, typography, and button treatments.
• Fixed image sizing, button width, container overflow, and absolute-positioned overlay behavior in the editor.
• Preserved user-cleared values and removed empty hidden markers that could trigger block validation failures.

Updates to Core Framework integration and field value handling.

• Added feature-flag support around Core Framework integration behavior.
• Improved spacing and typography transformation handling across the integration layer.
• Normalized typed field defaults so select, number, image, and boolean values resolve consistently.
• Kept explicit empty meta values intact instead of silently replacing them with field defaults.

Compatibility and test coverage updates.

• PHP 7.4 compatibility remains a first-class constraint for the distributed plugin.
• Added coverage for Gutenberg iframe compatibility, block-definition creation, rendering, caching, and Core Framework behavior.
• Removed legacy route and bootstrap pieces as the v2 application wiring settles into its current shape.