r-zakarya
eb9999c4b2
Conflict detected, fresh snapshot pulled, the change applied ON TOP of it, publish accepted. Nothing clobbered - which is the whole point of dropping the pre-publish fetch. The second attempt also derived the key again, 4397 ms: the desktop had re-encrypted its container with a fresh salt, so the key in hand no longer fitted. That is exactly the case the reuse guards against, seen firing for the first time. It costs one derivation per desktop publish, no more.
