REPORT: live verification of v0.82.0 on guest 9201 (F2 no-op + change paths, F1 NO-RESTIC)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FpBYrZCt9sFDqLgbG5GRGD

REPORT.md

@@ -45,7 +45,18 @@ the dashboard/UI): `ResticSchedule` config, `migrateResticToRsync` settings migr
 
 ## Deploy & verify (guest 9201 / felhom-pve)
 
-- Deployed image: `gitea.dooplex.hu/admin/felhom-controller:0.82.0` — _status filled after live deploy_
-- `docker exec felhom-controller command -v restic` → `NO-RESTIC` (F1)
-- FileBrowser `StartedAt` UNCHANGED across a no-op sync / controller restart (F2)
-- Sanity: a real config change (drive enroll/deregister) DID recreate FileBrowser (StartedAt changed)
+Deployed via the golden bootstrap mechanism: `docker pull …:0.82.0` into the guest, set
+`/etc/felhom-controller-image` → `0.82.0`, `systemctl restart felhom-controller-bootstrap.service`.
+
+- `docker ps` → `gitea.dooplex.hu/admin/felhom-controller:0.82.0 Up … (healthy)` ✓
+- **F1:** `docker exec felhom-controller command -v restic` → `NO-RESTIC` ✓
+- **F2 (no-op):** deploying 0.82.0 restarted the controller; its startup sync logged
+  `FileBrowser sync — no config/compose change, ensured running without recreate (3 storage path(s))`,
+  and FileBrowser `StartedAt` stayed `2026-06-23T18:15:47` (UNCHANGED — not bounced) ✓
+- **F2 (change path):** dirtied the on-disk `config.yaml` + restarted the controller → log
+  `FileBrowser mounts synced (recreated) — 3 storage path(s), config updated`, FileBrowser `StartedAt`
+  advanced to `2026-06-24T09:05:53` (recreated on a real change) ✓. The sync regenerated `config.yaml`
+  back to canonical (test line gone), FileBrowser + controller healthy — state restored.
+
+Method: invoked the exact server-side sync (controller restart → `syncFileBrowserMounts`) on the live
+guest; no browser tool needed for this check (it's container-lifecycle, observed via `docker inspect`).