Preserve Docker container metadata in unified resources

docs/release-control/v6/internal/subsystems/frontend-primitives.md

@@ -188,6 +188,10 @@ and Kubernetes platform pages may add native API-backed sections, but the tabs
 must use `PlatformSectionTabs`, canonical table alignment helpers, and shared
 resource type presentation/reporting helpers rather than page-local tab shells,
 alignment classes, or ad hoc report-category coercion. Platform tabs are
+feature-owned consumers of canonical resource payloads: Docker page model
+helpers may prefer backend-authored `DockerData` stack and Podman metadata for
+search/display while shared primitives continue to own only the tab shell,
+filter controls, and reusable presentation affordances. Platform tabs are
 workflow-level navigation, not one visible tab per API resource kind, and they
 must be evidence-gated by their owning row or signal model. `Overview` is the
 stable landing surface; supporting workflow tabs appear only when the current

docs/release-control/v6/internal/subsystems/storage-recovery.md

@@ -762,6 +762,12 @@ recovery scope, or a storage/recovery-owned secret source.
     recovery must treat that fallback as descriptive host/VM uptime
     only; they must not reinterpret it as backup freshness, recovery
     point recency, or protection cadence.
+    Docker / Podman `DockerData` container lifecycle, Podman metadata, and
+    cumulative block I/O totals remain unified-resource runtime context.
+    Storage and recovery may use those fields only as workload description
+    when linking to an owning runtime/platform page; they must not reinterpret
+    container block I/O totals as backup throughput, recovery-point evidence,
+    protection cadence, or storage-health ownership.
 30. Keep VMware placement, cluster service state, guest-detail, VM snapshot-tree, VM virtual-hardware configuration, VMware Tools, VM hardware Ethernet, VM hardware disk, and network enrichment descriptive on that same shared unified-resource contract. When `internal/vmware/provider.go`, `internal/unifiedresources/types.go`, and `frontend-modern/src/hooks/useUnifiedResources.ts` project datacenter, cluster, `vmware.clusterHaEnabled`, `vmware.clusterDrsEnabled`, folder, runtime-host, datastore-attachment, guest-hostname, guest-IP, `vmware.currentSnapshotId`, `vmware.snapshotTree`, snapshot creation/state/quiesce/current markers, child snapshot metadata, `vmware.hardware`, virtual hardware version, hardware upgrade policy/version/status/error, boot type/order/retry/setup-mode flags, CPU cores-per-socket and hot-add/remove flags, memory hot-add settings, `vmware.tools`, Tools run state, version status, version number/string, install type, upgrade policy, auto-update support, install-attempt count, guest reboot requests, `vmware.networkAdapters`, adapter MAC address/type, backing network id/name, backing type, connection state, start-connected / guest-control flags, `vmware.virtualDisks`, virtual disk label/type, IDE/SCSI/SATA/NVMe placement, VMDK path, backing type, datastore name, capacity, `vmware.networkType`, `vmware.networkHostNames`, or `vmware.networkVmNames` onto canonical VMware `agent` / `vm` / `storage` / `network` resources, storage and recovery may use that detail for labeling, navigation, and VM investigation context only; they must not promote those topology, cluster-service, guest, snapshot-tree, virtual-hardware, VMware Tools, vNIC, virtual disk, or network fields into recovery ownership, restore targeting, protection grouping, compliance scoring, or a VMware-local recovery taxonomy without a separately governed slice.
 31. Keep VMware datastore classification neutral on the shared storage adapter contract. When `frontend-modern/src/features/storageBackups/resourceStorageMapping.ts`, `frontend-modern/src/features/storageBackups/resourceStoragePresentation.ts`, and `frontend-modern/src/features/storageBackups/storageAdapters.ts` evolve canonical storage-record mapping, VMware-backed datastores must continue to land on the shared storage route as inventory-only datastores with neutral protection fallback, not as backup repositories, backup targets, or recovery-protected resources.
     That same shared storage adapter boundary also owns canonical platform

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

@@ -246,6 +246,11 @@ those rows through a variant-switched generic inventory table. Swarm service
 rows must preserve the service update status emitted by the Docker adapter, and
 engine storage rows must stay host-scoped with table proof hooks so browser
 proof can distinguish a populated disk-usage tab from an empty fixture.
+Runtime container detail payloads must preserve the agent-reported lifecycle
+timestamps, Podman pod/compose/auto-update/user-namespace metadata, and
+cumulative block I/O totals on `DockerData`; frontend detail summaries and
+Docker page search consume those backend-authored fields before falling back to
+legacy labels.
 Docker network rows must consume canonical runtime attachment relationships,
 not page-local topology inference, when the unified-resource snapshot provides
 them. Runtime container-to-network membership is represented as active