align-documentation

Documentation drift happens when feature merges, bug fixes, or refactors alter source code without updating AGENTS.md, API docs, and architecture docs. It occurs because impacted files are not mapped to corresponding documentation artifacts for synchronization.

You keep API docs in sync by parsing code diffs to identify modified files, mapping impacted files to relevant API documentation, and generating an update plan that validates references and maintains consistency across architecture docs.

You need to update AGENTS.md during a refactor when source code changes alter architecture or interface contracts. Detecting drift requires parsing diffs and mapping the impacted files to generate updated documentation artifacts.

Yes, you can automatically generate an update plan for architecture docs after a feature merge. The process parses diffs, maps impacted source files to documentation, and validates references to ensure consistency without manual tracking.

The best way to prevent documentation drift is triggering an alignment workflow after code changes. This maps impacted source files to AGENTS.md, API docs, and architecture docs, validating references to maintain consistency.

No, you do not need to manually track impacted files to sync documentation. The alignment process automatically parses diffs from code changes and maps the impacted files to AGENTS.md, API docs, and architecture docs.