mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
421d1e5423
The Patrol summary card was deleted in 27ba85ddc6 (2026-06-23), but most
of the presenters in utils/patrolSummaryPresentation.ts stayed exported.
A TypeScript import graph rooted at src/index.tsx (static and dynamic
imports, re-exports) shows reachable code imports only two of them:
getPatrolRecencyPresentation for the header recency line and
getPatrolVerificationPresentation for the findings empty state. Apart
from two positive pins removed here, ?raw and readFileSync guards
reference the rest only in negative not.toContain checks, which stay.
getPatrolAssessmentPresentation, getPatrolAssessmentShellPresentation
and getPatrolSummaryMetricState lost their last caller with the card.
getPatrolSummaryPresentation, getPatrolScoreChipLabel and
getPatrolAssessmentAction had lost theirs in May, the
PATROL_NO_ISSUES_LABEL export in March, and getPatrolNoIssuesPresentation
and getPatrolCompactAssessmentLabel never had a production caller. They
go along with their types and the private helpers that only they used,
which a noUnusedLocals check found (repeated until it reported nothing).
The same card deletion left getPatrolConfigurationFailureInlineDetails
in PatrolIntelligenceHeader.tsx formatting an inline save-failure state
the header no longer renders, so it goes too.
88 presenter test cases and 2 header cases go with them. v8 coverage
before and after, matched by function and source text, shows no
statement or branch in the surviving code losing coverage.
The JavaScript output is unchanged. Of 187 production dist files, 93
are byte-identical and 93 differ only in chunk-hash references. The CSS
drops one rule, .bg-emerald-50/60, which only the deleted assessment
shell's class string generated. The bundle-size check passes. The
header recency line and the findings empty state read the same before
and after, at desktop and phone widths.
The contracts described the removed presenters as live.
patrol-intelligence, frontend-primitives and api-contracts now say that
no shared presenter derives an assessment, shell, score chip or next
step today, and they keep those rules as conditions for any returning
surface. They also correct claims that no longer match the code:
- the recency line says "checked N resources" for any completed run
and never "verified", and labels the latest completed run of any
type "Last check";
- the findings empty state treats any coverage factor as incomplete
coverage, even after a clean full run, and the health summary picks
that empty state's title, not the workspace heading;
- a save that is not ready raises a warning toast, not an inline
"Patrol control needs attention" state.
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.