check-docs

To audit docs for code-consistency, cross-reference your documentation directories against key source files like types.ts and engine.ts. This flags mismatches in parameter definitions, component references, and ADR statuses without modifying any files.

Checking Mermaid diagram and ADR alignment involves cross-referencing documentation against actual code implementations like state.svelte.ts and worklet-processor.ts. The audit reports drift in ADR statuses and diagram logic without making changes.

Documentation drift occurs when docs and code fall out of sync. You detect it by scanning architecture and data model docs against source files to surface mismatches, reporting findings like outdated parameter definitions without modifying any repository files.

Yes, you can verify site docs and app help references against types.ts and paramDefs.ts. The audit cross-references these specific source files to flag mismatches in component references and parameter definitions without altering your codebase.

No, the documentation audit does not automatically fix mismatches. It strictly flags inconsistencies and drift between your docs and codebase, enabling maintainers to review findings and manually update files without unintended modifications.

The best way to catch drift is running a cross-reference audit between internal AI docs under docs/ai/ and key source files like dsp/types.ts. This surfaces inconsistencies in parameter definitions and component references for maintainer review.