Record live Mol terrain validation

backend/README.md

@@ -1193,6 +1193,13 @@ The default 5 m analysis copy keeps complete-Mol processing bounded while
 retaining native 1 m resolution, EPSG:31370, TAW, `-9999` nodata and the
 2013-2015 acquisition period in provenance.
 
+Municipality-sized requests are split into sequential WCS tiles of at most
+10 km per side. The client sends the explicit media accept header required by
+the production service, waits between requests, retries transient provider
+statuses once and mosaics only tiles that validate against EPSG:31370, one
+band and the requested resolution. Every tile URL and aggregate transfer
+checksum remains in provenance.
+
 Run the complete Mol operator after the regional workspace and Mol Area exist:
 
 ```bash

backend/tests/test_sprint205_dhmv_terrain.py

@@ -422,6 +422,7 @@ def test_frontend_and_runtime_expose_dhmv_workflow() -> None:
     assert "digitaal_vlaanderen_dhmv" in app_source
     assert "Hoogte & reliëf" in map_source
     assert "terrainImageUrl" in map_source
+    assert "analysisMode === 'current' && activeTheme.id === 'buildings' && mapSelectionBbox" in map_source
     assert "selectTerrain" in hook_source
     assert "/raster/terrain/select" in service_source
     for path in (