compound-refresh

Solution documentation staleness is detected by walking docs/solutions/**/*.md files, verifying referenced code paths exist, checking for moved paths, and flagging invalid references during scheduled maintenance or post-refactor audits.

Markdown documentation duplication and consolidation candidates are identified by reading frontmatter and body content, computing age-versus-severity heuristics, and classifying each file into Keep, Update, Consolidate, Replace, or Delete outcomes.

Report-only mode generates a classification table of docs/solutions files without modifying anything, allowing you to review Keep, Update, Consolidate, Replace, and Delete recommendations before staging changes.

Automated documentation maintenance enforces commit and worktree safety rules before applying changes, stages only touched docs and the run artifact, and supports interactive, autofix, and report-only modes to control application.

A solution docs audit should be run post-refactor to detect identifier drift, missing referenced code, and moved file paths, ensuring documentation accuracy and reducing retrieval noise and onboarding friction.

Solution documentation maintenance avoids external model invocation entirely, relying on file existence probes, identifier checks, and age-versus-severity heuristics to classify files and produce corrective action recommendations.