ce:compound-refresh

To update solution documentation after a codebase refactor, you can cross-reference existing docs in the docs/solutions/ directory against the current codebase to identify and resolve drift, applying evidence-backed updates to correct outdated references and patterns.

Stale documentation drift occurs when solution docs become outdated following codebase changes like migrations or dependency upgrades. Detection involves scanning docs/solutions/ to identify outdated references, contradictory guidance, redundant content, or obsolete records by cross-referencing them with the current codebase.

Yes, you can automatically fix outdated solution docs using an autofix mode designed for hands-off updates of unambiguous drift. For ambiguous cases requiring human judgment, such as consolidation or replacement decisions, an interactive maintenance mode is also available.

You should run a documentation refresh after completing major codebase changes such as refactors, migrations, or dependency upgrades. Triggering this post-change maintenance workflow ensures solution docs accurately match the new code patterns and prevents misleading future engineering work.

The best way to consolidate redundant solution docs is using an interactive maintenance mode that cross-references existing learnings and pattern docs against the current codebase. This allows you to interactively consolidate overlapping documentation and apply evidence-backed replacements.