cleanup: remove unused benchmarks, deep_probe, meta_reflect

Remove sealqa, babyvision, mathverse, mmrb, swebench envs and configs.
Remove deep_probe, deep_reflect, meta_reflect modules and prompts.
Remove download_babyvision script.
These are not part of the core released benchmarks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

skillopt/envs/livemathematicianbench/prompts/deep_probe.md

@@ -1,23 +0,0 @@
-You are an expert diagnostic-probe designer for theorem-grounded mathematical multiple-choice tasks.
-
-You will be shown representative trajectories, the current target skill, and the target's original prompt context.
-Design one SMALL diagnostic instruction that exposes the target's intermediate judgment without materially changing the original scaffold.
-
-## Hard Constraints
-1. Do NOT substantially change the original scaffold.
-2. Do NOT prescribe a new multi-step theorem-solving procedure.
-3. Do NOT ask for a full proof, full chain-of-thought, or exhaustive option-by-option derivation.
-4. Ask only for a short readout of the signals already behind the target's current answer.
-5. Keep it brief and structured, and require the final answer to remain in <answer>...</answer>.
-
-## Good Probe Targets
-- top choice and runner-up
-- decisive constraint
-- why the runner-up was rejected
-- strongest-vs-weaker discrimination signal
-
-Respond ONLY with a valid JSON object:
-{
-  "reasoning": "<why this probe is informative>",
-  "probe_instruction": "<the exact instruction text to append to the target prompt>"
-}

skillopt/envs/livemathematicianbench/prompts/deep_probe_codex.md

@@ -1,26 +0,0 @@
-You are an expert diagnostic-probe designer for theorem-grounded mathematical multiple-choice tasks executed through a Codex trace.
-
-You will be shown representative trajectories, the current target skill, the target's original prompt context, hidden reference fields, and numbered Codex trace steps.
-Choose exactly one trajectory and one probe point. The probe point determines how much of the prior Codex trace will be shown back to the target before asking a short diagnostic question.
-
-## Hard Constraints
-1. Do NOT reveal or paraphrase the hidden reference directly to the target.
-2. Do NOT prescribe a new full solving procedure.
-3. Do NOT ask for a full proof, full chain-of-thought, or exhaustive option-by-option derivation.
-4. Ask only for a short readout of the signal that should already exist at that point in the target's process.
-5. The probe instruction must explicitly request a short <analysis>...</analysis> block before the final <answer>...</answer>.
-6. Select a probe point that is informative about theorem choice, decisive constraint, option elimination, or why a stronger/weaker option should be rejected.
-
-## Probe Point Semantics
-- `probe_target_id` must be one of the shown trajectory ids.
-- `probe_after_step` is the last numbered Codex trace step that should remain in the target's context.
-- The target will be re-run with the raw trace up to and including `probe_after_step`, then asked your `probe_instruction`.
-- To probe before a tool call, choose the step immediately before that tool call.
-
-Respond ONLY with a valid JSON object:
-{
-  "reasoning": "<why this trajectory and probe point expose the target's intermediate state>",
-  "probe_target_id": "<trajectory id>",
-  "probe_after_step": <integer step number>,
-  "probe_instruction": "<the exact instruction text to append to the target's prompt>"
-}