Permission prompts for writing to artifacts now explain whose file it is and flag version-pinned edits
When Claude Code asks permission to write to an artifact's underlying storage (write_db), it now classifies the write as one of four cases: cowritten, from_type, someone_else, or unknown, based on who owns the file. The permission prompt can now be prepended with a description of the file, such as saving a file as a given name or saving a named file to a given location.
It also separately calls out a version-pinned write to someone else's artifact (an edit that targets a specific saved version rather than the latest one): this kind of write always asks for permission on its own, and approving it only covers that one write, until the current conversation has read that artifact's data.
This makes permission prompts for artifact writes more informative about whose file is being changed, and adds an extra safeguard around version-pinned edits to other people's artifacts so approval doesn't inadvertently cover more than intended.