documentation-sync

To fix documentation drift after refactoring, validate that README.md, docs/, and OPENAPI specs align with the current codebase. This process checks Getting Started, Architecture, and API references to surface mismatches and ensure docs remain accurate.

Keeping OpenAPI specs aligned with code changes requires applying validation checks during major refactors or feature additions. This ensures API references and environment variable mentions accurately reflect the latest repository state before release.

Validating README consistency involves comparing documentation artifacts against the actual implementation and file structure. This checks key sections like Getting Started and Architecture to verify they match the current codebase and prevent misaligned expectations.

Yes, you can check environment variable mentions during feature additions. The validation process ensures plans and environment variable references stay aligned with the latest repository state, keeping documentation accurate across all artifacts.

Documentation validation works for major refactors and API changes by comparing docs against code changes in README.md, docs/, and OPENAPI specs. It surfaces mismatches across repository artifacts to maintain accurate, up-to-date documentation.