grace-status

To detect drift and missing module contracts in a GRACE repository, generate a health report that counts files with and without MODULE_CONTRACT, flags unpaired semantic blocks as integrity violations, and highlights mismatches between the knowledge graph and codebase.

Project health assessment checks knowledge graph alignment by comparing modules declared in docs/knowledge-graph.xml against modules found in the codebase, highlighting orphaned or missing entries to surface gaps for prioritized fixes.

To audit GRACE documentation artifacts, generate a project health report that verifies the presence and versions of key files including AGENTS.md, docs/requirements.xml, docs/technology.xml, and docs/development-plan.xml.

You can get actionable next steps by extracting recent CHANGE_SUMMARY entries and mapping detected issues to recommended grace CLI commands like grace-plan, grace-generate, grace-execute, grace-refresh, or grace-verification.

This project health check requires no external dependencies and applies directly to GRACE-based repositories to instantly audit project integrity, count semantic blocks, and summarize recent changes.

The best way to surface unpaired semantic blocks is to run a codebase metrics count that identifies total semantic blocks and reports any unpaired blocks directly as integrity violations within the health status summary.