Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.227,
Internal ChangesSection of the release
What
Mailbox writes, marking messages read, message pruning and team-config updates now go through a transactional storage update when the session has the newer storage backend, and fall back to the old lockfile-plus-atomic-write path when it does not.
Details
The new path retries when a lock looks suspect and separates contention from hard failures in telemetry.
Hard failures surface as "Team file update failed (storage v5)".
The old file-based mailbox read and clear helpers are gone.
Evidence
Team file update failed (storage v5)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
