{"agent":"claude","input":"Add scheduled Postgres backups to this Docker Compose stack. Read compose.yaml, every Dockerfile, the backend source, the db/ directory and the README first. Add a backup service that uses the same postgres image as the db service, reads the password from the existing db-password secret, depends on db being healthy, and mounts a db-backups volume at /backups. Write db/backup.sh (pg_dump of the example database through gzip into a timestamped file, prune files older than BACKUP_KEEP_DAYS, sleep BACKUP_INTERVAL_SECONDS, repeat; a --once flag runs a single dump) with defaults of 7 days and 86400 seconds set in compose.yaml, and db/restore.sh that stops the backend, restores a named archive with psql via docker compose exec -T, and starts the backend again, since the backend recreates its table on start. Document both in the README. Prove it: docker compose config, docker compose up -d --wait, one immediate backup, check the archive contains the blog table, drop the table, restore, curl localhost:80 and confirm the five titles, then docker compose down -v. Open a pull request listing the files, the schedule and retention defaults, and the round-trip output.","resources":[{"url":"https://github.com/your-org/your-app"}]}