Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Storage BackendArea: what it touches
In DevelopmentKind: in v2.1.223,
In DevelopmentSection of the release
What
Acquiring, reading, replacing and releasing the daemon lock, plus the auto-updater's stale-lock detection and release, now each have a storage-key branch alongside the original file-based logic.
Details
acquisition uses an ifAbsent write with a umask-derived mode; staleness is decided from stat; release deletes the key
lock-contention telemetry codes trigger a re-read and one retry before the acquisition fails
the file-based path is still present and is what runs without a backend
Evidence
[DaemonLock] Failed to acquire daemon lock:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
