Under the hood
Useful1 Signal0
Daemon login cooldown and status writes go through the storage backend and now surface errors instead of hiding them.
What's wrong with this entry?
Anonymous. No account, no email.
What
The browser-login cooldown timestamp and the auth_required status file go through the storage backend when one is available instead of direct file IO.
Details
- writes use a umask-derived file mode
- backend failures raise explicit errors carrying telemetry codes rather than being swallowed
Evidence
daemon-auth v5 cooldown write failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.