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
docs: correct customer docs that drifted from the source
rcourtman8a99b16d6cfc
diff --git a/.env.example b/.env.exampleindex 5c49930b70..58704db643 100644--- a/.env.example+++ b/.env.example@@ -17,7 +17,6 @@# -----------------------------------------------------------------------------# Optional security toggles# ------------------------------------------------------------------------------# DISABLE_AUTH=false# PULSE_AUDIT_LOG=true# -----------------------------------------------------------------------------diff --git a/ARCHITECTURE.md b/ARCHITECTURE.mdindex 4643dd3d6a..b8f63afa5e 100644--- a/ARCHITECTURE.md+++ b/ARCHITECTURE.md@@ -122,7 +122,7 @@ All backend code lives under `cmd/`, `internal/`, and `pkg/`. The binary is asse11. **Audit Logging (`pkg/audit`)**- Defence-in-depth: every mutation is logged to SQLite, optionally signed with per-tenant encryption keys.- - Async logging mode (`PULSE_AUDIT_ASYNC`) for high-throughput environments.+ - Async audit logging is on by default (`PULSE_AUDIT_ASYNC=false` disables it); see `docs/CONFIGURATION.md`.- Tenant-aware logger manager for isolated per-org audit trails.### Data Flowdiff --git a/SECURITY.md b/SECURITY.mdindex 2c73a2e3ff..739b72da95 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -366,7 +366,7 @@ Pulse supports **OIDC** and **SAML** SSO providers with multi-provider configura- **OIDC**: Google, Authentik, Keycloak, Auth0, or any compliant provider.- **SAML**: For enterprise IdPs that use SAML assertions.- Multiple providers can be enabled simultaneously; the login page shows all available SSO buttons.-- Configure via **Settings → Security → SSO Providers** (admin required).+- Configure via **Settings → Security → Single Sign-On** (admin required).See `docs/PROXY_AUTH.md` for proxy-based auth (Authentik, Authelia, Cloudflare).diff --git a/docs/AGENT_SECURITY.md b/docs/AGENT_SECURITY.mdindex 98ceeb2eff..e82c6b9970 100644--- a/docs/AGENT_SECURITY.md+++ b/docs/AGENT_SECURITY.md@@ -111,12 +111,17 @@ Inside-guest runtime visibility is explicit. Installing the agent inside a VM orLXC authorizes that guest-local agent to report Docker/Podman monitoring dataaccording to its local module flags. A Proxmox node agent does not look insideLXCs by default. Its automatic LXC filesystem collector is a node-local-capacity query only: it runs `pct list`, then `pct df <vmid>` for guests already-reported running, and reports mount keys, volume labels, mount paths, and-capacity/usage numbers. It does not run a command inside the guest or read-guest files, processes, environment, or container-runtime metadata. It skips-guests reported stopped and bounds command time, output, guest count, and disk-count.+capacity query only. On cgroup v2 PVE hosts it finds running guests from the+node's container configs and cgroup state, reads each running guest's init+process ID and status from cgroup and `/proc`, and measures mount capacity with+statfs through `/proc/<pid>/root`. When that discovery cannot establish a guest's state (for+example on cgroup v1 hosts) it falls back to `pct list`, with `lxc-info` to+find each guest's init process, and it runs `pct df <vmid>` for a guest only+when the statfs probe is unavailable or fails. It reports+mount keys, volume labels, mount paths, and capacity/usage numbers. It does not+run a command inside the guest or read guest file contents, environment, or+container-runtime metadata. It skips guests reported stopped and bounds command+time, output, guest count, and disk count.The node agent can collect Docker container inventory from LXC gueststhrough `pct exec`, but only after an explicit server-side opt-in: thediff --git a/docs/AI.md b/docs/AI.mdindex daa739f3e4..3737e50112 100644--- a/docs/AI.md+++ b/docs/AI.md@@ -75,7 +75,7 @@ Patrol is a scheduled model workflow that builds a rich, system-wide snapshot anScheduled/Event Trigger│▼-buildSeedContext() ── infrastructure evidence and policy context+buildTriageSeedSectionsState() ── infrastructure evidence and policy context│▼LLM analysis (with tools) ← pulse_storage, pulse_metrics, pulse_alerts, etc.@@ -118,7 +118,7 @@ can handle the steady-state signal.### The Patrol attention queue-The first thing Patrol shows is **Needs attention**, a single operator queue+The first thing Patrol shows is the **Inbox** tab, a decision inbox headed "N decisions need you" (or "No decisions are waiting"), a single operator queueprojected from Pulse's canonical alert lifecycle. It combines currentoperational state with evidence quality and protection context; it does notcreate a second finding lifecycle.@@ -168,7 +168,7 @@ Every patrol run passes the LLM comprehensive context about your environment:Beyond raw metrics, Patrol prepares structured evidence for the model:-- **Trend summaries** — 24h and 7d samples showing `growing`, `stable`, `declining`, or `volatile` behavior+- **Trend summaries** — 24h and 7d samples showing `growing`, `stable`, or `declining` behavior- **Baseline evidence** — Z-score anomaly evidence from historical metrics- **Capacity estimates** — "Storage pool reaches 95% in about 12 days at current growth rate"- **Infrastructure changes** — Detected config changes, VM migrations, new deployments@@ -228,7 +228,7 @@ Note: `info` and `watch` level findings are filtered out to reduce noise.Findings can be managed via the UI or API:-- **Get help**: Chat with AI to troubleshoot the issue+- **Open in Assistant**: Open Pulse Assistant with the finding attached to troubleshoot the issue (on Patrol findings it appears under **Resolve or dismiss**)- **Resolve**: Mark as fixed (finding will reappear if the issue resurfaces)- **Dismiss**: Record feedback about this finding; use **Reopen** to undo its dismissal- **Create rule**: Permanently auto-dismiss future findings for the selected resource and category@@ -368,9 +368,9 @@ Patrol supports four modes that decide how far Pulse can go after it finds an is| Mode | Behavior | Plan ||-------|----------|------|| **Watch only** | Detect issues only. No investigation or fixes. | Community (BYOK) |-| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |-| **Auto-fix safe issues** | Runs warning-level governed fixes automatically and verifies results. Critical findings still require approval by default. | Pro / hosted Cloud |-| **Policy autopilot** | Runs eligible governed fixes automatically and verifies results. Use only in environments where this is acceptable. | Pro / hosted Cloud |+| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |+| **Safe auto-fix** | Runs warning-level governed fixes automatically and verifies results. Critical findings still require approval by default. | Pro / hosted Cloud |+| **Autopilot** | Runs eligible governed fixes automatically and verifies results. Use only in environments where this is acceptable. | Pro / hosted Cloud |Community and Relay installs can still run scheduled Patrol findings with BYOK. Watch only remains the free-first baseline; investigation, proposed fixes, and fix execution are paid AI-operations capabilities rather than a core monitoring limit.@@ -409,8 +409,8 @@ MaybeInvestigateFinding()| Setting | Default | Description ||---------|---------|-------------|-| `MaxEvidenceCalls` | 15 | Maximum evidence-tool calls per investigation; the terminal typed proposal is reserved separately |-| `MaxTurns` | 17 | Internal provider-response safety ceiling derived from the evidence budget (budget + proposal + final summary) |+| `MaxEvidenceCalls` | 10 | Maximum evidence-tool calls per investigation; the terminal typed proposal is reserved separately |+| `MaxTurns` | 12 | Internal provider-response safety ceiling derived from the evidence budget (budget + proposal + final summary) || `Timeout` | 10 min | Maximum duration per investigation || `MaxConcurrent` | 3 | Maximum concurrent investigations || `MaxAttemptsPerFinding` | 3 | Maximum investigation attempts per finding |@@ -508,7 +508,7 @@ never excluded a guest from action plans, so it has been removed.## Weekly summary and emailPulse's **This week** summary adds up retained Patrol activity over the last-seven days. Open **Patrol → Activity** to read it; use **Settings → Reporting**+seven days. Open **Patrol → Activity** to read it; use **Settings → Data & Reports**to schedule the same summary by email. The card, weekly email and **Report type**selector are included in **v6.5.0**. An older build can lack these controls.@@ -545,7 +545,7 @@ grant scheduling access. See [Plans and entitlements](PULSE_PRO.md).1. Check that email notifications are **enabled and configured** under**Alerts → Notifications**. Listing recipients on a schedule does notconfigure a mail provider or enable email.-2. Open **Settings → Reporting**, choose **Create schedule**, then set+2. Open **Settings → Data & Reports**, choose **Create schedule**, then set**Report type** to **Patrol weekly summary**.3. Enter a schedule name, weekday, time and an IANA **Timezone**, such as`Europe/London`. The summary is weekly, covers the last seven days, and is@@ -841,7 +841,7 @@ Patrol runs on a configurable schedule:| 10 min – 7 days | Configurable interval (default: 6 hours) |Patrol can also be triggered by:-- **Manual run**: Click "Run Patrol" in the UI+- **Manual run**: Click "Check now" in the Patrol header (the button shows "Starting…" or "Running…" while a run is starting or in progress)- **Alert-triggered analysis (Pro and above)**: Runs when an alert fires- **API call**: `POST /api/ai/patrol/run`diff --git a/docs/AI_AUTONOMY.md b/docs/AI_AUTONOMY.mdindex d5f28ddb05..9a87c2e084 100644--- a/docs/AI_AUTONOMY.md+++ b/docs/AI_AUTONOMY.md@@ -24,14 +24,14 @@ Patrol mode sets how far Pulse can go when Patrol finds something that needs att| Mode | Key | Detect | Investigate | Fix warning-level issues | Fix critical issues | Plan ||-------|-----|:------:|:-----------:|:------------------------:|:-------------------:|------|| **Watch only** | `monitor` | Yes | No | No | No | Community |-| **Ask before changes** | `approval` | Yes | Yes | Approval required | Approval required | Pro / legacy Pro+ / Cloud |-| **Auto-fix safe issues** | `assisted` | Yes | Yes | Execute automatically | Approval required | Pro / legacy Pro+ / Cloud |-| **Policy autopilot** | `full` | Yes | Yes | Execute automatically | Execute automatically | Pro / legacy Pro+ / Cloud |+| **Ask first** | `approval` | Yes | Yes | Approval required | Approval required | Pro / legacy Pro+ / Cloud |+| **Safe auto-fix** | `assisted` | Yes | Yes | Execute automatically | Approval required | Pro / legacy Pro+ / Cloud |+| **Autopilot** | `full` | Yes | Yes | Execute automatically | Execute automatically | Pro / legacy Pro+ / Cloud |- **Watch only** (default): Patrol creates findings but takes no action. This is the Community and Relay baseline. Suitable for learning what Patrol detects before enabling investigation or fix execution.-- **Ask before changes** (Pro and above): Patrol investigates findings and proposes fixes. All fixes queue for manual approval before execution.-- **Auto-fix safe issues** (Pro and above): Warning-level safe fix plans can execute automatically. Critical findings still require approval. This is the recommended starting point for most Pro and legacy Pro+ users who enable fix execution.-- **Policy autopilot** (Pro and above): Safe fix plans can execute without approval. Requires an explicit toggle and a Pro, legacy Pro+, or Cloud license. Recommended only for environments with thorough alert coverage.+- **Ask first** (Pro and above): Patrol investigates findings and proposes fixes. All fixes queue for manual approval before execution.+- **Safe auto-fix** (Pro and above): Warning-level safe fix plans can execute automatically. Critical findings still require approval. This is the recommended starting point for most Pro and legacy Pro+ users who enable fix execution.+- **Autopilot** (Pro and above): Safe fix plans can execute without approval. Requires an explicit toggle and a Pro, legacy Pro+, or Cloud license. Recommended only for environments with thorough alert coverage.### Configuration@@ -158,10 +158,8 @@ When Patrol mode is `approval`, `assisted`, or `full`, Patrol investigates findi|---------|---------|-------|-------------|| `patrol_investigation_budget` | 10 | 5–30 | Maximum evidence-tool calls per investigation; Patrol derives a separate model-response safety ceiling || `patrol_investigation_timeout_sec` | 600 | 60–1800 | Maximum seconds per investigation |-| `max_concurrent_investigations` | 3 | — | Parallel investigation limit |-| `max_attempts_per_finding` | 3 | — | Retries before marking as `needs_attention` |-| `investigation_cooldown_sec` | 3600 | — | Cooldown before re-investigating a finding |-| `timeout_cooldown_sec` | 600 | — | Shorter cooldown after timeout failures |++The following limits are fixed and cannot be changed: up to 3 investigations run in parallel, up to 3 attempts per finding, a 1 hour cooldown before re-investigating a finding, and a shorter 10 minute cooldown after a timeout failure.---@@ -203,9 +201,9 @@ To stop Pulse acting on a specific guest, host or container, open its drawer, chFor new deployments, gradually increase Patrol mode:1. **Start with Watch only** — Run Patrol for a few cycles to see what it detects. Dismiss false positives.-2. **Move to Ask before changes where available** — Enable investigation. Review proposed fixes to build confidence.-3. **Use Auto-fix safe issues when fix execution is enabled** — Let Patrol execute warning-level fixes while you approve critical fixes.-4. **Consider Policy autopilot** — Only if your environment has comprehensive alerting and you trust the fix patterns.+2. **Move to Ask first where available** — Enable investigation. Review proposed fixes to build confidence.+3. **Use Safe auto-fix when fix execution is enabled** — Let Patrol execute warning-level fixes while you approve critical fixes.+4. **Consider Autopilot** — Only if your environment has comprehensive alerting and you trust the fix patterns.---diff --git a/docs/API.md b/docs/API.mdindex 1b5a6e56d8..0761aa6c7c 100644--- a/docs/API.md+++ b/docs/API.md@@ -159,7 +159,7 @@ State-changing session requests also require Pulse's CSRF protection, whichthe UI handles.Session endpoints:-- `POST /api/login` (sets `pulse_session` + `pulse_csrf`)+- `POST /api/login` (sets the session cookie, `pulse_session` over plain HTTP or `__Host-pulse_session` over HTTPS, plus `pulse_csrf`)- `POST /api/logout` (clears session)Login body:@@ -260,7 +260,7 @@ Lightweight HTML status page for quick checks.Returns the unified resource list with pagination + aggregations. Requires `monitoring:read`.Query params:-- `type`: comma-separated list (e.g., `agent`, `vm`, `system-container`, `container`, `docker-service`, `storage`, `pbs`, `pmg`, `k8s-cluster`, `k8s-node`, `pod`, `k8s-deployment`, `physical_disk`, `ceph`)+- `type`: comma-separated list (e.g., `agent`, `vm`, `system-container`, `app-container`, `docker-service`, `storage`, `pbs`, `pmg`, `k8s-cluster`, `k8s-node`, `pod`, `k8s-deployment`, `physical_disk`, `ceph`)- `source`: comma-separated list (e.g., `proxmox`, `agent`, `docker`, `pbs`, `pmg`, `kubernetes`)- `excludeSource`: comma-separated list of sources that must not be present on a matching resource- `status`: comma-separated list (`online`, `offline`, `warning`, `unknown`)@@ -795,7 +795,7 @@ node identity as the bootstrap response. The optional `backup_perms=true`query is supported only for `type=pve`.### Setup Script URL-`POST /api/setup-script-url` (auth)+`POST /api/setup-script-url` (admin, `settings:write`)Generates a one-time setup token and URL for `/api/setup-script`.Canonical callers must send a supported `type` of `pve` or `pbs` plus anon-empty `host`; the backend normalizes that host before minting the setup@@ -849,12 +849,15 @@ back to the installer or runtime-side Unified Agent:`{"status":"success","action":"use_token","type":"pve|pbs","source":"agent|script","host":"https://...","nodeId":"<stored-name>","nodeName":"<stored-name>",...}`.### Agent Install Command-`POST /api/agent-install-command` (auth)+`POST /api/agent-install-command` (admin, `settings:write`)Generates an API token and install command for agent-based Proxmox setup.### Discovery-`GET /api/discover` (auth)-Runs network discovery.+`GET /api/discover` (admin, `settings:write`)+Returns the last cached network discovery result from the background discovery service. It does not scan.++`POST /api/discover` (admin, `settings:write`)+Runs a manual network scan. JSON body: `{"subnet": "...", "use_cache": false}`. `subnet` defaults to `auto`; `use_cache: true` returns the cached result instead of scanning.### AI Discovery (Service Discovery)Service discovery is used by Pulse Assistant and the UI to inventory web services and enrich links.@@ -871,7 +874,7 @@ Service discovery is used by Pulse Assistant and the UI to inventory web service- `PUT /api/discovery/{type}/{targetId}/{resourceId}/notes`### Test Notification-`POST /api/test-notification` (auth)+`POST /api/test-notification` (admin, `settings:write`)Broadcasts a WebSocket test event.---@@ -1050,7 +1053,7 @@ it, use the snooze and unsnooze endpoints below.- `POST /api/alerts/unacknowledge` (body: `{ "alertIdentifier": "alert-id" }`)- `POST /api/alerts/snooze` (body: `{ "alertIdentifier": "alert-id", "until": "RFC3339 timestamp" }`; pauses delivery and escalation for up to 30 days while monitoring continues)- `POST /api/alerts/unsnooze` (body: `{ "alertIdentifier": "alert-id" }`; resumes normal policy without resolving the incident)-- `POST /api/alerts/clear` (body: `{ "id": "alert-id" }`)+- `POST /api/alerts/clear` (body: `{ "alertIdentifier": "alert-id" }`)---@@ -1124,7 +1127,7 @@ Returns a new raw token (shown once) and updates stored hashes:## 🧾 Audit Log (Pro)-These endpoints require admin access and the `settings:read` scope. On Community, the list endpoint returns an empty set and `persistentLogging: false`.+These endpoints require admin access and the `audit:read` scope. On Community (no `audit_logging` license), these endpoints return HTTP 402 Payment Required with `error: "license_required"` and `feature: "audit_logging"` before any events are read.### List Audit Events`GET /api/audit?limit=100&event=login&user=admin&success=true&startTime=2024-01-01T00:00:00Z&endTime=2024-01-31T23:59:59Z`@@ -1235,7 +1238,7 @@ Tests SSH connectivity for temperature collection (requires setup token or auth)### Scheduler Health`GET /api/monitoring/scheduler/health`-Returns scheduler health, DLQ, and breaker status. Requires `monitoring:read`.+Returns scheduler health, DLQ, and breaker status. Requires authentication (session or API token); no specific scope is enforced.### Updates (Admin)- `GET /api/updates/check`@@ -1254,7 +1257,7 @@ Returns scheduler health, DLQ, and breaker status. Requires `monitoring:read`.- `GET /api/infra-updates/{resourceId}` (requires `monitoring:read`)### Diagnostics-- `GET /api/diagnostics` (auth)+- `GET /api/diagnostics` (admin, `settings:read`)- `POST /api/diagnostics/docker/prepare-token` (admin, `settings:write`)The Docker migration token request accepts `agentId`, optional `tokenName`, and@@ -1292,7 +1295,7 @@ OIDC and SAML configuration is managed via SSO providers.Provider mutation request contract:- Max request body: 1MB.-- Strict JSON contract: unknown fields and trailing payload are rejected.+- Unknown JSON fields are ignored. A trailing payload after the JSON object is rejected with `invalid_json`.- Provider IDs must match server validation.- OIDC and SAML providers are included with the Community SSO entitlement.@@ -1302,8 +1305,8 @@ Provider mutation request contract:Test/preview request contract:- Max request body: 32KB.-- Strict JSON contract: unknown fields and trailing payload are rejected.-- Common errors include `invalid_json`, `validation_error`, `rate_limited`, `body_too_large`.+- Unknown JSON fields are ignored. A trailing payload after the JSON object is rejected with `invalid_json`.+- Common errors include `invalid_json`, `validation_error`, `rate_limited`. A body over the 32KB limit is silently truncated, so it fails as `invalid_json` (these endpoints do not return `body_too_large`).---@@ -1619,7 +1622,7 @@ Runs a focused investigation for an alert payload (used by the UI).- `GET /api/ai/approvals/{id}`- `POST /api/ai/approvals/{id}/approve`- `POST /api/ai/approvals/{id}/deny`-- `POST /api/ai/run-command` (execute an approved command)+- `POST /api/ai/run-command` (retired: always returns `410 Gone` with error code `raw_command_retired`; raw command execution is no longer supported, so use advertised typed resource actions instead)- `GET /api/ai/agents` (connected agents via `/api/agent/ws`)### Remediation Plans (Pro)@@ -1744,15 +1747,15 @@ Looks up an agent by ID or hostname/display name. Requires `agent:report`.`POST /api/agents/agent/uninstall`Agent self-unregister during uninstall. Requires `agent:report`.-`POST /api/agents/agent/unlink` (admin, `agent:manage`)+`POST /api/agents/agent/unlink` (admin, `settings:write`)Unlinks an agent from a node.-`DELETE /api/agents/agent/{agent_id}` (admin, `agent:manage`)+`DELETE /api/agents/agent/{agent_id}` (admin, `settings:write`)Removes an agent from state.### Agent Linking (Admin)-- `POST /api/agents/agent/link` (admin, `agent:manage`)-- `POST /api/agents/agent/unlink` (admin, `agent:manage`)+- `POST /api/agents/agent/link` (admin, `settings:write`)+- `POST /api/agents/agent/unlink` (admin, `settings:write`)### Agent Remote Config`GET /api/agents/agent/{agent_id}/config`@@ -1802,7 +1805,7 @@ These routes manage Docker / Podman telemetry and container actions reported by- `POST /api/agents/docker/containers/update` (`docker:manage`) — retired, returns `410 Gone`; use the `/api/actions` plan/decision/execute flow instead### Kubernetes Agent Management (Admin)-- `DELETE /api/agents/kubernetes/clusters/{clusterId}` (`kubernetes:manage`, supports `?hide=true` or `?force=true`)+- `DELETE /api/agents/kubernetes/clusters/{clusterId}` (`kubernetes:manage`) — removes the cluster and blocks re-enrollment until `allow-reenroll`; takes no `hide` or `force` query parameters- `POST /api/agents/kubernetes/clusters/{clusterId}/allow-reenroll` (`kubernetes:manage`)- `PUT /api/agents/kubernetes/clusters/{clusterId}/unhide` (`kubernetes:manage`)- `PUT /api/agents/kubernetes/clusters/{clusterId}/pending-uninstall` (`kubernetes:manage`)diff --git a/docs/AUDIT_LOGGING.md b/docs/AUDIT_LOGGING.mdindex 932122e630..8ec9e7c08c 100644--- a/docs/AUDIT_LOGGING.md+++ b/docs/AUDIT_LOGGING.md@@ -24,9 +24,9 @@ Pulse automatically captures the following events:| `password_change` | Password modifications | Password changed (Docker/systemd) || `csrf_failure` | Blocked cross-site request forgery attempts | Invalid CSRF token || `lockout_reset` | Account lockout resets | Admin reset lockout for user `bob` |-| `oidc_login` | OIDC SSO login attempts (success/failure at each stage) | OIDC login success |+| `sso_oidc_login` | OIDC SSO login attempts (success/failure at each stage) | OIDC login success || `oidc_token_refresh` | OIDC token refresh success/failure (global, not tenant-scoped) | Token refreshed successfully |-| `oidc_role_assignment` | Automatic role assignment from OIDC groups | Auto-assigned roles: operator, viewer |+| `sso_oidc_role_assignment` | Automatic role assignment from OIDC groups | Auto-assigned roles: operator, viewer || `saml_login` | SAML SSO login attempts | SAML login success via provider-id || `saml_role_assignment` | Automatic role assignment from SAML groups | Auto-assigned roles: admin || `sso_provider_created` | SSO provider configuration created | Created provider: Authentik |@@ -261,8 +261,8 @@ of historical events or proof that their signatures are valid.## StorageThe default audit store lives in the Pulse data directory:-- **Single-tenant:** `{data-dir}/audit/audit.db`-- **Multi-tenant:** `{data-dir}/orgs/{org-id}/audit/audit.db`+- **Single-tenant, and the default organisation in multi-tenant installs:** `{data-dir}/audit/audit.db`+- **Non-default organisations (multi-tenant):** `{data-dir}/orgs/{org-id}/audit/audit.db`The default encrypted signing key is `.audit-signing.key` **inside the auditstore directory**, alongside `audit.db`, not at the data-directory root. Itsdiff --git a/docs/AUTO_UPDATE.md b/docs/AUTO_UPDATE.mdindex 6d4ca8e557..156e239b5a 100644--- a/docs/AUTO_UPDATE.md+++ b/docs/AUTO_UPDATE.md@@ -32,9 +32,11 @@ For v5, PVE, disabled, or failed agent updates, use **Agent Doctor** at3. Click the button to open the confirmation dialog4. Review the update details:- Current version → New version- - Estimated time- - Changelog highlights-5. Click **"Install Update"** to begin+ - Major-version or pre-release warning, when the update carries one+ - Estimated time and prerequisites, when listed+ - Root-access notice, when the update requires root+ - Automatic backup notice, when rollback is supported+5. Click **"Start Update"** in the confirmation dialog to begin### Update Process@@ -61,7 +63,7 @@ In **Settings → System → Updates**:| Setting | Description ||---------|-------------|-| **Update Channel** | Stable (recommended for production) or Pre-release (opt-in preview) |+| **Update Channel** | Stable (recommended for production) or Preview (opt-in beta builds and release candidates) || **Automatic Stable Updates** | Allow unattended stable updates on supported host installations with an installed update timer |The update timer must already be installed and enabled for unattended updates.diff --git a/docs/CENTRALIZED_MANAGEMENT.md b/docs/CENTRALIZED_MANAGEMENT.mdindex 5874f32832..a0f9d9dc3d 100644--- a/docs/CENTRALIZED_MANAGEMENT.md+++ b/docs/CENTRALIZED_MANAGEMENT.md@@ -42,8 +42,9 @@ below also support live refresh when the host module is running:| `report_ip` | string | Reported host IP override; also refreshed live for the host module || `disable_ceph` | boolean | Disable local Ceph polling; also refreshed live for the host module |-`interval` accepts a positive duration string; JSON numbers are interpreted as-seconds. Do not enable Debug, shorten intervals or change monitoring scope just+`interval` must be a positive duration string such as `30s` or `1m`. Numeric+values are rejected when a profile is validated or saved; an agent still reads a+numeric interval in an older saved profile as seconds. Do not enable Debug, shorten intervals or change monitoring scope justto collect a report. Use the [bounded agent log readers](UNIFIED_AGENT.md#collect-agent-logs-safely)and evidence already available.@@ -140,8 +141,9 @@ These paths describe existing operations; do not run every operation as adiagnostic checklist. Replace `{id}`, `{agent_id}` and `{version}` with valuesfrom the current instance. Use the UI or an authenticated client that readscredentials and request bodies from private files, preserves CSRF protection-for session writes and verifies HTTPS. The example `pulse_api` helper supports-GET and POST only, not PUT or DELETE.+for session writes and verifies HTTPS. The example `pulse_api` helper from API.md+accepts GET, POST, PUT and DELETE, but this guide's examples are read-only and+use GET only.| Method | Path | Purpose || --- | --- | --- |@@ -167,7 +169,7 @@ Example **request bodies**, not credential-bearing HTTP commands:}```-For validation, send only `{"config": {...}}`. For assignment, use the actual+For validation, send only the configuration keys as the top-level JSON object, with no `config` wrapper, for example `{"interval": "60s", "enable_docker": true}`; a `config` wrapper is treated as one unknown key and the settings are not checked. For assignment, use the actual`id` returned by creation or the profile list, not `prod-servers`:```jsondiff --git a/docs/CLOUD.md b/docs/CLOUD.mdindex 613e3734b1..f521877b1b 100644--- a/docs/CLOUD.md+++ b/docs/CLOUD.md@@ -64,7 +64,7 @@ or substitute the top-level GitHub server installer.### 3. Add Proxmox / TrueNAS Connections-Add your Proxmox VE, PBS, PMG, or TrueNAS systems via **Settings → Infrastructure → Platform connections**.+Add your Proxmox VE, PBS, PMG, or TrueNAS systems via **Settings → Infrastructure** (**Add infrastructure**).### 4. Set Up Mobile Accessdiff --git a/docs/CONFIGURATION.md b/docs/CONFIGURATION.mdindex 5c8e8f591c..606e8ac58d 100644--- a/docs/CONFIGURATION.md+++ b/docs/CONFIGURATION.md@@ -235,7 +235,7 @@ Numeric intervals are **seconds** unless noted otherwise.| `allowedEmbedOrigins` | Comma-separated `frame-ancestors` allowlist || `webhookAllowedPrivateCIDRs` | Allowlist for private webhook targets || `updateChannel` | Update channel (`stable` or `rc`) |-| `autoUpdateEnabled` | Allow one-click updates |+| `autoUpdateEnabled` | Allow unattended automatic updates from the systemd update timer (`stable` channel only) || `publicURL` | Public URL used in links/notifications || `hideLocalLogin` | Hide username/password login form || `temperatureMonitoringEnabled` | Enable temperature monitoring (where supported) |@@ -267,12 +267,14 @@ Environment variables take precedence over `system.json`.| `FRONTEND_PORT` | Public listening port (web UI, API, and agent ingest) | `7655` || `PORT` | **Deprecated** legacy alias for `FRONTEND_PORT`, honored only when `FRONTEND_PORT` is unset. Logs a deprecation warning at startup; switch to `FRONTEND_PORT`. | *(unset)* || `PULSE_AGENT_INGEST_PORT` | Optional dedicated port for the complete agent control plane: reports/config (`/api/agents/*`), command admission (`/api/agent/ws`), version checks, and bootstrap downloads. The web UI and management API stay isolated. `0` = disabled (single port). See [Split-Port Agent Ingest](#split-port-agent-ingest-network-isolation). | `0` |+| `HTTP_REDIRECT_PORT` | Optional plain-HTTP port that redirects to HTTPS on `FRONTEND_PORT`. Requires `HTTPS_ENABLED=true` with `TLS_CERT_FILE` and `TLS_KEY_FILE`. Must differ from `FRONTEND_PORT`. `0` = disabled. | `0` || `LOG_LEVEL` | Log verbosity (see below) | `info` || `LOG_FORMAT` | Log output format (`auto`, `json`, `console`) | `auto` || `LOG_FILE` | Log file path (enables file logging) | *(unset)* || `LOG_MAX_SIZE` | Log rotation size (MB) | `100` |-| `LOG_MAX_AGE` | Keep rotated logs for N days (`0` disables cleanup) | `30` |+| `LOG_MAX_AGE` | Keep rotated logs for N days (positive integer; zero or negative values are ignored with a startup warning and the default applies) | `30` || `LOG_COMPRESS` | Gzip rotated logs | `true` |+| `PULSE_AUDIT_ASYNC` | Queues audit-log writes in memory (up to 4096 events) and saves them in the background, so requests do not wait on audit storage. If the queue is full, the event is written synchronously instead. Only the value `false` (case-insensitive) turns the queue off and writes each event synchronously. Events still queued when the process is killed without a clean shutdown are not written. | `true` |#### Log Levels@@ -334,7 +336,7 @@ not the whole bundle.| `DEMO_MODE` | Enable read-only demo mode | `false` || `PULSE_TRUSTED_PROXY_CIDRS` | Comma-separated immediate proxy IPs/CIDRs trusted for forwarded client IP, scheme, host and port. Use the peer seen by Pulse; wildcard ranges are rejected. See [Reverse Proxy](REVERSE_PROXY.md#before-configuring-the-proxy). | *(unset)* || `PULSE_TRUSTED_NETWORKS` | Comma-separated CIDRs treated as trusted local networks (does not bypass auth) | *(unset)* |-| `ALLOW_UNPROTECTED_EXPORT` | Allow unauthenticated config export on public networks when no auth is configured (use with caution) | `false` |+| `ALLOW_UNPROTECTED_EXPORT` | Set to `true` to allow unauthenticated config export from any non-loopback client (private LAN as well as public networks), only while no password, API token, proxy secret, SSO or hosted mode is configured. Export only: import is never enabled by this (use with caution) | `false` |### Split-Port Agent Ingest (Network Isolation)@@ -481,7 +483,7 @@ monitoring defect.| ---------- | ------------- | --------- || `LOG_FILE` | Log file path (empty = stderr only) | *(unset)* || `LOG_MAX_SIZE` | Log file max size (MB) | `100` |-| `LOG_MAX_AGE` | Log file retention (days, `0` disables cleanup) | `30` |+| `LOG_MAX_AGE` | Log file retention (positive days; zero or negative values are ignored with a startup warning and the default applies) | `30` || `LOG_COMPRESS` | Compress rotated logs | `true` |@@ -492,7 +494,7 @@ These are stored in `system.json` and managed via the UI.| Key | Description | Default || ----- | ------------- | --------- || `updateChannel` | Update channel (`stable` or `rc`) | `stable` |-| `autoUpdateEnabled` | Allow one-click updates | `false` |+| `autoUpdateEnabled` | Allow unattended automatic updates from the systemd update timer (`stable` channel only) | `false` |> **Note**: Update settings are stored in `system.json`. Legacy `.env` entries (`UPDATE_CHANNEL`, `AUTO_UPDATE_ENABLED`) are kept in sync for backwards compatibility but are not read at runtime. The former `autoUpdateCheckInterval` / `autoUpdateTime` fields were never consumed and are ignored if present; the update schedule lives in the systemd timer.>@@ -1061,6 +1063,8 @@ docker run --init -e HTTPS_ENABLED=true \-e TLS_KEY_FILE=/certs/key.pem ...```+To redirect plain-HTTP requests to HTTPS, set `HTTP_REDIRECT_PORT` to a port other than `FRONTEND_PORT` (for example `80`). Pulse listens on that port on the same bind address as the web UI and answers requests with a `301` redirect to the same host on the HTTPS `FRONTEND_PORT`. The redirect listener starts only when `HTTPS_ENABLED=true` and both `TLS_CERT_FILE` and `TLS_KEY_FILE` are set; otherwise the value has no effect. A non-numeric or out-of-range value is ignored silently, which leaves the redirect disabled.+> **Important (Docker with HTTPS)**: Always use `--init` (or `init: true` in docker-compose) when enabling HTTPS. The Alpine-based healthcheck uses busybox `wget`, which spawns `ssl_client` subprocesses. Without an init process to reap them, these become zombie processes over time.---@@ -1196,10 +1200,10 @@ Pulse v6 supports first-class TrueNAS SCALE and CORE monitoring.### Adding a TrueNAS Instance-1. Go to **Settings → TrueNAS**.-2. Click **Add Connection**.-3. Enter the URL (e.g., `https://truenas.local`) and an API key.-4. Click **Test Connection** to verify, then **Save**.+1. Go to **Settings → Infrastructure**.+2. Click **Add infrastructure** and choose **TrueNAS**.+3. Enter the host (e.g., `truenas.local`), the port and whether to use HTTPS, then the API key and the username that owns the key.+4. Click **Test connection** to verify, then **Add connection**.### Creating a TrueNAS API Key@@ -1217,8 +1221,8 @@ On your TrueNAS system:| Apps | TrueNAS Overview || ZFS Pools & datasets | Storage page || Physical disks | Storage page |-| ZFS Snapshots | Recovery page |-| Replication tasks | Recovery page |+| ZFS Snapshots | TrueNAS → Protection |+| Replication tasks | TrueNAS → Protection || TrueNAS alerts | Alerts page |TrueNAS connections are stored encrypted in `truenas.enc`.@@ -1233,8 +1237,8 @@ The relay protocol provides end-to-end encrypted remote access foundations for P### Configuration-1. Go to **Settings → Relay**.-2. Toggle relay **On**.+1. Go to **Settings → Pulse Mobile**.+2. Turn on **Allow Pulse Mobile connections**.3. Use the **QR Code** or **Deep Link** to pair a supported Pulse Mobile client.### Environment Overrides@@ -1249,7 +1253,7 @@ going through the UI, two environment variables override the persisted| `PULSE_RELAY_SERVER` | Override relay server URL. Must be a valid `ws://` or `wss://` URL with no userinfo, query, or fragment. Invalid values are logged and ignored. | `wss://relay.pulserelay.pro/ws/instance` |Precedence: env vars beat the file. If you set `PULSE_RELAY_ENABLED=true`,-saving the relay form in **Settings → Relay** will then persist the+saving the relay settings in **Settings → Pulse Mobile** will then persist theenv-effective state to disk, so removing the env var later does notautomatically revert relay back to its previous file-stored state — clearrelay in the UI as well if you want to fully disable it.diff --git a/docs/DOCKER.md b/docs/DOCKER.mdindex 7d435a312e..d699daa3a9 100644--- a/docs/DOCKER.md+++ b/docs/DOCKER.md@@ -396,7 +396,7 @@ not grant command execution permission to monitoring tokens. SeeTo disable registry checks entirely, set `PULSE_DISABLE_DOCKER_UPDATE_CHECKS=true` on the **agent**.-You can also toggle "Hide Docker Update Buttons" from the UI in **Settings → System → General** under **Docker / Podman updates**.+You can also toggle **Hide update buttons** from the UI in **Settings → System → General** under **Docker / Podman updates**.---@@ -409,7 +409,7 @@ Pulse can start, stop, and restart Docker / Podman containers directly from the- **Pulse Agent** installed on the container host (see [Unified Agent](UNIFIED_AGENT.md)) and currently connected- **Command execution enabled** on the agent — it is disabled by default. Either:- start the agent with `--enable-commands` (or `PULSE_ENABLE_COMMANDS=true`), or- - tick **Enable Pulse command execution** in **Settings → Infrastructure** before copying the install command, which adds the flag and grants the token the command execution permission+ - tick **Enable legacy combined command profile** in **Settings → Infrastructure** before copying the install command, which adds the flag and grants the token the command execution permission (this is the transitional combined profile, not a least-privilege setting)- **Admin approval**: every lifecycle action requires confirmation by an admin in the UI before it runs. The agent then verifies the container's state before the change and confirms it actually reached the requested state afterwards.### Limitationsdiff --git a/docs/FAQ.md b/docs/FAQ.mdindex 237352d175..803289ea31 100644--- a/docs/FAQ.md+++ b/docs/FAQ.md@@ -16,9 +16,9 @@ Go to **Settings → Infrastructure → Install on a host** for systems that shorun the unified agent directly.- **Recommended (agent setup)**: copy the generated install command and run it on the target host.-- **Manual/API-backed platforms**: use **Settings → Infrastructure → Platform connections** for systems such as Proxmox, PBS, PMG, or TrueNAS that connect over an API instead of running the agent locally.+- **Manual/API-backed platforms**: use **Settings → Infrastructure** (**Add infrastructure**) for systems such as Proxmox, PBS, PMG, or TrueNAS that connect over an API instead of running the agent locally.-If you want Pulse to find servers automatically, enable discovery in **Settings → System → Network** and then review discovered servers in **Settings → Infrastructure**.+If you want Pulse to find servers automatically, open **Settings → Infrastructure**, select **Configure discovery** (it reads **Settings** once discovery is on), turn on **Automatic scanning** in the Discovery settings dialog, and then review discovered servers in the same section.### How do I change the port?@@ -127,7 +127,7 @@ Yes! If Pulse detects Ceph storage, it automatically queries cluster health, OSD### Does Pulse monitor TrueNAS?Yes. Pulse includes first-class TrueNAS SCALE/CORE integration. Add your-TrueNAS server under **Settings → Infrastructure → Platform connections** with+TrueNAS server under **Settings → Infrastructure** (**Add infrastructure**) withthe URL and API key. Pulse monitors the appliance, native VMs, apps, pools,datasets, disks, ZFS snapshots, replication tasks, and alerts. Those resourcesappear on the dedicated TrueNAS page.@@ -202,7 +202,7 @@ steps; do not reset a working installation to retrieve that token.Set `HTTPS_ENABLED=true` and provide `TLS_CERT_FILE` and `TLS_KEY_FILE` environment variables. See [Configuration](CONFIGURATION.md#-https--tls).### Can I use Single Sign-On (SSO)?-Yes. Pulse supports **OIDC** and **SAML** SSO providers, with multi-provider support (multiple IdPs active simultaneously). Configure in **Settings → Security → SSO Providers**. Pulse also supports Proxy Auth (Authentik, Authelia, Cloudflare). See [Proxy Auth Guide](PROXY_AUTH.md).+Yes. Pulse supports **OIDC** and **SAML** SSO providers, with multi-provider support (multiple IdPs active simultaneously). Configure in **Settings → Security → Single Sign-On**. Pulse also supports Proxy Auth (Authentik, Authelia, Cloudflare). See [Proxy Auth Guide](PROXY_AUTH.md).---diff --git a/docs/KUBERNETES.md b/docs/KUBERNETES.mdindex d8df2d813d..13745ca28f 100644--- a/docs/KUBERNETES.md+++ b/docs/KUBERNETES.md@@ -2,7 +2,7 @@This guide explains how to deploy the Pulse Server (Hub) and Pulse Agents on Kubernetes clusters, including immutable distributions like Talos Linux.-> **Navigation note (v6):** Kubernetes cluster and node resources appear on the **Infrastructure** page, while pods appear on the **Workloads** page. The legacy `/kubernetes` URL redirects to `/workloads?type=k8s`.+> **Navigation note (v6):** Kubernetes has its own page at `/kubernetes`, with tabs for nodes, workloads (pods), services, storage, configuration, and events. Pods appear on the **Workloads** tab (`/kubernetes/workloads`).## Prerequisites@@ -205,7 +205,7 @@ spec:- --enable-kubernetesenv:- name: PULSE_URL- value: "http://pulse-server.pulse.svc.cluster.local:7655"+ value: "http://pulse.pulse.svc.cluster.local:7655"- name: PULSE_TOKENvalueFrom:secretKeyRef:diff --git a/docs/MSP.md b/docs/MSP.mdindex 9302b66a1d..56e016f1f0 100644--- a/docs/MSP.md+++ b/docs/MSP.md@@ -32,7 +32,8 @@ Day-2 operations run through the `pulse-control-plane` binary (via```bashpulse-control-plane provider-msp bootstrap --account-name "Your MSP" --owner-email [email protected]pulse-control-plane provider-msp status-pulse-control-plane provider-msp backup+pulse-control-plane provider-msp backup create+pulse-control-plane provider-msp backup verify [archive]pulse-control-plane provider-msp recover # restore workspaces from backup or diskpulse-control-plane provider-msp preflight # pre-install environment checks```diff --git a/docs/MULTI_TENANT.md b/docs/MULTI_TENANT.mdindex 884b020058..15a5bfba14 100644--- a/docs/MULTI_TENANT.md+++ b/docs/MULTI_TENANT.md@@ -19,8 +19,8 @@ The Community, Relay, and Pro tiers do not include the `multi_tenant` capability1. Set `PULSE_MULTI_TENANT_ENABLED=true` in your environment and restart Pulse.2. Activate your Enterprise license in **Settings → Plans & Billing**.-3. Go to **Settings → Organization** and click **Create Organization**.-4. Name your organization and assign infrastructure to it.+3. Create the organization with the session-authenticated `POST /api/orgs` endpoint (see [Creating an Organization](#creating-an-organization)). This build has no Create Organization button in **Settings → Organization**.+4. Assign infrastructure to the organization.5. Use the **Org Switcher** in the header bar to switch between organizations.## Concepts@@ -57,7 +57,7 @@ Organizations can share specific resources with other organizations:## Before Using the API-Create organizations and manage members and shares in the signed-in Pulse UI.+Manage members and shares in the signed-in Pulse UI. Organizations are created through the session-authenticated `POST /api/orgs` endpoint; the UI has no create control.These changes require **session-based user authentication** and the relevantorganization role; API tokens are rejected with `403 session_required`, evenwhen they have `settings:write`. The UI handles the session and CSRF protection.@@ -86,14 +86,14 @@ The helper's loopback origin applies on the Pulse host; remotely, follow itsHTTPS instructions and keep certificate verification enabled. Replace theexample organization ID `production-datacenter` with your own, and run eachread separately. The helper's support for other HTTP methods does not make-organization mutations token-authenticated; keep those changes in the+organization mutations token-authenticated; keep member and share changes in thesigned-in UI with its session and CSRF protection.## Managing Organizations### Creating an Organization-**UI:** Settings → Organization → Create Organization+**UI:** none in this build; Settings → Organization has no create control.**API contract:** `POST /api/orgs`, session authentication only:```json@@ -193,10 +193,10 @@ When multi-tenant is enabled, **Settings → Organization** shows:| Panel | Description ||---|---|-| **Overview** | Organization name, description, creation date |+| **Overview** | Organization display name (editable), org ID, creation date, member count || **Access** | Member list, invite/remove members, change roles || **Sharing** | Outgoing and incoming resource shares |-| **Billing & Plan** | Organization-level plan and license info |+| **Billing** | Organization plan, usage policies and subscription status (the "Billing & Usage" panel) |## API Reference@@ -237,11 +237,11 @@ or a token's organization binding.## Troubleshooting-### "Multi-tenant is not enabled on this server" (501)+### "Multi-tenant functionality is not enabled. Set PULSE_MULTI_TENANT_ENABLED=true to enable." (501)Set `PULSE_MULTI_TENANT_ENABLED=true` in your environment and restart Pulse.-### "Multi-tenant requires an Enterprise license" (402)+### "Multi-tenant access requires an Enterprise license" (402)Activate an Enterprise license with the `multi_tenant` capability in **Settings → Plans & Billing**.diff --git a/docs/OIDC.md b/docs/OIDC.mdindex 284fc6f3b6..e671f5fe98 100644--- a/docs/OIDC.md+++ b/docs/OIDC.md@@ -154,7 +154,7 @@ service as a substitute for verified revocation.### Microsoft Entra ID (formerly Azure AD)-Create the provider in Pulse first (**Settings → Security → Single Sign-On → Add Provider**) so it gets its ID — Pulse generates a UUID per provider and shows the resulting callback URL. You need that URL for the Entra redirect URI below.+Create the provider in Pulse first (**Settings → Security → Single Sign-On → Add OIDC**) so it gets its ID — Pulse generates a UUID per provider and shows the resulting callback URL. You need that URL for the Entra redirect URI below.**In the Entra admin center:**@@ -170,7 +170,7 @@ Create the provider in Pulse first (**Settings → Security → Single Sign-On- **Issuer URL**: `https://login.microsoftonline.com/<tenant-id>/v2.0`- **Client ID**: the app registration's *Application (client) ID*.- **Client Secret**: the secret value from step 3.-- **Redirect URI**: `https://pulse.example.com/api/oidc/<provider-id>/callback`, matching the app registration exactly. The bare `/api/oidc/callback` is a v5 compatibility path that only serves the legacy env-configured provider — don't use it for a new provider.+- **Redirect URI**: `https://pulse.example.com/api/oidc/<provider-id>/callback`, matching the app registration exactly. The bare `/api/oidc/callback` is a v5 compatibility path. It is mapped to the legacy (v5-migrated or env-configured) provider; if that provider is not enabled, Pulse instead serves the provider whose login started from it (recovered from the pending login state). Don't use it as the redirect URI for a new provider.- **Scopes**: exactly `openid profile email`. Do **not** add `groups`. Entra has no `groups` scope and fails the whole authorization request with `AADSTS650053`; group membership arrives in the ID token from the Token configuration step, not from a scope.- **Groups Claim**: `groups`- **Allowed Groups**: the group's Object ID (GUID), not its display name.@@ -187,7 +187,7 @@ Create the provider in Pulse first (**Settings → Security → Single Sign-On| **`invalid_id_token`** | Compare the configured issuer with the IdP issuer locally; use the existing redacted error, not a token dump or newly enabled Debug logs. || **`unexpected signature algorithm "HS256"`** | Your IdP is signing with HS256. Configure it to use **RS256**. || **Redirect Loop** | Check `X-Forwarded-Proto` header (must be `https`) and cookie settings. |-| **Self-Signed Certs** | Set the **CA Bundle** field on the SSO provider to a host path readable by Pulse (e.g. `/etc/ssl/certs/oidc-ca.pem` mounted into the container). The field is stored on the provider record as `oidc.caBundle`; there is no `OIDC_CA_BUNDLE` env var. |+| **Self-Signed Certs** | The SSO provider form in Settings has no CA Bundle field. Set `oidc.caBundle` on the provider through the SSO provider API (`/api/security/sso/providers`) to a host path readable by Pulse (e.g. `/etc/ssl/certs/oidc-ca.pem` mounted into the container). For a provider configured with the legacy `OIDC_ENABLED` environment variables, set `OIDC_CA_BUNDLE` instead (see [Configuration](CONFIGURATION.md)). |### Safe diagnosisdiff --git a/docs/PBS.md b/docs/PBS.mdindex 26f083fd3d..bfe3bb3981 100644--- a/docs/PBS.md+++ b/docs/PBS.md@@ -79,8 +79,9 @@ Use this only when you also need host-local telemetry. The Linux agent normallyruns as root; it is not required to fix API authentication or missing backuppermissions. Review [Agent Security](AGENT_SECURITY.md) first.-Create a separate Pulse token in **API Access**, using the **Agent host** preset-for reporting, configuration reads and agent management. This is a **Pulse**+Create a separate Pulse token in **API Access**, using the **Agent** preset+for reporting and configuration reads; it does not include agent lifecycle+management (`agent:manage`). This is a **Pulse**token, not the **PBS** token used above. Do not enable command execution justfor monitoring.diff --git a/docs/PRIVACY.md b/docs/PRIVACY.mdindex 5de0702446..af05e327c0 100644--- a/docs/PRIVACY.md+++ b/docs/PRIVACY.md@@ -133,7 +133,7 @@ Every field is listed below with the reason it exists. Nothing else is included| Notification failures TLS 7d (schema v5) | `0` | Count terminal failures classified locally as certificate or TLS failures without sending certificates, hostnames, or raw errors || Notification failures configuration 7d (schema v5) | `0` | Count terminal failures classified locally as missing or invalid destination configuration without sending configuration values || Notification failures rejected 7d (schema v5; new schema v15 classifications are HTTP 4xx) | `0` | Count terminal failures classified locally as destination request or payload rejection without sending response or payload content; schema v5-v14 included destination HTTP 5xx responses, and those locally retained rows can remain in this rolling count for up to seven days after upgrade |-| Notification failures server error 7d (schema v15) | `0` | Count terminal failures classified locally as destination HTTP 5xx server errors without sending response content, destination identity, or provider identity |+| Notification failures server error 7d (schema v15) | `0` | Count terminal failures classified locally as destination server-side or temporary failures (HTTP 5xx responses, the temporary HTTP 423 Locked and 425 Too Early responses, and transient SMTP 4xx replies) without sending response content, destination identity, or provider identity || Notification failures unknown 7d (schema v5) | `0` | Count terminal failures that do not match another fixed class without sending raw errors || Alert AI enabled | `true`/`false` | See whether AI analysis on alert firing is switched on, without sending alert content, resource identifiers, or analysis text || AI provider class | `local` | See one closed bucket for how the Patrol (or default) model is reached: `none`, `local` (Ollama or a private-network OpenAI-compatible endpoint), `cloud_byok` (a hosted provider with your own key), `cloud_subscription` (the Codex or Claude CLI subscription route), or `hosted_legacy` (the retired Pulse-hosted route), without sending the provider, model name, endpoint, or account |@@ -283,8 +283,9 @@ performed locally; raw error text and destination/provider identity are neverincluded in the payload.Schema v15 adds an eighth-fixed notification terminal-failure counter for destination HTTP 5xx server-errors. From v15 onward,+fixed notification terminal-failure counter for destination server-side or+temporary failures: HTTP 5xx responses, the temporary HTTP 423 Locked and 425+Too Early responses, and transient SMTP 4xx replies. From v15 onward,new terminal failures enter `notification_failures_rejected_7d` only for HTTP4xx destination or payload rejections. Locally retained v5-v14 rows may stillinclude HTTP 5xx responses for up to seven days after upgrade; first-heartbeatdiff --git a/docs/PRODUCTION_SECURITY.md b/docs/PRODUCTION_SECURITY.mdindex c6d47cef24..7f4eedebf9 100644--- a/docs/PRODUCTION_SECURITY.md+++ b/docs/PRODUCTION_SECURITY.md@@ -18,8 +18,8 @@ utilization, storage, guests, and status.| **Proxmox API plus host agent:** API coverage plus host-local SMART, temperatures, ZFS/Ceph/mdadm detail, arbitrary mount capacity, and full LXC filesystem capacity | The Linux agent runs as `root` by default for the supported full-telemetry profile. || **Guest-local agent:** Host metrics and optional Docker/Podman inventory inside a VM or LXC | The agent is trusted inside that guest only; it does not grant Pulse access to the hypervisor. |-For most Proxmox installations, begin with **Settings → Infrastructure →-Platform connections**. Add a host agent only after identifying a metric that+For most Proxmox installations, begin with **Settings → Infrastructure**+(**Add infrastructure**). Add a host agent only after identifying a metric thatthe Proxmox API cannot provide. The complete capability matrix is in[Agent Security](AGENT_SECURITY.md#proxmox-deployment-choices).@@ -112,7 +112,9 @@ and management API.permissions Pulse needs, and rotate a token before revoking the credentialcurrently used by a live connection or agent.- Do not put host SSH private keys in a Pulse Docker or LXC container. Pulse- blocks that pattern; use API-only monitoring or a host-local agent instead.+ logs a security warning when it collects temperatures over SSH from a+ container but still uses the key; use API-only monitoring or a host-local+ agent instead.- Restrict the Pulse data directory and backups as secrets. They containencrypted credentials as well as sessions, API-token state, and the keymaterial needed by the installation.diff --git a/docs/PULSE_PRO.md b/docs/PULSE_PRO.mdindex 6be31e96d3..e62835c643 100644--- a/docs/PULSE_PRO.md+++ b/docs/PULSE_PRO.md@@ -181,9 +181,9 @@ Patrol mode decides how far Pulse can go after Patrol finds something that needs| Mode | Behavior | Plan ||---|---|---|| **Watch only** | Detect issues only. No investigation or fix execution. | Community / legacy Relay payload |-| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |-| **Auto-fix safe issues** | Runs approved safe fixes and verifies the outcome. Critical findings require approval by default. | Pro / hosted Cloud |-| **Policy autopilot** | Runs eligible policy-approved fixes without approval when explicitly enabled. | Pro / hosted Cloud |+| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |+| **Safe auto-fix** | Runs approved safe fixes and verifies the outcome. Critical findings require approval by default. | Pro / hosted Cloud |+| **Autopilot** | Runs eligible policy-approved fixes without approval when explicitly enabled. | Pro / hosted Cloud |## What You Get (By Plan)diff --git a/docs/RBAC.md b/docs/RBAC.mdindex 0d41868368..b5e33e27fd 100644--- a/docs/RBAC.md+++ b/docs/RBAC.md@@ -38,7 +38,7 @@ user merely because no local administrator is configured.## Quick Start1. Activate a Pro, grandfathered Pro+, Cloud, MSP, or Enterprise/custom license in **Settings → Plans & Billing**.-2. Go to **Settings → Security → Access Control**.+2. Go to **Settings → Security → Roles**.3. Create roles with the permissions you need.4. Assign roles to users.@@ -48,7 +48,7 @@ user merely because no local administrator is configured.### Before Using the API-Prefer **Settings → Security → Access Control** for one-off administration.+Prefer **Settings → Security → Roles** and **Settings → Security → Users** for one-off administration.The API examples require the licensed `rbac` capability and permission toadminister users. With RBAC enabled, role and user administration requires afull-access (`*`) API token bound to an authorised administrator; a monitoring@@ -81,7 +81,7 @@ alone does not establish the intended access or disable an upstream IdP account.### Creating a Role-**UI:** Settings → Security → Access Control → Create Role+**UI:** Settings → Security → Roles → New RoleUse a new custom role ID. Built-in roles (`admin`, `operator`, `viewer`,`auditor`) cannot be modified or deleted. These examples use `alert-manager`.@@ -201,7 +201,7 @@ How it works:- Matching groups are mapped to Pulse roles.- A user can receive multiple roles from multiple group mappings.- Once a provider has any group role mappings configured, the mapping is authoritative: on every login the user's role assignments are replaced with whatever the mapping resolves to. A login that matches no mapped group resolves to an empty set, which clears the user's existing role assignments. Watch for identity providers that silently drop the groups claim (see the Entra ID group overage warning in [OIDC.md](OIDC.md#microsoft-entra-id-formerly-azure-ad)) — to Pulse that looks the same as losing every group.-- Role changes are logged to the [audit log](AUDIT_LOGGING.md) as `oidc_role_assignment` events.+- Logins that assign at least one role are logged to the [audit log](AUDIT_LOGGING.md) as `sso_oidc_role_assignment` events. A login that clears a user's roles does not write this event.See [OIDC documentation](OIDC.md#group-to-role-mapping) for full configuration details.diff --git a/docs/RELAY.md b/docs/RELAY.mdindex 3b96b8119a..39d155d8a0 100644--- a/docs/RELAY.md+++ b/docs/RELAY.md@@ -45,7 +45,7 @@ Relay was designed with a zero-trust model:| **Back-pressure** | Data limiters prevent channel flooding || **License-gated** | Requires an active Relay-or-higher license || **Configurable** | Can be enabled/disabled at any time via Settings |-| **Audit** | Relay connection events are logged to the audit trail |+| **Audit** | Pulse Mobile relay access token creation is recorded in the audit trail. Relay connection events are written to the Pulse server log. |## Configuration@@ -77,8 +77,8 @@ Relay configuration is stored encrypted in `relay.enc` in the Pulse data directo|---|---|---|---|| `GET` | `/api/settings/relay` | `settings:read` | Get relay status and config || `PUT` | `/api/settings/relay` | `settings:write` | Update relay settings |-| `POST` | `/api/onboarding/qr` | `settings:read` | Generate mobile onboarding QR code |-| `POST` | `/api/onboarding/deep-link` | `settings:read` | Generate mobile deep link |+| `GET` | `/api/onboarding/qr` | `settings:read` | Generate mobile onboarding QR code |+| `GET` | `/api/onboarding/deep-link` | `settings:read` | Generate mobile deep link |## Pulse Mobile Pairingdiff --git a/docs/REVERSE_PROXY.md b/docs/REVERSE_PROXY.mdindex e572d97048..533d9dd580 100644--- a/docs/REVERSE_PROXY.md+++ b/docs/REVERSE_PROXY.md@@ -129,9 +129,15 @@ ProxyPassReverse / http://127.0.0.1:7655/If your reverse proxy terminates SSL but Pulse shows "HTTPS: HTTP only" in Settings → Security:-Pulse recognises direct TLS, or `X-Forwarded-Proto: https` from an immediate-peer in `PULSE_TRUSTED_PROXY_CIDRS`. An untrusted peer's header is ignored even-when the browser used HTTPS. Adding the header alone is not sufficient.+Pulse's secure-cookie and request-origin logic recognises direct TLS, or+`X-Forwarded-Proto: https` from an immediate peer in+`PULSE_TRUSTED_PROXY_CIDRS`; a header from any other peer is ignored for those+decisions, even when the browser used HTTPS. Adding the header alone is not sufficient.+The Security Posture HTTPS+indicator is different: it is true when the request has direct TLS or any+`X-Forwarded-Proto: https` header, whatever the peer. A passing indicator+therefore does not prove that proxy trust is configured correctly, and+"HTTP only" means neither TLS nor that header reached Pulse.Check the proxy's actual backend connection address and the effective Pulsesetting first, then check that the TLS proxy sends exactly `https`. For Nginx,@@ -150,7 +156,7 @@ HTTP/error status, not cookies, proxy secrets or a full network export.### Other Issues-- **"Connection Lost"**: WebSocket upgrade failed. Check `Upgrade` and `Connection` headers.+- **"Connection lost" (Workloads) or "Disconnected", "Reconnecting...", "Sync reconnecting" or "Backend healthy" in the header status badge**: the live data stream is not connected, which can happen when the WebSocket upgrade fails. Check the proxy's `Upgrade` and `Connection` headers.- **502 Bad Gateway**: Check Pulse's actual listener and the proxy's upstream address, port and network reachability; this does not by itself prove Pulse is stopped. Container `localhost` refers to that container, not another service.- **CORS Errors**: Do not add CORS headers in the proxy; Pulse handles them. Set **Settings → System → Network → Allowed Origins** or use `ALLOWED_ORIGINS` if needed.- **OIDC redirects fail**: Ensure `X-Forwarded-Proto` is set (see above).diff --git a/docs/TEMPERATURE_MONITORING.md b/docs/TEMPERATURE_MONITORING.mdindex f491ba5621..7ea4b53d52 100644--- a/docs/TEMPERATURE_MONITORING.md+++ b/docs/TEMPERATURE_MONITORING.md@@ -119,7 +119,7 @@ Pulse can also collect temperatures by SSHing into each host that does not have### Setup1. Generate the node setup command from the UI:- **Settings -> Infrastructure -> Add Node**+ **Settings -> Infrastructure -> Add infrastructure**, choose **Proxmox VE**, and use the setup guide's **Copy command** button2. Run the command on each Proxmox host. The setup script can:- Create the required API user and permissions- Add a restricted SSH key entry for temperature collection@@ -131,7 +131,7 @@ The SSH entry added to `authorized_keys` is restricted to the Pulse sensor wrappcommand="/usr/local/sbin/pulse-sensors",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty <public-key> # pulse-sensors```-If you use a non-standard SSH port, set `SSH_PORT` (system-wide) or configure it in **Settings -> System**.+If you use a non-standard SSH port, set the `SSH_PORT` environment variable on the Pulse server (see `docs/CONFIGURATION.md`). There is no SSH port control in **Settings -> System**.### Containerized Pulsediff --git a/docs/TROUBLESHOOTING.md b/docs/TROUBLESHOOTING.mdindex 1ab6df91f3..1cf9be27ac 100644--- a/docs/TROUBLESHOOTING.md+++ b/docs/TROUBLESHOOTING.md@@ -256,7 +256,8 @@ for the different results and evidence to retain.#### Audit Log is empty-Clear the event, user, date and success filters, and check the selected+Clear the Event, user search, Outcome and Verification filters (or use+**Clear all filters** in the empty-state message), and check the selectedorganisation first. A query error is not an empty history. **Pulse Pro runtimerequired** means an active licence is running on the public community runtime;follow the panel's **Download Pulse Pro** link rather than buying anotherdiff --git a/docs/TRUENAS.md b/docs/TRUENAS.mdindex 42b718a448..8bd672a1e0 100644--- a/docs/TRUENAS.md+++ b/docs/TRUENAS.md@@ -6,10 +6,10 @@ Pulse v6 includes first-class monitoring for **TrueNAS SCALE** and **TrueNAS COR1. Go to **Settings → Infrastructure**.2. Click **Add infrastructure** and choose **TrueNAS**. Existing connections- are listed under **Platform connections**.+ are listed under **Connected systems**.3. Enter the TrueNAS URL (e.g., `https://truenas.local`), the API key, and theusername that owns the key.-4. Click **Test Connection**, then **Save**. The test reads system information+4. Click **Test connection**, then **Add connection**. The test reads system informationon a separate connection; it does not validate inventory or metric collection.5. Leave the saved connection enabled and allow at least one configured pollinginterval (60 seconds by default). Check that the appliance and expected@@ -79,9 +79,9 @@ only its colour. Heat, native SMART faults and stale or missing readings areseparate evidence. A cool disk can still have a SMART fault; a retained **lastknown** temperature is not a current reading, and no temperature is not zero.-Check the saved rule in **Alerts → Thresholds → TrueNAS → TrueNAS Disks**:+Check the saved rule in **Alerts → Thresholds → TrueNAS → Disks**:-- A disk's own temperature override takes precedence over the **TrueNAS Disks**+- A disk's own temperature override takes precedence over the **Disks**default. With neither set, it inherits **Disk temperature by type**.- The inherited type policy is off when the agent **Disk Temp** default is off;an explicit TrueNAS temperature rule can still enable it for TrueNAS disks.@@ -137,7 +137,7 @@ All endpoints require admin authentication.### Testing and adding a connection (API)-Prefer **Settings → Infrastructure → Platform connections** for setup. These+Prefer **Settings → Infrastructure** (**Add infrastructure**) for setup. TheseAPI examples are for an authorised administrator using curl 7.76 or later,not a way to diagnose stale polling. Testing makes a live system-informationrequest to TrueNAS; saving creates a connection and starts ordinary polling.@@ -233,7 +233,7 @@ Only after reviewing the test response, create the connection once:A successful save returns HTTP **201** and the new connection's `id`, notproof of a complete poll. If saving times out or loses its response, it may-already have created the connection. Check **Platform connections** or+already have created the connection. Check **Connected systems** or`/api/truenas/connections` in your existing signed-in Pulse browser beforetrying again; do not blindly repeat POST and create duplicates. Continue withthe [ordinary polling checks](#stale-truenas-data) for collection acceptance.diff --git a/docs/UNIFIED_AGENT.md b/docs/UNIFIED_AGENT.mdindex b7eb55ca73..dcc0457ba0 100644--- a/docs/UNIFIED_AGENT.md+++ b/docs/UNIFIED_AGENT.md@@ -516,14 +516,14 @@ sudo chmod 0700 /usr/local/libexec/pulse-queue-depth| Flag | Env Var | Description | Default ||------|---------|-------------|---------|| `--url` | `PULSE_URL` | Pulse server URL | `http://localhost:7655` |-| `--token` | `PULSE_TOKEN` | API token | *(required)* |+| `--token` | `PULSE_TOKEN` | API token. Required when enrolling (`--enroll`); otherwise the `token` file in the state directory is used when unset | *(none)* || `--observers-file` | `PULSE_OBSERVERS_FILE` | Private JSON file defining report-only destinations | *(none)* || `--custom-sensors-file` | `PULSE_CUSTOM_SENSORS_FILE` | Private YAML file defining command/REST custom metrics and thresholds | *(none)* || `--token-file` | - | Read API token from file | *(unset)* || `--interval` | `PULSE_INTERVAL` | Reporting interval | `30s` || `--enable-host` | `PULSE_ENABLE_HOST` | Enable host metrics | `true` || `--enable-docker` | `PULSE_ENABLE_DOCKER` | Enable Docker / Podman metrics | `false` (auto-detect if not configured) |-| `--docker-runtime` | `PULSE_DOCKER_RUNTIME` | Force Docker / Podman runtime: `auto`, `docker`, or `podman` | `auto` |+| `--docker-runtime` | `PULSE_DOCKER_RUNTIME` | Preferred Docker / Podman runtime: `auto`, `docker`, or `podman`. `docker` only uses an endpoint that reports Docker. `podman` is tried first, but if no Podman socket answers the agent falls back to a Docker endpoint and reports it as `docker` | `auto` || `--enable-kubernetes` | `PULSE_ENABLE_KUBERNETES` | Enable Kubernetes metrics | `false` (installer auto-detect if not configured) || `--enable-proxmox` | `PULSE_ENABLE_PROXMOX` | Enable Proxmox integration | `false` || `--proxmox-type` | `PULSE_PROXMOX_TYPE` | Proxmox type: `pve` or `pbs` | *(auto-detect)* |@@ -542,7 +542,7 @@ sudo chmod 0700 /usr/local/libexec/pulse-queue-depth| `--disable-docker-update-checks` | `PULSE_DISABLE_DOCKER_UPDATE_CHECKS` | Disable Docker image update detection | `false` || `--disable-registry-credentials` | `PULSE_DISABLE_REGISTRY_CREDENTIALS` | Do not read host Docker credentials (config.json / credential helpers) for registry update checks | `false` || `--insecure` | `PULSE_INSECURE_SKIP_VERIFY` | Skip TLS verification | `false` |-| `--allow-plaintext-http` | `PULSE_AGENT_ALLOW_PLAINTEXT_HTTP` | Allow plain HTTP to a Pulse server that does not look local (private IP, single-label, `.local`/`.lan`/`.home`/`.home.arpa`/`.internal`, or resolves to private addresses). Sends the API token in cleartext; only for networks you fully control, e.g. internal networks numbered from public IP space | `false` |+| `--allow-plaintext-http` | `PULSE_AGENT_ALLOW_PLAINTEXT_HTTP` | Allow plain HTTP to a Pulse server at an address that is not local. Local-network Pulse URLs (private IP, single-label, `.local`/`.lan`/`.home`/`.home.arpa`/`.internal`, or resolves to private addresses) already work over HTTP for the primary URL without this flag. The flag extends plain HTTP to any host, including servers numbered from public IP space. Sends the API token in cleartext; only for networks you fully control. Report-only observers still need their own `allowPlaintextHTTP` opt-in | `false` || `--hostname` | `PULSE_HOSTNAME` | Override hostname | *(OS hostname)* || `--agent-id` | `PULSE_AGENT_ID` | Unique agent identifier | *(saved ID, then machine ID)* || `--report-ip` | `PULSE_REPORT_IP` | Override reported IP (multi-NIC) | *(auto)* |@@ -555,7 +555,7 @@ Use `--health-addr :9191` only when another host must scrape thehealth/metrics endpoint over the network. Use `--health-addr ""` or`PULSE_HEALTH_ADDR=off` to disable that listener.-**Token resolution order**: `--token` → `--token-file` → `PULSE_TOKEN` → `/var/lib/pulse-agent/token`.+**Token resolution order**: `--token` → `--token-file` → `PULSE_TOKEN` → the `token` file in the state directory (`<state-dir>/token`; the default state directory is `/var/lib/pulse-agent` on Linux and macOS and `%ProgramData%\Pulse` on Windows).### Agent log level@@ -651,14 +651,14 @@ Auto-detection behavior:- **Host metrics**: Enabled by default.- **Docker/Podman**: Enabled automatically by the agent if Docker/Podman is detected and `PULSE_ENABLE_DOCKER` was not explicitly set. A local `--enable-docker=false` or `PULSE_ENABLE_DOCKER=false` is a hard opt-out and is not re-enabled by auto-detection or remote profile config.-- **Kubernetes**: Enabled automatically by the installer when a kubeconfig is detected and `PULSE_ENABLE_KUBERNETES` was not explicitly set.+- **Kubernetes**: Enabled automatically by the installer when a kubeconfig is detected and none of `--enable-kubernetes`, `--disable-kubernetes` or `--kubeconfig` was passed. The Linux/macOS installer (`install.sh`) does not read `PULSE_ENABLE_KUBERNETES` from the environment; pass `--disable-kubernetes` to opt out at install time.- **Proxmox**: Enabled automatically by the installer when Proxmox is detected. Type auto-detects `pve` vs `pbs` if not specified.To disable auto-detection, explicitly set the relevant flags or env vars, for example:- `--enable-docker=false` or `PULSE_ENABLE_DOCKER=false`-- `--enable-kubernetes=false` or `PULSE_ENABLE_KUBERNETES=false`-- `--enable-proxmox=false` or `PULSE_ENABLE_PROXMOX=false`+- `--enable-kubernetes=false` or `PULSE_ENABLE_KUBERNETES=false` (the Linux/macOS installer honours only the flag at install time)+- `--enable-proxmox=false` or `PULSE_ENABLE_PROXMOX=false` for the agent binary and `install.ps1`. `install.sh` ignores the environment variable; pass `--enable-proxmox=false` or `--disable-proxmox` to it instead.### Inside-Guest Runtime Boundaries@@ -668,10 +668,14 @@ and task inventory on the Docker page.Pulse does not use a Proxmox node agent to look inside LXCs by default. Thenode agent does automatically collect filesystem capacity for running LXCs-when the local `pct` tool is available. It uses bounded `pct list` and-`pct df <vmid>` calls and reports only mount keys, volume labels, mount paths,-and capacity/usage values; it does not run commands inside a guest or read-guest files. Stopped LXCs retain the normal API-derived disk view.+when the local `pct` tool is available. On cgroup v2 PVE hosts it finds running+guests from the node's container configs and cgroup state and measures mount+capacity with statfs through each guest's init process in `/proc`; it falls back+to bounded `pct list` and `pct df <vmid>` calls when that discovery or a+per-container probe cannot establish a guest's state. It reports only mount+keys, volume labels, mount paths, and capacity/usage values; it does not run+commands inside a guest or read guest files. Stopped LXCs retain the normal+API-derived disk view.The optional Proxmox-side LXC Docker hint is off unless the Pulse server is startedwith `PULSE_ENABLE_PROXMOX_GUEST_DOCKER_DETECTION=true`. That hint uses@@ -839,17 +843,21 @@ Use HTTPS or a trusted local network for that legacy migration. Forhigh-assurance environments, install the v6 `pulse-agent` through the signedinstaller path instead of relying on a plain-HTTP first hop.-To disable auto-updates:-```bash-# After private-file preparation and successful installer inspection-bash "$HOME/.config/pulse/agent-install.sh" \- --url https://pulse.example.com \- --token-file "$HOME/.config/pulse/agent-token" --disable-auto-update+To disable auto-updates, set `PULSE_DISABLE_AUTO_UPDATE=true` (or pass+`--disable-auto-update`) on the `pulse-agent` process itself. The agent+installer (`agent-install.sh`) does not accept `--disable-auto-update`, and+setting the variable in the shell that runs the installer does not reach the+installed service. For an agent installed as a Linux systemd service, add a+drop-in with `sudo systemctl edit pulse-agent`:-# Or set environment variable-PULSE_DISABLE_AUTO_UPDATE=true+```ini+[Service]+Environment="PULSE_DISABLE_AUTO_UPDATE=true"```+Then apply it with `sudo systemctl daemon-reload` and+`sudo systemctl restart pulse-agent`.+## Remote Configuration (Agent Profiles, Pro/legacy Pro+/Cloud)Pro, legacy Pro+, and Cloud can push centralized settings to agents via Agent Profiles.@@ -955,7 +963,7 @@ Use the unified installer (`install.sh`) for all new and existing deployments.## Health Checks & Metrics-The agent exposes HTTP endpoints for health checks and Prometheus metrics on port 9191 by default.+The agent exposes HTTP endpoints for health checks and Prometheus metrics on `127.0.0.1:9191` by default (loopback only; see `--health-addr` in the configuration table).### Endpoints@@ -974,6 +982,8 @@ The agent exposes HTTP endpoints for health checks and Prometheus metrics on por### Kubernetes Probes+The default listener binds to `127.0.0.1`, which kubelet probes cannot reach because they connect to the pod IP. Set `PULSE_HEALTH_ADDR=:9191` (or `--health-addr :9191`) on the agent container before using these probes. That exposes `/healthz`, `/readyz` and `/metrics` on all pod interfaces, so restrict access with a NetworkPolicy.+```yamllivenessProbe:httpGet:diff --git a/docs/UNIFIED_RESOURCES.md b/docs/UNIFIED_RESOURCES.mdindex 797f861368..2efd6a3b1c 100644--- a/docs/UNIFIED_RESOURCES.md+++ b/docs/UNIFIED_RESOURCES.md@@ -23,9 +23,9 @@ Every monitored entity is a `Resource` with:|---|---|| `id` | Globally unique identifier || `name` | Display name |-| `type` | `host`, `vm`, `container`, `storage`, `pool`, `dataset`, `disk`, `service`, `cluster`, `pod`, `deployment` |-| `status` | `online`, `warning`, `critical`, `offline`, `unknown` |-| `sources` | Array of contributing data sources (e.g., `["pve", "agent"]`) |+| `type` | `agent` (Proxmox node, host agent or other host-class parent; `docker-host` when it carries only Docker data), `vm`, `system-container`, `app-container`, `docker-service`, `storage`, `ceph`, `physical_disk`, `pbs`, `pmg`, `network-share`, `network-endpoint`, `pod`, `k8s-cluster`, `k8s-node`, `k8s-deployment`, plus further `docker-*` and `k8s-*` types |+| `status` | `online`, `warning`, `offline`, `unknown` (critical severity is reported separately as `critical` in the `health` object's verdict) |+| `sources` | Array of contributing data sources (e.g., `["proxmox", "agent"]`) || `sourceStatus` | Per-source health status || `metrics` | CPU, memory, disk, network (when available) || Platform extensions | `.kubernetes`, `.truenas`, `.docker`, etc. |@@ -35,9 +35,9 @@ Every monitored entity is a `Resource` with:A single resource can be reported by **multiple sources**. For example, a Proxmox node might have data from both the PVE API and a host agent:```-sources: ["pve", "agent"]+sources: ["proxmox", "agent"]sourceStatus:- pve: { status: "online", lastSeen: "..." }+ proxmox: { status: "online", lastSeen: "..." }agent: { status: "online", lastSeen: "..." }```@@ -47,7 +47,7 @@ The aggregate `status` is computed from all contributing sources.| Source | What it feeds ||---|---|-| `pve` | Proxmox VE API — nodes, VMs, containers, storage |+| `proxmox` | Proxmox VE API — nodes, VMs, containers, storage || `pbs` | Proxmox Backup Server — datastores, backups, sync jobs || `pmg` | Proxmox Mail Gateway — mail stats, cluster health || `agent` | Unified agent — host metrics, temperatures, S.M.A.R.T. |@@ -57,32 +57,21 @@ The aggregate `status` is computed from all contributing sources.## Unified Navigation-The v6 UI organises pages by **task** instead of **platform**:+The v6 UI keeps platform-shaped top-level navigation. The unified resource model sits behind it, but there are no separate Dashboard, Workloads, Storage or Recovery pages.| Page | What it shows ||---|---|-| **Dashboard** | Overview panels aggregating all sources |-| **Infrastructure** | All hosts: Proxmox nodes, Docker hosts, K8s nodes, TrueNAS systems, agent-only hosts |-| **Workloads** | All workloads: VMs, LXC containers, Docker containers, Kubernetes pods |-| **Storage** | All storage: Proxmox storage, PBS datastores, ZFS pools/datasets, Ceph |-| **Recovery** | All backup/snapshot artifacts: PBS backups, PVE local dumps, ZFS snapshots, replication |-| **Alerts** | Unified alert view across all platforms |+| **Proxmox**, **Docker**, **Kubernetes**, **TrueNAS**, **vSphere**, **Machines** | One page per platform, shown only when Pulse has resources for that platform |+| **Alerts** | Alerts across all platforms |+| **Patrol** | Patrol checks, shown only when AI is enabled |+| **Actions** | Approvals, ready work and recorded outcomes |+| **Settings** | Pulse configuration, shown only to users with settings access |-Every page supports **source filtering** — click a source badge to see only resources from that platform.+`/infrastructure` is not a page of its own. It redirects to the first available platform page, or to Settings (or Alerts when the user has no settings access) when no platform has resources.-### Legacy Route Compatibility+### Unified Routes-Legacy URLs redirect automatically with toast notifications:--| Legacy Route | Redirects To |-|---|---|-| `/proxmox/overview` | `/infrastructure` |-| `/hosts` | `/infrastructure?source=agent` |-| `/docker` | `/workloads?source=docker` |-| `/kubernetes` | `/infrastructure?source=kubernetes` |-| `/services`, `/mail` | `/infrastructure?source=pmg` |--See [Migration Guide](MIGRATION_UNIFIED_NAV.md) for the full mapping.+The unified `/workloads`, `/storage` and `/recovery` routes that briefly shipped in earlier release candidates were reverted in `v6.0.0-rc.6` and do not exist. See [Migration Guide](MIGRATION_UNIFIED_NAV.md) for the platform-shaped equivalents.## API@@ -96,10 +85,11 @@ Returns all unified resources. Supports query parameters:| Parameter | Description ||---|---|-| `type` | Filter by resource type (`host`, `vm`, `container`, etc.) |-| `source` | Filter by data source (`pve`, `docker`, `kubernetes`, etc.) |-| `status` | Filter by status (`online`, `warning`, `critical`, `offline`) |-| `search` | Full-text search across name, ID, tags |+| `type` | Filter by resource type, comma-separated (`agent`, `vm`, `system-container`, `app-container`, `storage`, `pod`, etc.). Unknown tokens return HTTP 400. |+| `source` | Filter by data source (`proxmox`, `docker`, `kubernetes`, etc.) |+| `status` | Filter by status (`online`, `warning`, `offline`, `unknown`) |+| `q` | Case-insensitive substring match on resource name |+| `tags` | Filter by resource tag |### Resource Details@@ -109,13 +99,9 @@ Individual resource details are available via the unified state WebSocket connecThe frontend uses SolidJS reactive selectors to derive views from the unified store:-- `useResources()` — access the full unified resource list-- `useInfrastructureResources()` — hosts filtered for the Infrastructure page-- `useWorkloadResources()` — VMs/containers/pods for the Workloads page-- `useStorageResources()` — storage pools/datasets for the Storage page-- `useRecoveryResources()` — backup/snapshot data for the Recovery page+- `useResources()` — access the full unified resource list, plus derived views such as `infra()` (nodes, agents, docker-hosts), `workloads()` (VMs, containers, docker-containers), `byType()`, `filtered()` and `children()`-These selectors read from a single SolidJS store that is updated in real-time via WebSocket.+The hook hydrates from the WebSocket state when available and falls back to the REST API.## See Alsodiff --git a/docs/WEBHOOKS.md b/docs/WEBHOOKS.mdindex eca89a612a..0356b8e132 100644--- a/docs/WEBHOOKS.md+++ b/docs/WEBHOOKS.md@@ -86,7 +86,7 @@ These fields and behaviors are stable; ticket-routing integrations can rely on t**Events.** `{{.Event}}` is `"alert"` or `"resolved"` — there is no separate"info" event class. A resolved event closes an alert occurrence, not necessarilya recovered condition; see [non-recovery closes](#resolved-does-not-always-mean-recovered).-Resolved delivery depends on **Notify on resolve** and a+Resolved delivery depends on **Recovery notifications** (Alerts → Schedule, set to Enabled) and asuccessful firing-delivery receipt for that occurrence and destination. Do notassume that every configured webhook receives both events.@@ -297,7 +297,7 @@ Keep ticket correlation separate from suppressing repeated processing:fractional seconds as below. Do not assume the shorter string is universallyunique. A test or legacy payload can lack member identity; keep incomplete orambiguous events for reconciliation rather than silently treating them as- duplicates. **Send test** alone does not validate this lifecycle.+ duplicates. **Test** alone does not validate this lifecycle.- Commit receiver state and the ticket action atomically, or use your ticketsystem's durable idempotent operation. Do not mark an event processed beforeits action succeeds. Exact signed-byte replays can be rejected separately,@@ -591,7 +591,8 @@ To acknowledge or clear from the PSA side, use a `monitoring:write` token: `POST| Action | Endpoint | Scope ||--------|----------|-------|-| Create / update / delete per-org webhook | `POST` / `PUT` / `DELETE /api/notifications/webhooks` | `settings:write` (admin) |+| Create per-org webhook | `POST /api/notifications/webhooks` | `settings:write` (admin) |+| Update / delete per-org webhook | `PUT` / `DELETE /api/notifications/webhooks/<id>` | `settings:write` (admin) || List per-org webhooks | `GET /api/notifications/webhooks` | `settings:read` (admin) || Read active / historical alerts | `GET /api/alerts/active`, `GET /api/alerts/history` | `monitoring:read` || Acknowledge / clear alerts | `POST /api/alerts/acknowledge`, `POST /api/alerts/clear` | `monitoring:write` |diff --git a/docs/ZFS_MONITORING.md b/docs/ZFS_MONITORING.mdindex 31ba953f9f..208cfa440c 100644--- a/docs/ZFS_MONITORING.md+++ b/docs/ZFS_MONITORING.md@@ -27,7 +27,8 @@ it appear in Pulse. For a pool you intentionally keep unregistered:* A **Unified Agent on the Proxmox host**, with a locally mounted ZFS datasetand access to `zpool`, can report capacity and usage in the node's- **Overview details → Disks** panel, under the selected mount point. Without+ **Overview** tab, in the **Storage** section of the technical details, which+ lists each mount point once the agent reports two or more. Withoutusable `zpool` output, the agent falls back to mounted-dataset counters;those are not necessarily whole-pool capacity.* That capacity view and physical-disk SMART data do **not** providediff --git a/docs/api/SCHEDULER_HEALTH.md b/docs/api/SCHEDULER_HEALTH.mdindex c25ecbb4b4..68228f8f13 100644--- a/docs/api/SCHEDULER_HEALTH.md+++ b/docs/api/SCHEDULER_HEALTH.md@@ -43,8 +43,7 @@ Returns a real-time snapshot of the adaptive scheduler, including queue state, c"instance": "pve-a","type": "pve","lastSuccess": "2025-10-20T13:05:10Z",- "stalenessSeconds": 32,- "stalenessScore": 0.12+ "score": 0.12}],"instances": [diff --git a/docs/monitoring/ADAPTIVE_POLLING.md b/docs/monitoring/ADAPTIVE_POLLING.mdindex b0f7604b55..d5c86387af 100644--- a/docs/monitoring/ADAPTIVE_POLLING.md+++ b/docs/monitoring/ADAPTIVE_POLLING.md@@ -31,7 +31,7 @@ The `circuitBreaker` (`internal/monitoring/circuit_breaker.go`) follows a standa1. **Closing the Circuit**: One successful poll moves *Half-Open* → *Closed* and resets failure count.2. **Backoff Calculation**: Retries use exponential backoff starting at 5s (multiplier 2, jitter 0.2) capped at 5m.3. **Transient vs. Permanent**:- - **Transient** errors (retryable) are retried up to 5 times before moving to the Dead Letter Queue.+ - **Transient** errors (retryable) are retried until they fail 5 times in a row (the first attempt plus 4 retries), then move to the Dead Letter Queue.- **Permanent** errors move directly to the Dead Letter Queue.**Note:** When `AdaptivePollingMaxInterval` is set to 15 seconds or less, the retry backoff is shortened (750ms initial, 4s max) to keep fast feedback loops during tight polling windows.diff --git a/frontend-modern/public/docs/AGENT_SECURITY.md b/frontend-modern/public/docs/AGENT_SECURITY.mdindex 98ceeb2eff..e82c6b9970 100644--- a/frontend-modern/public/docs/AGENT_SECURITY.md+++ b/frontend-modern/public/docs/AGENT_SECURITY.md@@ -111,12 +111,17 @@ Inside-guest runtime visibility is explicit. Installing the agent inside a VM orLXC authorizes that guest-local agent to report Docker/Podman monitoring dataaccording to its local module flags. A Proxmox node agent does not look insideLXCs by default. Its automatic LXC filesystem collector is a node-local-capacity query only: it runs `pct list`, then `pct df <vmid>` for guests already-reported running, and reports mount keys, volume labels, mount paths, and-capacity/usage numbers. It does not run a command inside the guest or read-guest files, processes, environment, or container-runtime metadata. It skips-guests reported stopped and bounds command time, output, guest count, and disk-count.+capacity query only. On cgroup v2 PVE hosts it finds running guests from the+node's container configs and cgroup state, reads each running guest's init+process ID and status from cgroup and `/proc`, and measures mount capacity with+statfs through `/proc/<pid>/root`. When that discovery cannot establish a guest's state (for+example on cgroup v1 hosts) it falls back to `pct list`, with `lxc-info` to+find each guest's init process, and it runs `pct df <vmid>` for a guest only+when the statfs probe is unavailable or fails. It reports+mount keys, volume labels, mount paths, and capacity/usage numbers. It does not+run a command inside the guest or read guest file contents, environment, or+container-runtime metadata. It skips guests reported stopped and bounds command+time, output, guest count, and disk count.The node agent can collect Docker container inventory from LXC gueststhrough `pct exec`, but only after an explicit server-side opt-in: thediff --git a/frontend-modern/public/docs/AI.md b/frontend-modern/public/docs/AI.mdindex daa739f3e4..3737e50112 100644--- a/frontend-modern/public/docs/AI.md+++ b/frontend-modern/public/docs/AI.md@@ -75,7 +75,7 @@ Patrol is a scheduled model workflow that builds a rich, system-wide snapshot anScheduled/Event Trigger│▼-buildSeedContext() ── infrastructure evidence and policy context+buildTriageSeedSectionsState() ── infrastructure evidence and policy context│▼LLM analysis (with tools) ← pulse_storage, pulse_metrics, pulse_alerts, etc.@@ -118,7 +118,7 @@ can handle the steady-state signal.### The Patrol attention queue-The first thing Patrol shows is **Needs attention**, a single operator queue+The first thing Patrol shows is the **Inbox** tab, a decision inbox headed "N decisions need you" (or "No decisions are waiting"), a single operator queueprojected from Pulse's canonical alert lifecycle. It combines currentoperational state with evidence quality and protection context; it does notcreate a second finding lifecycle.@@ -168,7 +168,7 @@ Every patrol run passes the LLM comprehensive context about your environment:Beyond raw metrics, Patrol prepares structured evidence for the model:-- **Trend summaries** — 24h and 7d samples showing `growing`, `stable`, `declining`, or `volatile` behavior+- **Trend summaries** — 24h and 7d samples showing `growing`, `stable`, or `declining` behavior- **Baseline evidence** — Z-score anomaly evidence from historical metrics- **Capacity estimates** — "Storage pool reaches 95% in about 12 days at current growth rate"- **Infrastructure changes** — Detected config changes, VM migrations, new deployments@@ -228,7 +228,7 @@ Note: `info` and `watch` level findings are filtered out to reduce noise.Findings can be managed via the UI or API:-- **Get help**: Chat with AI to troubleshoot the issue+- **Open in Assistant**: Open Pulse Assistant with the finding attached to troubleshoot the issue (on Patrol findings it appears under **Resolve or dismiss**)- **Resolve**: Mark as fixed (finding will reappear if the issue resurfaces)- **Dismiss**: Record feedback about this finding; use **Reopen** to undo its dismissal- **Create rule**: Permanently auto-dismiss future findings for the selected resource and category@@ -368,9 +368,9 @@ Patrol supports four modes that decide how far Pulse can go after it finds an is| Mode | Behavior | Plan ||-------|----------|------|| **Watch only** | Detect issues only. No investigation or fixes. | Community (BYOK) |-| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |-| **Auto-fix safe issues** | Runs warning-level governed fixes automatically and verifies results. Critical findings still require approval by default. | Pro / hosted Cloud |-| **Policy autopilot** | Runs eligible governed fixes automatically and verifies results. Use only in environments where this is acceptable. | Pro / hosted Cloud |+| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |+| **Safe auto-fix** | Runs warning-level governed fixes automatically and verifies results. Critical findings still require approval by default. | Pro / hosted Cloud |+| **Autopilot** | Runs eligible governed fixes automatically and verifies results. Use only in environments where this is acceptable. | Pro / hosted Cloud |Community and Relay installs can still run scheduled Patrol findings with BYOK. Watch only remains the free-first baseline; investigation, proposed fixes, and fix execution are paid AI-operations capabilities rather than a core monitoring limit.@@ -409,8 +409,8 @@ MaybeInvestigateFinding()| Setting | Default | Description ||---------|---------|-------------|-| `MaxEvidenceCalls` | 15 | Maximum evidence-tool calls per investigation; the terminal typed proposal is reserved separately |-| `MaxTurns` | 17 | Internal provider-response safety ceiling derived from the evidence budget (budget + proposal + final summary) |+| `MaxEvidenceCalls` | 10 | Maximum evidence-tool calls per investigation; the terminal typed proposal is reserved separately |+| `MaxTurns` | 12 | Internal provider-response safety ceiling derived from the evidence budget (budget + proposal + final summary) || `Timeout` | 10 min | Maximum duration per investigation || `MaxConcurrent` | 3 | Maximum concurrent investigations || `MaxAttemptsPerFinding` | 3 | Maximum investigation attempts per finding |@@ -508,7 +508,7 @@ never excluded a guest from action plans, so it has been removed.## Weekly summary and emailPulse's **This week** summary adds up retained Patrol activity over the last-seven days. Open **Patrol → Activity** to read it; use **Settings → Reporting**+seven days. Open **Patrol → Activity** to read it; use **Settings → Data & Reports**to schedule the same summary by email. The card, weekly email and **Report type**selector are included in **v6.5.0**. An older build can lack these controls.@@ -545,7 +545,7 @@ grant scheduling access. See [Plans and entitlements](PULSE_PRO.md).1. Check that email notifications are **enabled and configured** under**Alerts → Notifications**. Listing recipients on a schedule does notconfigure a mail provider or enable email.-2. Open **Settings → Reporting**, choose **Create schedule**, then set+2. Open **Settings → Data & Reports**, choose **Create schedule**, then set**Report type** to **Patrol weekly summary**.3. Enter a schedule name, weekday, time and an IANA **Timezone**, such as`Europe/London`. The summary is weekly, covers the last seven days, and is@@ -841,7 +841,7 @@ Patrol runs on a configurable schedule:| 10 min – 7 days | Configurable interval (default: 6 hours) |Patrol can also be triggered by:-- **Manual run**: Click "Run Patrol" in the UI+- **Manual run**: Click "Check now" in the Patrol header (the button shows "Starting…" or "Running…" while a run is starting or in progress)- **Alert-triggered analysis (Pro and above)**: Runs when an alert fires- **API call**: `POST /api/ai/patrol/run`diff --git a/frontend-modern/public/docs/AI_AUTONOMY.md b/frontend-modern/public/docs/AI_AUTONOMY.mdindex d5f28ddb05..9a87c2e084 100644--- a/frontend-modern/public/docs/AI_AUTONOMY.md+++ b/frontend-modern/public/docs/AI_AUTONOMY.md@@ -24,14 +24,14 @@ Patrol mode sets how far Pulse can go when Patrol finds something that needs att| Mode | Key | Detect | Investigate | Fix warning-level issues | Fix critical issues | Plan ||-------|-----|:------:|:-----------:|:------------------------:|:-------------------:|------|| **Watch only** | `monitor` | Yes | No | No | No | Community |-| **Ask before changes** | `approval` | Yes | Yes | Approval required | Approval required | Pro / legacy Pro+ / Cloud |-| **Auto-fix safe issues** | `assisted` | Yes | Yes | Execute automatically | Approval required | Pro / legacy Pro+ / Cloud |-| **Policy autopilot** | `full` | Yes | Yes | Execute automatically | Execute automatically | Pro / legacy Pro+ / Cloud |+| **Ask first** | `approval` | Yes | Yes | Approval required | Approval required | Pro / legacy Pro+ / Cloud |+| **Safe auto-fix** | `assisted` | Yes | Yes | Execute automatically | Approval required | Pro / legacy Pro+ / Cloud |+| **Autopilot** | `full` | Yes | Yes | Execute automatically | Execute automatically | Pro / legacy Pro+ / Cloud |- **Watch only** (default): Patrol creates findings but takes no action. This is the Community and Relay baseline. Suitable for learning what Patrol detects before enabling investigation or fix execution.-- **Ask before changes** (Pro and above): Patrol investigates findings and proposes fixes. All fixes queue for manual approval before execution.-- **Auto-fix safe issues** (Pro and above): Warning-level safe fix plans can execute automatically. Critical findings still require approval. This is the recommended starting point for most Pro and legacy Pro+ users who enable fix execution.-- **Policy autopilot** (Pro and above): Safe fix plans can execute without approval. Requires an explicit toggle and a Pro, legacy Pro+, or Cloud license. Recommended only for environments with thorough alert coverage.+- **Ask first** (Pro and above): Patrol investigates findings and proposes fixes. All fixes queue for manual approval before execution.+- **Safe auto-fix** (Pro and above): Warning-level safe fix plans can execute automatically. Critical findings still require approval. This is the recommended starting point for most Pro and legacy Pro+ users who enable fix execution.+- **Autopilot** (Pro and above): Safe fix plans can execute without approval. Requires an explicit toggle and a Pro, legacy Pro+, or Cloud license. Recommended only for environments with thorough alert coverage.### Configuration@@ -158,10 +158,8 @@ When Patrol mode is `approval`, `assisted`, or `full`, Patrol investigates findi|---------|---------|-------|-------------|| `patrol_investigation_budget` | 10 | 5–30 | Maximum evidence-tool calls per investigation; Patrol derives a separate model-response safety ceiling || `patrol_investigation_timeout_sec` | 600 | 60–1800 | Maximum seconds per investigation |-| `max_concurrent_investigations` | 3 | — | Parallel investigation limit |-| `max_attempts_per_finding` | 3 | — | Retries before marking as `needs_attention` |-| `investigation_cooldown_sec` | 3600 | — | Cooldown before re-investigating a finding |-| `timeout_cooldown_sec` | 600 | — | Shorter cooldown after timeout failures |++The following limits are fixed and cannot be changed: up to 3 investigations run in parallel, up to 3 attempts per finding, a 1 hour cooldown before re-investigating a finding, and a shorter 10 minute cooldown after a timeout failure.---@@ -203,9 +201,9 @@ To stop Pulse acting on a specific guest, host or container, open its drawer, chFor new deployments, gradually increase Patrol mode:1. **Start with Watch only** — Run Patrol for a few cycles to see what it detects. Dismiss false positives.-2. **Move to Ask before changes where available** — Enable investigation. Review proposed fixes to build confidence.-3. **Use Auto-fix safe issues when fix execution is enabled** — Let Patrol execute warning-level fixes while you approve critical fixes.-4. **Consider Policy autopilot** — Only if your environment has comprehensive alerting and you trust the fix patterns.+2. **Move to Ask first where available** — Enable investigation. Review proposed fixes to build confidence.+3. **Use Safe auto-fix when fix execution is enabled** — Let Patrol execute warning-level fixes while you approve critical fixes.+4. **Consider Autopilot** — Only if your environment has comprehensive alerting and you trust the fix patterns.---diff --git a/frontend-modern/public/docs/API.md b/frontend-modern/public/docs/API.mdindex 1b5a6e56d8..0761aa6c7c 100644--- a/frontend-modern/public/docs/API.md+++ b/frontend-modern/public/docs/API.md@@ -159,7 +159,7 @@ State-changing session requests also require Pulse's CSRF protection, whichthe UI handles.Session endpoints:-- `POST /api/login` (sets `pulse_session` + `pulse_csrf`)+- `POST /api/login` (sets the session cookie, `pulse_session` over plain HTTP or `__Host-pulse_session` over HTTPS, plus `pulse_csrf`)- `POST /api/logout` (clears session)Login body:@@ -260,7 +260,7 @@ Lightweight HTML status page for quick checks.Returns the unified resource list with pagination + aggregations. Requires `monitoring:read`.Query params:-- `type`: comma-separated list (e.g., `agent`, `vm`, `system-container`, `container`, `docker-service`, `storage`, `pbs`, `pmg`, `k8s-cluster`, `k8s-node`, `pod`, `k8s-deployment`, `physical_disk`, `ceph`)+- `type`: comma-separated list (e.g., `agent`, `vm`, `system-container`, `app-container`, `docker-service`, `storage`, `pbs`, `pmg`, `k8s-cluster`, `k8s-node`, `pod`, `k8s-deployment`, `physical_disk`, `ceph`)- `source`: comma-separated list (e.g., `proxmox`, `agent`, `docker`, `pbs`, `pmg`, `kubernetes`)- `excludeSource`: comma-separated list of sources that must not be present on a matching resource- `status`: comma-separated list (`online`, `offline`, `warning`, `unknown`)@@ -795,7 +795,7 @@ node identity as the bootstrap response. The optional `backup_perms=true`query is supported only for `type=pve`.### Setup Script URL-`POST /api/setup-script-url` (auth)+`POST /api/setup-script-url` (admin, `settings:write`)Generates a one-time setup token and URL for `/api/setup-script`.Canonical callers must send a supported `type` of `pve` or `pbs` plus anon-empty `host`; the backend normalizes that host before minting the setup@@ -849,12 +849,15 @@ back to the installer or runtime-side Unified Agent:`{"status":"success","action":"use_token","type":"pve|pbs","source":"agent|script","host":"https://...","nodeId":"<stored-name>","nodeName":"<stored-name>",...}`.### Agent Install Command-`POST /api/agent-install-command` (auth)+`POST /api/agent-install-command` (admin, `settings:write`)Generates an API token and install command for agent-based Proxmox setup.### Discovery-`GET /api/discover` (auth)-Runs network discovery.+`GET /api/discover` (admin, `settings:write`)+Returns the last cached network discovery result from the background discovery service. It does not scan.++`POST /api/discover` (admin, `settings:write`)+Runs a manual network scan. JSON body: `{"subnet": "...", "use_cache": false}`. `subnet` defaults to `auto`; `use_cache: true` returns the cached result instead of scanning.### AI Discovery (Service Discovery)Service discovery is used by Pulse Assistant and the UI to inventory web services and enrich links.@@ -871,7 +874,7 @@ Service discovery is used by Pulse Assistant and the UI to inventory web service- `PUT /api/discovery/{type}/{targetId}/{resourceId}/notes`### Test Notification-`POST /api/test-notification` (auth)+`POST /api/test-notification` (admin, `settings:write`)Broadcasts a WebSocket test event.---@@ -1050,7 +1053,7 @@ it, use the snooze and unsnooze endpoints below.- `POST /api/alerts/unacknowledge` (body: `{ "alertIdentifier": "alert-id" }`)- `POST /api/alerts/snooze` (body: `{ "alertIdentifier": "alert-id", "until": "RFC3339 timestamp" }`; pauses delivery and escalation for up to 30 days while monitoring continues)- `POST /api/alerts/unsnooze` (body: `{ "alertIdentifier": "alert-id" }`; resumes normal policy without resolving the incident)-- `POST /api/alerts/clear` (body: `{ "id": "alert-id" }`)+- `POST /api/alerts/clear` (body: `{ "alertIdentifier": "alert-id" }`)---@@ -1124,7 +1127,7 @@ Returns a new raw token (shown once) and updates stored hashes:## 🧾 Audit Log (Pro)-These endpoints require admin access and the `settings:read` scope. On Community, the list endpoint returns an empty set and `persistentLogging: false`.+These endpoints require admin access and the `audit:read` scope. On Community (no `audit_logging` license), these endpoints return HTTP 402 Payment Required with `error: "license_required"` and `feature: "audit_logging"` before any events are read.### List Audit Events`GET /api/audit?limit=100&event=login&user=admin&success=true&startTime=2024-01-01T00:00:00Z&endTime=2024-01-31T23:59:59Z`@@ -1235,7 +1238,7 @@ Tests SSH connectivity for temperature collection (requires setup token or auth)### Scheduler Health`GET /api/monitoring/scheduler/health`-Returns scheduler health, DLQ, and breaker status. Requires `monitoring:read`.+Returns scheduler health, DLQ, and breaker status. Requires authentication (session or API token); no specific scope is enforced.### Updates (Admin)- `GET /api/updates/check`@@ -1254,7 +1257,7 @@ Returns scheduler health, DLQ, and breaker status. Requires `monitoring:read`.- `GET /api/infra-updates/{resourceId}` (requires `monitoring:read`)### Diagnostics-- `GET /api/diagnostics` (auth)+- `GET /api/diagnostics` (admin, `settings:read`)- `POST /api/diagnostics/docker/prepare-token` (admin, `settings:write`)The Docker migration token request accepts `agentId`, optional `tokenName`, and@@ -1292,7 +1295,7 @@ OIDC and SAML configuration is managed via SSO providers.Provider mutation request contract:- Max request body: 1MB.-- Strict JSON contract: unknown fields and trailing payload are rejected.+- Unknown JSON fields are ignored. A trailing payload after the JSON object is rejected with `invalid_json`.- Provider IDs must match server validation.- OIDC and SAML providers are included with the Community SSO entitlement.@@ -1302,8 +1305,8 @@ Provider mutation request contract:Test/preview request contract:- Max request body: 32KB.-- Strict JSON contract: unknown fields and trailing payload are rejected.-- Common errors include `invalid_json`, `validation_error`, `rate_limited`, `body_too_large`.+- Unknown JSON fields are ignored. A trailing payload after the JSON object is rejected with `invalid_json`.+- Common errors include `invalid_json`, `validation_error`, `rate_limited`. A body over the 32KB limit is silently truncated, so it fails as `invalid_json` (these endpoints do not return `body_too_large`).---@@ -1619,7 +1622,7 @@ Runs a focused investigation for an alert payload (used by the UI).- `GET /api/ai/approvals/{id}`- `POST /api/ai/approvals/{id}/approve`- `POST /api/ai/approvals/{id}/deny`-- `POST /api/ai/run-command` (execute an approved command)+- `POST /api/ai/run-command` (retired: always returns `410 Gone` with error code `raw_command_retired`; raw command execution is no longer supported, so use advertised typed resource actions instead)- `GET /api/ai/agents` (connected agents via `/api/agent/ws`)### Remediation Plans (Pro)@@ -1744,15 +1747,15 @@ Looks up an agent by ID or hostname/display name. Requires `agent:report`.`POST /api/agents/agent/uninstall`Agent self-unregister during uninstall. Requires `agent:report`.-`POST /api/agents/agent/unlink` (admin, `agent:manage`)+`POST /api/agents/agent/unlink` (admin, `settings:write`)Unlinks an agent from a node.-`DELETE /api/agents/agent/{agent_id}` (admin, `agent:manage`)+`DELETE /api/agents/agent/{agent_id}` (admin, `settings:write`)Removes an agent from state.### Agent Linking (Admin)-- `POST /api/agents/agent/link` (admin, `agent:manage`)-- `POST /api/agents/agent/unlink` (admin, `agent:manage`)+- `POST /api/agents/agent/link` (admin, `settings:write`)+- `POST /api/agents/agent/unlink` (admin, `settings:write`)### Agent Remote Config`GET /api/agents/agent/{agent_id}/config`@@ -1802,7 +1805,7 @@ These routes manage Docker / Podman telemetry and container actions reported by- `POST /api/agents/docker/containers/update` (`docker:manage`) — retired, returns `410 Gone`; use the `/api/actions` plan/decision/execute flow instead### Kubernetes Agent Management (Admin)-- `DELETE /api/agents/kubernetes/clusters/{clusterId}` (`kubernetes:manage`, supports `?hide=true` or `?force=true`)+- `DELETE /api/agents/kubernetes/clusters/{clusterId}` (`kubernetes:manage`) — removes the cluster and blocks re-enrollment until `allow-reenroll`; takes no `hide` or `force` query parameters- `POST /api/agents/kubernetes/clusters/{clusterId}/allow-reenroll` (`kubernetes:manage`)- `PUT /api/agents/kubernetes/clusters/{clusterId}/unhide` (`kubernetes:manage`)- `PUT /api/agents/kubernetes/clusters/{clusterId}/pending-uninstall` (`kubernetes:manage`)diff --git a/frontend-modern/public/docs/ARCHITECTURE.md b/frontend-modern/public/docs/ARCHITECTURE.mdindex 4643dd3d6a..b8f63afa5e 100644--- a/frontend-modern/public/docs/ARCHITECTURE.md+++ b/frontend-modern/public/docs/ARCHITECTURE.md@@ -122,7 +122,7 @@ All backend code lives under `cmd/`, `internal/`, and `pkg/`. The binary is asse11. **Audit Logging (`pkg/audit`)**- Defence-in-depth: every mutation is logged to SQLite, optionally signed with per-tenant encryption keys.- - Async logging mode (`PULSE_AUDIT_ASYNC`) for high-throughput environments.+ - Async audit logging is on by default (`PULSE_AUDIT_ASYNC=false` disables it); see `docs/CONFIGURATION.md`.- Tenant-aware logger manager for isolated per-org audit trails.### Data Flowdiff --git a/frontend-modern/public/docs/AUDIT_LOGGING.md b/frontend-modern/public/docs/AUDIT_LOGGING.mdindex 932122e630..8ec9e7c08c 100644--- a/frontend-modern/public/docs/AUDIT_LOGGING.md+++ b/frontend-modern/public/docs/AUDIT_LOGGING.md@@ -24,9 +24,9 @@ Pulse automatically captures the following events:| `password_change` | Password modifications | Password changed (Docker/systemd) || `csrf_failure` | Blocked cross-site request forgery attempts | Invalid CSRF token || `lockout_reset` | Account lockout resets | Admin reset lockout for user `bob` |-| `oidc_login` | OIDC SSO login attempts (success/failure at each stage) | OIDC login success |+| `sso_oidc_login` | OIDC SSO login attempts (success/failure at each stage) | OIDC login success || `oidc_token_refresh` | OIDC token refresh success/failure (global, not tenant-scoped) | Token refreshed successfully |-| `oidc_role_assignment` | Automatic role assignment from OIDC groups | Auto-assigned roles: operator, viewer |+| `sso_oidc_role_assignment` | Automatic role assignment from OIDC groups | Auto-assigned roles: operator, viewer || `saml_login` | SAML SSO login attempts | SAML login success via provider-id || `saml_role_assignment` | Automatic role assignment from SAML groups | Auto-assigned roles: admin || `sso_provider_created` | SSO provider configuration created | Created provider: Authentik |@@ -261,8 +261,8 @@ of historical events or proof that their signatures are valid.## StorageThe default audit store lives in the Pulse data directory:-- **Single-tenant:** `{data-dir}/audit/audit.db`-- **Multi-tenant:** `{data-dir}/orgs/{org-id}/audit/audit.db`+- **Single-tenant, and the default organisation in multi-tenant installs:** `{data-dir}/audit/audit.db`+- **Non-default organisations (multi-tenant):** `{data-dir}/orgs/{org-id}/audit/audit.db`The default encrypted signing key is `.audit-signing.key` **inside the auditstore directory**, alongside `audit.db`, not at the data-directory root. Itsdiff --git a/frontend-modern/public/docs/AUTO_UPDATE.md b/frontend-modern/public/docs/AUTO_UPDATE.mdindex 6d4ca8e557..156e239b5a 100644--- a/frontend-modern/public/docs/AUTO_UPDATE.md+++ b/frontend-modern/public/docs/AUTO_UPDATE.md@@ -32,9 +32,11 @@ For v5, PVE, disabled, or failed agent updates, use **Agent Doctor** at3. Click the button to open the confirmation dialog4. Review the update details:- Current version → New version- - Estimated time- - Changelog highlights-5. Click **"Install Update"** to begin+ - Major-version or pre-release warning, when the update carries one+ - Estimated time and prerequisites, when listed+ - Root-access notice, when the update requires root+ - Automatic backup notice, when rollback is supported+5. Click **"Start Update"** in the confirmation dialog to begin### Update Process@@ -61,7 +63,7 @@ In **Settings → System → Updates**:| Setting | Description ||---------|-------------|-| **Update Channel** | Stable (recommended for production) or Pre-release (opt-in preview) |+| **Update Channel** | Stable (recommended for production) or Preview (opt-in beta builds and release candidates) || **Automatic Stable Updates** | Allow unattended stable updates on supported host installations with an installed update timer |The update timer must already be installed and enabled for unattended updates.diff --git a/frontend-modern/public/docs/CENTRALIZED_MANAGEMENT.md b/frontend-modern/public/docs/CENTRALIZED_MANAGEMENT.mdindex 5874f32832..a0f9d9dc3d 100644--- a/frontend-modern/public/docs/CENTRALIZED_MANAGEMENT.md+++ b/frontend-modern/public/docs/CENTRALIZED_MANAGEMENT.md@@ -42,8 +42,9 @@ below also support live refresh when the host module is running:| `report_ip` | string | Reported host IP override; also refreshed live for the host module || `disable_ceph` | boolean | Disable local Ceph polling; also refreshed live for the host module |-`interval` accepts a positive duration string; JSON numbers are interpreted as-seconds. Do not enable Debug, shorten intervals or change monitoring scope just+`interval` must be a positive duration string such as `30s` or `1m`. Numeric+values are rejected when a profile is validated or saved; an agent still reads a+numeric interval in an older saved profile as seconds. Do not enable Debug, shorten intervals or change monitoring scope justto collect a report. Use the [bounded agent log readers](UNIFIED_AGENT.md#collect-agent-logs-safely)and evidence already available.@@ -140,8 +141,9 @@ These paths describe existing operations; do not run every operation as adiagnostic checklist. Replace `{id}`, `{agent_id}` and `{version}` with valuesfrom the current instance. Use the UI or an authenticated client that readscredentials and request bodies from private files, preserves CSRF protection-for session writes and verifies HTTPS. The example `pulse_api` helper supports-GET and POST only, not PUT or DELETE.+for session writes and verifies HTTPS. The example `pulse_api` helper from API.md+accepts GET, POST, PUT and DELETE, but this guide's examples are read-only and+use GET only.| Method | Path | Purpose || --- | --- | --- |@@ -167,7 +169,7 @@ Example **request bodies**, not credential-bearing HTTP commands:}```-For validation, send only `{"config": {...}}`. For assignment, use the actual+For validation, send only the configuration keys as the top-level JSON object, with no `config` wrapper, for example `{"interval": "60s", "enable_docker": true}`; a `config` wrapper is treated as one unknown key and the settings are not checked. For assignment, use the actual`id` returned by creation or the profile list, not `prod-servers`:```jsondiff --git a/frontend-modern/public/docs/CLOUD.md b/frontend-modern/public/docs/CLOUD.mdindex 613e3734b1..f521877b1b 100644--- a/frontend-modern/public/docs/CLOUD.md+++ b/frontend-modern/public/docs/CLOUD.md@@ -64,7 +64,7 @@ or substitute the top-level GitHub server installer.### 3. Add Proxmox / TrueNAS Connections-Add your Proxmox VE, PBS, PMG, or TrueNAS systems via **Settings → Infrastructure → Platform connections**.+Add your Proxmox VE, PBS, PMG, or TrueNAS systems via **Settings → Infrastructure** (**Add infrastructure**).### 4. Set Up Mobile Accessdiff --git a/frontend-modern/public/docs/CONFIGURATION.md b/frontend-modern/public/docs/CONFIGURATION.mdindex 5c8e8f591c..606e8ac58d 100644--- a/frontend-modern/public/docs/CONFIGURATION.md+++ b/frontend-modern/public/docs/CONFIGURATION.md@@ -235,7 +235,7 @@ Numeric intervals are **seconds** unless noted otherwise.| `allowedEmbedOrigins` | Comma-separated `frame-ancestors` allowlist || `webhookAllowedPrivateCIDRs` | Allowlist for private webhook targets || `updateChannel` | Update channel (`stable` or `rc`) |-| `autoUpdateEnabled` | Allow one-click updates |+| `autoUpdateEnabled` | Allow unattended automatic updates from the systemd update timer (`stable` channel only) || `publicURL` | Public URL used in links/notifications || `hideLocalLogin` | Hide username/password login form || `temperatureMonitoringEnabled` | Enable temperature monitoring (where supported) |@@ -267,12 +267,14 @@ Environment variables take precedence over `system.json`.| `FRONTEND_PORT` | Public listening port (web UI, API, and agent ingest) | `7655` || `PORT` | **Deprecated** legacy alias for `FRONTEND_PORT`, honored only when `FRONTEND_PORT` is unset. Logs a deprecation warning at startup; switch to `FRONTEND_PORT`. | *(unset)* || `PULSE_AGENT_INGEST_PORT` | Optional dedicated port for the complete agent control plane: reports/config (`/api/agents/*`), command admission (`/api/agent/ws`), version checks, and bootstrap downloads. The web UI and management API stay isolated. `0` = disabled (single port). See [Split-Port Agent Ingest](#split-port-agent-ingest-network-isolation). | `0` |+| `HTTP_REDIRECT_PORT` | Optional plain-HTTP port that redirects to HTTPS on `FRONTEND_PORT`. Requires `HTTPS_ENABLED=true` with `TLS_CERT_FILE` and `TLS_KEY_FILE`. Must differ from `FRONTEND_PORT`. `0` = disabled. | `0` || `LOG_LEVEL` | Log verbosity (see below) | `info` || `LOG_FORMAT` | Log output format (`auto`, `json`, `console`) | `auto` || `LOG_FILE` | Log file path (enables file logging) | *(unset)* || `LOG_MAX_SIZE` | Log rotation size (MB) | `100` |-| `LOG_MAX_AGE` | Keep rotated logs for N days (`0` disables cleanup) | `30` |+| `LOG_MAX_AGE` | Keep rotated logs for N days (positive integer; zero or negative values are ignored with a startup warning and the default applies) | `30` || `LOG_COMPRESS` | Gzip rotated logs | `true` |+| `PULSE_AUDIT_ASYNC` | Queues audit-log writes in memory (up to 4096 events) and saves them in the background, so requests do not wait on audit storage. If the queue is full, the event is written synchronously instead. Only the value `false` (case-insensitive) turns the queue off and writes each event synchronously. Events still queued when the process is killed without a clean shutdown are not written. | `true` |#### Log Levels@@ -334,7 +336,7 @@ not the whole bundle.| `DEMO_MODE` | Enable read-only demo mode | `false` || `PULSE_TRUSTED_PROXY_CIDRS` | Comma-separated immediate proxy IPs/CIDRs trusted for forwarded client IP, scheme, host and port. Use the peer seen by Pulse; wildcard ranges are rejected. See [Reverse Proxy](REVERSE_PROXY.md#before-configuring-the-proxy). | *(unset)* || `PULSE_TRUSTED_NETWORKS` | Comma-separated CIDRs treated as trusted local networks (does not bypass auth) | *(unset)* |-| `ALLOW_UNPROTECTED_EXPORT` | Allow unauthenticated config export on public networks when no auth is configured (use with caution) | `false` |+| `ALLOW_UNPROTECTED_EXPORT` | Set to `true` to allow unauthenticated config export from any non-loopback client (private LAN as well as public networks), only while no password, API token, proxy secret, SSO or hosted mode is configured. Export only: import is never enabled by this (use with caution) | `false` |### Split-Port Agent Ingest (Network Isolation)@@ -481,7 +483,7 @@ monitoring defect.| ---------- | ------------- | --------- || `LOG_FILE` | Log file path (empty = stderr only) | *(unset)* || `LOG_MAX_SIZE` | Log file max size (MB) | `100` |-| `LOG_MAX_AGE` | Log file retention (days, `0` disables cleanup) | `30` |+| `LOG_MAX_AGE` | Log file retention (positive days; zero or negative values are ignored with a startup warning and the default applies) | `30` || `LOG_COMPRESS` | Compress rotated logs | `true` |@@ -492,7 +494,7 @@ These are stored in `system.json` and managed via the UI.| Key | Description | Default || ----- | ------------- | --------- || `updateChannel` | Update channel (`stable` or `rc`) | `stable` |-| `autoUpdateEnabled` | Allow one-click updates | `false` |+| `autoUpdateEnabled` | Allow unattended automatic updates from the systemd update timer (`stable` channel only) | `false` |> **Note**: Update settings are stored in `system.json`. Legacy `.env` entries (`UPDATE_CHANNEL`, `AUTO_UPDATE_ENABLED`) are kept in sync for backwards compatibility but are not read at runtime. The former `autoUpdateCheckInterval` / `autoUpdateTime` fields were never consumed and are ignored if present; the update schedule lives in the systemd timer.>@@ -1061,6 +1063,8 @@ docker run --init -e HTTPS_ENABLED=true \-e TLS_KEY_FILE=/certs/key.pem ...```+To redirect plain-HTTP requests to HTTPS, set `HTTP_REDIRECT_PORT` to a port other than `FRONTEND_PORT` (for example `80`). Pulse listens on that port on the same bind address as the web UI and answers requests with a `301` redirect to the same host on the HTTPS `FRONTEND_PORT`. The redirect listener starts only when `HTTPS_ENABLED=true` and both `TLS_CERT_FILE` and `TLS_KEY_FILE` are set; otherwise the value has no effect. A non-numeric or out-of-range value is ignored silently, which leaves the redirect disabled.+> **Important (Docker with HTTPS)**: Always use `--init` (or `init: true` in docker-compose) when enabling HTTPS. The Alpine-based healthcheck uses busybox `wget`, which spawns `ssl_client` subprocesses. Without an init process to reap them, these become zombie processes over time.---@@ -1196,10 +1200,10 @@ Pulse v6 supports first-class TrueNAS SCALE and CORE monitoring.### Adding a TrueNAS Instance-1. Go to **Settings → TrueNAS**.-2. Click **Add Connection**.-3. Enter the URL (e.g., `https://truenas.local`) and an API key.-4. Click **Test Connection** to verify, then **Save**.+1. Go to **Settings → Infrastructure**.+2. Click **Add infrastructure** and choose **TrueNAS**.+3. Enter the host (e.g., `truenas.local`), the port and whether to use HTTPS, then the API key and the username that owns the key.+4. Click **Test connection** to verify, then **Add connection**.### Creating a TrueNAS API Key@@ -1217,8 +1221,8 @@ On your TrueNAS system:| Apps | TrueNAS Overview || ZFS Pools & datasets | Storage page || Physical disks | Storage page |-| ZFS Snapshots | Recovery page |-| Replication tasks | Recovery page |+| ZFS Snapshots | TrueNAS → Protection |+| Replication tasks | TrueNAS → Protection || TrueNAS alerts | Alerts page |TrueNAS connections are stored encrypted in `truenas.enc`.@@ -1233,8 +1237,8 @@ The relay protocol provides end-to-end encrypted remote access foundations for P### Configuration-1. Go to **Settings → Relay**.-2. Toggle relay **On**.+1. Go to **Settings → Pulse Mobile**.+2. Turn on **Allow Pulse Mobile connections**.3. Use the **QR Code** or **Deep Link** to pair a supported Pulse Mobile client.### Environment Overrides@@ -1249,7 +1253,7 @@ going through the UI, two environment variables override the persisted| `PULSE_RELAY_SERVER` | Override relay server URL. Must be a valid `ws://` or `wss://` URL with no userinfo, query, or fragment. Invalid values are logged and ignored. | `wss://relay.pulserelay.pro/ws/instance` |Precedence: env vars beat the file. If you set `PULSE_RELAY_ENABLED=true`,-saving the relay form in **Settings → Relay** will then persist the+saving the relay settings in **Settings → Pulse Mobile** will then persist theenv-effective state to disk, so removing the env var later does notautomatically revert relay back to its previous file-stored state — clearrelay in the UI as well if you want to fully disable it.diff --git a/frontend-modern/public/docs/DOCKER.md b/frontend-modern/public/docs/DOCKER.mdindex 7d435a312e..d699daa3a9 100644--- a/frontend-modern/public/docs/DOCKER.md+++ b/frontend-modern/public/docs/DOCKER.md@@ -396,7 +396,7 @@ not grant command execution permission to monitoring tokens. SeeTo disable registry checks entirely, set `PULSE_DISABLE_DOCKER_UPDATE_CHECKS=true` on the **agent**.-You can also toggle "Hide Docker Update Buttons" from the UI in **Settings → System → General** under **Docker / Podman updates**.+You can also toggle **Hide update buttons** from the UI in **Settings → System → General** under **Docker / Podman updates**.---@@ -409,7 +409,7 @@ Pulse can start, stop, and restart Docker / Podman containers directly from the- **Pulse Agent** installed on the container host (see [Unified Agent](UNIFIED_AGENT.md)) and currently connected- **Command execution enabled** on the agent — it is disabled by default. Either:- start the agent with `--enable-commands` (or `PULSE_ENABLE_COMMANDS=true`), or- - tick **Enable Pulse command execution** in **Settings → Infrastructure** before copying the install command, which adds the flag and grants the token the command execution permission+ - tick **Enable legacy combined command profile** in **Settings → Infrastructure** before copying the install command, which adds the flag and grants the token the command execution permission (this is the transitional combined profile, not a least-privilege setting)- **Admin approval**: every lifecycle action requires confirmation by an admin in the UI before it runs. The agent then verifies the container's state before the change and confirms it actually reached the requested state afterwards.### Limitationsdiff --git a/frontend-modern/public/docs/FAQ.md b/frontend-modern/public/docs/FAQ.mdindex 237352d175..803289ea31 100644--- a/frontend-modern/public/docs/FAQ.md+++ b/frontend-modern/public/docs/FAQ.md@@ -16,9 +16,9 @@ Go to **Settings → Infrastructure → Install on a host** for systems that shorun the unified agent directly.- **Recommended (agent setup)**: copy the generated install command and run it on the target host.-- **Manual/API-backed platforms**: use **Settings → Infrastructure → Platform connections** for systems such as Proxmox, PBS, PMG, or TrueNAS that connect over an API instead of running the agent locally.+- **Manual/API-backed platforms**: use **Settings → Infrastructure** (**Add infrastructure**) for systems such as Proxmox, PBS, PMG, or TrueNAS that connect over an API instead of running the agent locally.-If you want Pulse to find servers automatically, enable discovery in **Settings → System → Network** and then review discovered servers in **Settings → Infrastructure**.+If you want Pulse to find servers automatically, open **Settings → Infrastructure**, select **Configure discovery** (it reads **Settings** once discovery is on), turn on **Automatic scanning** in the Discovery settings dialog, and then review discovered servers in the same section.### How do I change the port?@@ -127,7 +127,7 @@ Yes! If Pulse detects Ceph storage, it automatically queries cluster health, OSD### Does Pulse monitor TrueNAS?Yes. Pulse includes first-class TrueNAS SCALE/CORE integration. Add your-TrueNAS server under **Settings → Infrastructure → Platform connections** with+TrueNAS server under **Settings → Infrastructure** (**Add infrastructure**) withthe URL and API key. Pulse monitors the appliance, native VMs, apps, pools,datasets, disks, ZFS snapshots, replication tasks, and alerts. Those resourcesappear on the dedicated TrueNAS page.@@ -202,7 +202,7 @@ steps; do not reset a working installation to retrieve that token.Set `HTTPS_ENABLED=true` and provide `TLS_CERT_FILE` and `TLS_KEY_FILE` environment variables. See [Configuration](CONFIGURATION.md#-https--tls).### Can I use Single Sign-On (SSO)?-Yes. Pulse supports **OIDC** and **SAML** SSO providers, with multi-provider support (multiple IdPs active simultaneously). Configure in **Settings → Security → SSO Providers**. Pulse also supports Proxy Auth (Authentik, Authelia, Cloudflare). See [Proxy Auth Guide](PROXY_AUTH.md).+Yes. Pulse supports **OIDC** and **SAML** SSO providers, with multi-provider support (multiple IdPs active simultaneously). Configure in **Settings → Security → Single Sign-On**. Pulse also supports Proxy Auth (Authentik, Authelia, Cloudflare). See [Proxy Auth Guide](PROXY_AUTH.md).---diff --git a/frontend-modern/public/docs/KUBERNETES.md b/frontend-modern/public/docs/KUBERNETES.mdindex d8df2d813d..13745ca28f 100644--- a/frontend-modern/public/docs/KUBERNETES.md+++ b/frontend-modern/public/docs/KUBERNETES.md@@ -2,7 +2,7 @@This guide explains how to deploy the Pulse Server (Hub) and Pulse Agents on Kubernetes clusters, including immutable distributions like Talos Linux.-> **Navigation note (v6):** Kubernetes cluster and node resources appear on the **Infrastructure** page, while pods appear on the **Workloads** page. The legacy `/kubernetes` URL redirects to `/workloads?type=k8s`.+> **Navigation note (v6):** Kubernetes has its own page at `/kubernetes`, with tabs for nodes, workloads (pods), services, storage, configuration, and events. Pods appear on the **Workloads** tab (`/kubernetes/workloads`).## Prerequisites@@ -205,7 +205,7 @@ spec:- --enable-kubernetesenv:- name: PULSE_URL- value: "http://pulse-server.pulse.svc.cluster.local:7655"+ value: "http://pulse.pulse.svc.cluster.local:7655"- name: PULSE_TOKENvalueFrom:secretKeyRef:diff --git a/frontend-modern/public/docs/MSP.md b/frontend-modern/public/docs/MSP.mdindex 9302b66a1d..56e016f1f0 100644--- a/frontend-modern/public/docs/MSP.md+++ b/frontend-modern/public/docs/MSP.md@@ -32,7 +32,8 @@ Day-2 operations run through the `pulse-control-plane` binary (via```bashpulse-control-plane provider-msp bootstrap --account-name "Your MSP" --owner-email [email protected]pulse-control-plane provider-msp status-pulse-control-plane provider-msp backup+pulse-control-plane provider-msp backup create+pulse-control-plane provider-msp backup verify [archive]pulse-control-plane provider-msp recover # restore workspaces from backup or diskpulse-control-plane provider-msp preflight # pre-install environment checks```diff --git a/frontend-modern/public/docs/MULTI_TENANT.md b/frontend-modern/public/docs/MULTI_TENANT.mdindex 884b020058..15a5bfba14 100644--- a/frontend-modern/public/docs/MULTI_TENANT.md+++ b/frontend-modern/public/docs/MULTI_TENANT.md@@ -19,8 +19,8 @@ The Community, Relay, and Pro tiers do not include the `multi_tenant` capability1. Set `PULSE_MULTI_TENANT_ENABLED=true` in your environment and restart Pulse.2. Activate your Enterprise license in **Settings → Plans & Billing**.-3. Go to **Settings → Organization** and click **Create Organization**.-4. Name your organization and assign infrastructure to it.+3. Create the organization with the session-authenticated `POST /api/orgs` endpoint (see [Creating an Organization](#creating-an-organization)). This build has no Create Organization button in **Settings → Organization**.+4. Assign infrastructure to the organization.5. Use the **Org Switcher** in the header bar to switch between organizations.## Concepts@@ -57,7 +57,7 @@ Organizations can share specific resources with other organizations:## Before Using the API-Create organizations and manage members and shares in the signed-in Pulse UI.+Manage members and shares in the signed-in Pulse UI. Organizations are created through the session-authenticated `POST /api/orgs` endpoint; the UI has no create control.These changes require **session-based user authentication** and the relevantorganization role; API tokens are rejected with `403 session_required`, evenwhen they have `settings:write`. The UI handles the session and CSRF protection.@@ -86,14 +86,14 @@ The helper's loopback origin applies on the Pulse host; remotely, follow itsHTTPS instructions and keep certificate verification enabled. Replace theexample organization ID `production-datacenter` with your own, and run eachread separately. The helper's support for other HTTP methods does not make-organization mutations token-authenticated; keep those changes in the+organization mutations token-authenticated; keep member and share changes in thesigned-in UI with its session and CSRF protection.## Managing Organizations### Creating an Organization-**UI:** Settings → Organization → Create Organization+**UI:** none in this build; Settings → Organization has no create control.**API contract:** `POST /api/orgs`, session authentication only:```json@@ -193,10 +193,10 @@ When multi-tenant is enabled, **Settings → Organization** shows:| Panel | Description ||---|---|-| **Overview** | Organization name, description, creation date |+| **Overview** | Organization display name (editable), org ID, creation date, member count || **Access** | Member list, invite/remove members, change roles || **Sharing** | Outgoing and incoming resource shares |-| **Billing & Plan** | Organization-level plan and license info |+| **Billing** | Organization plan, usage policies and subscription status (the "Billing & Usage" panel) |## API Reference@@ -237,11 +237,11 @@ or a token's organization binding.## Troubleshooting-### "Multi-tenant is not enabled on this server" (501)+### "Multi-tenant functionality is not enabled. Set PULSE_MULTI_TENANT_ENABLED=true to enable." (501)Set `PULSE_MULTI_TENANT_ENABLED=true` in your environment and restart Pulse.-### "Multi-tenant requires an Enterprise license" (402)+### "Multi-tenant access requires an Enterprise license" (402)Activate an Enterprise license with the `multi_tenant` capability in **Settings → Plans & Billing**.diff --git a/frontend-modern/public/docs/OIDC.md b/frontend-modern/public/docs/OIDC.mdindex 284fc6f3b6..e671f5fe98 100644--- a/frontend-modern/public/docs/OIDC.md+++ b/frontend-modern/public/docs/OIDC.md@@ -154,7 +154,7 @@ service as a substitute for verified revocation.### Microsoft Entra ID (formerly Azure AD)-Create the provider in Pulse first (**Settings → Security → Single Sign-On → Add Provider**) so it gets its ID — Pulse generates a UUID per provider and shows the resulting callback URL. You need that URL for the Entra redirect URI below.+Create the provider in Pulse first (**Settings → Security → Single Sign-On → Add OIDC**) so it gets its ID — Pulse generates a UUID per provider and shows the resulting callback URL. You need that URL for the Entra redirect URI below.**In the Entra admin center:**@@ -170,7 +170,7 @@ Create the provider in Pulse first (**Settings → Security → Single Sign-On- **Issuer URL**: `https://login.microsoftonline.com/<tenant-id>/v2.0`- **Client ID**: the app registration's *Application (client) ID*.- **Client Secret**: the secret value from step 3.-- **Redirect URI**: `https://pulse.example.com/api/oidc/<provider-id>/callback`, matching the app registration exactly. The bare `/api/oidc/callback` is a v5 compatibility path that only serves the legacy env-configured provider — don't use it for a new provider.+- **Redirect URI**: `https://pulse.example.com/api/oidc/<provider-id>/callback`, matching the app registration exactly. The bare `/api/oidc/callback` is a v5 compatibility path. It is mapped to the legacy (v5-migrated or env-configured) provider; if that provider is not enabled, Pulse instead serves the provider whose login started from it (recovered from the pending login state). Don't use it as the redirect URI for a new provider.- **Scopes**: exactly `openid profile email`. Do **not** add `groups`. Entra has no `groups` scope and fails the whole authorization request with `AADSTS650053`; group membership arrives in the ID token from the Token configuration step, not from a scope.- **Groups Claim**: `groups`- **Allowed Groups**: the group's Object ID (GUID), not its display name.@@ -187,7 +187,7 @@ Create the provider in Pulse first (**Settings → Security → Single Sign-On| **`invalid_id_token`** | Compare the configured issuer with the IdP issuer locally; use the existing redacted error, not a token dump or newly enabled Debug logs. || **`unexpected signature algorithm "HS256"`** | Your IdP is signing with HS256. Configure it to use **RS256**. || **Redirect Loop** | Check `X-Forwarded-Proto` header (must be `https`) and cookie settings. |-| **Self-Signed Certs** | Set the **CA Bundle** field on the SSO provider to a host path readable by Pulse (e.g. `/etc/ssl/certs/oidc-ca.pem` mounted into the container). The field is stored on the provider record as `oidc.caBundle`; there is no `OIDC_CA_BUNDLE` env var. |+| **Self-Signed Certs** | The SSO provider form in Settings has no CA Bundle field. Set `oidc.caBundle` on the provider through the SSO provider API (`/api/security/sso/providers`) to a host path readable by Pulse (e.g. `/etc/ssl/certs/oidc-ca.pem` mounted into the container). For a provider configured with the legacy `OIDC_ENABLED` environment variables, set `OIDC_CA_BUNDLE` instead (see [Configuration](CONFIGURATION.md)). |### Safe diagnosisdiff --git a/frontend-modern/public/docs/PBS.md b/frontend-modern/public/docs/PBS.mdindex 26f083fd3d..bfe3bb3981 100644--- a/frontend-modern/public/docs/PBS.md+++ b/frontend-modern/public/docs/PBS.md@@ -79,8 +79,9 @@ Use this only when you also need host-local telemetry. The Linux agent normallyruns as root; it is not required to fix API authentication or missing backuppermissions. Review [Agent Security](AGENT_SECURITY.md) first.-Create a separate Pulse token in **API Access**, using the **Agent host** preset-for reporting, configuration reads and agent management. This is a **Pulse**+Create a separate Pulse token in **API Access**, using the **Agent** preset+for reporting and configuration reads; it does not include agent lifecycle+management (`agent:manage`). This is a **Pulse**token, not the **PBS** token used above. Do not enable command execution justfor monitoring.diff --git a/frontend-modern/public/docs/PRIVACY.md b/frontend-modern/public/docs/PRIVACY.mdindex 5de0702446..af05e327c0 100644--- a/frontend-modern/public/docs/PRIVACY.md+++ b/frontend-modern/public/docs/PRIVACY.md@@ -133,7 +133,7 @@ Every field is listed below with the reason it exists. Nothing else is included| Notification failures TLS 7d (schema v5) | `0` | Count terminal failures classified locally as certificate or TLS failures without sending certificates, hostnames, or raw errors || Notification failures configuration 7d (schema v5) | `0` | Count terminal failures classified locally as missing or invalid destination configuration without sending configuration values || Notification failures rejected 7d (schema v5; new schema v15 classifications are HTTP 4xx) | `0` | Count terminal failures classified locally as destination request or payload rejection without sending response or payload content; schema v5-v14 included destination HTTP 5xx responses, and those locally retained rows can remain in this rolling count for up to seven days after upgrade |-| Notification failures server error 7d (schema v15) | `0` | Count terminal failures classified locally as destination HTTP 5xx server errors without sending response content, destination identity, or provider identity |+| Notification failures server error 7d (schema v15) | `0` | Count terminal failures classified locally as destination server-side or temporary failures (HTTP 5xx responses, the temporary HTTP 423 Locked and 425 Too Early responses, and transient SMTP 4xx replies) without sending response content, destination identity, or provider identity || Notification failures unknown 7d (schema v5) | `0` | Count terminal failures that do not match another fixed class without sending raw errors || Alert AI enabled | `true`/`false` | See whether AI analysis on alert firing is switched on, without sending alert content, resource identifiers, or analysis text || AI provider class | `local` | See one closed bucket for how the Patrol (or default) model is reached: `none`, `local` (Ollama or a private-network OpenAI-compatible endpoint), `cloud_byok` (a hosted provider with your own key), `cloud_subscription` (the Codex or Claude CLI subscription route), or `hosted_legacy` (the retired Pulse-hosted route), without sending the provider, model name, endpoint, or account |@@ -283,8 +283,9 @@ performed locally; raw error text and destination/provider identity are neverincluded in the payload.Schema v15 adds an eighth-fixed notification terminal-failure counter for destination HTTP 5xx server-errors. From v15 onward,+fixed notification terminal-failure counter for destination server-side or+temporary failures: HTTP 5xx responses, the temporary HTTP 423 Locked and 425+Too Early responses, and transient SMTP 4xx replies. From v15 onward,new terminal failures enter `notification_failures_rejected_7d` only for HTTP4xx destination or payload rejections. Locally retained v5-v14 rows may stillinclude HTTP 5xx responses for up to seven days after upgrade; first-heartbeatdiff --git a/frontend-modern/public/docs/PRODUCTION_SECURITY.md b/frontend-modern/public/docs/PRODUCTION_SECURITY.mdindex c6d47cef24..7f4eedebf9 100644--- a/frontend-modern/public/docs/PRODUCTION_SECURITY.md+++ b/frontend-modern/public/docs/PRODUCTION_SECURITY.md@@ -18,8 +18,8 @@ utilization, storage, guests, and status.| **Proxmox API plus host agent:** API coverage plus host-local SMART, temperatures, ZFS/Ceph/mdadm detail, arbitrary mount capacity, and full LXC filesystem capacity | The Linux agent runs as `root` by default for the supported full-telemetry profile. || **Guest-local agent:** Host metrics and optional Docker/Podman inventory inside a VM or LXC | The agent is trusted inside that guest only; it does not grant Pulse access to the hypervisor. |-For most Proxmox installations, begin with **Settings → Infrastructure →-Platform connections**. Add a host agent only after identifying a metric that+For most Proxmox installations, begin with **Settings → Infrastructure**+(**Add infrastructure**). Add a host agent only after identifying a metric thatthe Proxmox API cannot provide. The complete capability matrix is in[Agent Security](AGENT_SECURITY.md#proxmox-deployment-choices).@@ -112,7 +112,9 @@ and management API.permissions Pulse needs, and rotate a token before revoking the credentialcurrently used by a live connection or agent.- Do not put host SSH private keys in a Pulse Docker or LXC container. Pulse- blocks that pattern; use API-only monitoring or a host-local agent instead.+ logs a security warning when it collects temperatures over SSH from a+ container but still uses the key; use API-only monitoring or a host-local+ agent instead.- Restrict the Pulse data directory and backups as secrets. They containencrypted credentials as well as sessions, API-token state, and the keymaterial needed by the installation.diff --git a/frontend-modern/public/docs/PULSE_PRO.md b/frontend-modern/public/docs/PULSE_PRO.mdindex 6be31e96d3..e62835c643 100644--- a/frontend-modern/public/docs/PULSE_PRO.md+++ b/frontend-modern/public/docs/PULSE_PRO.md@@ -181,9 +181,9 @@ Patrol mode decides how far Pulse can go after Patrol finds something that needs| Mode | Behavior | Plan ||---|---|---|| **Watch only** | Detect issues only. No investigation or fix execution. | Community / legacy Relay payload |-| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |-| **Auto-fix safe issues** | Runs approved safe fixes and verifies the outcome. Critical findings require approval by default. | Pro / hosted Cloud |-| **Policy autopilot** | Runs eligible policy-approved fixes without approval when explicitly enabled. | Pro / hosted Cloud |+| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |+| **Safe auto-fix** | Runs approved safe fixes and verifies the outcome. Critical findings require approval by default. | Pro / hosted Cloud |+| **Autopilot** | Runs eligible policy-approved fixes without approval when explicitly enabled. | Pro / hosted Cloud |## What You Get (By Plan)diff --git a/frontend-modern/public/docs/RBAC.md b/frontend-modern/public/docs/RBAC.mdindex 0d41868368..b5e33e27fd 100644--- a/frontend-modern/public/docs/RBAC.md+++ b/frontend-modern/public/docs/RBAC.md@@ -38,7 +38,7 @@ user merely because no local administrator is configured.## Quick Start1. Activate a Pro, grandfathered Pro+, Cloud, MSP, or Enterprise/custom license in **Settings → Plans & Billing**.-2. Go to **Settings → Security → Access Control**.+2. Go to **Settings → Security → Roles**.3. Create roles with the permissions you need.4. Assign roles to users.@@ -48,7 +48,7 @@ user merely because no local administrator is configured.### Before Using the API-Prefer **Settings → Security → Access Control** for one-off administration.+Prefer **Settings → Security → Roles** and **Settings → Security → Users** for one-off administration.The API examples require the licensed `rbac` capability and permission toadminister users. With RBAC enabled, role and user administration requires afull-access (`*`) API token bound to an authorised administrator; a monitoring@@ -81,7 +81,7 @@ alone does not establish the intended access or disable an upstream IdP account.### Creating a Role-**UI:** Settings → Security → Access Control → Create Role+**UI:** Settings → Security → Roles → New RoleUse a new custom role ID. Built-in roles (`admin`, `operator`, `viewer`,`auditor`) cannot be modified or deleted. These examples use `alert-manager`.@@ -201,7 +201,7 @@ How it works:- Matching groups are mapped to Pulse roles.- A user can receive multiple roles from multiple group mappings.- Once a provider has any group role mappings configured, the mapping is authoritative: on every login the user's role assignments are replaced with whatever the mapping resolves to. A login that matches no mapped group resolves to an empty set, which clears the user's existing role assignments. Watch for identity providers that silently drop the groups claim (see the Entra ID group overage warning in [OIDC.md](OIDC.md#microsoft-entra-id-formerly-azure-ad)) — to Pulse that looks the same as losing every group.-- Role changes are logged to the [audit log](AUDIT_LOGGING.md) as `oidc_role_assignment` events.+- Logins that assign at least one role are logged to the [audit log](AUDIT_LOGGING.md) as `sso_oidc_role_assignment` events. A login that clears a user's roles does not write this event.See [OIDC documentation](OIDC.md#group-to-role-mapping) for full configuration details.diff --git a/frontend-modern/public/docs/RELAY.md b/frontend-modern/public/docs/RELAY.mdindex 3b96b8119a..39d155d8a0 100644--- a/frontend-modern/public/docs/RELAY.md+++ b/frontend-modern/public/docs/RELAY.md@@ -45,7 +45,7 @@ Relay was designed with a zero-trust model:| **Back-pressure** | Data limiters prevent channel flooding || **License-gated** | Requires an active Relay-or-higher license || **Configurable** | Can be enabled/disabled at any time via Settings |-| **Audit** | Relay connection events are logged to the audit trail |+| **Audit** | Pulse Mobile relay access token creation is recorded in the audit trail. Relay connection events are written to the Pulse server log. |## Configuration@@ -77,8 +77,8 @@ Relay configuration is stored encrypted in `relay.enc` in the Pulse data directo|---|---|---|---|| `GET` | `/api/settings/relay` | `settings:read` | Get relay status and config || `PUT` | `/api/settings/relay` | `settings:write` | Update relay settings |-| `POST` | `/api/onboarding/qr` | `settings:read` | Generate mobile onboarding QR code |-| `POST` | `/api/onboarding/deep-link` | `settings:read` | Generate mobile deep link |+| `GET` | `/api/onboarding/qr` | `settings:read` | Generate mobile onboarding QR code |+| `GET` | `/api/onboarding/deep-link` | `settings:read` | Generate mobile deep link |## Pulse Mobile Pairingdiff --git a/frontend-modern/public/docs/REVERSE_PROXY.md b/frontend-modern/public/docs/REVERSE_PROXY.mdindex e572d97048..533d9dd580 100644--- a/frontend-modern/public/docs/REVERSE_PROXY.md+++ b/frontend-modern/public/docs/REVERSE_PROXY.md@@ -129,9 +129,15 @@ ProxyPassReverse / http://127.0.0.1:7655/If your reverse proxy terminates SSL but Pulse shows "HTTPS: HTTP only" in Settings → Security:-Pulse recognises direct TLS, or `X-Forwarded-Proto: https` from an immediate-peer in `PULSE_TRUSTED_PROXY_CIDRS`. An untrusted peer's header is ignored even-when the browser used HTTPS. Adding the header alone is not sufficient.+Pulse's secure-cookie and request-origin logic recognises direct TLS, or+`X-Forwarded-Proto: https` from an immediate peer in+`PULSE_TRUSTED_PROXY_CIDRS`; a header from any other peer is ignored for those+decisions, even when the browser used HTTPS. Adding the header alone is not sufficient.+The Security Posture HTTPS+indicator is different: it is true when the request has direct TLS or any+`X-Forwarded-Proto: https` header, whatever the peer. A passing indicator+therefore does not prove that proxy trust is configured correctly, and+"HTTP only" means neither TLS nor that header reached Pulse.Check the proxy's actual backend connection address and the effective Pulsesetting first, then check that the TLS proxy sends exactly `https`. For Nginx,@@ -150,7 +156,7 @@ HTTP/error status, not cookies, proxy secrets or a full network export.### Other Issues-- **"Connection Lost"**: WebSocket upgrade failed. Check `Upgrade` and `Connection` headers.+- **"Connection lost" (Workloads) or "Disconnected", "Reconnecting...", "Sync reconnecting" or "Backend healthy" in the header status badge**: the live data stream is not connected, which can happen when the WebSocket upgrade fails. Check the proxy's `Upgrade` and `Connection` headers.- **502 Bad Gateway**: Check Pulse's actual listener and the proxy's upstream address, port and network reachability; this does not by itself prove Pulse is stopped. Container `localhost` refers to that container, not another service.- **CORS Errors**: Do not add CORS headers in the proxy; Pulse handles them. Set **Settings → System → Network → Allowed Origins** or use `ALLOWED_ORIGINS` if needed.- **OIDC redirects fail**: Ensure `X-Forwarded-Proto` is set (see above).diff --git a/frontend-modern/public/docs/SECURITY.md b/frontend-modern/public/docs/SECURITY.mdindex 2c73a2e3ff..739b72da95 100644--- a/frontend-modern/public/docs/SECURITY.md+++ b/frontend-modern/public/docs/SECURITY.md@@ -366,7 +366,7 @@ Pulse supports **OIDC** and **SAML** SSO providers with multi-provider configura- **OIDC**: Google, Authentik, Keycloak, Auth0, or any compliant provider.- **SAML**: For enterprise IdPs that use SAML assertions.- Multiple providers can be enabled simultaneously; the login page shows all available SSO buttons.-- Configure via **Settings → Security → SSO Providers** (admin required).+- Configure via **Settings → Security → Single Sign-On** (admin required).See `docs/PROXY_AUTH.md` for proxy-based auth (Authentik, Authelia, Cloudflare).diff --git a/frontend-modern/public/docs/TEMPERATURE_MONITORING.md b/frontend-modern/public/docs/TEMPERATURE_MONITORING.mdindex f491ba5621..7ea4b53d52 100644--- a/frontend-modern/public/docs/TEMPERATURE_MONITORING.md+++ b/frontend-modern/public/docs/TEMPERATURE_MONITORING.md@@ -119,7 +119,7 @@ Pulse can also collect temperatures by SSHing into each host that does not have### Setup1. Generate the node setup command from the UI:- **Settings -> Infrastructure -> Add Node**+ **Settings -> Infrastructure -> Add infrastructure**, choose **Proxmox VE**, and use the setup guide's **Copy command** button2. Run the command on each Proxmox host. The setup script can:- Create the required API user and permissions- Add a restricted SSH key entry for temperature collection@@ -131,7 +131,7 @@ The SSH entry added to `authorized_keys` is restricted to the Pulse sensor wrappcommand="/usr/local/sbin/pulse-sensors",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty <public-key> # pulse-sensors```-If you use a non-standard SSH port, set `SSH_PORT` (system-wide) or configure it in **Settings -> System**.+If you use a non-standard SSH port, set the `SSH_PORT` environment variable on the Pulse server (see `docs/CONFIGURATION.md`). There is no SSH port control in **Settings -> System**.### Containerized Pulsediff --git a/frontend-modern/public/docs/TROUBLESHOOTING.md b/frontend-modern/public/docs/TROUBLESHOOTING.mdindex 1ab6df91f3..1cf9be27ac 100644--- a/frontend-modern/public/docs/TROUBLESHOOTING.md+++ b/frontend-modern/public/docs/TROUBLESHOOTING.md@@ -256,7 +256,8 @@ for the different results and evidence to retain.#### Audit Log is empty-Clear the event, user, date and success filters, and check the selected+Clear the Event, user search, Outcome and Verification filters (or use+**Clear all filters** in the empty-state message), and check the selectedorganisation first. A query error is not an empty history. **Pulse Pro runtimerequired** means an active licence is running on the public community runtime;follow the panel's **Download Pulse Pro** link rather than buying anotherdiff --git a/frontend-modern/public/docs/TRUENAS.md b/frontend-modern/public/docs/TRUENAS.mdindex 42b718a448..8bd672a1e0 100644--- a/frontend-modern/public/docs/TRUENAS.md+++ b/frontend-modern/public/docs/TRUENAS.md@@ -6,10 +6,10 @@ Pulse v6 includes first-class monitoring for **TrueNAS SCALE** and **TrueNAS COR1. Go to **Settings → Infrastructure**.2. Click **Add infrastructure** and choose **TrueNAS**. Existing connections- are listed under **Platform connections**.+ are listed under **Connected systems**.3. Enter the TrueNAS URL (e.g., `https://truenas.local`), the API key, and theusername that owns the key.-4. Click **Test Connection**, then **Save**. The test reads system information+4. Click **Test connection**, then **Add connection**. The test reads system informationon a separate connection; it does not validate inventory or metric collection.5. Leave the saved connection enabled and allow at least one configured pollinginterval (60 seconds by default). Check that the appliance and expected@@ -79,9 +79,9 @@ only its colour. Heat, native SMART faults and stale or missing readings areseparate evidence. A cool disk can still have a SMART fault; a retained **lastknown** temperature is not a current reading, and no temperature is not zero.-Check the saved rule in **Alerts → Thresholds → TrueNAS → TrueNAS Disks**:+Check the saved rule in **Alerts → Thresholds → TrueNAS → Disks**:-- A disk's own temperature override takes precedence over the **TrueNAS Disks**+- A disk's own temperature override takes precedence over the **Disks**default. With neither set, it inherits **Disk temperature by type**.- The inherited type policy is off when the agent **Disk Temp** default is off;an explicit TrueNAS temperature rule can still enable it for TrueNAS disks.@@ -137,7 +137,7 @@ All endpoints require admin authentication.### Testing and adding a connection (API)-Prefer **Settings → Infrastructure → Platform connections** for setup. These+Prefer **Settings → Infrastructure** (**Add infrastructure**) for setup. TheseAPI examples are for an authorised administrator using curl 7.76 or later,not a way to diagnose stale polling. Testing makes a live system-informationrequest to TrueNAS; saving creates a connection and starts ordinary polling.@@ -233,7 +233,7 @@ Only after reviewing the test response, create the connection once:A successful save returns HTTP **201** and the new connection's `id`, notproof of a complete poll. If saving times out or loses its response, it may-already have created the connection. Check **Platform connections** or+already have created the connection. Check **Connected systems** or`/api/truenas/connections` in your existing signed-in Pulse browser beforetrying again; do not blindly repeat POST and create duplicates. Continue withthe [ordinary polling checks](#stale-truenas-data) for collection acceptance.diff --git a/frontend-modern/public/docs/UNIFIED_AGENT.md b/frontend-modern/public/docs/UNIFIED_AGENT.mdindex b7eb55ca73..dcc0457ba0 100644--- a/frontend-modern/public/docs/UNIFIED_AGENT.md+++ b/frontend-modern/public/docs/UNIFIED_AGENT.md@@ -516,14 +516,14 @@ sudo chmod 0700 /usr/local/libexec/pulse-queue-depth| Flag | Env Var | Description | Default ||------|---------|-------------|---------|| `--url` | `PULSE_URL` | Pulse server URL | `http://localhost:7655` |-| `--token` | `PULSE_TOKEN` | API token | *(required)* |+| `--token` | `PULSE_TOKEN` | API token. Required when enrolling (`--enroll`); otherwise the `token` file in the state directory is used when unset | *(none)* || `--observers-file` | `PULSE_OBSERVERS_FILE` | Private JSON file defining report-only destinations | *(none)* || `--custom-sensors-file` | `PULSE_CUSTOM_SENSORS_FILE` | Private YAML file defining command/REST custom metrics and thresholds | *(none)* || `--token-file` | - | Read API token from file | *(unset)* || `--interval` | `PULSE_INTERVAL` | Reporting interval | `30s` || `--enable-host` | `PULSE_ENABLE_HOST` | Enable host metrics | `true` || `--enable-docker` | `PULSE_ENABLE_DOCKER` | Enable Docker / Podman metrics | `false` (auto-detect if not configured) |-| `--docker-runtime` | `PULSE_DOCKER_RUNTIME` | Force Docker / Podman runtime: `auto`, `docker`, or `podman` | `auto` |+| `--docker-runtime` | `PULSE_DOCKER_RUNTIME` | Preferred Docker / Podman runtime: `auto`, `docker`, or `podman`. `docker` only uses an endpoint that reports Docker. `podman` is tried first, but if no Podman socket answers the agent falls back to a Docker endpoint and reports it as `docker` | `auto` || `--enable-kubernetes` | `PULSE_ENABLE_KUBERNETES` | Enable Kubernetes metrics | `false` (installer auto-detect if not configured) || `--enable-proxmox` | `PULSE_ENABLE_PROXMOX` | Enable Proxmox integration | `false` || `--proxmox-type` | `PULSE_PROXMOX_TYPE` | Proxmox type: `pve` or `pbs` | *(auto-detect)* |@@ -542,7 +542,7 @@ sudo chmod 0700 /usr/local/libexec/pulse-queue-depth| `--disable-docker-update-checks` | `PULSE_DISABLE_DOCKER_UPDATE_CHECKS` | Disable Docker image update detection | `false` || `--disable-registry-credentials` | `PULSE_DISABLE_REGISTRY_CREDENTIALS` | Do not read host Docker credentials (config.json / credential helpers) for registry update checks | `false` || `--insecure` | `PULSE_INSECURE_SKIP_VERIFY` | Skip TLS verification | `false` |-| `--allow-plaintext-http` | `PULSE_AGENT_ALLOW_PLAINTEXT_HTTP` | Allow plain HTTP to a Pulse server that does not look local (private IP, single-label, `.local`/`.lan`/`.home`/`.home.arpa`/`.internal`, or resolves to private addresses). Sends the API token in cleartext; only for networks you fully control, e.g. internal networks numbered from public IP space | `false` |+| `--allow-plaintext-http` | `PULSE_AGENT_ALLOW_PLAINTEXT_HTTP` | Allow plain HTTP to a Pulse server at an address that is not local. Local-network Pulse URLs (private IP, single-label, `.local`/`.lan`/`.home`/`.home.arpa`/`.internal`, or resolves to private addresses) already work over HTTP for the primary URL without this flag. The flag extends plain HTTP to any host, including servers numbered from public IP space. Sends the API token in cleartext; only for networks you fully control. Report-only observers still need their own `allowPlaintextHTTP` opt-in | `false` || `--hostname` | `PULSE_HOSTNAME` | Override hostname | *(OS hostname)* || `--agent-id` | `PULSE_AGENT_ID` | Unique agent identifier | *(saved ID, then machine ID)* || `--report-ip` | `PULSE_REPORT_IP` | Override reported IP (multi-NIC) | *(auto)* |@@ -555,7 +555,7 @@ Use `--health-addr :9191` only when another host must scrape thehealth/metrics endpoint over the network. Use `--health-addr ""` or`PULSE_HEALTH_ADDR=off` to disable that listener.-**Token resolution order**: `--token` → `--token-file` → `PULSE_TOKEN` → `/var/lib/pulse-agent/token`.+**Token resolution order**: `--token` → `--token-file` → `PULSE_TOKEN` → the `token` file in the state directory (`<state-dir>/token`; the default state directory is `/var/lib/pulse-agent` on Linux and macOS and `%ProgramData%\Pulse` on Windows).### Agent log level@@ -651,14 +651,14 @@ Auto-detection behavior:- **Host metrics**: Enabled by default.- **Docker/Podman**: Enabled automatically by the agent if Docker/Podman is detected and `PULSE_ENABLE_DOCKER` was not explicitly set. A local `--enable-docker=false` or `PULSE_ENABLE_DOCKER=false` is a hard opt-out and is not re-enabled by auto-detection or remote profile config.-- **Kubernetes**: Enabled automatically by the installer when a kubeconfig is detected and `PULSE_ENABLE_KUBERNETES` was not explicitly set.+- **Kubernetes**: Enabled automatically by the installer when a kubeconfig is detected and none of `--enable-kubernetes`, `--disable-kubernetes` or `--kubeconfig` was passed. The Linux/macOS installer (`install.sh`) does not read `PULSE_ENABLE_KUBERNETES` from the environment; pass `--disable-kubernetes` to opt out at install time.- **Proxmox**: Enabled automatically by the installer when Proxmox is detected. Type auto-detects `pve` vs `pbs` if not specified.To disable auto-detection, explicitly set the relevant flags or env vars, for example:- `--enable-docker=false` or `PULSE_ENABLE_DOCKER=false`-- `--enable-kubernetes=false` or `PULSE_ENABLE_KUBERNETES=false`-- `--enable-proxmox=false` or `PULSE_ENABLE_PROXMOX=false`+- `--enable-kubernetes=false` or `PULSE_ENABLE_KUBERNETES=false` (the Linux/macOS installer honours only the flag at install time)+- `--enable-proxmox=false` or `PULSE_ENABLE_PROXMOX=false` for the agent binary and `install.ps1`. `install.sh` ignores the environment variable; pass `--enable-proxmox=false` or `--disable-proxmox` to it instead.### Inside-Guest Runtime Boundaries@@ -668,10 +668,14 @@ and task inventory on the Docker page.Pulse does not use a Proxmox node agent to look inside LXCs by default. Thenode agent does automatically collect filesystem capacity for running LXCs-when the local `pct` tool is available. It uses bounded `pct list` and-`pct df <vmid>` calls and reports only mount keys, volume labels, mount paths,-and capacity/usage values; it does not run commands inside a guest or read-guest files. Stopped LXCs retain the normal API-derived disk view.+when the local `pct` tool is available. On cgroup v2 PVE hosts it finds running+guests from the node's container configs and cgroup state and measures mount+capacity with statfs through each guest's init process in `/proc`; it falls back+to bounded `pct list` and `pct df <vmid>` calls when that discovery or a+per-container probe cannot establish a guest's state. It reports only mount+keys, volume labels, mount paths, and capacity/usage values; it does not run+commands inside a guest or read guest files. Stopped LXCs retain the normal+API-derived disk view.The optional Proxmox-side LXC Docker hint is off unless the Pulse server is startedwith `PULSE_ENABLE_PROXMOX_GUEST_DOCKER_DETECTION=true`. That hint uses@@ -839,17 +843,21 @@ Use HTTPS or a trusted local network for that legacy migration. Forhigh-assurance environments, install the v6 `pulse-agent` through the signedinstaller path instead of relying on a plain-HTTP first hop.-To disable auto-updates:-```bash-# After private-file preparation and successful installer inspection-bash "$HOME/.config/pulse/agent-install.sh" \- --url https://pulse.example.com \- --token-file "$HOME/.config/pulse/agent-token" --disable-auto-update+To disable auto-updates, set `PULSE_DISABLE_AUTO_UPDATE=true` (or pass+`--disable-auto-update`) on the `pulse-agent` process itself. The agent+installer (`agent-install.sh`) does not accept `--disable-auto-update`, and+setting the variable in the shell that runs the installer does not reach the+installed service. For an agent installed as a Linux systemd service, add a+drop-in with `sudo systemctl edit pulse-agent`:-# Or set environment variable-PULSE_DISABLE_AUTO_UPDATE=true+```ini+[Service]+Environment="PULSE_DISABLE_AUTO_UPDATE=true"```+Then apply it with `sudo systemctl daemon-reload` and+`sudo systemctl restart pulse-agent`.+## Remote Configuration (Agent Profiles, Pro/legacy Pro+/Cloud)Pro, legacy Pro+, and Cloud can push centralized settings to agents via Agent Profiles.@@ -955,7 +963,7 @@ Use the unified installer (`install.sh`) for all new and existing deployments.## Health Checks & Metrics-The agent exposes HTTP endpoints for health checks and Prometheus metrics on port 9191 by default.+The agent exposes HTTP endpoints for health checks and Prometheus metrics on `127.0.0.1:9191` by default (loopback only; see `--health-addr` in the configuration table).### Endpoints@@ -974,6 +982,8 @@ The agent exposes HTTP endpoints for health checks and Prometheus metrics on por### Kubernetes Probes+The default listener binds to `127.0.0.1`, which kubelet probes cannot reach because they connect to the pod IP. Set `PULSE_HEALTH_ADDR=:9191` (or `--health-addr :9191`) on the agent container before using these probes. That exposes `/healthz`, `/readyz` and `/metrics` on all pod interfaces, so restrict access with a NetworkPolicy.+```yamllivenessProbe:httpGet:diff --git a/frontend-modern/public/docs/UNIFIED_RESOURCES.md b/frontend-modern/public/docs/UNIFIED_RESOURCES.mdindex 797f861368..2efd6a3b1c 100644--- a/frontend-modern/public/docs/UNIFIED_RESOURCES.md+++ b/frontend-modern/public/docs/UNIFIED_RESOURCES.md@@ -23,9 +23,9 @@ Every monitored entity is a `Resource` with:|---|---|| `id` | Globally unique identifier || `name` | Display name |-| `type` | `host`, `vm`, `container`, `storage`, `pool`, `dataset`, `disk`, `service`, `cluster`, `pod`, `deployment` |-| `status` | `online`, `warning`, `critical`, `offline`, `unknown` |-| `sources` | Array of contributing data sources (e.g., `["pve", "agent"]`) |+| `type` | `agent` (Proxmox node, host agent or other host-class parent; `docker-host` when it carries only Docker data), `vm`, `system-container`, `app-container`, `docker-service`, `storage`, `ceph`, `physical_disk`, `pbs`, `pmg`, `network-share`, `network-endpoint`, `pod`, `k8s-cluster`, `k8s-node`, `k8s-deployment`, plus further `docker-*` and `k8s-*` types |+| `status` | `online`, `warning`, `offline`, `unknown` (critical severity is reported separately as `critical` in the `health` object's verdict) |+| `sources` | Array of contributing data sources (e.g., `["proxmox", "agent"]`) || `sourceStatus` | Per-source health status || `metrics` | CPU, memory, disk, network (when available) || Platform extensions | `.kubernetes`, `.truenas`, `.docker`, etc. |@@ -35,9 +35,9 @@ Every monitored entity is a `Resource` with:A single resource can be reported by **multiple sources**. For example, a Proxmox node might have data from both the PVE API and a host agent:```-sources: ["pve", "agent"]+sources: ["proxmox", "agent"]sourceStatus:- pve: { status: "online", lastSeen: "..." }+ proxmox: { status: "online", lastSeen: "..." }agent: { status: "online", lastSeen: "..." }```@@ -47,7 +47,7 @@ The aggregate `status` is computed from all contributing sources.| Source | What it feeds ||---|---|-| `pve` | Proxmox VE API — nodes, VMs, containers, storage |+| `proxmox` | Proxmox VE API — nodes, VMs, containers, storage || `pbs` | Proxmox Backup Server — datastores, backups, sync jobs || `pmg` | Proxmox Mail Gateway — mail stats, cluster health || `agent` | Unified agent — host metrics, temperatures, S.M.A.R.T. |@@ -57,32 +57,21 @@ The aggregate `status` is computed from all contributing sources.## Unified Navigation-The v6 UI organises pages by **task** instead of **platform**:+The v6 UI keeps platform-shaped top-level navigation. The unified resource model sits behind it, but there are no separate Dashboard, Workloads, Storage or Recovery pages.| Page | What it shows ||---|---|-| **Dashboard** | Overview panels aggregating all sources |-| **Infrastructure** | All hosts: Proxmox nodes, Docker hosts, K8s nodes, TrueNAS systems, agent-only hosts |-| **Workloads** | All workloads: VMs, LXC containers, Docker containers, Kubernetes pods |-| **Storage** | All storage: Proxmox storage, PBS datastores, ZFS pools/datasets, Ceph |-| **Recovery** | All backup/snapshot artifacts: PBS backups, PVE local dumps, ZFS snapshots, replication |-| **Alerts** | Unified alert view across all platforms |+| **Proxmox**, **Docker**, **Kubernetes**, **TrueNAS**, **vSphere**, **Machines** | One page per platform, shown only when Pulse has resources for that platform |+| **Alerts** | Alerts across all platforms |+| **Patrol** | Patrol checks, shown only when AI is enabled |+| **Actions** | Approvals, ready work and recorded outcomes |+| **Settings** | Pulse configuration, shown only to users with settings access |-Every page supports **source filtering** — click a source badge to see only resources from that platform.+`/infrastructure` is not a page of its own. It redirects to the first available platform page, or to Settings (or Alerts when the user has no settings access) when no platform has resources.-### Legacy Route Compatibility+### Unified Routes-Legacy URLs redirect automatically with toast notifications:--| Legacy Route | Redirects To |-|---|---|-| `/proxmox/overview` | `/infrastructure` |-| `/hosts` | `/infrastructure?source=agent` |-| `/docker` | `/workloads?source=docker` |-| `/kubernetes` | `/infrastructure?source=kubernetes` |-| `/services`, `/mail` | `/infrastructure?source=pmg` |--See [Migration Guide](MIGRATION_UNIFIED_NAV.md) for the full mapping.+The unified `/workloads`, `/storage` and `/recovery` routes that briefly shipped in earlier release candidates were reverted in `v6.0.0-rc.6` and do not exist. See [Migration Guide](MIGRATION_UNIFIED_NAV.md) for the platform-shaped equivalents.## API@@ -96,10 +85,11 @@ Returns all unified resources. Supports query parameters:| Parameter | Description ||---|---|-| `type` | Filter by resource type (`host`, `vm`, `container`, etc.) |-| `source` | Filter by data source (`pve`, `docker`, `kubernetes`, etc.) |-| `status` | Filter by status (`online`, `warning`, `critical`, `offline`) |-| `search` | Full-text search across name, ID, tags |+| `type` | Filter by resource type, comma-separated (`agent`, `vm`, `system-container`, `app-container`, `storage`, `pod`, etc.). Unknown tokens return HTTP 400. |+| `source` | Filter by data source (`proxmox`, `docker`, `kubernetes`, etc.) |+| `status` | Filter by status (`online`, `warning`, `offline`, `unknown`) |+| `q` | Case-insensitive substring match on resource name |+| `tags` | Filter by resource tag |### Resource Details@@ -109,13 +99,9 @@ Individual resource details are available via the unified state WebSocket connecThe frontend uses SolidJS reactive selectors to derive views from the unified store:-- `useResources()` — access the full unified resource list-- `useInfrastructureResources()` — hosts filtered for the Infrastructure page-- `useWorkloadResources()` — VMs/containers/pods for the Workloads page-- `useStorageResources()` — storage pools/datasets for the Storage page-- `useRecoveryResources()` — backup/snapshot data for the Recovery page+- `useResources()` — access the full unified resource list, plus derived views such as `infra()` (nodes, agents, docker-hosts), `workloads()` (VMs, containers, docker-containers), `byType()`, `filtered()` and `children()`-These selectors read from a single SolidJS store that is updated in real-time via WebSocket.+The hook hydrates from the WebSocket state when available and falls back to the REST API.## See Alsodiff --git a/frontend-modern/public/docs/WEBHOOKS.md b/frontend-modern/public/docs/WEBHOOKS.mdindex eca89a612a..0356b8e132 100644--- a/frontend-modern/public/docs/WEBHOOKS.md+++ b/frontend-modern/public/docs/WEBHOOKS.md@@ -86,7 +86,7 @@ These fields and behaviors are stable; ticket-routing integrations can rely on t**Events.** `{{.Event}}` is `"alert"` or `"resolved"` — there is no separate"info" event class. A resolved event closes an alert occurrence, not necessarilya recovered condition; see [non-recovery closes](#resolved-does-not-always-mean-recovered).-Resolved delivery depends on **Notify on resolve** and a+Resolved delivery depends on **Recovery notifications** (Alerts → Schedule, set to Enabled) and asuccessful firing-delivery receipt for that occurrence and destination. Do notassume that every configured webhook receives both events.@@ -297,7 +297,7 @@ Keep ticket correlation separate from suppressing repeated processing:fractional seconds as below. Do not assume the shorter string is universallyunique. A test or legacy payload can lack member identity; keep incomplete orambiguous events for reconciliation rather than silently treating them as- duplicates. **Send test** alone does not validate this lifecycle.+ duplicates. **Test** alone does not validate this lifecycle.- Commit receiver state and the ticket action atomically, or use your ticketsystem's durable idempotent operation. Do not mark an event processed beforeits action succeeds. Exact signed-byte replays can be rejected separately,@@ -591,7 +591,8 @@ To acknowledge or clear from the PSA side, use a `monitoring:write` token: `POST| Action | Endpoint | Scope ||--------|----------|-------|-| Create / update / delete per-org webhook | `POST` / `PUT` / `DELETE /api/notifications/webhooks` | `settings:write` (admin) |+| Create per-org webhook | `POST /api/notifications/webhooks` | `settings:write` (admin) |+| Update / delete per-org webhook | `PUT` / `DELETE /api/notifications/webhooks/<id>` | `settings:write` (admin) || List per-org webhooks | `GET /api/notifications/webhooks` | `settings:read` (admin) || Read active / historical alerts | `GET /api/alerts/active`, `GET /api/alerts/history` | `monitoring:read` || Acknowledge / clear alerts | `POST /api/alerts/acknowledge`, `POST /api/alerts/clear` | `monitoring:write` |diff --git a/frontend-modern/public/docs/ZFS_MONITORING.md b/frontend-modern/public/docs/ZFS_MONITORING.mdindex 31ba953f9f..208cfa440c 100644--- a/frontend-modern/public/docs/ZFS_MONITORING.md+++ b/frontend-modern/public/docs/ZFS_MONITORING.md@@ -27,7 +27,8 @@ it appear in Pulse. For a pool you intentionally keep unregistered:* A **Unified Agent on the Proxmox host**, with a locally mounted ZFS datasetand access to `zpool`, can report capacity and usage in the node's- **Overview details → Disks** panel, under the selected mount point. Without+ **Overview** tab, in the **Storage** section of the technical details, which+ lists each mount point once the agent reports two or more. Withoutusable `zpool` output, the agent falls back to mounted-dataset counters;those are not necessarily whole-pool capacity.* That capacity view and physical-disk SMART data do **not** providediff --git a/scripts/release_control/ai_runtime_docs_policy_test.py b/scripts/release_control/ai_runtime_docs_policy_test.pyindex 836cf747c3..0e6e4d2946 100644--- a/scripts/release_control/ai_runtime_docs_policy_test.py+++ b/scripts/release_control/ai_runtime_docs_policy_test.py@@ -232,8 +232,8 @@ class AIRuntimeDocsPolicyTest(unittest.TestCase):control_doc = read_repo_text("docs/AI_AUTONOMY.md")normalized_control = " ".join(control_doc.split())- self.assertIn("| `MaxEvidenceCalls` | 15 |", overview)- self.assertIn("| `MaxTurns` | 17 |", overview)+ self.assertIn("| `MaxEvidenceCalls` | 10 |", overview)+ self.assertIn("| `MaxTurns` | 12 |", overview)self.assertIn("terminal typed proposal is reserved separately", overview)self.assertIn("Maximum evidence-tool calls per investigation", normalized_control)self.assertIn("separate model-response safety ceiling", normalized_control)@@ -286,9 +286,9 @@ class AIRuntimeDocsPolicyTest(unittest.TestCase):self.assertIn("## Patrol Modes", overview)self.assertIn("four modes", overview)self.assertIn("**Watch only**", overview)- self.assertIn("**Ask before changes**", overview)- self.assertIn("**Auto-fix safe issues**", overview)- self.assertIn("**Policy autopilot**", overview)+ self.assertIn("**Ask first**", overview)+ self.assertIn("**Safe auto-fix**", overview)+ self.assertIn("**Autopilot**", overview)self.assertIn("When a finding is created in a Pro Patrol mode", overview)self.assertIn("**Patrol modes (Pro and above)**", overview)self.assertIn("**Governed fixes (Pro and above)**", overview)diff --git a/scripts/release_control/documentation_currentness_test.py b/scripts/release_control/documentation_currentness_test.pyindex 6b9a903253..61ecf2cd51 100644--- a/scripts/release_control/documentation_currentness_test.py+++ b/scripts/release_control/documentation_currentness_test.py@@ -131,7 +131,7 @@ class DocumentationCurrentnessTest(unittest.TestCase):pulse_pro_doc = read("docs/PULSE_PRO.md")self.assertIn(- "| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |",+ "| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |",ai_doc,)self.assertIn(@@ -148,11 +148,11 @@ class DocumentationCurrentnessTest(unittest.TestCase):)self.assertNotIn("Upgrade to Assisted", autonomy_doc)self.assertIn(- "| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |",+ "| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Pro / hosted Cloud |",pulse_pro_doc,)self.assertNotIn(- "| **Ask before changes** | Investigates findings and proposes fixes. All fixes require approval before execution. | Community / Relay |",+ "| **Ask first** | Investigates findings and proposes fixes. All fixes require approval before execution. | Community / Relay |",pulse_pro_doc,)for rel in ("docs/AI.md", "docs/PULSE_PRO.md", "docs/FAQ.md", "docs/README.md"):diff --git a/scripts/tests/test_agent_docs.py b/scripts/tests/test_agent_docs.pyindex db318ac5b4..47fd870a8e 100644--- a/scripts/tests/test_agent_docs.py+++ b/scripts/tests/test_agent_docs.py@@ -83,7 +83,7 @@ class AgentDocsTest(unittest.TestCase):count += 1# Include the separate runner-only removal command, not just the# collector uninstall and the existing setup/cleanup recipes.- self.assertEqual(count, 18)+ self.assertEqual(count, 17)def test_private_file_preparation_preserves_existing_token(self):command = recipe(NAMES[0], 'credential_file="$config_dir/agent-token"')@@ -321,7 +321,7 @@ Path(os.environ['HOME'], '.config/pulse/agent-install.sh').write_text('other savprofiles = []for name in NAMES:profiles.extend(block for block in blocks(name) if 'bash "$HOME/.config/pulse/agent-install.sh"' in block and "--token-file" in block)- self.assertEqual(len(profiles), 11)+ self.assertEqual(len(profiles), 10)fixture = '''#!/bin/bashpython3 - "$@" <<'PY'import json, os, stat, sys@@ -364,7 +364,7 @@ PY["--enable-proxmox", "--proxmox-type", "pbs"],["--enable-docker"], ["--enable-docker=false"],["--enable-kubernetes"], ["--enable-host=false", "--enable-docker"],- ["--disable-auto-update"], ["--enable-proxmox"]]+ ["--enable-proxmox"]]actual_profiles = [re.findall(r"--(?:enable-[a-z]+(?:=false)?|disable-auto-update|proxmox-type\s+(?:pve|pbs))", p) for p in profiles]for expected in expected_profiles:# Compare the actual argv tokens, retaining the type's value.diff --git a/scripts/tests/test_agent_profile_docs.py b/scripts/tests/test_agent_profile_docs.pyindex d8a3ee3a54..f088de4b1c 100644--- a/scripts/tests/test_agent_profile_docs.py+++ b/scripts/tests/test_agent_profile_docs.py@@ -53,7 +53,7 @@ class AgentProfileDocsTest(unittest.TestCase):for key in keys:with self.subTest(key=key):self.assertIn(f'case "{key}":', startup)- self.assertIn("JSON numbers are interpreted as seconds", self.guide)+ self.assertIn("must be a positive duration string", self.guide)def test_host_metrics_do_not_grant_command_authority(self):row = next(line for line in self.central.splitlines() if line.startswith("| `enable_host`"))@@ -136,7 +136,7 @@ class AgentProfileDocsTest(unittest.TestCase):"automatic retries", "Never paste a token or session cookie","Copy as cURL", "not full responses", "manually redacted excerpt","may call the configured AI provider", "not a read-only diagnostic",- "not an empty profile list", "GET and POST only, not PUT or DELETE"):+ "not an empty profile list", "accepts GET, POST, PUT and DELETE"):self.assertIn(phrase, self.guide)diff --git a/scripts/tests/test_truenas_docs.py b/scripts/tests/test_truenas_docs.pyindex 2b36f69b77..49a899a9db 100644--- a/scripts/tests/test_truenas_docs.py+++ b/scripts/tests/test_truenas_docs.py@@ -85,7 +85,7 @@ class TrueNASDocsTest(unittest.TestCase):for boundary in ("Heat, native SMART faults and stale or missing readings are separate evidence","last known** temperature is not a current reading", "no temperature is not zero",- "Alerts → Thresholds → TrueNAS → TrueNAS Disks", "own temperature override",+ "Alerts → Thresholds → TrueNAS → Disks", "own temperature override","takes precedence", "inherits **Disk temperature by type**","agent **Disk Temp** default is off", "explicit TrueNAS temperature rule","Thresholds are in **°C**", "**Save Changes**", "unsaved edit is not the running rule",