diff --git a/REPORT.md b/REPORT.md
index ebaac64..726fee2 100644
--- a/REPORT.md
+++ b/REPORT.md
@@ -39,13 +39,20 @@ the controller's display + its own registry bookkeeping/impact lookups now use t
   pattern).
 
 ## Deploy (v0.80.0 → guest 9201)
-- _(filled at deploy)_ built+pushed `:0.80.0` on 192.168.0.180; deployed to 9201; `:0.80.0 Up (healthy)`.
+- Built + pushed `gitea.dooplex.hu/admin/felhom-controller:0.80.0` on 192.168.0.180; deployed to 9201
+  (pull → `/etc/felhom-controller-image` → restart bootstrap unit); `docker ps` → `:0.80.0 Up (healthy)`.
 
-## Verification
-- _(filled at verify)_ disk card sub-line shows `/mnt/felhom-drives/felhom-flash` (+usb); the rendered
-  eject/wipe button onclick args carry the stable path; "Regisztrálva" intact; `2 connected`.
+## Verification (served page JS + data the card renders from)
+- Served `/settings` JS (the disk card is built client-side from these): sub-line
+  `… +(d.mount_path?' · '+esc(regKey(d)):'')` (stable); `confirmEject('+reg+')` and
+  `confirmWipe('+dev+','+reg+')` (stable); `registerDrive('+mpRaw+')` (raw). Confirms v0.80.0 shipped.
+- `GET /api/disks`: `felhom-flash → guest_path=/mnt/felhom-drives/felhom-flash`,
+  `felhom-usb → guest_path=/mnt/felhom-drives/felhom-usb` ⇒ the card renders the stable path and the
+  eject/wipe buttons carry it.
+- Regression: `[PASS] Storage paths: 2 connected, 0 disconnected`; `[PASS] System data path: /mnt/sys_drive`.
 - NOT live-clicked: the destructive eject/wipe buttons (would unmount/format the demo drives). Verified
-  the path-mapping logic by inspection + the agent ops are unchanged (raw via `agentWhere`/device).
+  the path-mapping logic by inspection + the agent ops are unchanged (raw via `agentWhere`/device); the
+  rendering is pure client-side JS over the confirmed-correct inputs (bridge not attached this session).
 
 ## Observations (recorded, NOT acted on)
 - `pendingActivationDrives` still keys off the agent's raw `MountPath` (the "~30 mp újraindítás" banner);