Repository navigation
M5.2: portable restore planning dry-run - #28
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.
Adds dry-run planning for portable archive restore.
POST /api/recording-archive/planvalidates the same M5.0 archive structure, manifest version, managed paths, sizes, SHA-256 values, WAV/FLAC signatures, rebuilt metadata/previews and annotation validity used by restore, then classifies each recording as import, duplicate, conflict or unmatched without committing metadata or moving managed audio to final paths. Plans include per-recording reasons plus annotation import/skip counts. Temporary validation staging is removed before the request completes. UI adds Plan restore alongside the existing safe restore action. Includes backend/API/state-mutation tests, embedded UI qualification, README and M5.2 docs.