Record live Mol flood hazard validation

docs/CODEX_EXECUTION_LOG.md

@@ -8747,7 +8747,7 @@ Implemented:
   remains unavailable.
 - Added a fixed VMM OGRK registry for twelve water-depth scenarios: fluvial and
   pluvial, current climate and climate projection 2050, each at T10/T100/T1000.
-- Added bounded WCS 1.1 retrieval, 10 km tiling, multipart GeoTIFF extraction,
+- Added bounded WCS 1.1 retrieval, provider-safe 5 km tiling, multipart GeoTIFF extraction,
   georeferenced mosaicking, exact persisted-Area clipping and conversion from
   positive source centimetres to normalized metres.
 - Persisted scenario, probability, units, bounds, request URLs and response,
@@ -8762,7 +8762,7 @@ Implemented:
 - Added Docker/Unraid configuration, packaging and focused backend/frontend/AI
   contracts without a new dependency.
 
-Validation evidence before live deployment:
+Validation evidence:
 - Official WCS capabilities and DescribeCoverage confirmed EPSG:31370, 2 m
   GridOffsets, Float32 values, null value 0 and `image/tiff` multipart output.
 - A live bounded VMM request returned valid georeferenced data; official
@@ -8770,8 +8770,30 @@ Validation evidence before live deployment:
   water surface and terrain.
 - Synthetic GIS fixtures confirmed 200 positive 5 m cells at 1 m depth produce
   0.5 ha mapped area and exactly 5,000 m3 maximum-depth area integral.
-- Focused flood-hazard and Ollama tests passed; frontend typecheck and build
-  passed. Full readiness and Tower provisioning follow in this same pass.
+- Full local readiness passed compilation, 679 backend tests, one Alembic head
+  (`202607150001`), frontend TypeScript typecheck/build and shell syntax gates.
+- The first full-Mol WCS smoke exposed the provider's 4.88 MB generated-output
+  limit for a 10 km request. The client now uses 5 km tiles (one million cells
+  at 5 m) and surfaces the official XML exception text. The focused suite
+  directly guards both constraints.
+- Tower deployment passed all-in-one health, PostGIS 3.6 migration/schema
+  smoke, frontend proxy and icon verification.
+- Live provisioning created twelve unique ready Mol Datasets with all governed
+  product keys, twelve DatasetVersions and no `observed_at` values. Every
+  dataset is attached to Area `7233f575-dbac-4e83-b9fa-e3fd99453722`; a second
+  complete run reused all twelve immutable outputs.
+- Full-Mol current pluvial T100 reports 451.0425 ha mapped inundation (3.9376%),
+  mean local maximum depth 0.2419 m, P90 0.4318 m and maximum 2.4809 m. Current
+  fluvial T100 reports 98.805 ha (0.8626%). These remain scenario-bound values,
+  not actual event measurements or permanent water volumes.
+- The raster image endpoint returned a valid 273,330-byte PNG generated from
+  persisted Dataset `5d37d9cb-cad5-446e-bfd9-ec30e308d4bd`; provenance records
+  twelve bounded WCS requests for that scenario.
+- Browser validation confirmed twelve scenario choices, MapLibre overlay,
+  exact full-Area metrics and the volume limitation. A live-discovered theme
+  collision was fixed so `Water` retains GRB water geometry while only
+  `Overstroming` can activate VMM flood rasters. The final 1280 px and 3440 px
+  checks had no horizontal overflow or console warnings/errors.
 
 Known limitations:
 - The scenario raster represents modeled local maximum depth at 1:100,000
@@ -8782,6 +8804,7 @@ Known limitations:
   exposed as a historical temporal series.
 
 Next:
-- Complete live twelve-scenario Mol provisioning and browser validation. After
-  that, treat permanent inland bathymetry as an external-data prerequisite,
-  not as a value derivable from DHMV or the flood-hazard maps.
+- Treat permanent inland bathymetry as an external-data prerequisite, not as a
+  value derivable from DHMV or flood-hazard maps. Continue the independent P5
+  waterbody linkage/uncertainty design only when governed depth profiles exist;
+  otherwise proceed with the regional historical buildings/water/roads backlog.