grace-refresh

Knowledge graph drift is detected by running a full repository scan that compares actual imports and CrossLinks against docs/knowledge-graph.xml to identify missing modules, orphaned entries, and stale connections. It generates a structured integrity report detailing the discrepancies.

Synchronizing module contracts after multi-agent changes is done by performing a targeted scan of changed modules and their immediate dependency surfaces. It extracts MODULE_CONTRACT and MODULE_MAP data, compares them against the graph, and proposes user-approved updates to reconcile drift.

CrossLink integrity reporting works by extracting MODULE_CONTRACT and MODULE_MAP files, comparing their declared imports against docs/knowledge-graph.xml, and producing a structured report. It lists missing, orphaned, and stale entries to highlight exactly where the graph and codebase diverge.

You cannot automatically apply changes; the remediation workflow proposes concrete fixes like generating missing contracts or updating entries, but changes apply only after explicit user approval. This safe workflow ensures you retain full control over knowledge graph modifications.

Run a targeted scan during active multi-agent waves to validate specific cross-module changes and immediate dependencies. A full refresh is intended for use after large refactors or when broad drift is suspected across the entire repository codebase.