{"version":"2.1.277","anchor":"multi-store-sync-basis-loader-now-recognizes-a-non-empty-he","canonical_anchor":"multi-store-sync-basis-loader-now-recognizes-a-non-empty-he","heading":"Multi-store-sync basis loader now recognizes a non-empty 'held' set as valid state","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/multi-store-sync-basis-loader-now-recognizes-a-non-empty-he","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Multi-store-sync basis loader now recognizes a non-empty 'held' set as valid state\n\nA sync data store with a non-empty 'held' set is no longer wrongly treated as empty\n\n**What**\n\nWhen Claude Code loads the saved state used to keep multiple stores in sync, it used to treat a store with zero entries as automatically empty. Now, if that store has a non-empty `held` set, it's no longer considered empty just because its entry count is zero.\n\n**Why**\n\nThis avoids an incorrect \"empty store\" rejection for a store that actually holds valid state in its `held` set, preventing that state from being wrongly discarded during sync.\n\n- Area: Team Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}