pristine-sweep-drift-accumulates-without-active-resolution
The nightly pristine-sweep cron logged the same two findings (MEMORY.md over 130 lines, CLAUDE.md over 45 lines) for 4 consecutive nights, generating stale [DRIFT] entries that cluttered session-learnings. Sweep findings must be resolved in the next available session; unresolved entries compound into false-signal noise that masks new real drift.
Related
- 2026-04-04-oracle-001-self-architecture-analysis
- self-maintaining-skill-enforcement-triad
- 4-dimension-parallel-audit-pattern-for-setup-hygiene
- brainstorm-service-systemd-deployment-with-env-isolation
- setup-curator-skill-triad-vs-passive-skill-only-approach
- react-native-web-is-wrong-pwa-stack
- dependabot-first-cycle-floods-repo-with-prs