Unclear guidance on artifact sharing 'editor' permission vs. actual edit capability

Description

When sharing a Claude-published Artifact with another user, the sharing UI offers an "editor" permission level. However, the internal tool guidance for artifacts states that shared artifacts can only ever be read (via WebFetch) by non-owners, and that updating an artifact "requires an artifact the user owns."

This creates ambiguity: it's unclear what the "editor" permission actually grants a shared user, since artifact updates appear to be restricted to the owner regardless of the permission level selected at share time.

Question / Ask

Could the documentation/guidance clarify:

1. What capabilities does the "editor" sharing permission actually unlock for a non-owner (if not the ability to update/redeploy the artifact)?
2. If "editor" is meant to allow edits, is there a gap between the sharing UI and current tool/API behavior?
3. If "editor" controls something else (e.g., comments, annotations, forking), it would help to have that documented explicitly.

Context

This came up while using Claude Code's Artifact tool, whose guidance says:

Shared artifacts can be read with WebFetch but never updated — updating requires an artifact the user owns.

This seems to conflict with the existence of an "editor" role in the sharing UI, or at least isn't reconciled anywhere in the available documentation.