Repository navigation
feat: ship eval-harness v0.5.0 and Janus benchmark - #44
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
jq/printf/wc -lrunner. This is a documented breaking change: migrate other shell checks to typed graders or opt in only for trusted case content withunsafe_shell: true/EVAL_ALLOW_UNSAFE_SHELL=1; this is not an OS sandbox.Janus benchmark
docs/JANUS_BENCHMARK.mdfor Janusharness-cliv0.1.10.checks: []as PASS with zero checks; recommendation: no native executor adapter until Janus fixes both behaviors.Verification
npm test: all 57 evaluation test suites pass.PATH.npm pack --dry-run: 149 files; required runner, pricing, example, and Janus report included.runblocks parse; Mermaid validation passes for four docs.cargo test -p harness-cli --features eval(66 passed) andcargo build -p harness-cli --features evalpassed.Release is GitHub tag/release only after merge; npm publication is not configured or attempted.