Repository navigation
Group shared Control readiness prerequisites - #56
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
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 missing Program schedule-set approval now appears as one action with its affected Controls linked as dependents. Each Control retains the readiness gate, while individual implementation gaps remain separate actions and progress counts.
Mapped evidence-source setup uses the same grouping. Missing Control mappings remain individual, and older model source-family gates remain intact. CLI workflow findings, recommendations, readiness counts, and browser lists consume the shared bindings.
Validation: fresh Node 24
CI=true npm run validate, seven focused regression cases, CLI/browser parity across shared-only, mixed, approved, and shared-source scenarios, clean browser console and requests, fresh consumer validation, package dry runs, npm audit, and private-source/secret scans. Independent code and security reviews found no remaining issues.Coordinated backward-compatible patch release: 0.17.3.