Repository navigation
docs: add Game qualification population source - #702
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.
Add the product population source required by the published Binding3 parser for the existing FS.GG.Game — Product V2 qualification fixture (Project 4). Select only Game#7 as verified remaining follow-up work, using its canonical issue URL and fresh native issue/dependency snapshot. This fixture is for qualification; source delivery does not select a workspace default or activate a consumer.
Bind the import recipe to published source 2ab0c0ff9f37bdec9a11ba3604ebdc230711934f and its actual engine artifact cb318977a143085680b27ba4c86fffd6fb3f5a91dc6a7e07cf79ef7c67825615. These are the root-selected import authority identities. The execution GitHub adapter identity is separate and belongs in the later private execution binding.
Validation: exact structural comparisons against root-selected authority and fresh native project/issue inputs passed, including eight negative identity/freshness/scope controls; routine eligibility and operation-boundary doctrine fixtures passed; git diff check passed. These are source checks. Shipped product parser, installed/native qualification, membership and consumer adoption remain separate root-owned work. Human fixture planning remains Backlog/Follow-up/ObservationUnknown.
After native merge readback, use the actual protected merge revision as PopulationRevision. Re-read issue freshness before installed qualification; Renovate edits truthfully require freshness handling.