Repository navigation
Reconstruct native outputs from nested BSA 104 containers - #65
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.
Recipes can now reconstruct exact loose files from BSA 104 containers inside original ZIP, 7z and RAR downloads. The explicit extract-bsa104 action locks the outer archive, container and inner file independently; direct extraction keeps its existing meaning. All container/member checks run before installation writes, with bounded temporary staging and cleanup that preserves changed or unfamiliar files.
The shared output writer preserves hashes, timestamps, cancellation, resume and repair behavior. Tests cover malformed/ambiguous archives, limits, failed staging writes, awaited consumers, cancelled reconstruction, conflict/save preservation and actual Electron ZIP/RAR flows. The new Electron checks also run against the staged executable in Windows CI.
Validation: Svelte check has zero errors/warnings; the full local suite passes 225 tests with one optional runtime skip. Public documentation defines the supported subset and hard-termination cleanup limits. Automatic nested-source ledger mapping, other BSA/BA2 variants, generated transforms and gameplay acceptance remain separate work.