{"version":"2.1.221","anchor":"new-namespaced-storage-key-factory-storagev5","canonical_anchor":"new-namespaced-storage-key-factory-storagev5","heading":"New namespaced storage key factory (\"storageV5\")","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/new-namespaced-storage-key-factory-storagev5","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### New namespaced storage key factory (\"storageV5\")\n\nA new namespaced storage-key system exists for transcripts, settings and memory, but nothing supplies its backend.\n\n**What**\n\nA key-builder module now constructs storage keys under fixed namespaces instead of raw filesystem paths, but it only comes into play when a storageV5 backend is supplied, and nothing observable in this build was confirmed to supply one.\n\n**Details**\n\n- Namespaces covered: transcript, history, mailbox, log, globalConfig, settings (user\/project\/local), task, memory, pluginRegistry, pluginCache, cache, paste, state, feedbackDraft, agentMemory, identity, team, sidecar, scratch, userConfigDir and job.\n- A validator rejects names containing slashes, NUL, \".\" or \"..\", so keys cannot escape their namespace.\n- Transcript loading uses the factory when a storageV5 backend is passed, and falls back to the existing filesystem path otherwise, so current behaviour is unchanged.\n- What provides a storageV5 backend could not be determined from the build.\n\n**Evidence**\n\n`namespace: \"pluginRegistry\"`\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}