DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
Storage naming rules now carry per-field error guidance
Under the hood
Useful2Signal2
Internals
Storage naming rules now give specific error messages and document the key layout.
What's wrong with this entry?
Anonymous. No account, no email.
What
The storage layer gained explicit tables of which names are streams and which are scopes, with a specific message for each misuse, plus allow-lists of permitted directory names and files. They document the layout: task ids, mailbox teammates and cache ids are individual keys, not scopes you can narrow by.
Evidence
names one task value, a key, not a scope: a list scope narrows with listId only
Strings lifted out of the shipped bundle, so the claim above can be checked against them.