feat: ship VS2010-inspired release toolkit foundation - #31
Merged
Conversation
TrapEmAll
marked this pull request as ready for review
August 1, 2026 08:50
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
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.
Summary
This prepares UnityScraper 1.2.0-beta.1 as a safer, more complete Xbox 360 knowledge and preservation workspace.
Migration notes
Database schema version advances from 9 to 10. Migration 10 is additive and creates:
metadata_snapshot_runslibrary_intelligence_runspreservation_report_runscorrection_packageshardware_inventory_recordspackage_extraction_runsExisting library, download, knowledge, profile, save, and transfer data is preserved. No destructive migration or user reset is required.
Safety and privacy
Source and licensing considerations
UnityScraper stores provenance, source URLs, revisions, and license metadata rather than flattening third-party knowledge into unattributed claims. The STFS reader follows the public Free60 format reference. Existing source adapters retain their source-specific policy and licensing boundaries; no commercial game content, encryption keys, firmware, or restricted binaries are bundled by this work.
Validation
Follow-up adapters
The next source-specific increments should deepen, rather than blur, the existing adapter boundary:
Each adapter should retain raw-cache provenance, rate limits, source revisions, conflicts, and field-specific trust priorities.