Diagnose the live SDK result contract without account data - #23
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.
The latest live run showed the Accessibility category but no matching issue label in the DOM. Record narrowly validated SDK JavaScript bundle locations and selected-view and synthetic-image-handoff booleans so the result implementation can be inspected without guessing another label.
Only official SDK/CDN origins and known static bundle paths are allowed. Strip query strings; reject fragments, credentials, application routes and unrelated origins. No report text, screenshots, response bodies or account URLs are retained. The required issue assertions and timeouts are unchanged.
Validation: 18 unit tests passed, including rejection of unsafe diagnostic values, and four synthetic navigation cases passed across Chromium and Firefox. This is diagnostic work; it does not claim the missing result assertion is fixed.