[FEATURE] allow unattended (Routines) republish to refresh the shared/public version of an artifact

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Environment

Claude Code Routines (cloud, scheduled) + Artifacts shared via "Anyone with the link"

Current behavior

• Once an artifact is shared publicly, logged-out viewers are served a snapshot pinned to the version at share time.
• Subsequent republishes to the same canonical URL (from unattended Routine runs and from local CLI sessions; the Artifact tool returns success and the returned URL matches) update only the owner's logged-in view. The public snapshot never refreshed across 5+ publishes over 17 hours.
• In interactive sessions, publishing prompts "Publishing to a shared-live artifact requires confirmation".

Proposed Solution

Requested feature

If the owner has already approved publishing to that canonical URL, allow scheduled/unattended runs to refresh the shared (public) version as well — or provide a pre-authorization setting (e.g., per-artifact "allow automated updates").

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

Configuration and settings

Use Case Example

Use case

A daily internal news digest is generated by a weekday-morning Routine and distributed to employees who do not have Claude accounts, via a single stable URL. Today the public version stays frozen at the share-time snapshot, so the automated distribution cannot work.

Additional Context

_No response_