{"version":"2.1.271","anchor":"artifact-publish-now-explains-why-a-comment-notification-blo","canonical_anchor":"artifact-publish-now-explains-why-a-comment-notification-blo","heading":"Artifact publish now explains why a comment notification blocks reading, and how to clear it","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-publish-now-explains-why-a-comment-notification-blo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact publish now explains why a comment notification blocks reading, and how to clear it\n\nPublish-blocked message now names a comment notification specifically and explains how to clear it\n\n**What**\n\nWhen publishing an artifact is withheld because a pending notification requires the user's consent before the live artifact can be read, the message now specifically says a \"comment notification\" is pending, instead of the previous wording about an \"unattended auto-reply notification.\" It also now explains that the user's next typed message usually lifts the hold, but re-saving the local file or stopping the watch does not.\n\n**Why**\n\nThis gives Claude a clearer, more accurate explanation of why a publish is blocked and what actually resolves it, so it doesn't try ineffective workarounds like re-saving the file or stopping the watch.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}