docs-audit-and-refresh

To audit repository documentation, compare the `docs/` content against the live codebase to identify missing, incorrect, or stale information. This process uses repository evidence to ensure developer and user-facing docs accurately reflect current features.

Refreshing outdated technical documentation after a feature update involves scanning the `docs/` directory to find pages that no longer match new functionality. Updates are prioritized based on reader impact and corrected using current repository evidence for accuracy.

No, documentation updates are limited to the `docs/` directory. The audit identifies stale or incorrect user-facing and developer-facing behavior across the repository, but targeted refreshes and corrections are only applied to files within this specific folder.

A documentation refresh prioritizes fixes based on reader impact, focusing on user-facing and developer-facing behavior. By evaluating repository evidence, it targets the most critical missing or incorrect information to ensure documentation accurately reflects current features.

You need a codebase sync for developer docs when codebases evolve and documentation becomes outdated or incomplete. Auditing identifies stale information and missing features, ensuring documentation accurately reflects the current state of the repository.

Yes, docs-audit-and-refresh operates without external dependencies. It uses the repository's internal references to compare existing `docs/` content against the codebase, identifying and correcting missing or stale information to keep documentation in sync.