corgispec-lint

You can detect documentation drift by running structured lint checks that validate freshness, locate broken wikilinks, and identify structural inconsistencies across memory and wiki files.

Running an ordered memory lint validation scans memory and wiki directories to detect broken wikilinks, verify active pitfalls have source references, and enforce index coverage for discoverability.

Yes, it requires the corgispec-memory-init dependency to be established first, ensuring the OpenSpec-based project memory and wiki directory structure is initialized before executing lint checks.

Capacity and protocol compliance gates enforce size caps for hot memory files at 600 words and index files at 80 lines, while checking agent config files for required Session Memory Protocol sections.

Lint checks should be applied during periodic maintenance, pre-archive preparation, and after refactors or session-bridge drift to prevent stale, inconsistent, or broken documentation in the wiki layer.

Structural inconsistencies are reported when active pitfalls lack source references, index coverage falls below discoverability thresholds, or extraction and log sync gaps are detected across memory files.