A storageV5 key factory covering transcripts, history, memory and settings exists; no backend supplies it here.
What
A 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.
Details
- 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.
- A validator rejects names containing slashes, NUL, "." or "..", so keys cannot escape their namespace.
- 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.
- What provides a storageV5 backend could not be determined from the build.
Evidence
namespace: "pluginRegistry"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.