fix(backup): '&&' line-leading in folded YAML crashed the backup service

[CheeryProgrammer]

Problem

The backup service (profiles: ["backup"]) crash-loops and writes zero backups — backups/ stays empty.

Its entrypoint is a > folded scalar, but the inner lines are indented deeper than while true; do, so YAML preserves their newlines instead of folding them to spaces. That leaves && at the start of a line, so /bin/sh reports Syntax error: "&&" unexpected and the container restart-loops. No automated DB backups are taken (data-safety gap).

Fix

Move && to the end of the pg_dump line so it's a valid line continuation (… .sql.gz &&\n echo …), regardless of how YAML folds the block:

-  pg_dump … | gzip > /backups/brainiac-$$ts.sql.gz
-  && echo "backup: wrote brainiac-$$ts.sql.gz";
+  pg_dump … | gzip > /backups/brainiac-$$ts.sql.gz &&
+  echo "backup: wrote brainiac-$$ts.sql.gz";

Verification (real run)

docker compose --profile backup up -d backup:

• Service stays Up (was Restarting).
• Writes brainiac-<ts>.sql.gz (~160 KB); gzip -t passes; content starts -- PostgreSQL database dump.
• Log: backup: wrote brainiac-<ts>.sql.gz — no && syntax error.

One-line compose change; no app/schema impact.

---

🤖 Generated with Claude Code