Execute all ProofRun V1 journeys in GitHub CI - #5
Open
ty-everett wants to merge 6 commits into
Open
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.
Runs every existing executable ProofRun V1 journey through the private hosted control plane on same-repository pull requests, manual dispatch, and a staggered weekly schedule. Vendors only immutable, credential-free customer/device contracts; secrets remain GitHub/runner handles. Browser cases use cloud workers, while capability-matched iOS, Android, and Metanet Client cases lease the Evans Creek Mac. Stateful and spending journeys retain manual approval boundaries.\n\nAll workflows compile against their vendored catalog and the GitHub workflow parses successfully.