A reply to an unactivated artifact thread would show as its own state, once comments are live.
A distinct not-activated reply state exists on artifact comments, whose enablement is unresolved.
What's wrong with this entry?
A reply to a thread the viewer has not activated is surfaced in the transcript as its own state rather than a generic error.
- the "artifact_comment_reply" telemetry outcome is recorded as not_activated
- rides on the same artifact comment/reply actions whose enablement is unresolved in this build
reply needs thread activation by the user
Strings lifted out of the shipped bundle, so the claim above can be checked against them.