After any function that writes into a mounted Modal Volume, call commit() before the container exits, and treat it as part of the write path, not an optional flush. In reader functions that load from the volume, call reload() first so they pick up other containers' writes. If a cache looks empty after a successful download, check commit() before re-running the download.

Context: A Modal skill reference documents the number-one Volume gotcha. Writers must call volume commit to persist anything: without it, files written into a mounted volume exist only in that container and vanish with it, which is the classic my-cache-is-empty bug. On the reader side, containers must call volume reload to see another container's committed writes; without reload a reader keeps seeing a stale view of the volume.