feat: provision regional Kempen context layers

scripts/README.md

@@ -1325,6 +1325,38 @@ buildings from 879 GRB source pages. Its 28 retained partitions produce one
 `e236fa03-7fce-4b37-bc7d-8bddd4d50346`; an immediate repeat run reused the
 same checksums and Dataset instead of fetching or inserting duplicates.
 
+### Regional Kempen GRB roads, water and parcels
+
+Provision the remaining current GRB context snapshots after the scope
+foundation is present:
+
+```bash
+docker exec -it geointel python3 /app/scripts/provision_regional_grb_context.py \
+  --scope kempen-transport-region \
+  --layers roads water parcels
+```
+
+Each theme has an independent manifest and can be resumed or rerun alone:
+
+```bash
+docker exec -it geointel python3 /app/scripts/provision_regional_grb_context.py \
+  --scope kempen-transport-region --layers roads
+```
+
+Use `--fetch-only` to prepare checksummed artifacts without database writes.
+Artifacts are retained below
+`/app/storage/operator-data/regional-themes/kempen-transport-region/<theme>/<date>`.
+The operator follows all OGC API pagination links, fails rather than hiding a
+safety-limit truncation and persists one normal PostGIS dataset per theme via
+DatasetService. Repeat runs reuse valid partitions, combined artifacts and
+datasets; `--force` refreshes the selected observation date.
+
+The semantic limits are deliberate: `Wegsegment` is road-map context rather
+than traffic or routing data; `WTZ`/`WLAS`/`WGR` are heterogeneous water
+objects rather than a volume metric; `ADP` is the graphical presumed cadastral
+parcel location rather than a legal survey. The public GRB provider remains
+`not_configured`, and no fetch runs from the browser or during startup.
+
 ## Tower deployment
 
 Push the local branch to Gitea, then rebuild the Unraid/Tower Docker runtime: