ln-614-docs-fact-checker

Documentation consistency checking works by extracting verifiable claims such as paths, versions, counts, configurations, names, and endpoints from Markdown files, then validating each claim directly against the source code.

Contradiction detection between Markdown files is performed by cross-checking all extracted claims across documents to identify discrepancies in paths, versions, counts, configurations, names, and endpoints.

Yes, API endpoints mentioned in Markdown files are targeted by extracting endpoint claims and verifying them directly against the codebase to ensure code-documentation alignment.

Yes, this fact-checking process works with all Markdown files in a repository by extracting and verifying claims from every `.md` file to ensure complete code-documentation alignment.

Verifiable claims extracted from Markdown files include paths, versions, counts, configurations, names, and endpoints, all of which are cross-referenced with the codebase for accuracy.

You should run documentation consistency checks before a new release to ensure all version numbers, API endpoints, and configuration parameters in Markdown files accurately reflect the deployed codebase.