A watch can register a wake-up instead of streaming, waking your session when the artifact publishes.
Durable wake watch results and a registration-failure message are present under off-by-default artifact gating.
What's wrong with this entry?
A watch can come back marked as a durable wake, meaning no live updates arrive and the session is instead woken by a new turn the next time the artifact is published, with instructions to re-read the artifact on wake. A separate message covers the case where that durable subscription could not be registered.
- Nothing in this build requests this mode; it applies only when the server returns it for a watch.
this session will be woken by a new turn when the artifact is next published; no live updates are streamed, so re-read the artifact on wake.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.