{"version":"2.1.251","anchor":"publishing-refuses-pages-wrapped-in-repeated-runtime-markup","canonical_anchor":"publishing-refuses-pages-wrapped-in-repeated-runtime-markup","heading":"Nested runtime-marker wrapper detection blocks artifact\/page publishing","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/publishing-refuses-pages-wrapped-in-repeated-runtime-markup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Nested runtime-marker wrapper detection blocks artifact\/page publishing\n\nPublishing stops if your page got wrapped repeatedly in runtime scaffolding, asking for the innermost document.\n\nArtifact and page publishing now detects content recursively wrapped in repeated runtime marker blocks, such as `<!-- frame-runtime -->`, `data-frame-runtime`, `<!-- chart-runtime -->`, mermaid\/hljs marker blocks, `<base href=\"\/_f\/...\">` skeletons, or repeated `<!doctype html>` skeletons. The code explicitly notes this is a pattern that \"nothing a genuine page or a fetched artifact contains.\"\n\nNew unwrap logic (`MDt`\/`oi`\/`So` plus the `zRe` error class) caps how many nested skeleton\/wrapper layers it will unwrap before refusing to publish. When the cap is hit, publishing is refused with an explicit instruction telling the author to delete the fake\/nested wrapper markup and republish just the innermost document.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}