Add operator hard-negative detection matrix

scripts/README.md

@@ -365,6 +365,29 @@ The expanded 50-epoch candidate improved dense Geel/Mol/Turnhout/Retie scores,
 but the sparse Kasterlee-bos run still showed too many false positives. Treat it
 as the best current experimental dense-AOI candidate, not as a V1 default.
 
+Run a dedicated hard-negative matrix against documented background candidates
+before changing model defaults:
+
+```bash
+OPERATOR_SAMPLE_MANIFEST_PATH=storage/operator-data/operator_samples_manifest.json \
+OPERATOR_BACKGROUND_SAMPLE_SLUGS="postel_bos lommel_heide kasterlee_bos" \
+QUALITY_MODEL_ASSET_IDS="geointel-building-yolov8n-expanded160e50-pt geointel-building-yolov8n-tile30-pt yolov8s-building-segmentation-pt" \
+QUALITY_TILE_SIZES="640" \
+QUALITY_TILE_OVERLAPS="64" \
+QUALITY_THRESHOLDS="0.25 0.15 0.05" \
+HARD_NEGATIVE_OUTPUT_DIR=artifacts/detection-hard-negatives/expanded160e50-live \
+bash scripts/run_operator_hard_negative_detection_matrix.sh http://192.168.10.150:1202
+```
+
+The hard-negative matrix uploads only the background raster, generates tiles,
+runs configured-YOLO detection and counts persisted detections as
+`false_positive_pressure`. It does not upload a reference vector and does not
+run QA/QC, because empty or sparse background AOIs do not have a meaningful
+precision/recall target. In the first live run, `geointel-building-yolov8n-expanded160e50-pt`
+was clean on Postel-bos and Lommel-heide at thresholds `0.25` and `0.15`, but
+produced 38 detections on Kasterlee-bos even at `0.25`. That blocks it from
+becoming a V1 default until a hard-negative-balanced candidate improves.
+
 Export calibration QA evidence for visual review:
 
 ```bash