Resuming artifact auto-replies now explains precisely which stop is blocking you.
What's wrong with this entry?
Resuming automatic replies on an artifact now distinguishes two situations that previously fell together. A live watch connection that began before the watch was stopped and is still winding down cannot be attached to by a resume, and replies being held by the artifact's own watch stop rather than by a separate stop on the replies are refused with a message that there is no separate auto-reply stop to resume and that only an approved re-watch releases them.
- The tool's permission description now discloses that resuming will also restart watching the artifact, so the reader knows a re-watch is coming before approving.
- The still-winding-down connection case is tracked internally as
arm_in_flight, the marker for a watch connection that opened before the stop and has not yet finished closing. - Two new explanations cover wake subscriptions, the mechanism that lets an artifact wake a session, failing to be set up, including
Wake subscriptions are not provisioned in this deployment; retrying will not help.which tells the reader a retry is pointless. - Unconditional and part of the artifact tool surface, with no flag, setting or environment variable gating it.
Wake subscriptions are not provisioned in this deployment; retrying will not help., arm_in_flight
Strings lifted out of the shipped bundle, so the claim above can be checked against them.