{"version":"2.1.257","anchor":"artifact-publish-result-can-now-describe-a-live-doc-shim","canonical_anchor":"artifact-publish-result-can-now-describe-a-live-doc-shim","heading":"Artifact publish result can now describe a \"live doc shim\"","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-publish-result-can-now-describe-a-live-doc-shim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact publish result can now describe a \"live doc shim\"\n\nArtifact publish results can show a live doc shim status line with edit counts, copy path and live path.\n\nArtifact publish results can now render a \"live doc shim\" status line, showing edits, whether it's onto current, completeness, whether the source is a copy, the copy path, and the live path, via a new `liveDocShimLine` formatter that runs ahead of the existing `liveDocVersion`\/publish branches.\n\nThe publish flow also gained a shim path (`applyPublishShim`) that validates a live document target is HTML, not stale, has been read, is actually live, and has a title before publishing, producing specific refusal codes such as `live_doc_shim_not_html` when a check fails.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}