Checks for explicitly set settings keys can now read from the newer settings store.
What's wrong with this entry?
The check for whether a key such as cleanupPeriodDays is written explicitly in a settings file is now asynchronous and can be given a reader, in which case user settings come from the newer store instead of the file on disk. A read failure is logged and treated as unknown rather than as absent, and the retention cleanup gate became async to match.
rawSettingsKeyPresence: v5 user-settings read failed
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.248
Cleanup skip message names the setting at fault
Both mention cleanup period
-
v2.1.248
Desktop-released session cleanup path
Both mention cleanup period
-
v2.1.248
Transcripts owned by the Claude desktop app are exempt from the retention sweep
Both mention cleanup period