Repository navigation
docs: align ecosystem with Evals 0.11 containment - #46
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
🟡 Changes recommended
The new compatibility guide remains unpublishable in the strict MkDocs build and its example commands reference unavailable Evals v0.11 artifacts.
2 open issues
What changed in this PR
This documentation-only pull request aligns the ecosystem guidance with Evals 0.11 containment scoring while preserving native schema ownership, producer-declared coverage, and the separation between containment evidence and deployment health.
Changes:
- Adds an Evals 0.11 containment compatibility guide with ownership boundaries and operator examples.
- Links the guide from the README and roadmap.
- Documents compatibility expectations, containment gates, and unchanged runtime dependencies.
| File | Changes reviewed | Findings |
|---|---|---|
ROADMAP.md |
Adds the Evals 0.11 containment milestone and compatibility guide link. | Nit (1 vote): The surrounding text still describes containment scoring as a future milestone, creating an internal status contradiction. |
README.md |
Adds user-facing references to the containment compatibility guidance. | No file-specific findings. |
docs/evals-0.11-containment.md |
Defines package responsibilities, compatibility details, schema boundaries, and operator commands. | Nit (3 votes): Add the page to the MkDocs navigation. Nit (3 votes): Update the link and commands to reference available 0.11 artifacts, or mark the examples as unreleased. Nit (1 vote): Present MCP 0.6.1 and Evals 0.11.0 as planned/target compatibility until those versions and references are published. |
Review effort: Lite
| @@ -0,0 +1,34 @@ | |||
| # Evals 0.11 containment compatibility | |||
Comment on lines
+15
to
+19
| Use the [Evals guide and passing/failing example](https://github.com/DeepAgentLabs/agentic-evals/blob/main/docs/containment.md): | ||
|
|
||
| ```bash | ||
| uv run --extra integrity python examples/containment/generate.py | ||
| uv run --extra integrity agentic-evals evaluate examples/containment/suite.json \ |
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.
Align README, roadmap, compatibility documentation and operator examples with Evals 0.11 containment scoring. Preserve each package’s ownership, the unchanged native report/gate schema 1.0, host-owned trust and scope, and producer-declared coverage limits.
Validation: repository make check passed. Runtime dependency ranges remain sufficient; this documentation-only update needs no package release.