Run multilingual audit via serverpillar salt

docs/CI_MULTILINGUAL_AUDIT.md

@@ -55,18 +55,13 @@ The audit summary is interpreted as follows:
 
 This keeps deploys safe without making warning-level cleanup a hard blocker.
 
-## Required Jenkins credential
-Credential location:
-- `Manage Jenkins -> Credentials -> System -> Global credentials`
+## Jenkins requirements
+No dedicated staging SSH credential is required for the multilingual audit stage.
 
-Credential to add:
-- `Kind`: `SSH Username with private key`
-- `ID`: `staging-root-ssh`
-- `Username`: `root`
-- `Private key`: staging SSH key
+The audit runs from the Jenkins built-in node through the same `serverpillar` / Salt transport used by staging deployment.
 
 Current implementation uses the following environment defaults:
-- `STAGING_AUDIT_HOST=root@welkombij.mandelblog.com`
+- `STAGING_AUDIT_MINION=welkombij.mandelblog.com`
 - `STAGING_AUDIT_PROJECT_DIR=/home/www-mandelstudio/mandelstudio`
 - `STAGING_AUDIT_MANAGE=/var/lib/virtualenv/mandelstudio/bin/manage.py`
 
@@ -106,7 +101,7 @@ This happens when the remote audit times out or fails, and is intentional so Jen
 ## Local rerun
 To rerun the same remote audit flow locally:
 ```bash
-export STAGING_AUDIT_HOST='root@welkombij.mandelblog.com'
+export STAGING_AUDIT_MINION='welkombij.mandelblog.com'
 export STAGING_AUDIT_PROJECT_DIR='/home/www-mandelstudio/mandelstudio'
 export STAGING_AUDIT_MANAGE='/var/lib/virtualenv/mandelstudio/bin/manage.py'
 ./scripts/run_remote_multilingual_audit.sh