A storage backend for plugin cache writes with file-operation fallbacks, decided once per process from a remote setting that defaults off.
What
Publishing, adopting, probing and clearing plugin cache folders can go through a storage interface instead of direct file calls, falling back to ordinary file operations on invalid-argument, not-a-directory and cross-device errors. It is off unless a remote setting turns it on, and the decision is fixed once per process.
Details
- Publishing is refused when the cache path is reached through a symlink.
- Stray orphan markers and set-aside replaced versions are cleaned up.
- Session transcript appends, saved tool results and stored shell output use the same path.
Evidence
refused to publish a staged plugin through a symlinked cache folder (v5 backend)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.