{"version":"2.1.225","anchor":"daemon-auth-cooldown-and-status-write-through-the-v5-backend","canonical_anchor":"daemon-auth-cooldown-and-status-write-through-the-v5-backend","heading":"Daemon auth cooldown and status write through the v5 backend","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/daemon-auth-cooldown-and-status-write-through-the-v5-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Daemon auth cooldown and status write through the v5 backend\n\nDaemon login cooldown and status writes go through the storage backend and now surface errors instead of hiding them.\n\n**What**\n\nThe browser-login cooldown timestamp and the `auth_required` status file go through the storage backend when one is available instead of direct file IO.\n\n**Details**\n\n- writes use a umask-derived file mode\n- backend failures raise explicit errors carrying telemetry codes rather than being swallowed\n\n**Evidence**\n\n`daemon-auth v5 cooldown write failed`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}