doc-maintenance

Documentation drift is detected by auditing top-level files like README.md, doc/SPEC.md, and doc/PRODUCT.md against recent git history. This process identifies shipped features missing from docs or features incorrectly listed as upcoming, generating a concise change summary of discrepancies.

Automatically fixing outdated docs involves a structured workflow that detects changes, builds a concise change summary, creates a feature branch, and opens a pull request with minimal, fact-based edits to restore accuracy after major feature merges.

Auditing SPEC and PRODUCT docs for accuracy is best achieved by comparing them against recent commits to find alignment gaps. This targeted review catches discrepancies between shipped features and documented claims, proposing minimal edits to correct the record.

A documentation health check against git history should be run during periodic reviews after releases, after major feature merges, or on a scheduled basis. This ensures top-level documentation accurately reflects the current state of shipped features.

Yes, reviewing README drift and opening a pull request without manual editing is possible. The workflow detects discrepancies, proposes minimal fact-based edits, creates a feature branch, and opens a PR automatically, restoring accuracy without direct human intervention.