feat: stream municipality vectors by viewport

scripts/README.md

@@ -167,6 +167,28 @@ REAL_REFERENCE_VECTOR_PATH=/mnt/user/appdata/geointel/storage/operator-data/geel
 bash scripts/verify_real_data_detection_qa_workflow.sh http://192.168.10.150:1202
 ```
 
+Reuse the definitive Mol municipality project for a bounded Mol-Centrum
+analysis zone while keeping the municipality-wide reference layer distinct:
+
+```bash
+REAL_PROJECT_ID=d74c1f87-29c0-4c67-adfc-560764f2b80e \
+REAL_PROJECT_NAME='Mol Municipality Workbench' \
+REAL_PROJECT_REGION='Mol, Kempen' \
+REAL_AREA_NAME='Mol Centrum - AI analysezone 500m' \
+REAL_AREA_BBOX='5.113116,51.189653,5.120284,51.194147' \
+REAL_DATASET_NAME_PREFIX='mol_center_ai_500m' \
+REAL_RASTER_PATH=/mnt/user/appdata/geointel/storage/operator-data/mol_orthophoto_wms_512.tif \
+REAL_REFERENCE_VECTOR_PATH=/mnt/user/appdata/geointel/storage/operator-data/mol_grb_gbg_buildings.geojson \
+bash scripts/verify_real_data_detection_qa_workflow.sh http://192.168.10.150:1202
+```
+
+`REAL_PROJECT_ID` is validated through the canonical project endpoint; it does
+not create a shadow validation project. When `REAL_AREA_BBOX` is present, both
+the raster and matching reference upload persist that new Area id. The optional
+safe filename prefix prevents the bounded sample from sharing a display name
+with the complete Mol GRB dataset. The workflow still performs no data fetch or
+model download: the files and configured local model asset must already exist.
+
 Those files are runtime artifacts generated from Digitaal Vlaanderen's
 OMWRGBMRVL WMS `Ortho` layer and GRB OGC API Features `GBG` building collection
 for a small Geel AOI. They are intentionally not repository fixtures.