What the mjswan demo loads. These files live here rather than in the repository, so a clone stays small and a build fetches what it needs. The scenes mjlab supplies as tasks — G1, Go1, Yam, cartpole — are deliberately not under scenes/: addscenemjlab assembles those from the task itself. What is here is the one scene mjlab has no task for, and the trained policies, which no package ships. Needs pip install mjswan[hf]. Nothing here requires mjlab or torch to load — those are needed only to build a scene from an mjlab task. Every ONNX under checkpoints/ carries mjlab's metadataprops except the two cartpole tasks, whose environment has no robot entity and no jointpos action term for mjlab's…