Two sessions watching the same artifact comments can hand off, but the takeover step is off.
A full three-outcome handover protocol exists, but the claim step needs tengu_cobalt_plinth_thistle, which falls back off.
tengu_cobalt_plinth_thistle Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.242: on
Read once, for one account on one subscription tier, against v2.1.242. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When two live sessions of the same conversation are both set to reply to artifact comments, the old behaviour was a warning that every comment would get answered twice. This build adds a real handover protocol with wording for all three outcomes: one session took over, one yielded, or they are still doubling up. The step that actually makes a takeover stick is behind tengu_cobalt_plinth_thistle, which falls back to off.
- New exported operations request a takeover, hand a claimed artifact back, and announce that a taken-over artifact stopped.
- The takeover request is issued at the conflict site, but the claim it depends on is only computed when the gate reads true.
- There is a second early return inside the takeover routine that reports a disabled state; what drives that check is not identifiable from the surrounding code.
- The gate name is new in this build. Without server configuration, users still see the old double-reply warning.
tengu_cobalt_plinth_thistle
Strings lifted out of the shipped bundle, so the claim above can be checked against them.