Terminal recordings could live in a storage backend instead of loose files, but that backend is off.
Recordings gain a stored-entry path keyed by project and session, taken only when a default-off storage flag is on.
tengu_hover_rest Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.235: on
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Asciicast terminal recordings gain a path that stores them under a recording key namespace keyed by project, session and timestamp, with the recording list merging stored entries and on-disk .cast files. Only taken when the storage backend flag tengu_hover_rest is on and a storage handle exists; otherwise recordings stay plain files.
- Renaming a stored recording goes through a callback held on the recorder rather than a filesystem rename.
- The old
<sessionId>-<timestamp>.castfile rename remains the fallback path.
namespace: "recording"
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.