{"version":"2.1.236","anchor":"more-config-writes-logout-and-cache-clearing-take-an-explici","canonical_anchor":"more-config-writes-logout-and-cache-clearing-take-an-explici","heading":"More config writes, logout and cache clearing take an explicit storage handle","tier":"internal","area":"Config Storage","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/more-config-writes-logout-and-cache-clearing-take-an-explici","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### More config writes, logout and cache clearing take an explicit storage handle\n\nMore config writes, logout and cache clearing name their storage explicitly.\n\n**What**\n\nThe default nudge, organisation default model tracking, daemon install prompt dismissal, GitHub repository path tracking, the feedback survey timestamp and Chrome onboarding all write through a named storage handle now. Logout takes credentials directly, session cache clearing and post-compaction cleanup take the handle, and transcript path validation only runs when the newer storage backend is active.\n\n**Evidence**\n\n`if (fr() && t !== void 0 && o === void 0)`\n\n- Area: Config Storage\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}