Use a subagent to audit docs-vs-code, then verify its findings too

When a project has design docs plus a partial implementation, docs drift into stating aspirational/spec things in the present tense as if built. A cheap, high-value pass: spawn a subagent whose ONLY job is to cross-check every doc claim against the actual code (grep for named functions/constants, check what is imported where, confirm numbers in docs match test output) and report file:line inconsistencies WITHOUT editing. Key framing that made it work: give the auditor the ground-truth context up front (e.g. "module X is standalone and NOT imported by the live engine; feature Y computes a split, not a persisted object") so it flags overclaims instead of trusting the prose. IMPORTANT gotcha: verify the auditors own findings before applying them — mine correctly caught 5 real honesty gaps but ALSO misflagged a lookup table as stale that was actually correct (it showed sample INPUTS 1/4/12/40 mapping to output tiers under thresholds 1/3/9/27, not the thresholds themselves). One grep of the actual test settled it. Cross-referencing superseded docs (add "see D36/docs14" pointers) is as important as fixing the new ones.