Add regional flood hazard provisioning

docs/CODEX_EXECUTION_LOG.md

@@ -8940,3 +8940,40 @@ Boundaries and next step:
   governed municipality partitions and measured VMM scenario rasters before
   attempting a full-resolution regional DHMV expansion; no water volume or
   inland bathymetry may be inferred from flood depth.
+
+## Sprint 211 - Regional VMM flood-hazard provisioning support (2026-07-16)
+
+Implemented:
+- Added `scripts/provision_regional_flood_hazards.py`, an explicit operator
+  that resolves the approved geographic scope, validates the fixed twelve-item
+  VMM flood-hazard registry and acquires scenarios per persisted municipality
+  Area through the existing canonical API endpoints.
+- Kept all raster persistence inside the existing `FloodHazardAcquisitionService`
+  and Dataset/DatasetVersion/Job flow. The operator performs no direct WCS
+  requests, no direct PostGIS writes and no browser/startup provider fetching.
+- Added `--dry-run`, `--members`, `--products`, `--force` and
+  `--stop-on-error` controls so Mol, selected municipalities or the complete
+  28-member scope can be run safely and resumed.
+- Added packaging/readiness support so the operator is compiled and available
+  in the all-in-one Unraid image.
+- Documented that regional flood coverage remains municipality-partitioned
+  because one monolithic Kempen raster would exceed practical WCS/pixel limits.
+
+Validation:
+- Focused tests cover product/member resolution, dry-run planning, canonical
+  acquisition/selection calls and release packaging.
+
+Known limitations:
+- This pass adds the operational regional provisioner and validation contract.
+  A complete live run of all 336 municipality/scenario acquisitions is long
+  operator work and should be launched deliberately on Tower after reviewing
+  the dry-run matrix.
+- VMM flood depth remains modelled local maximum scenario depth. GeoIntel still
+  must not expose permanent waterbody volume, current water level or
+  bathymetry from this source.
+
+Next:
+- Run the regional VMM operator first for Mol/Geel with `pluviaal_current_t100`
+  on Tower, then expand to the full twelve-scenario municipality matrix if the
+  provider remains stable. After that, prioritize regional DHMV DTM/DSM with
+  the same partitioned operator discipline.