ci(workflow): add trace-backed harness scoring - #2930
Open
quanruzhuoxiu wants to merge 5 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
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
Validation
Local:
PR-native workflows on the final SHA:
Artifact verification:
Two earlier manual Headless runs caught the dark timeline assertion as a product failure while preserving complete Trace, request IDs, screenshots, raw responses, token usage, and reproducible manifests. The final PR-native rerun passed, so this is recorded as a flaky UI/model signal rather than a harness infrastructure failure.
The new Nightly Harness workflow cannot be manually registered until the workflow file exists on the default branch; its workflow graph is covered by actionlint and activates after merge.