docs(report): §2 reflects the PROVEN-LIVE upgrade the evidence earned

REPORT.md

@@ -31,15 +31,13 @@ v0.156.0) and `felhom-agent/REPORT.md` (R-54, v0.92.1).
 
 ## 2. Capability map
 
-New row in section: **"Box survives an unattended app or guest-network failure"** — status
-**IMPLEMENTED**, deliberately **not** PROVEN-LIVE.
+New row: **"Box survives an unattended app or guest-network failure"** — **PROVEN-LIVE (2026-07-21)**.
 
-One leg genuinely is live and is cited as such: the guest-network watchdog's healthy cycle on
-felhom-pve (`ok=68 total=68 degraded=0` and `DEBUG guestnet: guest network healthy vmid=9201
-mode=dhcp has_route=true dhclient_alive=true`, 12:34:15 CEST). The three legs that would earn
-PROVEN-LIVE are all destructive and operator-present, and none has run: killing immich's primary,
-rebooting 9201 to strand and recover boot orphans, and replaying the dhclient kill. The strict enum
-says a row without that evidence is not PROVEN-LIVE, so it is not.
+It was written as IMPLEMENTED and upgraded only after the evidence existed, which is the order the
+strict enum demands. All three legs then ran operator-present in one session (§4b) and each is cited
+with timestamps in the row itself. The row also carries the gap the validation found (**R-55**) and
+the leg deliberately left out of scope (the static guest → **R-50**), so the badge does not imply
+more than was proven.
 
 The existing **"Box survives a site/network change"** row (PARTIAL) already pointed at R-51/R-52 as
 related work; it stays PARTIAL — R-50 is still its durable fix.