Fleet git-state o11y: detect and alert on unpushed, dirty, and stranded work #319
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/infrastructure#319
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Kai loses track of unpushed work routinely. 2026-06-12 alone produced four specimens: an atlas commit stranded on kai-server (1 ahead, 5 behind, existed nowhere else), the agentic-os GitHub mirror silently 5 commits stale, kai-server checkouts reporting ahead counts against a deleted origin tracking ref, and a dirty voice-flow-learning-loop tree.
Design (devex o11y, no new UI - rides the ser8 o11y pipeline):
Related: #309 push mirrors delete the forgejo-to-github staleness class entirely and should land regardless. Sequencing: needs the ser8 metrics pipeline (o11y burn-down items 2-4) as the sink.