{"version":"2.1.236","anchor":"early-artifact-comment-read-is-behind-two-flags-both-off","canonical_anchor":"early-artifact-comment-read-is-behind-two-flags-both-off","heading":"Early artifact comment read is behind two flags, both off","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/early-artifact-comment-read-is-behind-two-flags-both-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Early artifact comment read is behind two flags, both off\n\nThe early artifact comment read needs two separate switches, both of which default off.\n\n**What**\n\nThe pre-startup control-plane comment read has one caller, the artifact comment auto-reply scan, and it passes the option only when `tengu_slate_lantern_ember` is on. Even then the read itself needs `tengu_onyx_sluice`. Both fall back to off, so neither half runs unless remote config enables both.\n\n**Details**\n\n- The option defaults to false at the reader itself, and no other code in the build passes it.\n- The attempt carries a callback so it is scored whether it succeeds or falls back to the normal read.\n- The same change lets a session whose outbound network is blocked reuse an already-successful control-plane result rather than reporting a denial.\n\n**Evidence**\n\n`controlPlaneReadBeforeBoot`\n\n- Flag `tengu_slate_lantern_ember`: Off in both readings (read for one account on one subscription tier against v2.1.236; this account: off, anonymous baseline: off, compiled default: off)\n- Flag `tengu_onyx_sluice`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.236; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}