Document canonical Eval Lab failure and workload boundaries#2
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.
Outcome
Reconciles gdev-agent documentation with the published Eval Ground Truth Lab result for exact revision
0e4c5f0fd50382bbf12ffd35cfca4632384fb0cc.The local 55-case conformance suite passes, while the unchanged public 100-case release gate correctly fails. The evidence pack is content-addressed as
sha256:656face21f27b496d4d3e8bb0b588824f5737d122c1275c710f3e5b15ff94b4band is published under Eval Labv0.2.0.Changes
Verification
310 passed180/180, pass (run before the final docs-only boundary commit; executable code and cases are unchanged)No production, pilot, external-user, live-traffic, or customer claim is made.