fix: keep Mol database layers explicit on map

docs/CODEX_EXECUTION_LOG.md

@@ -7510,3 +7510,49 @@ Open:
   guard, suppressed the incorrect empty-layer state and loaded an actual
   viewport slice with `2 visible of 36,941 total features`. No browser warnings
   or errors were recorded.
+
+# Sprint 183 - Mol map source clarity and live AI validation
+
+## Runtime evidence
+
+- Deployed commit `1ba479b` to the all-in-one Tower runtime at
+  `http://192.168.10.150:1202`. The deployment rebuilt the updated
+  `postgres:16-bookworm` GIS runtime and installed the configured CPU AI image.
+- Live migration smoke passed against PostGIS `3.6` with required runtime
+  schema objects, geometry indexes and the single Alembic head
+  `202606120900`. `/health` reported service, backend version and database as
+  healthy.
+- Reused project `d74c1f87-29c0-4c67-adfc-560764f2b80e` and created bounded
+  area `0a38dd7a-d55a-4453-ae59-db8579ed8170` for
+  `Mol Centrum - AI analysezone 500m`.
+- Persisted raster dataset `e9a292e2-57d2-4a85-9df6-32580ba6ea98` and GRB
+  reference dataset `bfc83882-2acc-470d-baec-ee828b4428f8` through the
+  canonical upload and vector persistence paths.
+- Ran local model asset
+  `geointel-building-yolov8s-smallbld-minpx3-img640-ft30-pt` against the
+  persisted tile manifest. Analysis run
+  `97c204cc-bc75-4139-aab5-25397dd0d87e` persisted `36` detections.
+- Quality check `1edb81ec-6799-41c1-ae25-9145f52407bd` persisted `17` matches,
+  `19` false positives and `357` false negatives. Persisted metrics were
+  precision `0.472222`, recall `0.045455`, F1 `0.082927` and mean IoU
+  `0.595803`; the workflow works, but these figures do not justify production
+  model acceptance.
+- Detection export `d18946c4-b7c5-4262-83ad-6c406c6aa59c` was persisted.
+
+## Map-source correction
+
+- Live browser review exposed that the automatically selected detection run
+  could mask an explicitly selected database layer and leave the header at
+  `36 features`. Added a Database/Analysis result source mode and made
+  database selection return to Database mode.
+- Local browser verification then selected the complete
+  `mol_grb_gbg_buildings.geojson` dataset, rendered a real `1,000`-feature
+  PostGIS viewport slice over the OpenStreetMap road basemap, displayed the
+  truncation/zoom guidance, switched to the 36-feature detection overlay and
+  back without state loss, and recorded no console errors.
+
+## Next pass
+
+- Clip detection QA reference populations to actual raster/tile coverage and
+  add box-to-building-footprint matching diagnostics before any further model
+  training or promotion decision.

docs/TODO.md

@@ -21,6 +21,9 @@ This file now starts with the current implementation status. Older preparation/b
 - [x] Make Mol the primary workbench, AOI and operator-sample context while preserving broader Kempen coverage.
 - [x] Add a Mol multi-zone operational pack with independent positive holdouts, background control and persisted map-ready AOIs.
 - [x] Execute the Mol pack on live Tower/PostGIS with real orthophotos, GRB references, configured YOLO, persisted QA/QC and a zero-building background control.
+- [x] Persist and stream the complete official Mol municipality boundary plus all 36,941 clipped GRB buildings through the Map workspace.
+- [x] Run a bounded Mol-center raster, tile, configured-YOLO, persisted detection, GRB QA and export workflow on live Tower/PostGIS.
+- [x] Separate persisted database layers from available analysis-result overlays with an explicit Map content mode.
 - [x] Persist combined Mol operator evidence under the Unraid storage mount so reports survive all-in-one container replacement.
 - [x] Visually review Mol Postel and Donk false-positive/false-negative evidence, classify the dominant error modes and only then decide whether another model-training pass is justified.
 - [ ] Clip detection QA populations to persisted raster/tile coverage and add box-to-footprint matching diagnostics before reconsidering model training.