Artifact comment-read failures now show specific reasons instead of one generic error
When Claude Code can't read comments on an artifact (a shared document or file created in a conversation), it now explains why in more detail. A new internal helper translates specific failure reasons, such as the artifact belonging to another organization, not being a shared link, not currently being served, being blocked by a permission rule, having a pending notice, or a check failing, into a plain-language explanation plus a suggested next step (like saying so, making your own calls, or listing available items).
Previously all these situations produced the same generic "its sharing could not be checked" message. Now you get a more specific reason and a hint about what to try next, making it easier to understand why an artifact comment couldn't be read.