A failed config save is reported, not dropped

A config file that cannot be written — a read-only file in a mis-frozen build slot, most often — threw before the change event fired, so nothing persisted and nothing driven by that event re-applied either. Settings appeared to do nothing at all, in silence.

A config file that could not be written threw before the change event fired. Nothing persisted, and nothing driven by that event re-applied either — so theme, spaciness and docking appeared to do nothing at all, in silence, while you were still in the window. The real-world cause was a read-only config.yaml in a mis-frozen build slot.

A failed save is reported rather than dropped, so the window says the setting did not stick instead of pretending it did.

• The source catalogue records no separate caveats for this entry. The implementation and evidence above define its scope.