ce-compound-refresh

Documentation drift is detected by auditing existing learnings and pattern docs against the current codebase state to identify inconsistencies and outdated guidance.

Yes, you can automate refreshing outdated documentation under docs/solutions by running the audit in headless mode to refresh or consolidate drifted learnings without manual intervention.

The best way to consolidate outdated pattern docs is to audit the documented learnings against the live repository state, applying updates or removing obsolete guidance while validating parser-safety.

Yes, the documentation refresh workflow supports interactive mode, allowing you to manually review ambiguous drift cases where the system otherwise marks them as stale in the final report.

Parser-safety is validated by reading the updated learnings and pattern docs, then checking the canonical artifacts for syntax compliance before finalizing the consolidation changes.

The documentation audit report separates Applied and Recommended sections to distinguish actions already executed to fix drift from suggested actions that require further manual review.