reference-audit

To keep documentation synced with infrastructure artifacts, an automated reference audit scans the codebase to detect gaps, validate MCP mappings, and flag stale Docker references across multi-service projects.

Detecting stale documentation references is handled by scanning docs and flagging entries based on their Last verified dates, ensuring your project's knowledge base stays accurate and synchronized with the actual codebase.

Cross-referencing MCP entries between services-and-access.md and tool-routing.md is automated by running a full reference audit command, which validates the mappings and identifies inconsistencies across your multi-service architecture.

Yes, you can automatically populate missing sections in docs/references with discovered artifacts by using optional flags during the reference audit, which auto-populates the discovered infrastructure mappings into the documentation.

Yes, the reference audit supports scanning Docker references and secret tables. It validates these infrastructure artifacts to ensure they stay synchronized across multi-service projects during the automated documentation audit.