Add regional flood hazard provisioning

scripts/README.md

@@ -1579,6 +1579,40 @@ docker exec geointel python /app/scripts/provision_mol_flood_hazards.py --produc
 docker exec geointel python /app/scripts/provision_mol_flood_hazards.py --resolution-m 5 --force
 ```
 
+## Regional VMM flood-hazard scenarios
+
+Provision governed VMM flood-depth scenarios for every persisted municipality
+Area in an approved scope:
+
+```bash
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --scope kempen-transport-region --dry-run
+
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --scope kempen-transport-region
+```
+
+The command requires `provision_geographic_scope.py --scope
+kempen-transport-region` to have created the regional project and member
+Areas. It uses only canonical API calls, validates the backend twelve-product
+registry and runs a full-Area selection smoke after each acquisition. Existing
+scenario Datasets are reused unless `--force` is supplied.
+
+Useful bounded runs while validating source availability:
+
+```bash
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --members Mol --products pluviaal_current_t100
+
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --members Mol,Geel --products pluviaal_current_t10,pluviaal_current_t100
+```
+
+A complete Kempen run plans 28 municipalities times 12 scenario rasters. It can
+take a long time because every VMM WCS tile is bounded, rate-limited and
+validated. This is expected operator work; the app never fetches these rasters
+on page load or map click.
+
 ## Tower deployment
 
 Push the local branch to Gitea, then rebuild the Unraid/Tower Docker runtime: