v0.137.0: guard empty-email notification save (prevents alert-delivery wipe)

Saving the notifications form with a blank email box while events are enabled wiped the customer's hub-side alert address (SyncPreferences pushed empty) — the 2026-07-15 demo incident. settingsNotificationsHandler now refuses that save before SetNotificationPrefs + hub sync, re-renders a Hungarian error, and repaints the submitted checkboxes. Empty email + zero events (clear-all) still proceeds. Tests + red-proof (remove guard -> stored email wiped to empty).
2026-07-15 19:40:01 +02:00
parent 0ef6648e12
commit c124d0adf2
4 changed files with 201 additions and 0 deletions
@@ -1436,6 +1436,12 @@ Notification preferences (email, enabled events, cooldown hours) are:
 - Synced to Hub on save and on controller startup via `POST /api/v1/preferences`
 - Hub sync failure doesn't block local save

+**Empty-email save guard (v0.137.0):** the save handler REFUSES a submit with a blank e-mail box
+while any event is still enabled (it would store an empty address AND push it to the hub, wiping the
+provisioning-seeded alert delivery). The form re-renders with a Hungarian error and the customer's
+ticked events preserved; no save, no sync. Clearing the e-mail with **zero** events enabled is
+allowed (an intentional turn-everything-off).
+
 ---

 ### 7. Update Management