feat: add measured detection review loop

docs/AI_PIPELINES.md

@@ -427,6 +427,21 @@ remains available as a higher-precision legacy `0.15` choice. The older
 default-promotion blocker. Every production-like run still requires persisted
 QA/QC against suitable reference data.
 
+The map-driven building workflow uses canonical footprint IoU `0.25`, matching
+the promotion evidence above. A July 2026 Mol-only holdout audit compared
+confidence `0.10` and `0.15` over Achterbos, Gompel, Donk and Postel. Confidence
+`0.15` produced the better F1 in all four positive zones; both thresholds
+produced zero detections in the pure-empty Postel forest control. The active
+confidence therefore remains `0.15`. This result does not claim production
+perfection and does not justify another model-training run by itself.
+
+False-positive and false-negative evidence from persisted detection QA can be
+classified through `detection_reviews`. The queue derives from quality-check
+evidence ids and resolves persisted Detection and reference VectorFeature rows.
+`qa_alignment_mismatch`, `reference_gap_or_change`, uncertain imagery and
+unreviewed items must never be exported as hard-negative or missed-positive
+training labels. Canonical QA metrics remain unchanged after review.
+
 The persisted seven-AOI evidence for this profile contains 5,568 false
 positives among 13,613 candidate detections. The read-only audit command in
 `scripts/README.md` reports the largest review volumes in Turnhout, Herentals