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
Point Patrol trigger contracts at the Patrol settings page (#2691)
rcourtman537a32d8ad09
diff --cc docs/release-control/v6/internal/subsystems/api-contracts.mdindex a722d20815,eecf925ff6..8315578386--- a/docs/release-control/v6/internal/subsystems/api-contracts.md+++ b/docs/release-control/v6/internal/subsystems/api-contracts.md@@@ -3319,14 -3304,41 +3320,14 @@@ a new API state machine, queue contractand the `/api/ai/intelligence/changes` route plus `internal/api/contract_test.go`, so the canonical recent-changes endpoint stays on the same intelligence facade and contract snapshot instead of bypassing the shared timeline sourceand the canonical policy-posture snapshot derived from unified resources, so sensitivity, routing, and redaction counts stay owned by the same AI summary contract instead of being reconstructed as a page-local governance rollupand the resource-intelligence payload carried by the drawer AI card, so the resource-detail surface stays on one canonical intelligence contract instead of introducing a separate detail endpoint- and the learned-correlation payload loaded into the shared AI intelligence store, so the Patrol intelligence page and the AI summary page consume the same governed correlation slice instead of each page fetching its own copy+ and the global learned-correlation route `/api/ai/intelligence/correlations`, which has no frontend client today: no page renders that list, so the shared AI intelligence store neither loads nor holds it and the resource drawer reads per-resource correlations from the resource-intelligence payload; a surface that later renders the global list must add one store-owned load instead of a page-local fetchand the shared dashboard-load bundle inside `frontend-modern/src/stores/aiIntelligence.ts`, so the page orchestration stays on the store-owned bundle instead of enumerating the AI fetches inlineand the Patrol page refresh lifecycle in `frontend-modern/src/features/patrol/usePatrolIntelligenceState.ts`, so slow or stalled secondary reads from that shared dashboard-load bundle may continue resolving in the background while the operator-facing Patrol refresh control remains generation-aware, timeout-bounded, and reusable once Patrol findings and status are already visible- and the Patrol header support drawer in `frontend-modern/src/features/patrol/PatrolIntelligenceHeader.tsx`, so API-owned Patrol status and trigger facts can feed a secondary Schedule & model surface without turning provider model, schedule, trigger tuning, or background-only runtime-policy pauses into the primary Patrol control decision+ and the Patrol header in `frontend-modern/src/features/patrol/PatrolIntelligenceHeader.tsx`, which outside setup-only states may summarize noteworthy API-owned `status.trigger_status` facts in one compact line and, unless a provider setup block shows `Fix setup` instead, links to Settings > Pulse Intelligence > Patrol, where the Patrol model, schedule, and trigger tuning are saved through `PUT /api/settings/ai/update`, so none of those settings or background-only runtime-policy pauses become the primary Patrol control decision and the header carries no schedule and model drawerand any frontend presentation of the AI summary's `policy_posture` counts, which must render that canonical snapshot through one shared component instead of page-local posture loops; no frontend surface renders those counts today, and the resource drawer stays on per-resource policy lines- and the dedicated `frontend-modern/src/features/patrol/patrolInvestigationContextModel.ts` owner, so recent-change, learned-correlation, and policy-coverage summary text stays derived from the canonical AI payload in one place instead of as hook-local count and pluralization logic+ and the dedicated `frontend-modern/src/features/patrol/patrolInvestigationContextModel.ts` owner, so if Patrol recent-change, learned-correlation, or policy-coverage summary text returns, it is derived from the canonical AI payload in that one place instead of as hook-local count and pluralization logic; Patrol renders no such summary today and the model carries no such derivationand the Watch-only forward-path handoffs owned by `frontend-modern/src/features/patrol/patrolControlPresentation.ts` together with the Actions inbox empty-state read of `GET /api/ai/patrol/autonomy`, so finding-level and inbox-level mode guidance consumes the canonical Patrol autonomy read/save contract through the Patrol state hook (`handleAutonomyChange`) instead of introducing a second mode mutation path or a page-local autonomy dialect- and that same Patrol investigation-context owner, so the current Patrol- assessment summary may open Assistant with bounded model-only assessment,- verification, latest-run, supporting-context, active-finding, and- resource reference context while leaving prioritization and next-step- reasoning to the configured LLM; active- finding entries may carry live pending Patrol approval posture only as safe- structured handoff actions with approval ID/status/risk/target/request/expiry- metadata, action plan identity/policy/expiry, dry-run posture, and command- counts instead of pasting page-local UI text or raw command payloads into chat,- the drawer target must stay `patrol-assessment` rather than a retired- dashboard target,- and may derive model-only approval/action posture from that same safe- metadata, while visible drawer copy stays compact and does not expose- Patrol-authored recommendations, prompt chips, or action labels as the- answer,- and that same Patrol investigation-context owner, so coverage signals from- the canonical AI summary remain secondary caveats when the same assessment- carries active findings, pending approvals, or governed action references;- Assistant context, briefing action labels, and safety notes must- carry finding priority, affected resources, evidence, and governed approval- posture as context instead of recasting the whole handoff as a coverage gap- and that same Patrol investigation-context owner, so coverage-incomplete- assessments with no active infrastructure findings are serialized as a- verification-gap handoff: model-only context and visible briefing copy must explain what- scoped activity did and did not prove, keep latest-run and supporting-context- facts model-only, and leave next-step selection to the configured LLM- handoff-only metadata, and avoid introducing backend fields beyond the- existing Patrol status plus run-history contracts+ and the Patrol finding-to-Assistant handoff owned by `frontend-modern/src/components/AI/FindingsPanel.tsx`, so the pending-approval, investigation, and proposed-fix reads behind that handoff happen once in the panel instead of in a second, unwired copy inside the Patrol state hookand that same Patrol investigation-context owner, so visible Assistantdrawer handoffs may include live pending-approval metadata only as safeoperator context: approval ID, status, risk, requested/expiry timestamps,diff --cc docs/release-control/v6/internal/subsystems/patrol-intelligence.mdindex ee881010cb,91b836ed78..b8edee3b53--- a/docs/release-control/v6/internal/subsystems/patrol-intelligence.md+++ b/docs/release-control/v6/internal/subsystems/patrol-intelligence.md@@@ -1548,23 -1561,23 +1567,23 @@@ same shared catalog and must remaistate-driven across async settings/catalog loading: a saved direct-providermodel such as `deepseek:deepseek-v4-flash` must render as that provider modelonce the shared catalog supplies it, not fall back visually to the default- model or an unrelated OpenRouter entry because the popover mounted after the+ model or an unrelated OpenRouter entry because the field rendered before thecatalog request completed.The Patrol page now also treats Patrol runtime availability as a first-class-render contract: the header chip, primary summary card, and status bar must-all route through the shared `frontend-modern/src/utils/patrolRuntimePresentation.ts`+render contract: any Patrol surface that presents runtime availability must+route through the shared `frontend-modern/src/utils/patrolRuntimePresentation.ts`helper plus the backend `runtime_state` payload instead of inferring operatorstate from the last healthy summary snapshot or run history alone.-The primary summary strip is descriptive only: it surfaces the current Patrol-assessment label and compact counts, while action choices remain in the-Findings/Runs workspace, header controls, and the LLM-driven Assistant chat.-`frontend-modern/src/features/patrol/patrolInvestigationContextModel.ts` may-package the current Patrol assessment, verification posture, latest run,-secondary investigation context, bounded recent-change and learned-correlation-evidence, bounded active-finding summaries, deduped resource references, and-safe structured approval/action references as model-only context, but visible-drawer copy must not promote Pulse-authored next-step metadata, action chips, or-suggested prompts as the answer. Command payloads stay out of drawer chrome.+Patrol renders no primary summary strip today. If one returns it stays+descriptive only: it surfaces the current Patrol assessment label and compact+counts, while action choices remain in the workspace, header controls, and the+LLM-driven Assistant chat.+`frontend-modern/src/features/patrol/patrolInvestigationContextModel.ts`+packages the Patrol finding, attention-item, and run handoffs, carrying only+bounded model-only context, resource references, and safe structured+approval/action references, and visible drawer copy must not promote+Pulse-authored next-step metadata, action chips, or suggested prompts as the+answer. Command payloads stay out of drawer chrome.Run-history rows now follow that same Assistant handoff model. A selected`frontend-modern/src/components/patrol/RunHistoryEntry.tsx` row may openAssistant through@@@ -1941,13 -1945,13 +1960,13 @@@ plain-text renders: the latest-run segmseparator between run kind and result, so degraded entries read as`Scoped run · error` rather than collapsing into concatenated strings like`Scoped runerror`.- Those runtime facts must stay aligned with Patrol mode copy. The- header settings surface should expose alert-triggered and anomaly-triggered- scoped patrols as separate controls, with the legacy aggregate event-trigger- toggle treated as compatibility-only transport rather than the primary product+ Those runtime facts must stay aligned with Patrol mode copy. Settings > Pulse+ Intelligence > Patrol, not the Patrol header, exposes alert-triggered and+ anomaly-triggered scoped Patrols as separate controls, with the legacy aggregate+ event-trigger toggle treated as compatibility-only transport rather than the primary productmodel.-The findings empty state must also stay subordinate to the Patrol header and-assessment shell rather than mirroring their timing metadata. In the primary+The findings empty state must also stay subordinate to the Patrol header+rather than mirroring its timing metadata. In the primaryPatrol page, `frontend-modern/src/components/AI/FindingsPanel.tsx` shouldexplain the absence of active findings without repeating `Last activity`,`Next run`, or interval schedule details that already belong to the header and