Keep thematic reference years accurate

2026-07-17 18:45:34 +02:00
parent c28958d9c7
commit 972c3f0e1b
4 changed files with 28 additions and 0 deletions
@@ -10182,3 +10182,21 @@ Validation:
 - The complete local release gate passed 932 backend tests, backend
  compilation, the 116-route contract audit, Alembic head `202607160001`,
  frontend TypeScript typecheck and the production Vite build.
+
+Final live acceptance:
+- The Sprint 237 commits were pushed to Gitea and deployed through the
+  all-in-one Tower flow. Container health, PostGIS 3.6, collation,
+  required schema/indexes, Alembic head `202607160001`, frontend proxy and
+  icon checks passed.
+- Browser acceptance exposed and then closed one usability gap: entering
+  Flanders with an unavailable prior theme now automatically selects the
+  usable ruimtebeslag profile.
+- A complete exact-Area Mol run persisted all five official policy rasters and
+  returned six real themes including the existing VHA partition: 3,638.41 ha
+  ruimtebeslag, 8,139.67 ha open space, an estimated 36,783 inhabitants for
+  2019, mean node value 0.68, mean service level 0.16 and 828 bathymetry
+  profiles. A repeated run reused the retained raster requests.
+- The five new full-Mol Datasets are `ready`, linked to the canonical Mol Area
+  and labelled `coverage_scope=municipality`. The UI reports product reference
+  years directly so an end-of-year UTC timestamp cannot roll 2025 into a
+  misleading local `1 jan 2026` label.