vf-setup: prefer endpoints.toml, rename configs/lab->configs/rl, add GEPA configs, deprecate --vf-rl

[willccbb]

Motivation

• Make vf-setup use the TOML endpoints registry (preferred) rather than the legacy Python registry to align with other tooling and tests.
• Move example Hosted Training configs from configs/lab/ to configs/rl/ to reflect the current naming and packaging for RL examples.
• Provide a minimal GEPA config template and example for quick prompt-optimization runs and stop bundling the legacy vf-rl configs from vf-setup.

Description

• Switched default endpoints source and destination to configs/endpoints.toml in verifiers/scripts/setup.py and updated code paths that referenced the old endpoints.py.
• Renamed repo example configs from configs/lab/* to configs/rl/* and updated vf-setup to download the configs/rl batch by default.
• Added GEPA templates under configs/gepa/ (base.toml with single-environment keys and wordle.toml example) and wired vf-setup to download them.
• Marked --vf-rl as deprecated in vf-setup (prints a warning and no longer downloads vf-rl bundles) and updated docs (AGENTS.md, docs/overview.md, docs/training.md) to reference endpoints.toml and configs/rl/.
• Added unit tests tests/test_setup_script.py to assert that run_setup downloads the TOML endpoints, the GEPA configs, and the rl configs by default and that vf_rl=True only triggers the endpoints + GEPA downloads.

Testing

• Ran style checks with uv run ruff check --fix . which completed successfully.
• Ran unit tests with uv run pytest tests/test_setup_script.py which produced 2 passed.
• Verified manual inspection of the new configs/gepa/ templates and doc updates to ensure references point to configs/endpoints.toml and configs/rl/.

---

Codex Task

---

Note

Medium Risk
Changes default workspace setup artifacts and download behavior (endpoints/config packs) and adds new TOML parsing paths for the prime gepa CLI, which could break existing workflows if paths/flags are relied on.

Overview
Workspace setup is updated to prefer the TOML endpoints registry (configs/endpoints.toml) and to download new default config bundles: RL examples under configs/rl/, eval examples under configs/eval/, and new GEPA prompt-optimization starters under configs/gepa/ (with deduping of overlapping destination paths).

The GEPA CLI (verifiers/scripts/gepa.py) now accepts either an env_id or a .toml config file via env_id_or_config, adds schema validation for [env]/[gepa]/[execution] tables, resolves config-relative paths (e.g., endpoints_path), and maps save_results to --no-save.

Docs are refreshed to match the new paths/commands, eval example TOMLs are cleaned up, and new tests assert the setup script’s download set and that bundled eval/GEPA configs parse under the current schemas.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Config-relative path resolution misses env_dir_path

Low Severity

The config-relative path resolution section in load_gepa_toml_config resolves endpoints_path and run_dir relative to the TOML config file's parent directory, but env_dir_path — also a supported path key extracted at line 79 — is not resolved. If a user specifies a relative env_dir_path in a GEPA TOML config placed in a subdirectory (like configs/gepa/), it will be interpreted relative to CWD instead of the config file, inconsistent with how the other two path fields behave.