Add governed VMM flood hazard scenarios

backend/README.md

@@ -1217,6 +1217,32 @@ Settings: `DHMV_ENABLED`, `DHMV_WCS_URL`, `DHMV_RESOLUTION_M`,
 `DHMV_MIN_SIDE_M`, `DHMV_MAX_SIDE_M`, `DHMV_MAX_PIXELS`,
 `DHMV_TIMEOUT_SECONDS` and `DHMV_MAX_RESPONSE_MB`.
 
+## Governed VMM flood-hazard depth scenarios
+
+`GET /api/v1/projects/{project_id}/datasets/flood-hazard/products` exposes the
+twelve allowlisted VMM OGRK coverages. `POST .../flood-hazard/acquire` performs
+bounded WCS 1.1 requests, exact Area clipping, checksum validation and ordinary
+Dataset/DatasetVersion/Job persistence. The source's positive centimetre
+values are normalized to metres; null/zero cells are transparent nodata.
+
+Run all scenarios for Mol after the regional workspace and Mol Area exist:
+
+```bash
+docker exec geointel python /app/scripts/provision_mol_flood_hazards.py
+```
+
+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.
+The `modelled_max_depth_area_integral_m3` metric is an area integral of local
+maxima and must not be called actual, permanent or concurrent water volume.
+`GET .../raster/flood-hazard/image` serves the constrained transparent PNG.
+
+Settings: `FLOOD_HAZARD_ENABLED`, `FLOOD_HAZARD_WCS_URL`,
+`FLOOD_HAZARD_RESOLUTION_M`, `FLOOD_HAZARD_MIN_SIDE_M`,
+`FLOOD_HAZARD_MAX_SIDE_M`, `FLOOD_HAZARD_MAX_PIXELS`,
+`FLOOD_HAZARD_TIMEOUT_SECONDS` and `FLOOD_HAZARD_MAX_RESPONSE_MB`.
+
 ## Waterinfo station histories
 
 Run the explicit operator after the regional workspace and Mol Area exist: