fix: preserve local files when changing sync targets - #74
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changing sync folders could import pre-existing skills unexpectedly or leave instruction files as broken symlinks. Rerunning setup could also replace custom target paths and copy mode with defaults.
Setup now preserves configured targets, and changing a target or scan path starts a fresh adoption baseline. Instruction path changes leave standalone copies at removed destinations. Profile switches check every destination for unmanaged-file conflicts before updating any links.
Existing vault formats are unchanged. Closes #73.
Validation: all 118 tests pass, including regressions for these failures and retained path aliases.
npm pack --dry-runandgit diff --checkpass.