Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Team MemoryArea: what it touches
In DevelopmentKind: in v2.1.232,
In DevelopmentSection of the release
Memory sync reads and writes can route through a storage backend that nothing in this build enables.
What
Manifest, read, write, stat and delete steps in team memory sync now go through a storage backend when one is present, falling back to plain filesystem calls when it is not. Nothing in this build turns that backend on.
Details
Listing and reading of memory entries gained storage-backed paths too.
Each operation has its own failure message, so a backend fault names the step that failed.
Evidence
multi-store-sync: local entry not writable via storage
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
