Add Claude observability parity and prepare v0.2.0 - #35
Merged
Conversation
Contributor
|
Claude parity focused tests failed: |
Contributor
|
Claude parity focused tests failed: |
Contributor
|
Claude parity hygiene validation failed: |
Owner
Author
|
Final validation update: the earlier red→green attribution failures and EOF hygiene failure were intermediate staging findings and are superseded. The cleaned head |
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
Brings the Claude harness up to the same observability contract as the merged Codex checkpoint path and prepares the repository for a v0.2.0 release.
Claude parity
Provider capability rubric
Adds
docs/capabilities.mdwith a Claude/Codex matrix covering:The README includes a short provider-observability callout and link.
v0.2.0 preparation
0.1.0to0.2.0.The tag/release should be created from
mainafter this PR merges; this PR deliberately does not create a tag from an unmerged branch.Adversarial boundary
Parity means equivalent evidence standards, not interchangeable units. Claude turns/tool-result boundaries and Codex provider items remain distinct. Claims about the first evaluator-green observed boundary require
checkpoint_coverage_complete=true; neither path claims an instruction-level instant. Post-functional work is not automatically waste when it completes required bench-ready evidence.Validation
benchmark_harness/testssuite: passed.git diff --check: passed.The final diff contains only the 11 intended implementation, test, documentation, and release-metadata files.