mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
843daf7ae3
Stacked on #2674 (branch `refactor/drop-patrol-context-summary`); this branch contains that commit. ## What Removes the two Patrol-to-Assistant handoff builders in `frontend-modern/src/features/patrol/patrolInvestigationContextModel.ts` that no production code calls: - `buildPatrolAssessmentAssistantHandoff`: its caller, the summary card's Discuss handler, went ineac7dfe9ef(2026-05-15). - `buildPatrolConfigurationFailureHandoff`: its last caller went in27ba85ddc6(2026-06-23). With them go `PatrolInvestigationContextSummary`, their input and output types, and the private helpers only they used. The model drops from 2,326 to 1,257 lines. ## Why it is safe - A TypeScript compiler export graph rooted at `src/index.tsx` shows no reachable importer of either builder, and `git grep` finds only their own tests. - Production builds of the parent tree and this tree are byte-identical across all 187 dist files (`shasum`). `check-bundle-size.mjs` passes. - The Assistant drawer still restores saved `patrol_assessment` and `patrol_configuration_failure` sessions. That code (`components/AI/Chat/index.tsx`, `workflowStarters.ts`, `internal/ai/chat/session.go`) is unchanged. ## Tests - The removed builders' cases are gone. - Two cases covered branches the live finding handoff still uses, so they now go through the live builders: a typed pending action stays approval-bound without a legacy approval id, and the resource node qualifier plus long-line truncation. - v8 coverage of the surviving model code matches the baseline from before the removal. The one exception is a defensive guard the live caller cannot reach. ## Contracts and docs Eight contracts changed: `patrol-intelligence`, `ai-runtime`, `api-contracts`, `frontend-primitives`, `security-privacy`, `storage-recovery`, `agent-lifecycle` and `unified-resources`. - No contract describes either handoff as a live producer any more. Statements about restoring saved sessions of those kinds stay. - Some clauses described a rendered Patrol summary card, assessment strip or readout, score chip, header trust line, or inline save-failure surface. They are now conditional or say what renders instead. - The run-history handoff clauses now say the browser sends the briefing and safe run metadata, and `internal/ai/patrol_assistant_handoff.go` rebuilds the model context from the run ID. - `docs/AI.md` and its public mirror pointed users at a legacy operational score in a collapsed supporting-context section. Neither exists any more. The section now points at **Activity > Finding options and history > History**. - `ai_runtime_docs_policy_test.py` is the registered proof for `docs/AI.md`. It now pins that location and rejects the retired claim. It also had a stale pin that has failed on main since 2789a15fe5; that pin now matches the current Patrol mode API wording. Prose about the remaining test-only summary presenters in `utils/patrolSummaryPresentation.ts` is left for a separate follow-up that removes those presenters. ## Browser verification Receipt `frontend-modern/browser-verification/6e6cbc66d62863d1.json`. Checked on an embedded production build on a private demo mock stack, at 1440x900 and 390x844: - Inbox "Explain with Assistant" opens the drawer with the Pulse Patrol attention briefing. - The run-history "Discuss" button opens the drawer with the "Patrol run attached" briefing.
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.