Under the hood
Artifact file-read functions gain options for public reads, byte limits, and a new file-existence check
What
The functions that read a single artifact file or a batch of artifact files now accept extra options: whether to admit a public (non-member) read, and for batch reads, a byte budget limiting how much data is fetched at once. A new helper also does a quick existence check (an HTTP HEAD request, which asks whether a file exists without downloading it) for a specific artifact version's asset bundle.
Why
These options let artifact file reads be tuned per request, controlling both who can read public artifacts and how much data a batch read pulls back, and let Claude Code confirm an asset exists before trying to fetch it.