Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.232,
Internal ChangesSection of the release
What
The result of a settings write now records missing when there was no prior file, and on an actual write includes a backup holding the exact bytes it replaced plus a flag saying the write came from a cached copy. These sit alongside the existing did-write, legacy-repair and corrupt fields and the guard that prevents losing stored credentials.
Details
Backup bytes are kept as replaced: new Uint8Array(...).
The locked re-read path measures byte length from the cached value directly and reports missing: !0 in its no-write result.
Evidence
legacyRepair, repairingFromCache
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
