Under the hood
Useful2 Signal0
Background daemon login cooldown and status can live in a storage service instead of local files.
What's wrong with this entry?
Anonymous. No account, no email.
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-cooldownanddaemon-auth-status.jsonfiles 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.