Enforce orchestration evidence and add evaluation benchmarks#6
Merged
Conversation
whchi
marked this pull request as ready for review
July 15, 2026 11:50
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.
What changed
Why
The existing runtime could trust maker self-reporting, lose evidence attribution across child sessions, and discover malformed envelopes only after execution. The benchmark pipeline also used single runs and default-pass labels that could overstate quality.
Impact
Runtime verification and trace diagnostics become stricter and more observable. Benchmark results require explicit acceptance data, report cost/time before token detail, and can evaluate routing and checker quality independently.
Validation
bun test— 193 passed, 0 failedbun run build— passedgit diff --check— passed