[davior]

Why

Before #10, renders were written to /data, outside the volume. Every rebuild deleted the files but kept the database rows, so a project's render list offers videos that 404 when played, and "Save to GAM" refuses them.

What

backend/app/render/cleanup.py, run as a module inside the container:

docker compose exec gvc-backend python -m app.render.cleanup            # list only
docker compose exec gvc-backend python -m app.render.cleanup --apply    # delete

• It only checks finished renders (status == "done"), and counts one as orphaned when its video file isn't there. Failed and cancelled renders never had a file, and a running one is still writing it, so all three are left alone.
• By default it only lists. The output shows the renders directory it checked, how many renders have their video and how many don't, and one line per orphan: id, project, version, preview or full, date, and its GAM asset if it was saved there. Deleting can't be undone, and a misconfigured data directory would make every render look orphaned, so the command warns when no render has its video.
• --apply deletes the rows plus any leftover poster or subtitle files. A copy already saved to GAM lives in GAM independently and is untouched.

Testing

• tests/test_render_cleanup.py sets up four renders through the real routes (one with its video, two orphaned, one of them saved to GAM, and one failed). The tests check that the default only lists, that --apply removes exactly the two orphans and their leftover files, and the warning when no video is found.
• I ran the command against a freshly migrated empty database to confirm it runs as a module.
• pytest -q: 665 passed.

---

Generated by Claude Code