fix(runtime): serialize deploys and clarify regional sources
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s

This commit is contained in:
Codex
2026-07-22 02:36:33 +02:00
parent 0aff8e3b8c
commit 17d4442e60
7 changed files with 111 additions and 2 deletions
+24
View File
@@ -11039,3 +11039,27 @@ Validated during implementation:
- the final repository readiness gate passed with 1,084 backend tests, 31
frontend unit tests, compile, typecheck, production build, Alembic head
`202607160001` and all script syntax/contract checks.
## 2026-07-22 - Live national deployment verification follow-up
Implemented after deploying the national-scope revision:
- reproduced and removed a national UI ambiguity where the Belgium land scope
displayed the final Brussels UrbIS catalog item as the active country-wide
source; multiple applicable regional products are now grouped as an official
source-per-region contract until the actual rectangle resolves its zones;
- added exclusive locks for release deployment and container replacement plus
a bounded wait for Docker's asynchronous removal, after an interrupted Codex
session exposed a concurrent replacement race on Tower.
Live evidence:
- immutable AI image `0aff8e3b8c551a9d1aa29a8495a17e5a858205ab-ai` became healthy on
port 1202 and applied Alembic migrations during startup;
- `scripts/live_migration_smoke.sh` passed against the embedded PostGIS 3.6
runtime with all required tables/indexes and single head `202607160001`;
- the production model catalog exposes exactly the configured approved local
model instead of 25 training artifacts;
- coverage resolution is zone-correct for Brussels, Wallonia and all three
Belgian maritime legal zones. Unimplemented WALOUS, Walloon raster and MDK
acquisition stays explicitly `not_configured`.