ci(fleet): make browser release evidence manually dispatched - #65
Merged
Conversation
Four consecutive CI runs starved the CUA fixture startup budgets on shared two-vCPU runners (vite readiness alone exceeded 90s with high variance even though vite itself boots in ~200ms). The release-grade browser/desktop evidence lane now runs via workflow_dispatch on a host that can afford it; the owner's verified local cua:release flow remains the release gate, and automatic CI keeps the verify and bundle contracts that guard every push and pull request.
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.
Four consecutive CI runs starved the CUA fixture startup budgets on shared two-vCPU runners (vite readiness alone exceeded 90s with high variance even though vite itself boots in ~200ms on the same runners). The release-grade browser/desktop evidence lane now runs via workflow_dispatch on a host that can afford it; the owner's verified local cua:release flow remains the release gate, and automatic CI keeps the verify and bundle contracts that guard every push and pull request.