Artifact wake notifications can report which events they were armed for.
Observed-event lists on wake results live in the artifact watch subsystem, whose own flags decide whether anything runs.
What's wrong with this entry?
A durable wake result, and the reply saying a watch is already running, can now carry the list of observed events rather than just a trigger id and a timestamp. This sits inside the artifact watch subsystem, which has its own flag checks and skips work when they are off, so whether any of it runs depends on server config.
rail: "durable_wake"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.