V6.1 continue refining backup: switch to Synology Drive Client for remote backup

docs/production-runbook.md

@@ -21,6 +21,7 @@ This runbook is the operational checklist for releasing and monitoring the trans
 
 1. Deploy artifact/config to target environment.
    - V6.0 Phase 1 production stack: `docker compose -f docker-compose.production.yml up -d --build`
+   - For Runtime Settings writes in production, mount `.env.production` into the app container and set `RUNTIME_SETTINGS_ENV_FILE=/app/.env.production`.
    - For SQLite -> PostgreSQL cutover, run `uv run python tools/export_import_migration.py verify --source-db <sqlite-path-or-url> --target-db <postgres-url>` before switching runtime.
 2. Validate service startup:
    - `/healthz` responds `200`
@@ -36,7 +37,7 @@ This runbook is the operational checklist for releasing and monitoring the trans
    - stdout aggregation receives events
    - file logs are written under `./data/logs`
 5. Create a fresh PostgreSQL backup after successful deployment:
-   - `sh deploy/backup/create_postgres_backup.sh` (creates local DB dump + Synology DB/config/log artifacts + incremental media mirror)
+   - `sh deploy/backup/create_postgres_backup.sh` (creates local DB dump + local incremental uploads mirror under `DATABASE_BACKUP_DIR`)
 
 ## 3. Rollback triggers and actions
 
@@ -108,7 +109,7 @@ This runbook is the operational checklist for releasing and monitoring the trans
 1. Verify `postgres` container is healthy and accepting connections.
 2. Confirm dump file exists and is non-zero size.
 3. Re-run backup/restore scripts with explicit `ENV_FILE` and `COMPOSE_FILE` if using non-default paths.
-4. If Synology copy fails, keep local backup and resolve mount/network before next backup cycle.
+4. If direct Synology copy fails, keep local backup and resolve mount/network before next backup cycle.
    - For LXC setups, use `deploy/backup/mount_synology_cifs.example.sh` as the persistent mount template.
 
 ## 6. Dependency upgrade policy