{"version":"2.1.227","anchor":"storage-backend-addressing-added-across-transcripts-sidecars","canonical_anchor":"storage-backend-addressing-added-across-transcripts-sidecars","heading":"Storage-backend addressing added across transcripts, sidecars and caches","tier":"soon","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/storage-backend-addressing-added-across-transcripts-sidecars","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Storage-backend addressing added across transcripts, sidecars and caches\n\nTranscripts, caches, plugin state and more gained storage-backend addresses that no ordinary install uses.\n\n**What**\n\nA wide set of on-disk state gained backend-addressed equivalents with filesystem fallbacks: subagent transcripts and their `.meta.json` sidecars, session alias files, the MCP discovery cache, marketplace manifests and installed-plugin state, forked-skill scoping records, and the active-time ledger. These paths are only taken when a v5 storage backend is supplied, so on an ordinary install nothing changes.\n\n**Details**\n\n- Listings are paginated with explicit page budgets, and log when a listing was cut short or failed.\n- A failed listing yields an empty result rather than a partial one.\n\n**Evidence**\n\n`recordSessionAlias: update failed via storage`\n\n- Area: Storage Backend\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}