Wait for live report readiness before opening the panel - #19
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.
The diagnostic live run reached Siteimprove login but failed opening the report panel. Wait for authenticated report data for the exact mapped URL before opening the panel, matching the WordPress live runner.
Also retain allowlisted HTTP status codes and boolean readiness indicators so API failures and panel/report state can be distinguished without uploading URLs, response bodies, account text or credentials. Add fixed prepublish stages for subsequent diagnosis. Assertions and skipped issue-result coverage remain unchanged.
Local validation: 17 unit tests passed, including rejection of unknown fields and invalid diagnostic values; live test discovery and diff checks passed. Live confirmation requires a new approved run after merge.