Renames the backup script to match the instance, not the software

backup-slpmodularcms-db.sh named the CMS; this backs up slpsoftware
specifically, same as every other instance-scoped path already does.
Hardcoded in deploy-scp.yaml itself, so this is the actual pipeline
code, not just docs describing it.

aidlc-docs/features/gitea-deployment-workflow/operations/deployment/deployment-instructions.md

@@ -431,7 +431,7 @@ Already built (U5/U6) — this is the read-only walkthrough for whoever operates
 
 ## 4. Database Backup Script
 
-👤 **pi-main / `gitea-workflow`** — create `~/scripts/backup-slpmodularcms-db.sh` on the Pi (this
+👤 **pi-main / `gitea-workflow`** — create `~/scripts/backup-slpsoftware-db.sh` on the Pi (this
 script is host-side by design — never part of this repository, so no DB credential ever reaches
 Gitea):
 
@@ -439,7 +439,7 @@ Gitea):
 #!/usr/bin/env bash
 set -euo pipefail
 
-ENVIRONMENT="${1:?Usage: backup-slpmodularcms-db.sh <environment>}"
+ENVIRONMENT="${1:?Usage: backup-slpsoftware-db.sh <environment>}"
 CREDENTIALS_FILE="$HOME/.config/slpsoftware-db-backup.env"
 
 if [[ ! -f "$CREDENTIALS_FILE" ]]; then
@@ -473,13 +473,13 @@ has the older `mysqldump` name, substitute it — same tool, same flags.
 
 👤 **pi-main / `gitea-workflow`:**
 ```bash
-chmod +x ~/scripts/backup-slpmodularcms-db.sh
+chmod +x ~/scripts/backup-slpsoftware-db.sh
 ```
 
 **Verify once, manually**, before relying on it in a real deploy — 👤 **pi-main / `gitea-workflow`**
 (this matches exactly how `deploy-scp.yaml` itself invokes the script over SSH):
 ```bash
-~/scripts/backup-slpmodularcms-db.sh production
+~/scripts/backup-slpsoftware-db.sh production
 ```
 Confirm a `.sql.gz` file appears under `~/backups/slpsoftware/production/` and that the dump didn't
 silently fail (the script uses `set -euo pipefail`, so a real error does propagate as a non-zero