Fix readme and docs to reflect provider/model syntax #780
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.
Description
When using the latest stable version of Verifiers (v0.1.9.post3), running
prime eval run my-env -m gpt-5-nanofails with:Using
prime eval run my-env -m openai/gpt-5-nanoworks instead.So I thought of updating README and docs. I also made some other small fixes.
@willccbb
Type of Change
Testing
uv run pytestlocally.Checklist
Additional Notes
Note
Low Risk
Docs-only changes (plus a README template string) with no runtime behavior impact; risk is limited to potential confusion if examples are still incomplete or mismatch the CLI.
Overview
Documentation examples for
prime eval runare updated to use the provider-qualified model format (e.g.-m openai/gpt-4.1-mini/openai/gpt-5-nano) instead of bare model names, aligning with current CLI behavior.Fixes minor doc inconsistencies by qualifying
Rubricasvf.Rubricin example code and updating README links to point at thedocs/paths; the environment init README template is updated to match the new model syntax.Written by Cursor Bugbot for commit 726ffd9. This will update automatically on new commits. Configure here.