Add Mol multi-zone operational validation

scripts/README.md

@@ -203,6 +203,41 @@ GeoJSON files record `reference_pages_fetched`, `reference_truncated`,
 `reference_page_limit`, `reference_max_features` and every fetched
 `source_urls` page for auditability.
 
+Mol has a dedicated operational pack with five positive contexts: center,
+Achterbos residential, Gompel mixed settlement, Donk canal/industrial and
+Postel rural village. The four new contexts are validation holdouts and are not
+silently added to training. Postel-bos remains a separate background control.
+Prepare the 1 km / 1024 px pack explicitly:
+
+```bash
+docker exec -it geointel python3 /app/scripts/prepare_operator_real_data_samples.py \
+  --output-dir /app/storage/operator-data/mol-operational-1024 \
+  --samples mol,mol_achterbos,mol_gompel,mol_donk,mol_postel,postel_bos \
+  --width 1024 \
+  --height 1024 \
+  --half-size-scale 2 \
+  --force
+```
+
+Then run the existing persisted positive QA and background-control paths as one
+operator command:
+
+```bash
+docker exec -it \
+  -e OPERATOR_SAMPLE_MANIFEST_PATH=/app/storage/operator-data/mol-operational-1024/operator_samples_manifest.json \
+  -e MOL_VALIDATION_OUTPUT_DIR=/app/artifacts/mol-operational-validation/current \
+  geointel bash /app/scripts/run_mol_operational_validation.sh http://127.0.0.1
+```
+
+The runner defaults to the active local model at tile `512`, overlap `64`,
+confidence `0.15` and QA IoU `0.25`. Every positive run persists Project, Area,
+Dataset, Job, AnalysisRun, Detection, QualityCheck, Metric and Export records.
+The background run persists its project, AOI, raster, job, analysis and
+detections but intentionally does not invent QA metrics for an empty or sparse
+reference context. The combined JSON/Markdown summary reports
+`evidence_ready`; this records completed evidence and is not an automatic model
+promotion decision.
+
 For model-training candidates, prepare a larger operator-only sample manifest so
 tile overlap can create meaningful context instead of one tile per source
 raster:
@@ -301,6 +336,9 @@ plus a combined `multi_sample_quality_summary.json` with
 `best_overall_by_precision` and `best_by_sample` rankings. It resolves
 container-style `/app/storage/...` manifest paths to repo-relative
 `storage/...` paths when run from the Tower host checkout.
+Manifest-backed runs also persist the declared EPSG:4326 AOI and municipality
+region, and retain municipality/operational-zone metadata in the combined
+summary.
 
 Export the same operator samples to a local YOLO detection dataset when the
 public model candidates are not strong enough for the target imagery: