vc-update

Yes, a dry-run diff summary provides a preview of file modifications, deletions, and symlinks before any changes are applied. This allows you to review exactly what the remote repository update will alter in your local environment.

User confirmation requires explicit approval before the script applies any updates from the remote repository. This ensures you maintain control over the final version management step and prevent unintended file modifications.

Yes, you need both git and node.js installed in your environment to run this version management process. These dependencies are required to pull improvements from the remote repository and execute the update scripts.

The best way to handle file deletions and symlinks is using an automated version management script that tracks these changes during the remote repository pull. It provides a diff summary and requires confirmation before applying these specific modifications.

A dry-run summary is essential for agent harness version management because it shows exactly what file modifications and deletions will occur before they happen. This prevents breaking changes by requiring your confirmation prior to applying updates.