ce:compound-refresh

To keep pattern docs in sync with the codebase after a refactor, you need to detect stale learnings by comparing existing documentation against the current codebase, then apply updates, consolidations, or deletions to resolve drift.

The best way to reduce documentation drift is to review related pattern docs against the live codebase, consolidate overlapping content, and remove duplicates to ensure consistency across both English and Chinese solution spaces.

Yes, you can mark ambiguous learnings as stale during docs maintenance by using an autofix mode, which also enforces frontmatter and content validity while generating a maintenance report summarizing all actions and outcomes.

You need to refresh stale pattern docs and learnings after major refactors, migrations, or dependency upgrades to ensure the documentation accurately reflects the evolved codebase and maintains consistency across languages.

Documentation maintenance enforces frontmatter and content validity by reviewing existing docs against the current codebase, identifying formatting or structural issues, and applying necessary updates to produce a valid maintenance report.