Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
In DevelopmentKind: in v2.1.225,
In DevelopmentSection of the release
What
The headless daemon's browser-login cooldown and auth-status records can now be read and written through the v5 storage client instead of files in the config dir.
Details
both records gained state keys for the v5 layer
active only when the supervisor is constructed with a storageV5 client
dedicated failure reporting on that path, for example daemon-auth v5 cooldown read failed
falls back to the daemon-auth-cooldown and daemon-auth-status.json files under the config dir when no client is passed
Evidence
daemon-auth-cooldown
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
