Repository navigation
Support named checkbox audits and organize validation guidance - #54
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.
What changes
Add an opt-in
checkboxSelectorsmode tocheckbox-auditfor controls that expose an exact name and CheckBox type but no AutomationId. Preserve the existing ID-based input, result and validation contracts. Named audits retain raw property gaps and reject ambiguous identity, unknown required state and incomplete scope or traversal evidence.Organize the README documentation entry points and condense the current-work document into remaining limitations and acceptance criteria. Keep client defaults unchanged.
Validation
Privacy and scope
Only 8 reviewed source, test and documentation files are included. Screenshots, raw window contents, account data, machine paths and diagnostic logs remain in ignored local storage and are not attached to this PR. The staged-file review found no known personal identifiers or credential patterns. No dependency, native Host, deployment or client-default change is included.