pub const SIMULATION_IMAGES_DIR: &'static str;Expand description
Simulation billboard-image assets directory (type: "image" environment.json/
task.json objects’ source fields point here) - flat, no per-environment nesting: a
project only ever has one pool of these images, so the earlier shared-vs-env-specific
tiering (mecha10_cli_core::simulation_assets, now removed) was unneeded complexity.
Nested under SIMULATION_DIR (not a top-level assets/ sibling) so mecha10 config push/pull covers it like every other simulation asset - the previous top-level
<project>/assets/ location was never synced anywhere, which silently broke remote RL
training for any environment with an image billboard.