Fix YOLO class normalization

CHANGELOG.md

@@ -7,6 +7,13 @@
 
 # Changelog
 
+## Sprint 123 YOLO class normalization and real-data inference fix (2026-07-07)
+
+- Fixed configured-YOLO class filtering so model labels such as `Building` match operator/domain filters such as `building`.
+- Persisted configured-YOLO class names as canonical lowercase values while preserving the original model label in detection provenance.
+- Added regression coverage for the mixed-case YOLO class route that caused the Geel real-data smoke to persist zero detections.
+- Confirmed through direct Tower inference that the active local building model returns raw detections on the prepared Geel orthophoto tile; the remaining work is threshold/QA calibration rather than model availability.
+
 ## Sprint 122 Real operator data availability and raster metadata fix (2026-07-07)
 
 - Created Tower operator sample artifacts under `/mnt/user/appdata/geointel/storage/operator-data`:
@@ -15,7 +22,7 @@
 - Fixed raster upload metadata mapping so uploaded rasters persist canonical `bounds_json`, `resolution_json` and `bands_json` from extracted raster metadata.
 - Added regression coverage for raster upload metadata mapping.
 - Deployed the fix to Tower and ran the real-data detection + QA workflow against `http://192.168.10.150:1202`.
-- The workflow passed with persisted raster/reference datasets, tile manifest, AnalysisRun, QualityCheck and detection GeoJSON export. The configured evaluation model returned zero detections on the Geel AOI, so model quality/calibration remains a follow-up.
+- The workflow passed with persisted raster/reference datasets, tile manifest, AnalysisRun, QualityCheck and detection GeoJSON export. A follow-up pass identified case-sensitive class filtering as the reason the initial Geel run persisted zero detections.
 
 ## Sprint 121 Real data detection and QA workflow smoke (2026-07-07)