/* godigital-sections — legacy front-end guard. NOT part of the versioned bundle: hand-written, safe to edit, never concatenated by verify-library.sh --emit-bundle. */
/* Why this exists: sections published before bundle 1.4.0 (text-image v1/v2, gallery-grid v1, team v1) ship an image slot as <figure class="wp-block-image size-large"></figure> with no <img> child at all. */
/* Those versions are IMMUTABLE, so their "+ Add an image" prompt can never be edited. It stays off live sites only because core's render_block_core_image() returns '' when the block content has no "<img" — an implementation detail, not a contract. */
/* (WP 6.9.4 has a second bail for an <img> with no src attribute, which is what keeps the 1.4.0+ slots off the front end. Neither bail is guaranteed to survive a core release.) */
/* If either check ever goes away, the legacy prompt would appear on live customer pages fleet-wide. These two rules make it genuinely editor-only instead. */
/* .editor-styles-wrapper is on the body of the editor canvas AND of every pattern-preview iframe; a front-end document never has it. */
body:not(.editor-styles-wrapper) [class*="gd-lib-"] .wp-block-image:not(:has(img))::before { content: none !important; }
body:not(.editor-styles-wrapper) [class*="gd-lib-"] .wp-block-image:not(:has(img)) { display: none !important; }