Not switched on
Useful1 Signal3
Team memory sync can use a storage backend instead of plain files, but nothing turns it on.
Memory sync reads and writes can route through a storage backend that nothing in this build enables.
What's wrong with this entry?
Anonymous. No account, no email.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Team-memory mount conflicts fail closed on write and recover automatically
Both mention team
-
v2.1.224
Failed
@namemessages now tell you they failedBoth mention team
-
v2.1.224
Plan approvals report mailbox write failures instead of claiming success
Both mention team