docs: REPORT — clarify hub v0.7.2 deploy deferred (live hub at v0.6.3)

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

REPORT.md

@@ -8,11 +8,17 @@
 
 ## Outcome
 
-**Pushed as hub `v0.7.2`.** The felhom-agent slice-5 Phase A work populates the host-report's
-`storage_targets` (previously a defined-but-empty stub). This change is the hub half: accept
-and persist them. Deliberately minimal — the authoritative storage manifest (desired
-class/role/policy/creds) is hub-owned and arrives at slice 10; this slice only mirrors what the
-agent observes.
+**Code committed + pushed (changelogged as `v0.7.2`); image build/deploy deferred.** The
+felhom-agent slice-5 Phase A work populates the host-report's `storage_targets` (previously a
+defined-but-empty stub). This change is the hub half: accept and persist them. Deliberately
+minimal — the authoritative storage manifest (desired class/role/policy/creds) is hub-owned and
+arrives at slice 10; this slice only mirrors what the agent observes.
+
+> **Deploy note:** the live hub is **v0.6.3**, behind the changelog (v0.7.0/v0.7.1 were
+> committed but appear undeployed). Building+deploying v0.7.2 would also ship those intervening
+> versions, so the deploy is deferred to an operator decision — flagged, not silently done. The
+> change is backward-compatible (an agent sending `storage_targets: []` is accepted unchanged),
+> so the live hub keeps ingesting host-reports fine until then.
 
 ## What landed (`hub/internal/api/handler.go`, `host_test.go`, golden)