Trim the card

README.md

@@ -14,80 +14,56 @@ size_categories:
 
 # llm-debugger evaluation transcripts
 
-Every turn of every evaluation episode behind the results reported in
-[`llm-debugger`](https://github.com/mufeez-amjad/llm-debugger).
-
-This covers the arms the reported numbers rest on — the base model, the SFT
-initialisation, and the RL policies trained from it. Exploratory runs that no
+Every turn behind the results reported in
+[`llm-debugger`](https://github.com/mufeez-amjad/llm-debugger): the base model,
+the SFT initialisation, and the RL policies trained from it. Exploratory runs no
 reported figure depends on are not included.
 
 ## Layout
 
-| path | what it is |
+| path | what |
 | --- | --- |
 | `runs/base/` | `Qwen3-Coder-30B-A3B-Instruct`, 8 runs on the 30-task test split |
 | `runs/sft/` | the SFT initialisation, 3 runs on the test split |
-| `runs/rl-gate-arc/` | the RL gate arc, policy v15 through v120 (3 runs each, 8 at v90) |
-| `runs/rl-v90-test/` | RL policy v90, 8 runs on the test split |
+| `runs/rl-gate-arc/` | the RL gate arc, v15 through v120 (3 runs each, 8 at v90) |
+| `runs/rl-v90-test/` | RL policy v90, 8 runs on test |
 | `runs/rl-v90-val/` | RL policy v90, 8 runs on the 40-task validation split |
-| `runs/sft-trajectories/` | the SFT model's evaluation trajectories, turn by turn |
-
-`runs/sft/` is the gate at policy v0, which carries a zero-initialised RFT
-delta, so it measures the frozen SFT model exactly. `runs/sft-trajectories/`
-holds those same three runs turn by turn — every tool call, every observation,
-every edit — rather than as per-defect outcome records.
+| `runs/sft-trajectories/` | the SFT model's runs turn by turn |
 
-A trajectory is paired to its run by the `eval_id` both carry, not by the
-timestamp in the filename: a run directory is named when the run is scheduled
-and the `eval_id` is stamped when it starts, so matching on time shifts every
-run by one.
+`runs/sft/` is the gate at policy v0, which carries a zero-initialised RFT delta,
+so it measures the frozen SFT model exactly.
 
-Each run directory is one gzipped archive, because thousands of small JSON files
-make a Hub repo unbrowsable and the download one request per file. Fields that
-name the run directory, such as `run_dir` in the per-task summary, are rewritten
-to the published name so they resolve against what you extracted.
-`manifest.json` lists every run with its file count and uncompressed size.
+One archive per run. `manifest.json` lists file counts and uncompressed sizes.
+Fields naming the run directory, such as `run_dir`, are rewritten to the
+published name so they resolve against what you extract.
 
 ```bash
 tar -xzf runs/rl-v90-val/v90_val_a_run1.tar.gz
 ```
 
-Inside a run:
-
-| file | what it is |
-| --- | --- |
-| `combined_results.json` | every episode's full `conversation_log` |
-| `<model>.json` | per-defect run records for that arm |
-| `evaluation_summary.json` | solve rate, turns, cost and tokens for the run |
-| `per_task_summary.json` | per-defect outcome for the run |
-
-## Reading these honestly
+Inside a run: `combined_results.json` (full `conversation_log` per episode),
+`<model>.json` (per-defect records), `evaluation_summary.json`,
+`per_task_summary.json`.
 
-Transcripts are model output. They contain wrong diagnoses, abandoned edits and
-failed episodes — that is what they are for. Solve rates come from
-`final_test_passed`, the suite passing after the episode, not from anything the
-model claims about its own work.
+## Reading these
 
-Note that a trajectory file carries `success`, which is **not** the solve
-metric. `success` requires the model to have called `done`; an episode that ran
-to the turn cap with the suite passing has `success: false` and
-`final_test_passed: true`. One of the 90 SFT trajectories published here is
-exactly that case. Score from the run records in `runs/sft/`, and read the
-trajectories for behaviour.
+Solve rate is `final_test_passed`, not anything the model claims. Trajectory
+files carry `success`, which is **not** the solve metric — it requires the model
+to have called `done`, so an episode that hit the turn cap with the suite passing
+reads `success: false` and `final_test_passed: true`. One of the 90 SFT
+trajectories here is that case. Score from the run records; read the trajectories
+for behaviour.
 
-The gate arc is included because it is the evidence for a caveat rather than a
-result. v90 was chosen by stop-at-peak on that arc, and the arc ran on the set
-that is the pristine test split under `defect_split_v2.json`:
+The gate arc is included as evidence for a caveat, not a result. v90 was chosen
+by stop-at-peak on that arc, and the arc ran on the pristine test split:
 
     v0 64.4 | v15 65.6 | v30 63.3 | v45 70.0 | v60 62.2 | v75 72.2 |
     v90 76.7 | v105 68.9 | v120 66.7
 
 So v90's test figure is the argmax of nine noisy draws on the set it was then
-scored against, and the drop to 72.9 at 8 runs per arm is that winner's curse
-resolving. Cite the validation number, 75.9 / 93.1, which did not select the
-checkpoint.
+scored against. Cite the validation number, 75.9 / 93.1.
 
-## Usage
+## Use
 
 ```python
 from huggingface_hub import snapshot_download