Add regional historical land-use operator

docs/CODEX_EXECUTION_LOG.md

@@ -8808,3 +8808,47 @@ Next:
   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.
+
+## Sprint 209 - Regional historical land-use expansion (2026-07-15)
+
+Implemented:
+- Audited the production Digitaal Vlaanderen Historical Land Use WFS and its
+  1778, 1873 and 1969 collections. Broad regional hit counts stop at 10,000,
+  confirming that one transport-region bounding request is not a defensible
+  completeness strategy.
+- Added `scripts/provision_regional_historical_landuse.py` for historical
+  building, water and road land-use classes over the 28 registered transport-
+  region municipalities. It requires the checksummed VRBG scope artifact and
+  never infers or broadens the regional definition.
+- Added resumable municipality partitions with exact WFS JSON response bytes
+  retained as deterministic gzip artifacts, source/artifact SHA256, request
+  pagination evidence, boundary hashes, clipping diagnostics and combined
+  regional output manifests.
+- Clipped and validated polygonal geometry per municipality, suffixing source
+  ids with NIS codes to prevent cross-boundary collisions. Source identities
+  remain explicitly unstable and do not enable object lineage.
+- Added one canonical Dataset upload per theme/year with regional Area scope,
+  immutable temporal identity, hectare aggregation and methodological warning.
+  No API route, database migration or direct PostGIS write was added.
+- Extended `provision_regional_timeseries.py`, all-in-one packaging, readiness
+  compilation and operator/source documentation.
+
+Validation evidence before live provisioning:
+- Fourteen focused partition, raw-evidence, clipping, assembly, upload,
+  coordinator and packaging tests pass.
+- The official source catalog still reports the production WFS and the three
+  governed historical collections. Live partition provisioning and browser
+  Evolution validation follow in this pass.
+
+Known limitations:
+- Historical `buildings` are mapped built land-use surfaces, not individual
+  building footprints. Historical `roads` and `water` are mapped surfaces,
+  not current centerlines, bathymetry or volume.
+- The three editions use different source maps and cartographic methods.
+  Comparisons are exploratory hectare changes within one series, never a
+  continuous equivalent to modern GRB or 10 m land-use products.
+
+Next:
+- Run the complete nine-snapshot operator on live Tower/PostGIS, verify all 28
+  partition manifests and then validate regional/municipality Evolution in the
+  browser before marking the backlog item complete.