Under the hood
Useful1 Signal3
Skills in team memory can be read through the memory backend instead of the filesystem.
What's wrong with this entry?
Anonymous. No account, no email.
What
Skills stored under a team-memory mount can now be listed and read through the memory backend's own hardened text reader rather than reading files from disk. The disk path is kept for mounts that have no backend handle.
Details
- Taken only when both a backend handle and a project key are supplied; nothing in the code read shows what turns that backend on.
- New diagnostics distinguish a skill not at its expected location, one that moved, one carrying other names, and one that is not a plain small file.
- One message covers "a second name on the file, or the backend's own publish in flight".
Evidence
a second name on the file, or the backend's own publish in flight
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