{"version":"2.1.222","anchor":"more-state-gains-v5-backed-code-paths","canonical_anchor":"more-state-gains-v5-backed-code-paths","heading":"More state gains v5-backed code paths","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/more-state-gains-v5-backed-code-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### More state gains v5-backed code paths\n\nThemes, settings, tasks and transcripts gained alternative storage paths that stay dormant without a backend.\n\n**What**\n\nSeveral stores now have a v5 backend path sitting alongside the existing file path, taken only when a backend is supplied.\n\n**Details**\n\n- Covers theme listing and saving, MCP task metadata (write, delete and list under an `mcp-tasks` sidecar), scheduled-task status, user settings writes, and ranged transcript reads.\n- Settings write failures now raise a distinct error naming the failure class.\n- Each path is inert unless a v5 backend is passed in; what supplies it could not be determined.\n\n**Evidence**\n\n`settings storageV5 write failed`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}