{"version":"2.1.223","anchor":"more-on-disk-state-moved-behind-the-abstract-state-store","canonical_anchor":"more-on-disk-state-moved-behind-the-abstract-state-store","heading":"More on-disk state moved behind the abstract state store","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/more-on-disk-state-moved-behind-the-abstract-state-store","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### More on-disk state moved behind the abstract state store\n\nSome local lock and cache files can now live in a shared state store instead of loose files.\n\n**What**\n\nFive pieces of local state became addressable as named state entries rather than only files under the Claude home dir.\n\n**Details**\n\n- covers the auto-updater lock, GitHub PR status cache, daemon lock, deep-link-register-failed marker and last-cleanup stamp\n- the updater's acquire and release functions take an optional store and delegate to store-based variants when one is given\n- without a store they keep using the `.update.lock` file and `gh-pr-status-cache.json`\n- the store-backed path only runs when a call site passes a handle, so this is per call site\n\n**Evidence**\n\n`AutoUpdater: failed to release update lock: `\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}