Add files using upload-large-folder tool

README.md

@@ -40,7 +40,9 @@ m1_mix_submit/
 ├── README.md                                   # this file
 ├── task_instructions.json                      # verbatim --global_task per task + scores
 ├── checkpoint/
-│   └── m1_mix_final_step50000.pt               # 15.3 GB full training checkpoint (see below)
+│   ├── m1_mix_final_step50000.pt.part00 … part03   # 15.3 GB full training ckpt, split into 4×≤4 GB parts
+│   ├── m1_mix_final_step50000.pt.sha256        # SHA-256 of the reassembled checkpoint
+│   └── README_REASSEMBLE.md                    # how to cat the parts back together + verify
 ├── norm_stats/
 │   └── norm_stats.json                         # min-max state/action stats → [-1, 1]
 ├── configs/
@@ -58,7 +60,18 @@ m1_mix_submit/
 
 ### About the checkpoint
 
-`checkpoint/m1_mix_final_step50000.pt` is the **full training checkpoint** at step 50000:
+> **Reassemble first.** The 15.3 GB checkpoint is uploaded as 4 byte-split parts
+> (`m1_mix_final_step50000.pt.part00…03`) because the upload path capped single files at
+> ~9.7 GB. Concatenation reproduces the original **bit-for-bit**:
+>
+> ```bash
+> cat m1_mix_final_step50000.pt.part?? > m1_mix_final_step50000.pt
+> sha256sum -c m1_mix_final_step50000.pt.sha256   # -> m1_mix_final_step50000.pt: OK
+> ```
+>
+> See `checkpoint/README_REASSEMBLE.md` for details.
+
+Once reassembled, `m1_mix_final_step50000.pt` is the **full training checkpoint** at step 50000:
 
 | key                    | content                                                              |
 |------------------------|----------------------------------------------------------------------|

checkpoint/README_REASSEMBLE.md

@@ -0,0 +1,40 @@
+# Reassembling the checkpoint
+
+The full training checkpoint `m1_mix_final_step50000.pt` (15.3 GB) is uploaded as **4
+byte-split parts** because the upload path capped single files at ~9.7 GB. The parts are a
+plain `split -b 4G` of the original file, so concatenating them in order reproduces the
+checkpoint **bit-for-bit**.
+
+| part                                    | size      |
+|-----------------------------------------|-----------|
+| `m1_mix_final_step50000.pt.part00`      | 4.0 GiB   |
+| `m1_mix_final_step50000.pt.part01`      | 4.0 GiB   |
+| `m1_mix_final_step50000.pt.part02`      | 4.0 GiB   |
+| `m1_mix_final_step50000.pt.part03`      | ~2.25 GiB |
+
+## 1. Reassemble
+
+```bash
+cat m1_mix_final_step50000.pt.part?? > m1_mix_final_step50000.pt
+```
+
+(`part??` expands to `part00 part01 part02 part03` in sorted order.)
+
+## 2. Verify integrity
+
+```bash
+sha256sum -c m1_mix_final_step50000.pt.sha256
+# expected:  m1_mix_final_step50000.pt: OK
+```
+
+The expected SHA-256 of the full file is:
+
+```
+df149a0d27c85ad76217552c4005bee0094f6068fdb92bd9f6b256190f5aa09a
+```
+
+## 3. Load
+
+Load as usual — the deploy loader reads `payload["model_state_dict"]` and calls
+`load_state_dict(..., strict=False)`. See the top-level `README.md` for the full
+inference / evaluation instructions and the optional inference-only slimming snippet.

checkpoint/m1_mix_final_step50000.pt.sha256

@@ -0,0 +1 @@
+df149a0d27c85ad76217552c4005bee0094f6068fdb92bd9f6b256190f5aa09a  m1_mix_final_step50000.pt