mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
a9f23501eb
Stacked on #2695 (branch contains its head32fad38aa4). Once #2695 merges, this PR's diff is the single commit776c2774ba. ## What `resolvePatrolAutonomyLevelForSave` and `resolvePatrolAutonomySettingsForSave` in `features/patrol/usePatrolIntelligenceState.ts` had no production caller. Only their own unit tests imported them. Patrol mode saves go through `handleAutonomyChange` and `acknowledgeAndActivateAutopilot`, whose payload type `PatrolAutonomyUpdate` has no `full_mode_unlocked` field, and both reconcile from `GET /api/ai/patrol/autonomy`. This PR deletes both helpers and their tests. Contract prose in patrol-intelligence, api-contracts, frontend-primitives and ai-runtime described the helpers' model rather than the live path: the browser clearing stale full-mode unlock state before a monitor-only save, sending `full_mode_unlocked:false` when locked, and sending `full_mode_unlocked:true` for Autopilot. The API does that work. `HandleUpdatePatrolAutonomyMonitorOnly` and the paid handler's `SaveAutonomySettings` adapter clear the unlock and Autopilot activation on every save below Autopilot, and `GatePatrolAutonomyUpdate` derives the compatibility flag from a recorded acknowledgement. The prose now says what the header, the state owner and the API each do. Three neighbouring api-contracts sentences about the same save were also corrected: - a `full` request without a current acknowledgement is refused by the gate before any licence check; - the "Patrol mode dialog" (removed in27ba85ddc6) is now the header's `Mode and automation` disclosure, with the same wording as #2691; - the lock is checked "when a save starts", not "never submits", because the Autopilot flow checks it only at entry. The deleted helper tests are replaced by tests of the live locked path. A page test loads stale paid state (Safe auto-fix plus the compatibility unlock) under a runtime lock. It checks that Watch only is presented, that the paid choices are disabled and save nothing, and that Watch only sends exactly `autonomy_level`, `investigation_budget` and `investigation_timeout_sec`. A source pin keeps the state owner's own lock guards. ## Verification - Production build: parent and this change produce byte-identical dists (187 files), because Rollup had already dropped both helpers. - Browser pass on pulse-dev, before and after, one DEMO_MODE stack at a time, 1440x900 and 390x844. Covered paid saves (Ask first, Watch only, Autopilot through the acknowledgement dialog) and the runtime lock with and without the demo presentation override. 6 sessions and 80 recorded fields, with 0 differences between before and after. No PUT ever carried `full_mode_unlocked`. Receipt `frontend-modern/browser-verification/994121d9684bd9f0.json`. - `tsc --noEmit` and the Patrol hook, page, header, workspace, commercial-boundary and resource-boundary suites pass (84 tests). - Negative controls, each failing the intended test: - header showing the stale paid mode while locked; - payload carrying `full_mode_unlocked`; - hook lock guard removed; - paid choices enabled while locked.
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.