Repository navigation
docs: qualify #214/#217/#218 acceptance boundaries - #234
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.
Independent acceptance audit for #214, #217 and #218 on
main@c6c47bdd, against deployed sourceac906946and the integrator's candidate3e49d9d.E401 Unauthorizedfor@lyyzka/lingxios@3.5.6; zero product browser cases ran in this session.e2e@0.17.0and@e2e-dev/web@0.12.0. The browser started, but normal TLS navigation failedERR_CERT_AUTHORITY_INVALID(0/1). Raw report, screenshot, video and trace are retained. No certificate, sandbox or package-auth workaround was used.Complete audit and source/evidence links. This documentation draft does not claim acceptance, modify product code, merge, deploy, publish packages or close issues.