Background artifact watching stops retrying once it is refused permission to wake your session.
The durable artifact watch path is behind a remote config check that reports flag_off when it fails.
What's wrong with this entry?
The background watch that wakes a session when a remote artifact changes now remembers when it was refused permission to wake, so later attempts stop immediately and report a distinct reason rather than retrying. The whole durable path is behind a feature check that reads remote configuration, and returns a skipped result with reason flag_off when that check fails, so the source does not say whether it is on for you.
- Subscribe operations for a given watch are serialized, tracked in a pending set, and flushed on shutdown with a 10 second cap.
- The keepalive ping for the live connection is now a named 25 second constant.
no_originator_latched
Strings lifted out of the shipped bundle, so the claim above can be checked against them.