Centralize connected infrastructure display names

docs/release-control/v6/internal/subsystems/monitoring.md

@@ -137,6 +137,9 @@ The same applies to proxmox topology coordinates exposed through typed views:
 node, cluster, and instance accessors must return canonical trimmed values so
 monitoring consumers do not fork topology grouping or labeling on `" pve-a "`
 versus `pve-a`.
+Connected infrastructure and monitored-system projections now also use the
+shared unified-resource display-name fallback, so the monitoring layer does
+not rebuild its own canonical name-or-hostname selection for those surfaces.
 
 Storage-backup preservation now also derives node-to-storage membership from
 canonical `ReadState.StoragePools()` instead of from snapshot-owned storage

docs/release-control/v6/internal/subsystems/unified-resources.md

@@ -193,8 +193,9 @@ shared `ResourcePolicyLabel(...)` and `ResourcePolicyRedactedValue(...)`
 helpers instead of through AI-local presentation shims, so policy copying and
 policy-bound labels both stay centralized in the resource model.
 That same contract also owns the canonical resource display-name fallback, so
-name-or-ID presentation stays consistent between the unified AI adapter and
-the AI resource context instead of being recomputed locally.
+name-or-ID presentation stays consistent between the unified AI adapter, the
+AI resource context, and the connected-infrastructure / monitored-system
+projections instead of being recomputed locally.
 
 That same shared store now also persists append-only action lifecycle, action
 audit, and export audit records, giving the control-plane verbs a durable home