Under the hood
Useful1 Signal2
Many background writes now name which storage they use instead of assuming one.
What's wrong with this entry?
Anonymous. No account, no email.
What
Feedback 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.
Evidence
storageV5
Strings lifted out of the shipped bundle, so the claim above can be checked against them.