docs: close doc-gaps (hub v0.11.0, onlyoffice:nextcloud occ internals, metricsDBPath verified)

- 05-hub-architecture.md: stale 'felhom-hub v0.6.3' -> v0.11.0 (design-draft note).
- auth-hub-sync-integrations.md: full onlyoffice:nextcloud occ command sequence.
- storage-monitoring-metrics.md: metricsDBPath verified to coincide with the volume-backed
  data_dir on the bootstrap guest (persists; hardcoding is latent fragility only).
- REORG-NOTES: gaps 2/3 CLOSED, gap 5 partially closed.

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

documentation/REORG-NOTES-2026-06-13.md

@@ -86,18 +86,23 @@ anchors):
    daily scheduled path calls it or the unsafe `DumpAppVolumes`, and the exact volume-tar trigger on the
    daily cadence, was not fully traced from `main.go`. Backup doc describes volume tars without asserting
    live-dump consistency. (Trace `cmd/controller/main.go` schedule wiring next.)
-2. **`metricsDBPath` hardcoded** to `/opt/docker/felhom-controller/data/metrics.db` in `main.go` even on
-   the bootstrap-managed guest (no compose). Documented as-is; whether that path is correct under the
-   golden/bootstrap data volume was not assessed.
-3. **`onlyoffice:nextcloud` integration internals** not opened (only confirmed registered + occ-based);
-   documented at one-line depth.
+2. **`metricsDBPath` — CLOSED (2026-06-13).** Verified on the live bootstrap-managed guest 9201: the
+   `felhom-controller-data` volume mounts at `/opt/docker/felhom-controller`, `data_dir` =
+   `/opt/docker/felhom-controller/data`, and `metrics.db` lives there — so the hardcoded
+   `metricsDBPath` (`main.go:189`) **coincides** with the volume-backed `data_dir` and metrics persist
+   correctly. Residual (low-priority backlog, not a live bug): the path is hardcoded rather than derived
+   from `cfg.Paths.DataDir`, so it would diverge if `data_dir` were ever reconfigured. Documented in the
+   storage doc.
+3. **`onlyoffice:nextcloud` internals — CLOSED (2026-06-13).** Read `internal/integrations/onlyoffice_nextcloud.go`;
+   documented the full `occ` command sequence (install/enable + DocumentServerUrl/InternalUrl/jwt_secret/
+   StorageUrl + trusted_domains; `Revoke` = `app:disable`) in `auth-hub-sync-integrations.md`.
 4. **`selfUpdateAuthMiddleware`** (API auth wrapper for the hub-callback `/api/selfupdate|config|geo`
-   routes) referenced but its implementation not read in depth.
+   routes) referenced but its implementation not read in depth. (Still open.)
 5. **Agent/platform/hub design docs (`architecture/01,03,04,05`, `proxmox-platform.md`)** are explicit
-   *design drafts*. I did NOT rewrite them — a half-verified refresh risks regressing decision content.
-   Known drift to fix in a dedicated pass: `05-hub-architecture.md` prose still says "felhom-hub v0.6.3"
-   (live is v0.11.0); `02`/`03` reference v0.33 controller precedent. The top index records the current
-   versions; full grounding of these against agent v0.29.1 / hub v0.11.0 is the recommended next docs slice.
+   *design drafts*. PARTIALLY CLOSED: `05-hub-architecture.md`'s stale "felhom-hub v0.6.3" corrected to
+   v0.11.0 (with a design-draft note). `01,03,04` + `proxmox-platform.md` still reference older precedent
+   and remain design-drafts — full grounding against agent v0.30.0 / hub v0.11.0 is the recommended next
+   docs slice (the top index already records current versions).
 6. **Front-end (templates) deploy progress markup** lives in `web/templates`, documented only via the
    in-memory state it polls, not the template/endpoint markup.