[mikasenghaas]

Summary

• Remove the vf-replay console script and its stack: verifiers/v1/cli/replay.py, verifiers/v1/configs/cli/replay.py (ReplayConfig), the Rich replay dashboard (cli/dashboard/replay.py), and tests/unit/cli/test_replay.py.
• Drop saved_config_path from cli/output.py, which only vf-replay used.
• Remove vf-replay from the command table in docs/getting_started.md and from docs/debugging.md. The "Re-score without rerunning the agent" section now documents Task.rescore(trace), which stays as the library API.

Stacked on #2610 (removes vf-eval). Land after it.

Breaking

• vf-replay no longer exists. To score a saved trace again, call Task.rescore(trace) on it.
• verifiers.v1.configs.cli.replay is gone.

Verification

• pytest tests/unit: passes.
• No vf-replay, ReplayConfig, or replay dashboard references remain in verifiers or prime-rl.

🤖 Generated with Claude Code

Note

Remove the vf-replay CLI and its replay workflow

Deletes the replay CLI module, its ReplayConfig model, the replay dashboard renderer, and related tests. The console-script entry for vf-replay is removed from pyproject.toml. Docs now describe offline re-scoring via Task.rescore(trace) instead: it clears scores and runs scoring hooks and judges that need only the saved trace, skipping setup, finalize, and runtime-dependent hooks (debugging.md, getting_started.md).

• Behavioral Change: vf-replay no longer installs as a console command; verifiers.v1.cli.replay, run_replay, ReplayConfig, and ReplayProgress are gone. Use Task.rescore(trace) for offline re-scoring.

^{Macroscope summarized ab141b6.}

---

Note

Medium Risk
Breaking CLI removal changes how users re-score saved runs, though the supported path is the existing Task.rescore API rather than deleted scoring logic.

Overview
Removes the vf-replay CLI and its supporting code: the verifiers.v1.cli.replay entrypoint, ReplayConfig, the Rich replay dashboard, unit tests, and the vf-replay console script in pyproject.toml. saved_config_path in cli/output.py is dropped because only replay used it.

Docs now count four CLI commands instead of five. The debugging guide no longer documents batch re-scoring from a run directory; offline re-scoring is described as calling Task.rescore(trace) on a saved trace (same behavior replay relied on: clear scores, run trace-only hooks and judges, skip runtime-dependent setup).

Breaking: uv run vf-replay … is gone; re-score traces in application code via Task.rescore.

^{Reviewed by Cursor Bugbot for commit ab141b6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at ab141b6

Macroscope's review found this PR approvable — Removes the optional vf-replay CLI and its supporting modules while retaining Task.rescore(trace) for offline scoring. Existing command users must switch to the library API; saved runs and core scoring behavior are unchanged.

^{You can add or adjust custom eligibility rules. Learn more.}