mvt-sync-context

You can synchronize completed change artifacts by interactively selecting finished work, resolving knowledge conflicts, and merging stable updates into project-context.md and project-context.yaml files through an atomic backup-and-merge process.

Artifact-driven context synchronization aggregates finished analysis and implementation outputs into canonical project knowledge files. You need it when completed features must fold new domain rules and module knowledge into shared context to prevent long-term project memory from drifting.

Before merging, the workflow presents mapped items, conflicts, ambiguous entries, and implied YAML updates for user confirmation. You interactively select completed changes and resolve any conflicts for modified knowledge before the atomic merge is applied.

Yes, you can perform an optional read-only code verification to confirm that artifact-claimed modules, files, and symbols actually exist in the codebase, while explicitly avoiding any undocumented code-only additions or full codebase regeneration.

Limitations include strict avoidance of full codebase regeneration and deletion handling, explicit exclusion of undocumented code-only additions during verification, and the requirement for interactive conflict resolution rather than automatic overwrites of modified knowledge.

Yes, project context synchronization works by merging stable, high-value knowledge from completed artifacts directly into both project-context.md and project-context.yaml files, ensuring structured YAML indexes and markdown documentation stay aligned with delivered work.