audit-validation

Verify stale codebase audit claims by running deterministic repository checks for each assertion, using grep, wc, and ls to validate file existence, LOC counts, and pattern presence before acting on the audit.

Validate duplication claims by locating duplication markers with grep and sampling matched contexts to ensure they are truly duplicates, rather than trusting the audit's interpretation of the pattern presence.

When an audit claims a component is missing, search for similarly named modules and canonical call-site patterns with grep to cross-check functionality, recording verified measurements or reframing the plan when the premise fails.

Check if analysis LOC counts match actual repository state by running wc commands to count lines of code, then recording verified measurements and noting mismatches in the plan scope instead of glossing over them.

Run grep validation against third-party codebase measurements when inputs contain stale measurements, missing-component assertions, duplication counts, or symbol existence claims that would change the plan's shape if incorrect.

When verified measurements differ from audit findings, the plan scope should record actual measurements and note the mismatches explicitly, ensuring discrepancy-aware planning instead of proceeding on failed premises.