Reading files from a first-party artifact's own file cache no longer always requires approval, and its progress text now says 'read' instead of 'save'
What
Reading files or assets from the user's own artifact can now be exempted from the usual approval prompt when the artifact was made from a published first-party Artifact type, with a new decision-reason message explaining why. There's also a shortcut for resources that were already read or approved earlier under a display name.
The user-facing progress text for these actions was also updated: the read_file action now shows "read " instead of "save file ", and read_asset now shows "read asset " instead of "save asset ". A destination arrow in the progress text is now suppressed when the resolved destination is a default directory.
Why
These file-cache operations are reads, not writes, so treating them as reads both reduces unnecessary approval prompts for trusted first-party artifacts and makes the displayed action text accurately describe what's happening.