Verify documentation accuracy against implementation code

Keeping distributed documentation synchronized with code changes without manual review

• · documentation file paths (array)
• · implementation code accessible

• · evidence-backed edits to documentation files
• · adversarial verification confirmations

• · Read
• · Edit
• · Glob
• · Grep

• · Documentation directory structure exists
• · Source code accessible for validation

• · Stale code invalidates doc edits
• · Adversarial agent misses valid fixes
• · Cascade regressions from incorrect edits

• · Audit & Fix phase with per-doc agents
• · Adversarial Verify phase refutes each finding
• · Explicit evidence citations (file:line)