docs: record live orthophoto analysis proof

docs/CODEX_EXECUTION_LOG.md

@@ -8103,3 +8103,35 @@ Next:
 - Deploy to Tower, execute one bounded Mol rectangle through the real WMS,
   local model and GRB QA, and verify persistence plus browser state before
   accepting the flow as operational.
+
+Live operational proof:
+- Deployed commits `daccd38` and `ec1e1af` to the Tower all-in-one runtime on
+  port 1202. The latter keeps acquisition inside the approved Kempen regional
+  Area while municipality selection remains an independent map filter.
+- A rectangle in Mol fetched a 244 x 207, 1 m/pixel RGB GeoTIFF from the
+  Digitaal Vlaanderen `OMWRGBMRVL` `Ortho` WMS in EPSG:31370. Acquisition job
+  `8f6fd7f6-8f8a-436f-be54-d2c7e28ea250` completed successfully and created
+  Dataset `35f9f72e-edec-4053-887c-f4524222756d` with exactly one immutable
+  DatasetVersion.
+- Existing canonical tiling produced one persisted inference tile. Analysis
+  run `e68a6291-9c46-4f23-832a-3c2b7480f94f` completed with model
+  `yolo-configured` and exactly 78 persisted Detection rows.
+- Existing bounded GRB QA materialized 117 of 466,078 reference buildings for
+  the persisted tile footprint. Quality check
+  `3f1223f0-7dc1-40bb-a48b-910af2a343bf` persisted six Metric rows: 44 matches,
+  34 false positives, 73 false negatives, precision 0.5641, recall 0.3761,
+  F1 0.4513 and mean IoU 0.6622 at IoU 0.50. The result remains explicitly
+  labelled as AI output requiring review.
+- The in-app browser completed the full action, displayed the 78 persisted
+  geometries over the road basemap and reported no console errors. Layout
+  checks passed at 1280 x 720 and 3440 x 1440 without horizontal overflow; at
+  3440 px the MapLibre stage used about 2,408 px.
+- Full readiness passed 588 backend tests, backend compile, one Alembic head,
+  API/document audits, frontend typecheck/build and shell smoke checks. The
+  Tower runtime passed health, PostGIS 3.6, migration/schema/index and reverse
+  proxy validation.
+
+Next:
+- Add a review workflow for accepted/rejected detections and use those audited
+  labels as the gate for model calibration or retraining. Do not present the
+  current F1 score as production-grade accuracy.