Prepare GovOPlaN self-hosted release workflow

docs/DEPLOYMENT_OPERATOR_GUIDE.md

@@ -7,6 +7,30 @@ files.
 
 ## Runtime Configuration Contract
 
+Self-hosted installability follows the staged approach documented in
+`SELF_HOSTED_INSTALLABILITY.md`: generate an explicit env template, validate it,
+run production-like rehearsal with Compose-backed dependencies, then use the
+installer CLI/daemon for package mutation under maintenance mode.
+
+Generate a deployment-local template:
+
+```bash
+cd /mnt/DATA/git/govoplan-core
+./.venv/bin/python -m govoplan_core.commands.config env-template \
+  --profile self-hosted \
+  --generate-secrets \
+  --output .env.self-hosted
+```
+
+Validate the active shell environment before migration or startup:
+
+```bash
+set -a
+. .env.self-hosted
+set +a
+./.venv/bin/python -m govoplan_core.commands.config validate --profile self-hosted
+```
+
 ### Required Runtime Identity
 
 | Setting | Required outside dev | Purpose |
@@ -231,6 +255,16 @@ cd /mnt/DATA/git/govoplan-core
 scripts/launch-production-like-dev.sh
 ```
 
+The helper wrapper provides explicit lifecycle commands:
+
+```bash
+scripts/production-like-dev.sh validate-config
+scripts/production-like-dev.sh seed
+scripts/production-like-dev.sh start
+scripts/production-like-dev.sh stop
+scripts/production-like-dev.sh reset --yes
+```
+
 The launcher uses `dev/production-like/.env` when present, otherwise the checked
 in `.env.example`. It runs: