---

`. * `cdd_pattern_content()` strips to the FIRST `?>` — the doc header’s — so that would * have shipped as literal text inside the attribute. 99 of the 210 core-block * harvested patterns carry PHP like this somewhere in the body. * ② **FOUR HARDCODED COLOURS.** `#222230e0` card, `#fafafa14` rules, `#a8b8cd` answer * text, `#00000000` overlay — greenshift’s dark theme, applied to every client * whatever their palette said. Now `secondary` / `muted` / `base` through * `color-mix`, so the band follows the brand. * ③ **FOUR BLOCK-STYLE CLASSES WE DO NOT SHIP** — `is-style-containbg`, * `is-style-color-inherit`, `is-style-gradientmask`, and the * `creative-btn` GRADIENT, which our theme.json does not define at all (it has no * gradients). The numbers rendered as a plain colour; the cover’s contain-fit did * not happen. Removed rather than faked. * ④ **A FOREIGN ATTACHMENT ID** — `”id”:2551` / `wp-image-2551`, greenshift’s media * library, meaningless in a client’s. * ⑤ **THREE FOREIGN FONT-SIZE SLUGS** — `big`, `max-huge`, `subheading`. Ours is * small/medium/large/x-large/xx-large/huge, so all three matched nothing and * rendered at default size: the “max-huge” headline this design is built around was * body-sized. * * ⚠ THE NUMBERS 01–04 ARE AUTHORED STRUCTURE, NOT DEMO COPY. They label the position, * not the content, so they stay as literals — the same way `ls-faq`’s own furniture * does. They are inside the `cdd:slot`, so a client with two questions gets 01 and 02 * and no gap. */ ?>