Raise est_disk_mb 1024->20480 (1->20 GB) for 3 CalibForge clean-fast tasks that hit 'No space left' in 1030c training (torchtitan#309); only calibforge_clean_fast, 3 rows x est_disk_mb, nothing else changed
Drop B10 games_20260611_112034_001 and one CalibForge security row (B19) from calibforge_clean + calibforge_clean_fast (user decision, torchtitan#309); card counts + BUILD_RECORD correction; tars and every other file byte-identical
Five rows to repair after a post-publish verifier audit 2026-10-24: clean 341 -> 340, repair 170 -> 171, calibforge_clean 401 -> 397, calibforge_repair 226 -> 230; the fast copies drop them
Four data files added and README.md updated with the two split entries and the Terminal-Lego section; clean, repair, calibforge_clean, calibforge_repair and metadata/ unchanged.
tb-training-mix-agentpick: CalibForge in two splits of its own (calibforge_clean 240, calibforge_repair 51); clean and repair unchanged; card: CalibForge section and each re-pinned row's Debian release
tb-training-mix-agentpick: req_* takes the maximum across measured sources (our newest, the replay, the upstream agent rollout); 21 SWE rows get more RAM
tb-training-mix-agentpick: directly consumable by the training side -- shard, environment/Dockerfile in every TMAX package, req_* filled from measured peaks; 440 rows, TerminalWorld follows later