Watching an artifact can register a wake trigger instead of a live stream, and says which you got.
Durable wake watches with trigger and status fields are new here and sit behind off-by-default artifact gating.
What's wrong with this entry?
A watch on an artifact can return on a "durable wake" path: rather than holding a live subscription and receiving streamed updates, the session registers a trigger and is woken with a new turn the next time that artifact is published. The tool result explains which of the two you got. The watch data gained rail, trigger_id, durable_since, status and note fields. None of this exists in v2.1.226.
outcome: "durable_wake_registered",
Strings lifted out of the shipped bundle, so the claim above can be checked against them.