# THE ALARMS WERE DELIVERED, NOT JUST RAISED - mailbox read 2026-09-17T00:38Z
# The truth table proves 17 alarms fired and all 17 were true. That is the FEED. This is the
# MAILBOX: proof they actually reached a person. In a project whose recurring trap is "stored is
# not delivered" (91 events once sat in a database having e-mailed nobody), the two are not the
# same claim and only one of them was evidenced before now.

All mails below are from monitoring@felhom.eu to admin@felhom.eu, subject "[Felhom] ... tester-1".
Times are the mail's own; the box and hub run UTC, the mail body prints CEST.

## ROUND 11 - the drive pulled out for twenty minutes. The whole set arrived.
  23:51:31Z  storage_disconnected   "Meghajto varatlanul levalasztva: Adatlemez"
  23:51:49Z  app_start_failed       "Telepitett alkalmazas nem fut: Paperless-ngx"
  23:51:50Z  app_start_failed       "... Nextcloud"
  23:51:50Z  app_start_failed       "... Jellyfin"
  23:51:50Z  app_start_failed       "... Immich"
  23:53:20Z  health_degraded        "Rendszer allapot romlott (volt: ok)"
Four apps named individually, and they are EXACTLY the four whose data lived on the pulled drive.

## ROUND 6 - the whole-guest backup, local tier
  21:59:55Z  whole_guest_backup_failed
             "Whole-guest backup FAILED on the local tier - retrying with backoff (next attempt in 15m0s)"
It names the TIER in the mail subject line's body, not just in the feed.

## ROUND 4 and the OOM
  21:43:07Z  health_critical        "Rendszer allapot kritikus (volt: ok)"
  21:20:26Z  app_oom                "Alkalmazas memoriaja elfogyott: immich (immich-postgres)"

## ROUND 1 - the off-site control round
  21:08:58Z  backup_run_failures    "1 of 12 apps failed to back up in this nightly run: nextcloud"
  21:09:00Z  offbox_repo_orphaned   "A tavoli mentesi tarolo elarvult: a benne levo mentesek egy
                                     korabbi, mar nem elerheto kulccsal..."
The orphan the household would need to know about was MAILED at 21:09, within seconds of the run.

## PHASE 0 - my own seeding damage, reported honestly by the product
  20:32:50Z  app_deploy_failed      "Alkalmazas telepitese nem sikerult: Gokapi - exit code 1"
  20:34:32Z  storage_fill_critical  "Host tester-1-022354: storage \"local-lvm\" CRITICALLY full at
                                     100% (threshold 95%)"
  20:39:58Z  storage_disconnected   an earlier drive event during setup, before round 1
That storage_fill_critical is the thin pool I filled by firing twelve deploys at once. Note which
host it names: tester-1-022354, the NESTED box - not demo-hp. The fence held and the mail proves it.

## WHAT IS NOT HERE, AND WHY THAT MATTERS
NO node_stale mail for tonight's box after round 9's hub outage. The node_stale mails in the
mailbox are from 12:27Z and 18:17Z and name DIFFERENT host ids (tester-1-652049, tester-1-33b6a9) -
earlier boxes, not this one. That is exactly what R-549 predicts: the gap was 29m59s against a
30-minute threshold, so the alarm never fired and no mail was sent. One second the other way and
this section would list a page-out for a box that was healthy and had already repaired itself.

## BASELINE FOR THE TEARDOWN'S CONNECT MAIL
The newest mail in the mailbox at 00:38Z is the 23:53:20Z health_degraded. There is NO self-bind or
connect mail from tonight. The last one was 18:17:46Z, BEFORE the drill began.
So any connect mail appearing after the host delete is provably NEW. The brief specifically flagged
that a previous claim about "the automatic mail waiting in the mailbox" had been read from
yesterday's delete rather than checked - this baseline is what makes tonight's quote checkable.
