What problem does it solve? Project documentation drifts out of sync with code, commands, and folder structure as a Kotlin Multiplatform project evolves, leaving stale READMEs, broken links, and disorganized docs folders that mislead developers. ## Core Features & Use Cases - Docs Drift Repair: Updates README, GETTING_STARTED, INSTALL, RELEASING, and docs/reference pages so they match the actual code, commands, and module layout. - Self-Healing Automation: Ships scripts that auto-rename snake_case files to kebab-case, archive completed tasks, regenerate the docs/README.md sitemap, and sync the docs/tasks.md progress index. - Structured Docs Topology: Enforces a canonical docs/ layout with task lanes, ADR decision records, per-module READMEs, and hygiene limits validated by audit tooling. - Use Case: After renaming a Gradle module and adding a new feature, run the healing scripts to re-sync the sitemap, archive finished task notes, and update every doc that referenced the old module name. ## Quick Start Ask the agent to audit and update the project README and docs folder so they match the current modules, commands, and architecture.