chore: bootstrap Atay Makhzan ops repo

docs/RESTORE.md

@@ -0,0 +1,32 @@
+# Restore Notes
+
+Restoring Atay Makhzan can destroy or overwrite live data. Do not run restore actions without explicit owner approval.
+
+## Backup artifacts expected
+
+A complete backup directory should contain:
+
+- `gitea-dump-<timestamp>.zip`
+- `gitea-postgres-<timestamp>.dump`
+- `docker-compose.yml`
+- `app.ini`
+- `metadata.txt`
+- `SHA256SUMS`
+
+## Safer restore principle
+
+Prefer restoring to a fresh VPS or staging directory first, then verifying repository data before touching production.
+
+## High-level restore sequence
+
+1. Provision VPS and install Docker/Nginx.
+2. Restore sanitized Compose configuration.
+3. Restore PostgreSQL dump into a fresh database.
+4. Restore Gitea data from Gitea dump according to the Gitea version documentation.
+5. Start containers.
+6. Verify API, web, SSH auth, and `git ls-remote` on known repositories.
+7. Switch DNS/proxy only after verification.
+
+## Production warning
+
+Do not remove `/opt/gitea/gitea-data` or `/opt/gitea/postgres-data` unless a verified backup exists and Saad explicitly approved the restore.