Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Reconcile optional Proxmox denial repair with current backup contracts
pulse-triage[bot]1d13f0a0adcf
diff --cc docs/release-control/v6/internal/subsystems/unified-resources.mdindex 10ee3e81ea,628a5f7cc3..e7bc95920a--- a/docs/release-control/v6/internal/subsystems/unified-resources.md+++ b/docs/release-control/v6/internal/subsystems/unified-resources.md@@@ -23,29 -23,26 +23,49 @@@ and sort the complete canonical change## Purpose+### A dated backup disclosure identifies the restore point, not only its owner++The By date table keeps its existing native disclosure visible at phone widths,+with a reserved 36px target beside the wrapping identity. A disclosure names the+workload/PVE connection, source kind, precise creation time (or Unknown), backup+reader, location and native identifier. Repeated workloads, tied dates and+unavailable dates do not collapse into indistinguishable controls; sorting does+not supply identity. Visible Created detail uses the same year/second/time-zone+precision. Its Identifier is the native record ID, not a file count or format;+the previous file/path metadata remains separately labelled. State-only polls do not rename the point; revised reader/location+facts update the existing disclosure without dropping focus or changing owners.++Normal-suite `ProxmoxRecoverableTable.test.tsx` and+`recoverableIdentityAccess.test.tsx` cover names, unknown/tied dates, raw inventory+consumption, visible controls, single native activation and scoped refresh.+Actual-App desktop/narrow browser proof exercises point selection by accessible+identity, keyboard/phone activation, close-focus return and same-ID polling,+with inspected pixels. No shared primitive, source identity, provider read,+classification, count, policy or guest/backup/restore operation changes. This+makes existing inspection usable; it does not establish a tested restore,+original guest recovery or release availability.+++ ### Explicit Proxmox update verdicts carry their complete wire observation++ `internal/unifiedresources/proxmox_update_evidence_json.go` serializes a PVE+ node's explicit pending-update status with its count, successful origin and+ fixed reason together. It includes a measured zero, an empty cleared reason+ and a null absent origin. Generic canonical facet merges otherwise retain+ omitted keys: after a stale seven-package observation, a successful empty+ response must show checked zero without inherited access-denial help. Losing+ the successful origin must likewise clear it, not retain an older date.++ The canonical API resource and realtime/broadcast projection use the same+ Proxmox metadata serializer. Guests and legacy sources without an explicit+ update verdict retain their previous payload exactly, including omitted zero+ fields; no new observation, permission, identity, polling or UI policy is added.+ `proxmox_update_evidence_test.go` covers checked/stale zero, unavailable/offline+ clears, generic merge behaviour, API/realtime parity and unchanged guest/legacy/+ nil payloads. Consuming browser proof must exercise the actual producer frames+ through the existing canonical merger and open node drawer at desktop/narrow+ widths, not replace an omitted zero with a fixture-supplied value.+### Restore-point inspection states what its evidence cannot confirmThe existing By date record detail places a visible, wrapping evidence-limits