sync-templates

To synchronize scaffold templates with your vault, run the sync engine to perform a bidirectional interactive merge. It compares template files across environments, provides diffs for changed files, and prompts for merge actions to resolve conflicts.

Bidirectional template merging pushes core scaffold updates to your personal vault and pulls custom vault changes back into the scaffold. This prevents template drift and manages consistency across development and user environments.

To update vault templates after modifying a scaffold file, initiate the template sync process. The engine detects the changes, displays a diff for the modified file, and prompts you to explicitly confirm the file operation to push the update.

Yes, you need to manually resolve conflicts during template synchronization because the sync engine requires explicit user confirmation for all merge resolutions. It provides interactive diffs to help you decide how to handle each changed file.

Yes, you can pull custom changes from your vault back into the engine scaffold. The bidirectional sync mechanism compares both directories and allows you to selectively merge your personal vault configurations into the core scaffold.