Audit documentation for semantic drift classes

Catching documentation claims that grep/structural validators miss (citations, superlatives, stale enumerations, business facts, capability contradictions).

• · documentation file paths (from both repos)
• · scope parameter: main/site/all

• · inventory of doc groups by area
• · findings array with file, line, claim, drift_class, evidence, suggested_fix
• · verdict report: confirmed drift + gateable classes

• · access to both atmosphere main repo and atmosphere.github.io site repo
• · git available for file listing

• · missed semantic drift due to ambiguous claim interpretation
• · false positives on stale/historical claims that are actually correct
• · inability to find site repo if not at standard locations

• · explicit phases: Inventory, Audit, Verify, Synthesize
• · VERDICT_SCHEMA with confirmed boolean + corrected_truth field
• · adversarial verification step (refute findings before confirming)