-- 3. IS THE CUSTOMER LEG EVEN CAPABLE? (or is 'no customer row' true for the wrong reason) --
Error: in prepare, no such table: notification_prefs

-- the customer leg DOES deliver other event types for this same customer: --
event_type           severity  status   channel   created_at         
-------------------  --------  -------  --------  -------------------
backup_run_failures  error     skipped  customer  2026-08-22 22:20:32
backup_run_failures  error     skipped  customer  2026-08-22 22:17:44
backup_run_failures  error     skipped  customer  2026-08-22 21:11:19
backup_run_failures  error     skipped  customer  2026-08-22 16:06:21
backup_run_failures  error     skipped  customer  2026-08-21 21:20:36

-- 4. HOW MANY notification rows did app_start_failed EVER produce before today? --
0 rows before 2026-08-23 09:00
91 app_start_failed EVENTS stored, all-time
-- 3b. the customer's own preferences (does app_start_failed appear?) --
-- 3b. the customer's own preferences (does app_start_failed appear?) --
-- HONESTY CHECK: demo-hp has NO customer_notifications row at all --
0 prefs rows for demo-hp

-- why the customer channel logs 'skipped' for other types: --
event_type           status   reason       
-------------------  -------  -------------
backup_run_failures  skipped  operator_only
backup_run_failures  skipped  operator_only
backup_run_failures  skipped  operator_only
