Add regional flood hazard provisioning

backend/README.md

@@ -1246,6 +1246,37 @@ Run all scenarios for Mol after the regional workspace and Mol Area exist:
 docker exec geointel python /app/scripts/provision_mol_flood_hazards.py
 ```
 
+Provision the same official VMM scenario set for every persisted municipality
+Area in the approved Kempen regional workspace:
+
+```bash
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --scope kempen-transport-region
+```
+
+Inspect the planned municipality/scenario matrix without writing data:
+
+```bash
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --scope kempen-transport-region --dry-run
+```
+
+Useful bounded runs:
+
+```bash
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --members Mol,Geel --products pluviaal_current_t100
+docker exec geointel python /app/scripts/provision_regional_flood_hazards.py \
+  --members 13025 --products pluviaal_current_t10,pluviaal_current_t100
+```
+
+The regional operator uses the canonical API only. It requires the geographic
+scope Areas to exist first, persists one ordinary raster Dataset per
+municipality/scenario and reuses existing Datasets unless `--force` is supplied.
+The full Kempen scope with all products means 28 municipalities times 12
+scenario rasters. This is intentionally explicit operator work, not startup
+work and not a browser-side provider fetch.
+
 Use `--products pluviaal_current_t100`, `--resolution-m 5` or `--force` for an
 explicit subset/refresh. `POST .../raster/flood-hazard/select` returns mapped
 inundated hectares, selection share and local modeled maximum-depth statistics.