docs: REPORT/CHANGELOG/README — v0.72.0 FileBrowser boot-recreate convergence + live x2 reboot acceptance

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

controller/README.md

@@ -663,6 +663,15 @@ not just those with HDD data. Non-HDD apps can configure destination, method, an
 >   path — merging `local_api` from `bootstrap.json` into an existing controller.yaml that lacks it (seeded
 >   before `local_api` existed) — because without it `agentClient()` returns "agent not configured" and the
 >   entire gate + boot recovery silently die.
+>   **v0.72.0 — FileBrowser convergence on boot-recreate:** FileBrowser is base-infra (it binds each
+>   drive's `userdata` but has no `HDD_PATH`, so it is NOT in the drive-backed recreate set) — after a
+>   host reboot its mounts could be stale (the early first-boot bring-up bound them before the drives went
+>   live). `processGuestBootChange` now, **after** `pollLiveBinds` confirms the binds and the apps are
+>   recreated, triggers `go s.SyncFileBrowserMounts()` so FileBrowser converges against the now-live drives.
+>   The sync runs unconditionally (FileBrowser reflects the current bind state even if no app needed
+>   recreating). The recreate loop is a pure `recreateDriveBackedApps(stacks, present, recreate, syncFB)`
+>   that calls `syncFB` exactly once, after every recreate. Live-accepted over two real `felhom-pve`
+>   reboots (FileBrowser non-stale, all drive-backed apps recovered, agent tolerated a `/dev/sdX` swap by UUID).
 >
 > **⚠️ Rebuilt on the agent-delegated disk model (v0.43.0), made ROLE-AWARE in v0.44.0, UX-polished in
 > v0.45.0.** After the 8C