{"version":"2.1.227","anchor":"session-state-and-module-caches-reorganised-into-resettable-","canonical_anchor":"session-state-and-module-caches-reorganised-into-resettable-","heading":"Session state and module caches reorganised into resettable objects","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/session-state-and-module-caches-reorganised-into-resettable-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Session state and module caches reorganised into resettable objects\n\nSession state is built by a factory so caches clear as a unit instead of individually.\n\n**What**\n\nSession state is now built by a factory with a nested project group, and many long-lived caches (git availability, plugin agents, ripgrep availability and file counts, footer-link regexes, team-artifact scanning, temp directory resolution, marketplace loads, messaging socket state) became classes with an explicit reset. Per-session state is cleared as a unit rather than cache by cache; behaviour is meant to be unchanged.\n\n**Evidence**\n\n`project: { originalCwd: e, projectRoot: e, cwd: e },`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}