Memory store errors now say no store is available and list the ids you can use.
What's wrong with this entry?
There is no longer a connecting state when resolving a memory store. A session with no store bound says none is available, an unknown store id lists the ids you can use, and a personal id used where a project one is expected is rejected as unknown.
- Read-only stores still list the ids you can write to.
- The resolver returns the store together with its backend instead of building one on the spot.
No memory store is available in this session.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.