Add adaptive harness receipt eval - #11
Merged
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.
Summary
Decision
The focused three-sample run passed with +0.4250 weighted delta, 0.9750 candidate score, zero boundary violations, and all DF-03/DF-08 candidate samples strict-pass. The retained sealed run scored 0.9281, below the frozen v0.2.0 floor of 0.9673, so the behavior candidate is rejected and the shipped skill remains unchanged.
Proof
npm test— passnpm run benchmark:adaptive-harness— pass; focused receipt atresults/2026-07-15T00-11-39-008Z-gpt-5.5/npm run benchmark:sealed— intentional failed decision gate; relative comparison passed, absolute0.9281 < 0.9673npm run benchmark:trajectories— pass, 6/6npm run smoke:cold-start— passNo global install, hook, permanent agent, skill-text change, deploy, or runtime mutation is included.