ce:compound-refresh

To refresh stale pattern docs, you can automate the alignment of learnings under docs/solutions with the current codebase. This process audits drift, applies evidence-backed actions like update, consolidate, replace, or delete, and generates a two-part report.

Auditing documentation drift is handled by scanning existing learnings against the live codebase to identify stale references. The automation produces a comprehensive report detailing recommended actions and applied updates to keep docs aligned with reality.

Consolidating outdated learnings involves reviewing derived pattern docs against the current codebase and executing evidence-backed replace or consolidate actions. Uncertain items are marked as stale, ensuring valid information is preserved while drift is corrected.

Yes, you can run an automated documentation sweep across both interactive and autofix flows. When you ask to refresh, audit, sweep, or consolidate drift, the process applies updates and generates a report detailing actions taken or advised.

You should avoid automated refresh when your learnings lack sufficient codebase evidence to verify accuracy. The process marks uncertain items as stale rather than deleting them, requiring manual review before final consolidation or replacement.