update-api-artifacts

Syncing API documentation with source code requires static analysis of route files to automatically rebuild API-ROUTES.md, ensuring documentation accurately reflects the current codebase state.

API permissions auditing compares permissions used in code against the permissions.ts registry, using static analysis to detect and report mismatches between declared and applied access controls.

You can check for stale references in project documentation by spot-checking files like AGENT.md and CLAUDE.md against current source code to identify and correct outdated or inconsistent information.

Yes, static analysis of route definition files can automatically generate API routes documentation by systematically rebuilding artifacts, which is particularly effective for maintaining accuracy in rapidly evolving codebases.

Maintaining documentation accuracy in a large codebase is best achieved by systematically rebuilding and auditing documentation artifacts from source code, preventing inconsistencies after significant feature updates or refactoring.

You need to regenerate API documentation artifacts after significant code refactoring or feature updates, ensuring that all project references and route definitions remain current, accurate, and consistent.