Artifact wake subscriptions now explain when a session has no human owner to wake.
What's wrong with this entry?
The reasons an artifact wake subscription can fail moved into a lookup table and gained a new case, no_originator, for sessions with no linked human owner. It explains that such a session cannot hold wake subscriptions, that retrying deliberately re-checks, and that automatic retries are answered locally.
- A latched form of the same condition is reported in telemetry as
no_originator_latched. - Sits behind the same artifact gating as the rest of the artifact wake feature.
no_originator
Strings lifted out of the shipped bundle, so the claim above can be checked against them.