Artifact tool cannot move the share pin, so shared readers stay frozen on an old version

What's missing

When an artifact is shared by link, viewers are pinned to a specific published version. Republishing the artifact does not move that pin, so a shared reader stays frozen on an old version while the agent keeps publishing updates. The reader sees a stale page and has no indication that newer versions exist.

Why it's a problem

The Artifact tool exposes actions for publish, read, list, watch, unwatch, status, comments, reply, resolve, upload_asset and the artifact database — but nothing for the share pin.

So an agent asked to "keep this page updated so my colleague can read along as work lands" can do every part of that job except the one step that makes the updates visible. After every single publish it has to stop and ask a human to go click through the share menu. On a page that updates several times a day, that's the whole value of the feature gone.

The read result does surface the state (viewers currently see this version, but will not see future publishes until the share pin is moved), so the agent knows the problem exists — it just has no way to act on it.

Requested

Any one of these would solve it:

• a set_share_version / move_pin action taking the artifact url
• a pin_latest: true flag on publish
• an "always show latest" share mode set once at share time

Use case

A live status/ledger page for a project, republished multiple times a day, read by a colleague via a shared link. Every update currently requires manual intervention from the artifact owner before the intended reader can see it.