{"version":"2.1.242","anchor":"two-sessions-on-one-artifact-can-hand-comment-replies-to-eac","canonical_anchor":"two-sessions-on-one-artifact-can-hand-comment-replies-to-eac","heading":"Two sessions on one artifact can hand comment replies to each other, claim step gated off","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/two-sessions-on-one-artifact-can-hand-comment-replies-to-eac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Two sessions on one artifact can hand comment replies to each other, claim step gated off\n\nTwo sessions watching the same artifact comments can hand off, but the takeover step is off.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- New exported operations request a takeover, hand a claimed artifact back, and announce that a taken-over artifact stopped.\n- The takeover request is issued at the conflict site, but the claim it depends on is only computed when the gate reads true.\n- 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.\n- The gate name is new in this build. Without server configuration, users still see the old double-reply warning.\n\n**Evidence**\n\n`tengu_cobalt_plinth_thistle`\n\n- Flag `tengu_cobalt_plinth_thistle`: Not enough to say (read for one account on one subscription tier against v2.1.242; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}