Add real data detection QA workflow smoke

scripts/README.md

@@ -151,6 +151,27 @@ count is allowed because the demo raster is a synthetic runtime fixture; the
 script validates the operational path and provenance, not production model
 quality. The main readiness gate checks this script's syntax only.
 
+Verify the full operator-provided raster/reference detection and QA path:
+
+```bash
+REAL_RASTER_PATH=/mnt/user/appdata/geointel/data/orthophoto.tif \
+REAL_REFERENCE_VECTOR_PATH=/mnt/user/appdata/geointel/data/reference-buildings.geojson \
+bash scripts/verify_real_data_detection_qa_workflow.sh http://192.168.10.150:1202
+```
+
+The real-data smoke is intentionally mutating and refuses to run without
+operator-supplied files. Current V1 upload support expects a georeferenced
+`.tif`, `.tiff` or `.geotiff` raster and a `.geojson` or `.json` reference
+building vector. The script creates a project, uploads the raster as a source
+dataset, uploads the vector as a `reference` dataset, validates raster/vector
+metadata, tiles the raster, selects a mounted local model asset, verifies
+read-only YOLO preflight, runs configured YOLO detection, runs detection QA
+against persisted `vector_features`, and exports the detection run as GeoJSON.
+It does not seed demo data, enable fixture detections, fetch external data or
+download model weights. A zero detection count is accepted operationally, but
+must be interpreted as model/data quality evidence rather than as a successful
+building extraction result.
+
 Docker images install only the GIS runtime by default. To build a local/Tower
 image with PyTorch/Ultralytics available for the configured-YOLO preflight and
 runtime path, set: