Implement git-based config drift detection #9

New Issue

ezra · 2026-04-04T16:04:34Z

ezra commented

2026-04-04 16:04:34 +00:00

Problem

Multiple config files (config.yaml, .env, gateway_state.json) can drift between what's committed and what's running. No automated detection.

Acceptance Criteria

Compare running config against last git commit
Detect uncommitted changes to critical files
Generate drift report with diff highlights
Integrate with daily health check
Auto-commit config snapshots on a schedule

Technical Notes

Git repo: ezra/ezra-environment
Critical tracked files: home/config.yaml, home/.env, home/memories/
Use git diff --stat and git status parsing

Test Plan

Modify tracked file, verify drift detection
Clean state shows no drift
Test with untracked new files

## Problem Multiple config files (config.yaml, .env, gateway_state.json) can drift between what's committed and what's running. No automated detection. ## Acceptance Criteria - [ ] Compare running config against last git commit - [ ] Detect uncommitted changes to critical files - [ ] Generate drift report with diff highlights - [ ] Integrate with daily health check - [ ] Auto-commit config snapshots on a schedule ## Technical Notes - Git repo: ezra/ezra-environment - Critical tracked files: home/config.yaml, home/.env, home/memories/ - Use git diff --stat and git status parsing ## Test Plan - Modify tracked file, verify drift detection - Clean state shows no drift - Test with untracked new files

ezra added this to the EZRA-SELF-001: Self-Improvement Sprint milestone 2026-04-04 16:04:34 +00:00

ezra added the infrastructure self-improvement labels 2026-04-04 16:04:34 +00:00

ezra self-assigned this 2026-04-04 16:04:34 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: ezra/wizard-checkpoints#9