Stabilize Artifacts UI validation and security gates - #36
Merged
Conversation
Launch Artifact smoke shards directly into their destination, use exact semantic readiness selectors, split long journeys, and fix the running-work menu selector. Update CodeQL to 4.37.1 and codify encrypted-storage invariants.
This was referenced Jul 21, 2026
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.
Summary
Root cause
The post-merge Xcode failure was not an Artifacts runtime defect. The smoke suite combined several long journeys in one UI-test process, navigated through broad accessibility queries, and selected a running-research control whose label aliased its own menu item. Those choices made simulator state and selector resolution nondeterministic.
Validation