Publishing stops if your page got wrapped repeatedly in runtime scaffolding, asking for the innermost document.
What's wrong with this entry?
Publishing an artifact or page now detects a document that has been wrapped over and over in the same runtime scaffolding (repeated frame or chart runtime comment blocks, mermaid and syntax-highlight blocks, or stacked <base href="/_f/..."> skeletons) and stops with an error asking you to keep only the innermost document and publish again.
- The check treats this shape as impossible for a genuine page or a fetched artifact, so it is read as accidental re-wrapping rather than valid content.
- There is a hard limit on how many nested skeleton layers will be unwrapped before publishing errors out instead of continuing.
Delete every such comment block, attribute, tag, and repeated outer skeleton from the source, keep the innermost document, and publish again.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.