drift-check

Run a read-only drift check to detect git branch drift and cron staleness across frameworks. It compares harness state, prints DRIFT-CHECK findings with recommended remediation commands, and performs only a non-destructive git fetch without executing fixes.

Harness drift is the divergence of state across framework branches, origin and upstream repositories, append-files, and cron schedules. A drift check identifies these three drift classes and reports findings without altering local state.

No, the drift check never auto-remediates issues. It operates read-only and only performs a non-destructive git fetch to update remote-tracking refs, printing a recommended command for each finding without executing it.

Run a drift check before critical commits, after long periods of inactivity, or when memory and log files change unexpectedly. It serves as a kick-off gate to surface framework, branch, and cron staleness issues.

Yes, you can monitor MEMORY.md or log.md files for drift indicators. The drift check reads these files to detect unexpected changes and reports branch-behind, append-file, and cron-staleness drift.