mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-25 04:59:43 +00:00
rcourtman
92abdcd9ad
buildPatrolSettingsReadinessFailure built a full
PatrolConfigurationFailureInput (code, status, saved, details, mode,
budget, readiness, runtime and blocked state) for the Patrol page's inline
"needs attention" state. That state lost its render in 27ba85ddc6
(2026-06-23), when the Configure Patrol popover was removed. Since then the
only production caller, the Patrol on/off toggle, has read just `.message`
for a warning toast, and it always passed the fixed copy "Patrol setting
was saved, but Patrol is not ready to run." getPatrolSavedReadinessWarning
now returns that message when the saved response reports
patrol_readiness not_ready. The PatrolConfigurationFailureInput type goes
with it, because its other consumers were already removed.
Runtime: production builds before and after differ in one chunk,
AIIntelligence.js (the Patrol page), which is 935 bytes smaller. After
normalising chunk hashes, SRI strings and minified identifiers, the only
change is the removed builder and details helper, replaced by one status
check. The toast string is byte-identical. The minifier had already
folded `message || readiness.summary || default` to the caller's
constant, so the readiness-summary fallback was unreachable. The toggle
no longer reads seven Patrol signals to build the discarded object. The
bundle-size check passes. The same Playwright script ran against both
builds at 1440 and 390 px and gave identical results. It covered the
toggle off and on with a not-ready response, a failed and a successful
Patrol mode save, and Settings > Patrol and Provider & Models saves with
a not-ready response. Each shows only a toast, with no inline alert or
Assistant action.
Tests: the hook's unit tests now cover the warning helper. The #1789
test pinned `blockedCause: patrolStatus()?.blocked_cause`, which matched
only the removed dead field and not the blockedCause memo the test was
written for, so it now pins the memo. frontendResourceTypeBoundaries pins
the new helper name.
Contracts: patrol-intelligence, frontend-primitives and api-contracts
still described the retired Patrol schedule and model popover, its inline
dialog failure state, and a saved-configuration-issue surface with cause
metadata. They now say where Patrol settings live (Settings > Pulse
Intelligence > Patrol and Settings > Provider & Models), that every save
outcome is a toast, and that the Patrol page's readiness banner carries
the not-ready diagnosis. The popover rules apply only if a popover
returns.
The Assistant drawer's restore path for saved
patrol_configuration_failure sessions is unchanged.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.