Internal storage keys learned a "recording" kind, but nothing in the build creates one.
A recording storage kind keyed by project, session and timestamp exists with no writer.
What's wrong with this entry?
The component that builds and checks internal storage keys gained a recording kind, addressed by project, session id and a timestamp. Nothing in the build produces recordings, so what would create one is not settled here.
- The timestamp is validated like other key parts, and session id is checked on lookup.
- Requests that ask for a group of stored values but actually name a single stream are now rejected, with per-kind explanations for transcripts, logs and session logs:
names one agent transcript, a stream key, not a scope: narrow a scope with agentRelPath.
namespace: "recording", names one agent transcript, a stream key, not a scope: narrow a scope with agentRelPath
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.223
Compare-and-swap retry helper for versioned storage keys
Both mention storage backend
-
v2.1.223
Daemon lock and auto-update lock gained storage-backend implementations
Both mention storage backend
-
v2.1.223
Deep-link registration and cleanup sentinels can be stored as state keys
Both mention storage backend