ce-compound-refresh

Automated drift maintenance audits docs/solutions against the live codebase to detect stale learnings, then applies updates, consolidations, replacements, or deletions based on codebase evidence. It triggers via user requests to refresh, audit, sweep, or consolidate drifted content.

Consolidating drifted learning docs is handled by an evidence-based maintenance workflow that audits pattern docs against the current codebase. It detects drift and applies targeted actions like consolidation or replacement, yielding a two-section report of applied and recommended changes.

Autofix workflows are supported alongside interactive reviews for updating stale documentation patterns. Mode detection automatically identifies the requested workflow, applying evidence-backed updates, consolidations, or deletions across docs/solutions and related patterns.

The drift audit process always yields a two-section report containing both Applied and Recommended updates. This ensures you see what maintenance actions were automatically executed and what optional metadata updates or manual actions are still advised.

Sweeping and refreshing documentation after capturing a new learning is triggered by requesting a drift-maintenance pass. The workflow audits existing docs/solutions and related patterns against the codebase to ensure new learnings are accurately reflected without stale content.

You should avoid automated codebase-evidence drift maintenance when documentation updates require subjective context or external system references not present in the current codebase, as the workflow strictly enforces evidence-based decisions for all applied actions.