{"version":"2.1.247","anchor":"headless-resume-can-re-arm-for-artifact-comments-but-never-t","canonical_anchor":"headless-resume-can-re-arm-for-artifact-comments-but-never-t","heading":"Headless resume can re-arm for artifact comments but never takes over","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/headless-resume-can-re-arm-for-artifact-comments-but-never-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Headless resume can re-arm for artifact comments but never takes over\n\nResumed headless sessions re-arm for artifact comments but will never take over from another holder.\n\n**What**\n\nA resumed headless session now goes through a shared routine to re-arm for artifact comments, and that routine is wired with takeover requests hard-coded off, so such a session will never ask to take over from another holder.\n\n**Details**\n\n- Held state is re-probed after 10 seconds by default.\n- The comments gate is supplied as a dependency, and the existing message for a failed gate check is unchanged.\n\n**Evidence**\n\n`[frame-live] headless resume re-arm gate failed: `\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}