docs(integrations): backup provider integration (Cove) — design spec + W01–W05 plans (feature #6008) - #6018
Open
ToddHebebrand wants to merge 3 commits into
Open
docs(integrations): backup provider integration (Cove) — design spec + W01–W05 plans (feature #6008)#6018ToddHebebrand wants to merge 3 commits into
ToddHebebrand wants to merge 3 commits into
Conversation
…ta Protection phase 1 Provider-neutral external backup model (connections, customers, devices, observed-daily-health ledger) with a Cove JSON-RPC adapter, a unified backup health read model feeding the /backup overview (new all-orgs mode), device tab, client portal and reports, and sourced alerts for linked devices. Advisor quorum applied (Codex xhigh): breeze_device_id link column with synchronous detach on org move, coverage requires fresh success evidence, provider events do not reach notification channels in phase 1. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… issue #6008 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…n plans (feature #6008) Five per-wave plans for the Cove Data Protection integration: W01 foundation (schema, migration, RLS, registrations, health derivation, Cove adapter, connection + mapping routes), W02 sync (BullMQ job, persistence, auto-mapping, device matching, alerts + events), W03 read model + web (backupHealthReadModel, GET /backup/health/devices, Integrations Backup tab, overview all-orgs mode, device tab card), W04 portal + reports, W05 backup status report. Plan authoring surfaced and resolved: GET /backup/health already exists (verification summary) so the device listing is /backup/health/devices; status-bucket grouping is one shared constant (six buckets incl. 'other'); SELF_MANAGED_DB_CONTEXT_ROUTES registration for routes that call the vendor; /backup/dashboard never emitted overdueDevices; the portal has no i18n system. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Deploying breeze with
|
| Latest commit: |
2596a7a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6d23a79b.breeze-9te.pages.dev |
| Branch Preview URL: | https://spec-backup-provider-integra.breeze-9te.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design spec and five implementation plans for Breeze's first third-party backup integration: N-able Cove Data Protection, phase 1 (read-only status everywhere Breeze shows its own backups). Tracked as feature #6008 (waves #6009–#6013).
docs/superpowers/specs/integrations/2026-09-15-backup-provider-integration-cove-design.mddocs/superpowers/plans/integrations/2026-09-15-backup-provider-integration.mdWhat it builds
Provider-neutral model (
backup_provider_connectionspartner-scoped,backup_provider_customerswith org mapping,backup_provider_devicesorg-scoped,backup_provider_device_historyobserved-daily ledger) behind aBackupProviderAdapterinterface with a Cove JSON-RPC adapter; a 30-minute BullMQ sync copying the Huntress split-phase shape; one sharedderiveBackupHealthand onebackupHealthReadModelfeeding the/backupoverview (new All-organizations mode with the Cove-email status/recency buckets and device table), the device Backup tab, the client portal, the posture report and the org narrative; sourced alerts for linked devices with two-poll hysteresis.Review trail
Advisor quorum (Fable + Codex xhigh) applied to the spec:
breeze_device_idlink column with synchronous detach on org move (Intune pattern), "protected" requires fresh success evidence, provider events do not reach notification channels in phase 1. Plan authoring surfaced:GET /backup/healthalready exists →/backup/health/devices; a ninth registration list (SELF_MANAGED_DB_CONTEXT_ROUTES);/backup/dashboardnever emittedoverdueDevices; the portal has no i18n.Docs-only PR: no code changes.
🤖 Generated with Claude Code