overhaul docs + example configs

[willccbb]

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test improvement

Testing

• All existing tests pass when running uv run pytest locally.
• New tests have been added to cover the changes

Checklist

• My code follows the style guidelines of this project as outlined in AGENTS.md
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Additional Notes

---

Note

Significant docs overhaul plus example configs and setup tooling updates.

• Docs: Replaces/streamlines AGENTS.md; adds CLAUDE.md; major rewrites/expansions of docs/api.md, development.md, environments.md, evaluation.md, training.md; adds environments/AGENTS.md and verifiers/AGENTS.md with guidelines
• Configs: Adds configs/lab/* hosted-training TOMLs and updates local vf-rl/prime-rl examples; removes outdated vf-rl configs; tweaks wiki-search prime-rl config ([trainer.model.lora], sampling/buffer, seq len)
• Setup script: Enhances verifiers/scripts/setup.py with argparse flags (--prime-rl, --vf-rl, --skip-agents-md), downloads agents docs/configs conditionally, updates repo refs to main
• Misc: README uses uv run vf-setup --prime-rl; .gitignore adds .prime and /prime-rl

^{Written by Cursor Bugbot for commit 24f7997. This will update automatically on new commits. Configure here.}

[cursor]

VF_RL and PRIME_RL configs reference non-existent paths

High Severity

The VF_RL_CONFIGS and PRIME_RL_CONFIGS reference source paths in configs/local/vf-rl/ and configs/local/prime-rl/ that don't exist in the repository. The diff shows configs being added only to configs/lab/, while the old configs at configs/vf-rl/ and configs/prime-rl/ are deleted. When users run vf-setup --vf-rl or vf-setup --prime-rl, wget will fail with 404 errors because the download URLs point to non-existent files.

 

[cursor]

Deployment metadata accidentally committed to repository

Low Severity

The file environments/wordle/.prime/.env-metadata.json appears to be internal deployment metadata that was accidentally committed. It contains a specific owner field with a personal identifier ("will"), a unique environment_id, a wheel_sha256 hash, and a deployment timestamp. This looks like metadata generated by the Prime CLI or Environments Hub tooling rather than intentional repository content. The .prime hidden directory is not in .gitignore, suggesting this file was unintentionally included.