database backups

Determine the engine/version, database identity, configured backup tool, allowed destination and retention policy. Keep credentials in environment or the engine's protected credential mechanism. Prefer an existing verified project runner. Select a format with the required schema/data/large-object coverage and inspect exit status, size and digest. For PostgreSQL custom-format dumps, list the archive with the matching pg_restore; listing alone does not prove restorability. Prove recovery in an isolated disposable database when the task requires a verified backup. Never restore over the source or production database as a test. Record source identity, versions, timestamp, digest, restore result and omitted content in a private receipt. Preserve existing backups and report incomplete coverage. Do not delete backup generations or expose connection strings in reports.

Resolve helper paths from this skill directory. Run project commands from the target workspace.