[maximusunc]

Summary

In docker compose, the radiator's Postgres kept its data in the named volume radiator-db. That volume is lost on docker compose down -v, on docker volume prune and when Docker Desktop is reset, so the local results history didn't reliably survive.

This PR bind-mounts a host directory instead:

• compose.yml: radiator-db stores its data in ${RADIATOR_DB_DIR:-./data/radiator-db}. The radiator-db named volume is removed.
• .gitignore: ignores data/.
• README.md: the "Stop it" note now says where the data lives and how to wipe it (docker compose down, then delete the directory).

The Helm deployment is unchanged. Its Postgres was already on a PersistentVolumeClaim.

Migrating existing local data

Existing results in the old volume aren't moved automatically. To keep them, copy them across before the next up. The volume is usually named testharness_radiator-db (docker volume ls shows it):

mkdir -p data/radiator-db && docker run --rm -v testharness_radiator-db:/from -v "$PWD/data/radiator-db":/to alpine cp -a /from/. /to/

Testing

• docker compose config validates.
• Not yet run against a live Docker daemon: start the stack, add some data, run docker compose down -v, start it again and check the data is still there.

---

Generated by Claude Code