Repository navigation
fix: validate the reviewed organization component set - #2
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.
A coherent expanded catalog failed the organization profile check because it required exactly eight components. The checker also accepted duplicate component IDs when their task rows differed. It now derives exact row membership and count from the reviewed catalog, checks required text fields, and refuses duplicate identities and task/source pairs.
The normal build pool reproduced both defects before the change. The final tree passes all 10 navigation controls and reads all 12 public links. A separate anonymous readback retains the catalog and all 12 linked bodies.