Provision a ready Odinn benchmark agent fixture - #10
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
mainagent identity and valid integrity-bound manifest/registryBOOTSTRAP.mdso trials cannot enter onboardingRoot cause
The adapter advertised
workspace.writeandprocess.exec, but the benchmark had no enforced contract proving that the Odinn state fixture actually contained a completed identity, matching runtime grants, and an enabled main-agent registry. The mismatch allowed every tool-dependent Odinn trial to enter scoring with capabilities the runtime could not provide.Current-head proof
4edd035333de9447e969117294b3a833740b4cc8pnpm typecheck && pnpm test/tmp/agent-benchmarks-pr-odinn-ready-agent.logOperator usage
After configuring the isolated Odinn provider and protected OAuth state:
Not tested