=== SCENARIO G — open the settings page and Save, changing NOTHING ===
-- stored BEFORE (sha256 + value) --
  enabled_events: null
  sha256        : 74234e98afe7498fb5daf1f36ac2d78a
  email set     : False

-- RENDER the page, take exactly what it ticked, POST it back unchanged --
  render=200
  ticked boxes  : 10
  save=200

-- stored AFTER --
  enabled_events: null
  sha256        : 74234e98afe7498fb5daf1f36ac2d78a
=== SCENARIO G — REDONE ===
First attempt was INCONCLUSIVE and is reported: demo-hp has NO notification prefs, so the
page rendered the DEFAULTS ticked and the save was refused by the empty-email wipe guard.
Stored bytes were unchanged — but for the wrong reason. Seeding prefs makes it a real round trip.

  seed=200
  BEFORE: ["backup_failed", "db_dump_failed", "node_down", "disk_warning", "disk_critical", "expected_backup_missed", "expected_dbdump_missed"]
  sha   : 10840f3a95bac168f0d7c79760998138

  -- now RENDER and SAVE, changing nothing --
  render=200
  ticked: 7  email=
  save=200
  AFTER : ["backup_failed", "db_dump_failed", "node_down", "disk_warning", "disk_critical", "expected_backup_missed", "expected_dbdump_missed"]
  sha   : 10840f3a95bac168f0d7c79760998138
=== SCENARIO G — THIRD attempt, and the first CONCLUSIVE one ===
Attempt 2 also refused: the email <input> spans THREE LINES, so a single-line grep read it as
empty and the wipe guard declined the save — while still answering 200. A warning beside a
success reads as a success; the sha matching meant NOTHING was saved, not that nothing changed.

  BEFORE: ["backup_failed", "db_dump_failed", "node_down", "disk_warning", "disk_critical", "expected_backup_missed", "expected_dbdump_missed"]
  sha   : 10840f3a95bac168f0d7c79760998138
  render=200
  email read : [drill@felhom.eu]   ticked: 7
  HTTP=200
  refusal banner present? : 0  (0 = a REAL save)
  AFTER : ["backup_failed", "db_dump_failed", "node_down", "disk_warning", "disk_critical", "expected_backup_missed", "expected_dbdump_missed"]
  sha   : 10840f3a95bac168f0d7c79760998138
-- restoring demo-hp's notification settings to their pre-drill state (no email, no events) --
  restore=200
  enabled_events: null
  email set     : False
