chore: sync homelab ops, identity, and monitoring docs

docs/operations/PD_BACKUP_DEPLOYMENT.md

@@ -68,6 +68,12 @@ Preferred: install in **root's crontab** on PD.
 # END PD BACKUPS
 ```
 
+Quarterly restore verification:
+
+```cron
+30 3 1 */3 * cd /mnt/docker-ssd/docker/compose/automation && /usr/bin/bash bin/run_pd_restore_verification.sh >> /mnt/tank/docker/backups/pd-restore-verify.log 2>&1
+```
+
 ## Post-deploy checks
 
 ```bash
@@ -76,6 +82,22 @@ ls -lh /mnt/tank/docker/backups/db-dumps
 ssh root@10.5.1.5 'find /mnt/user/backups/plausible-deniability -maxdepth 2 -type d | sort | head -40'
 ```
 
+## Restore verification
+
+After the backup path is stable, run the staged restore verifier from PD:
+
+```bash
+cd /mnt/docker-ssd/docker/compose/automation
+/usr/bin/bash bin/run_pd_restore_verification.sh
+```
+
+What it proves:
+
+- the latest configured Postgres dumps can restore into a temporary container
+- a real appdata/config sample can be staged back from Serenity
+- expected files still exist inside the restored sample
+- the latest run state can be exported to Prometheus via node-exporter's textfile collector
+
 ## Important limitations
 
 - Do **not** use `systemctl restart docker` on PD.