{"version":"2.1.247","anchor":"three-session-settings-were-being-written-to-the-wrong-slots","canonical_anchor":"three-session-settings-were-being-written-to-the-wrong-slots","heading":"Three session settings were being written to the wrong slots","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/three-session-settings-were-being-written-to-the-wrong-slots","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Three session settings were being written to the wrong slots\n\nSkills-sync and plugin-sync toggles now stick instead of silently reverting.\n\n**What**\n\nSetting the skills-sync veto, the account plugins sync toggle and the plugins-sync veto each stored into a different field than the one read back, so none of the three survived a round trip. The writes now land where the reads look.\n\n**Details**\n\n- Affects `replaceSkillsSyncVetoed`, `replaceAccountPluginsSyncEnabled` and `replacePluginsSyncVetoed`.\n- The same change adds a one-shot flag for a pending context compaction, with arm, consume and forget operations.\n\n**Evidence**\n\n`consumePendingContextCompacted`\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}