{"version":"2.1.235","anchor":"the-storage-v5-backend-gains-four-more-subsystems-none-of","canonical_anchor":"the-storage-v5-backend-gains-four-more-subsystems-none-of","heading":"The \"storage v5\" backend gains four more subsystems, none of which can run: the backend factory returns nothing","tier":"soon","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/the-storage-v5-backend-gains-four-more-subsystems-none-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### The \"storage v5\" backend gains four more subsystems, none of which can run: the backend factory returns nothing\n\nFour more subsystems route through the unfinished 'storage v5' backend, but it still can't run in this build\n\nThis release wires more subsystems through the optional storage-v5 interface: a full second transcript compaction implementation (`performCompactTranscriptV5`, with failure reasons `snapshot_mid_line`, `shared_inode`, and `source_changed`), history-purge counting and rewriting via `replaceRecords`, session-directory moves via `moveScope` (including a stranded-leftover warning path), asciicast recording writes, a deep-link registration failure marker, and skill-as-plugin SKILL.md reads. Each of these is only selected when a backend object actually exists, but the factory that would construct that backend still just returns without building one, so none of these v5 branches can run in this build; only the legacy filesystem paths execute.\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.235; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}