{"version":"2.1.228","anchor":"storage-selector-threaded-through-many-call-sites","canonical_anchor":"storage-selector-threaded-through-many-call-sites","heading":"Storage selector threaded through many call sites","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/storage-selector-threaded-through-many-call-sites","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Storage selector threaded through many call sites\n\nMany background writes now name which storage they use instead of assuming one.\n\n**What**\n\nFeedback queue reads and pruning, theme saving, agent observer park and unpark, daemon job key deletion, worker roster updates, MCP connect and retry, and scheduled task arming all now pass an explicit storage selector rather than assuming one. Deleting a daemon record prefers removing the storage key and only unlinks the file as a fallback.\n\n**Evidence**\n\n`storageV5`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}