Artifact watch listings can distinguish a live connection from one that wakes a remote session.
Durable wake-style artifact watches are described in prompts and listings but sit behind off-by-default artifact gating.
What's wrong with this entry?
The list of artifact watches now distinguishes the live background connection from a durable subscription that wakes a remote session with a new turn when the artifact is published, with no live updates. The permission prompt shown for a first watch was rewritten to describe both, and the listing header no longer claims that no watch survives a restart when a durable one is present. This sits behind the same gating as the artifact comments and watch actions.
durable wake subscription (woken on publish; no live updates), since
Strings lifted out of the shipped bundle, so the claim above can be checked against them.