v5 storage paths sit beside the normal file paths for several stores, inert unless a backend handle is supplied.
What
Several stores now have a v5 backend path sitting alongside the existing file path, taken only when a backend is supplied.
Details
- Covers theme listing and saving, MCP task metadata (write, delete and list under an
mcp-taskssidecar), scheduled-task status, user settings writes, and ranged transcript reads. - Settings write failures now raise a distinct error naming the failure class.
- Each path is inert unless a v5 backend is passed in; what supplies it could not be determined.
Evidence
settings storageV5 write failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.