Backup and restore

The repository's production runbook requires a recoverable PostgreSQL backup and a tested restore path.

A restore exercise should confirm:

• schema/migrations;
• canonical source records;
• source hashes/version lineage;
• audit/event history;
• access controls;
• object storage references;
• queue/worker restart behavior.

The codebase cannot prove cloud-provider backup durability or a production RTO/RPO. Those are deployment/operator responsibilities.

Rollback

Rollback should prefer a known-good application artifact and a forward-compatible database strategy. Destructive database rollback is not assumed to be safe.