sol-max-v2 complete (36 ckpts); -data/-record repos; serving note

README.md

@@ -32,9 +32,11 @@ the performance-over-time curve, and sorting ids within a cell sorts them chrono
 | `sol-max` | Codex / gpt-5.6-sol | max | 13 |
 | `opus-high-v1` | Claude Code / claude-opus-5 | high | 3 |
 | `sol-max-opusnode` | Codex / gpt-5.6-sol | max | 9 |
-| `sol-max-v2` | Codex / gpt-5.6-sol | max | 2 (run still live) |
+| `sol-max-v2` | Codex / gpt-5.6-sol | max | 36 |
 
 `opus-high-v1` is the original opus@high; a rerun (v2) is in flight.
+`sol-max-v2` is the sol@max redo that ran the full 100 h after the original died at ~h16;
+it submitted an **h7** checkpoint over 75 further hours of its own training.
 `sol-max-opusnode` is an extra attempt, not one of the 7 plotted cells.
 
 ## Fields
@@ -57,11 +59,41 @@ the performance-over-time curve, and sorting ids within a cell sorts them chrono
 
 | value | n | meaning |
 |---|---|---|
-| `mtime` | 188 | checkpoint dir mtime on the PVC (exact) |
+| `mtime` | 222 | checkpoint dir mtime on the PVC (exact) |
 | `janitor` | 24 | archive timestamps from the arm's `ckpt-janitor.log` (exact) |
 | `extrapolated` | 7 | that family's own step→time cadence; validated against independent local anchors to within ~1.4 h |
 | `unrecoverable` | 15 | local copy pruned, no timing record survives. `hour` is null — use `hour_upper_bound` and step order, or exclude |
 
+## What else is published per cell
+
+Every cell has three companion repos beyond its checkpoints:
+
+| repo | type | contents |
+|---|---|---|
+| `agentic-ptb/{cell}-record` | model | driver trajectory (every turn), harness source, configs, the arm's own evals, RUNLOG, supervisor history |
+| `agentic-ptb/{cell}-data` | dataset | the training corpus the arm built for itself — downloaded, filtered and mixed |
+| `agentic-ptb/{cell}.h*` | model | the checkpoints, indexed here |
+
+Driver credentials are never included in a record repo.
+
+Automated scanners flag credential-shaped strings inside the `-data` corpora. They were
+checked: they are synthetic fixtures belonging to the training tasks themselves
+(secret-scanning exercises whose text embeds fake keys). No project credential is present.
+
+## Serving these checkpoints
+
+`Qwen/Qwen3.5-9B-Base` is `Qwen3_5ForConditionalGeneration` — a **vision** architecture, and
+the vision tower is present in every checkpoint here. prime-rl exports only the text-side
+files, so vLLM fails two different ways unless multimodality is switched off: it first demands
+a `preprocessor_config.json` that was never exported, and if you supply one it dies inside the
+vision kernel (`fmax() missing 1 required positional argument`).
+
+Serve text-only, which is what the arms themselves did:
+
+```
+--limit-mm-per-prompt '{"image": 0, "video": 0}'
+```
+
 ## Before you compare two checkpoints
 
 **Check `eos_ok`.** `248046` is `<|im_end|>`, which the Qwen3.5 chat template ends every