{"version":"2.1.234","anchor":"publishing-unwraps-an-artifact-page-that-got-nested-inside-a","canonical_anchor":"publishing-unwraps-an-artifact-page-that-got-nested-inside-a","heading":"Publishing unwraps an artifact page that got nested inside another","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/publishing-unwraps-an-artifact-page-that-got-nested-inside-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Publishing unwraps an artifact page that got nested inside another\n\nPublishing an artifact strips an already-wrapped page so you don't get a page inside a page.\n\n**What**\n\nIf the HTML being published already carries Claude Code's own generated page wrapper around the real content, publishing now strips it, repeatedly, up to a depth limit, so you do not get a page inside a page.\n\n**Details**\n\n- The wrapper is recognised by its shape: a doctype, a head, at most two inline scripts and a style block around the payload.\n- Reported as `nested_page_repaired` when fully unwrapped, or `nested_repair_partial` when the depth cap is hit first.\n\n**Evidence**\n\n`nested_page_repaired`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}