mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
77d2119792
Stacked on #2686, which sits on #2682 and #2674; its own change is the top commit,6d8dce2cae. It merges cleanly with main and with every other open PR touching these files. `usePatrolIntelligenceState()` still returned `summaryStats`, a closure counting critical, warning and active Patrol findings plus fixed outcomes. Its only reader was `PatrolIntelligenceSummary.tsx`, deleted in27ba85ddc6. A type-checker scan of the whole program (src and tests) finds no reference to the member outside the hook's return object, and nothing spreads, iterates or index-reads the returned state. - Removes the closure and its return entry. - Removes the `canonical-patrol/no-local-summary-card-presentation` audit rule. It matched only the deleted card's tint ternaries on `summaryStats()`, and it pointed authors at `patrolSummaryPresentation`, which no longer holds summary-card presentation. The three `not.toContain("summaryStats()...")` guards that pinned the same strings go too. - Takes `patrolSummaryPresentation.ts` off the audit allowlist. Its remaining presenters trip no rule, and a planted violation is now reported. - Contract notes in patrol-intelligence, api-contracts and frontend-primitives. The section-owner sentence that named the deleted summary surface now names the live tab panels and scopes the no-own-reads rule to the hook-backed surfaces. Runtime neutrality: of 187 dist files, 94 are byte-identical and 92 differ only in chunk-hash names and SRI strings. In the AIIntelligence chunk, after normalising hashes and short identifiers, the only residual is the removed closure and its return entry. The bundle-size check passes. The browser receipt covers the Patrol Inbox, Activity and Protection tabs at 1440 and 390 px. The `Contract-Neutral` trailer covers only the platform-support-manifest proof that the audit script's path policy names. This change leaves that projection check untouched.
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.