{"version":"2.1.223","anchor":"plan-mode-artifacts-first-field-is-present-but-inert","canonical_anchor":"plan-mode-artifacts-first-field-is-present-but-inert","heading":"Plan mode artifacts-first field is present but inert","tier":"soon","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/plan-mode-artifacts-first-field-is-present-but-inert","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Plan mode artifacts-first field is present but inert\n\nPlan mode has an artifacts-first switch wired up, but nothing in this build ever turns it on.\n\n**What**\n\nPlan mode reminder attachments carry a new `artifactsFirst` field with full reentry, refresh and telemetry handling, but nothing in this build ever sets it.\n\n**Details**\n\n- A change in the value forces a full rather than sparse plan_mode reminder, and a new predicate detects whether a prior attachment carried it.\n- A `plan_artifacts_first_active` telemetry event fires when the value is set but no attachment has carried it yet.\n- The helper that would supply the value declares its locals and returns them unassigned, so `artifactsFirst` is always undefined and the branch never activates. The gate that would set it appears to have been folded out at build time.\n\n**Evidence**\n\n`plan_artifacts_first_active`\n\n- Area: Plan Mode\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}