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
Integrate batch-start upstream main
pulse-triage[bot]fcfeba39e0c0
diff --cc docs/release-control/v6/internal/subsystems/ai-runtime.mdindex fa473ad85e,16be3542e0..6ac4fb49d5--- a/docs/release-control/v6/internal/subsystems/ai-runtime.md+++ b/docs/release-control/v6/internal/subsystems/ai-runtime.md@@@ -25,36 -25,27 +25,57 @@@ that same result. Successful reads reta## Purpose+### Guest-config tools require an unambiguous resource identity++The existing VM/system-container configuration tool selects an exact canonical+resource ID before considering a name or bare VMID. A name/VMID matching more+than one guest or a target lacking complete provider placement returns a useful+error without invoking the config provider. Successful configuration and its+governance metadata come directly from the selected typed guest view, never a+second name-based resolution. Unique aliases remain supported; app-container configuration,+command authority and provider permissions are unchanged.++`TestGuestConfigToolIdentity` covers both inventory orders, shared names/VMIDs,+canonical-ID/name collisions, unique aliases and missing/invalid placement at+the actual tool/provider boundary. It checks config attribution and no provider+read on refusal. Source controls are not installed multi-instance recovery.+++### Permanent suppression rules remain reversible — issue #2528++The existing manual suppression API/store semantics remain unchanged. Patrol+Activity now exposes scoped list/confirm/remove/readback for explicitly manual+rules. Deleting a rule permits future matches but does not reopen historical+dismissals, erase findings, broaden creation scope or modify other rules.+Finding-specific Reopen and remembered decisions remain distinct. Frontend+API/component controls plus authenticated handler/store controls verify these+boundaries; source/browser proof does not establish installed or reporter+acceptance.++Manual-rule confirmation retains a readable scope and exact ID with a scrollable long reason and separate action footer. This is an existing-flow accessibility repair, not a change to deletion, finding history or server authority.+++ ### Host filesystem alerts retain exact subjects in scoped Patrol++ An alert-button request may name a collected child subject such as+ `agent:<source-id>/disk:docker-data`. Patrol binds that reference through the+ shared current-inventory resolver only when the exact collected alert identifier+ and subject agree. The canonical owner becomes the collection scope. The alert+ keeps its original child identity, filesystem metadata, observed value, threshold+ and message in both full and budgeted model context. Related child alert evidence+ is retained only for the selected current owner. Missing owners, caller-authored+ child paths, names and conflicting source identities cannot broaden scope.++ Linked VM, container and node owners retain their agent observations. Node/host+ views of the same proven canonical owner are one identity. Automatic alert type+ hints follow that owner while explicit caller type restrictions stay intact.+ Admission and execution resolve independently against current collection state.+ `patrol_alert_scope_test.go` covers linked owners, evidence, repeated resolution+ and rejected subjects. `patrol_host_disk_scope_test.go` exercises the production+ host alert evaluator and HTTP handler. The opt-in browser backend and+ `scripts/check-host-disk-patrol.mjs` verify `/alerts` admission and feedback at+ 1440 and 390 pixels. Browser fixtures qualify admission, not model diagnosis.+### Fully cached Patrol usage — issues #2118 / #2350Zero ordinary input tokens do not mean a run was free or skipped. Any positivediff --cc docs/release-control/v6/internal/subsystems/unified-resources.mdindex 1b6bd2abb1,ff859e1348..58c462a1ce--- a/docs/release-control/v6/internal/subsystems/unified-resources.md+++ b/docs/release-control/v6/internal/subsystems/unified-resources.md@@@ -23,33 -23,21 +23,48 @@@ and sort the complete canonical change## Purpose+### Guest views retain exact governance identity for configuration reads++VM and system-container views expose cloned canonical policy/AI-safe metadata+for their own resource. This lets guest-config reads retain the chosen identity+when names repeat across installations without a second name-based resolution.+The accessor exposes no raw resource or mutation; classification/redaction rules+are unchanged. `TestGuestViewGovernanceIdentity` checks distinct same-name guests,+policy cloning and nil-view handling. Tool controls check its use at the provider+boundary; these are not native installation recovery.+++### Native guest admission replaces the previous canonical facet++A complete native Proxmox guest observation (non-zero VMID) owns its filesystem+read reason, guest-agent state and expectation in both directions. Repeated+ingestion must publish a new cooldown even when the retained disk number is+unchanged, and clear the reason/expectation when the native guest recovers or is+disabled. Non-guest partial Proxmox facets do not own these fields. Numeric+source selection, original memory observation times and identity stay unchanged.++`TestProxmoxGuestReadAdmissionReplacesPreviousFacet` covers available, paused,+recovered, offline and disabled transitions through repeated registry ingestion,+typed/detached reads and JSON. Monitoring's connected optional-command proof+also consumes that same live registry and production broadcast JSON while+checking History withholding. Source clearance is not independent guest thaw,+covered-filesystem writes or native monitoring recovery.++ ### Collected alert subjects share current canonical ownership++ `AlertResourceReferenceResolver` exposes the current-inventory identity owner+ used by history correlation to runtime consumers. Supported producer child+ references bind through durable source identities only. Resolution reads the+ owner, canonical type and source targets under one registry read lock. It never+ uses display names or retained history aliases to resurrect a removed owner.+ An agent's disk, temperature, RAID and custom observations remain owned when an+ operator link folds the agent into a VM, container or node. The presence of the+ agent facet is required for that cross-type ownership. Patrol can therefore+ select the canonical owner without interpreting alert strings independently.+ `alert_scope_test.go` verifies the registry and both read adapters, rejected+ references and absent current owners. Scoped Patrol tests cover linked owners+ and conflicting unqualified source IDs.+### Proxmox node temperature cell follows its own open alert — issue #2068`ProxmoxNodesTable` finds the node's own temperature alert through