-
Notifications
You must be signed in to change notification settings - Fork 111
Sync health observability (S1) #389
Copy link
Copy link
Closed
Labels
complexity-mediumComplexity: medium (board points 5-8)Complexity: medium (board points 5-8)priority-p2ImportantImportanttheme-reliabilityTheme: ReliabilityTheme: Reliabilitytype-featureNew functionalityNew functionality
Description
Activity
Metadata
Metadata
Assignees
Labels
complexity-mediumComplexity: medium (board points 5-8)Complexity: medium (board points 5-8)priority-p2ImportantImportanttheme-reliabilityTheme: ReliabilityTheme: Reliabilitytype-featureNew functionalityNew functionality
Summary
Add sync health tracking, dashboard indicators, and auto-sync to catch silent desync before it accumulates.
Context
Problem P1: An agent can run for weeks with failing syncs while appearing "healthy" in the dashboard. No sync-health signal exposed at fleet level, and no autonomous sync cadence.
Problem P6: The ahead/behind count compares against `origin/main`, not the working branch. External writes to the working branch are invisible.
Acceptance Criteria
Database: New agent_sync_state table
Dashboard indicators
Operator queue alerts
Fix P6: Dual ahead/behind
Auto-sync (S1a)
Config flag
Technical Notes
Files to modify:
Part of Epic #381