{"version":"2.1.223","anchor":"session-file-message-cache-consolidated","canonical_anchor":"session-file-message-cache-consolidated","heading":"Session-file message cache consolidated","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/session-file-message-cache-consolidated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Session-file message cache consolidated\n\nSession message loading now uses one cache instead of three, with no change you'll see.\n\n**What**\n\nThe caching behind session message loading was collapsed from three separate memoized caches into one memoized session-messages loader, changing what the reset helper has to clear.\n\n**Details**\n\n- The reset helper now clears the single memoized session-messages loader instead of three caches.\n- A separate new helper clears two workload caches plus a nested one.\n- The test-reset path for another module switched from calling `clearForTest()` to clearing two maps directly.\n- No user-visible surface; failures during load still report through the same message.\n\n**Evidence**\n\n`getSessionMessages: loadSessionFile failed: `\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}