Record live Mol terrain validation

docs/CODEX_EXECUTION_LOG.md

@@ -8690,9 +8690,10 @@ Next:
 Implemented:
 - Added a fixed `dtm_1m`/`dsm_1m` product registry for the official Digitaal
   Vlaanderen production WCS and rejected arbitrary coverage identifiers.
-- Added bounded WCS scaling, multipart GeoTIFF extraction, exact persisted-Area
-  clipping and validation of EPSG:31370, one Float32 band, resolution, nodata
-  and valid cells before canonical DatasetService persistence.
+- Added bounded, rate-limited 10 km WCS tiling, multipart GeoTIFF extraction,
+  georeferenced mosaicking, exact persisted-Area clipping and validation of
+  EPSG:31370, one Float32 band, resolution, nodata and valid cells before
+  canonical DatasetService persistence.
 - Retained response, coverage and normalized-output SHA256 evidence plus native
   1 m resolution, default 5 m analysis resolution, TAW and period 2013-2015.
 - Added exact masked terrain selection with governed height, relief and slope
@@ -8702,9 +8703,28 @@ Implemented:
   readable period/source labels and raster-aware rectangle/full-Area queries.
 - Added `scripts/provision_mol_dhmv.py`, Docker/Unraid settings and documentation.
 
-Initial validation:
-- Focused acquisition, raster, GIS metric, API, frontend and packaging tests
-  pass with deterministic synthetic GeoTIFF fixtures.
+Validation evidence:
+- Full local readiness passed compilation, 669 backend tests, one Alembic head
+  (`202607150001`), frontend TypeScript typecheck/build and shell syntax gates.
+- The production WCS required an explicit `Accept: */*` header and rejected
+  rapid municipality tile requests. The governed client now waits two seconds
+  between requests and retries a transient provider status once. Four real
+  requests produced one `2928 x 3794`, EPSG:31370, 5 m Mol bounding raster
+  before exact municipality masking.
+- Tower deployment passed all-in-one health, PostGIS 3.6 migration/schema
+  smoke, frontend proxy and icon verification.
+- Live DTM Dataset `eccb9174-edb9-4867-928c-9acc5d686fa5` is ready with
+  checksum `9c5f06f5ce2070128aca06e3cbcec00ec8f698bf592c1745245280cd0488ad9b`.
+  Live DSM Dataset `34d1be8e-3a80-4ea3-98e5-238739000524` is ready with
+  checksum `54e36a2aada03f52eb24a7b6af505871d33ed52a5c2af04500793dbfca72f7af`.
+  Both contain 4,581,867 valid 5 m cells and report complete Mol coverage.
+- Full-Mol DTM metrics are mean 31.8985 m TAW, minimum 20.8598 m TAW,
+  maximum 48.4594 m TAW, relief 27.5996 m and mean slope 1.2377 degrees.
+  Re-running the operator reused both immutable datasets.
+- Browser validation selected Mol, activated DTM by default, rendered the
+  colour-relief overlay, returned all terrain metrics, retained the explicit
+  water-depth/volume limitation, showed no horizontal overflow and emitted no
+  browser console warnings/errors.
 - No migration, direct raster database write, LiDAR point-cloud processing or
   water-volume inference was introduced.
 
@@ -8715,5 +8735,5 @@ Known limitations:
   explicit smaller acquisition. DSM-DTM building height remains future work.
 
 Next:
-- Complete the full readiness and live Mol operator/browser validation, then
-  audit P5 bathymetry sources before enabling any water depth or volume metric.
+- Audit P5 official bathymetry and water-depth sources before enabling any
+  water depth or volume metric. Keep DHMV as height/relief input only.