feat(scope): make Belgium and North Sea operational default
This commit is contained in:
@@ -11011,3 +11011,31 @@ Validation:
|
||||
passed (12 tests);
|
||||
- live redeployment and a repeated Belgium-scale rectangle follow on the
|
||||
immutable patch revision.
|
||||
## 2026-07-22 - National scope and governed Brussels land cover
|
||||
|
||||
Implemented:
|
||||
|
||||
- made the persisted Belgium/North Sea project the unconditional startup
|
||||
workspace and changed the initial basemap extent and form defaults from Mol
|
||||
to Belgium plus its legally labelled maritime scope;
|
||||
- retained Mol/Kempen provisioning and tests strictly as golden regression
|
||||
evidence instead of product routing;
|
||||
- live-validated the UrbIS WFS `Blocks` contract and added bounded land-cover,
|
||||
FO/GB forest/park and WB permanent-water products with clipped PostGIS area
|
||||
metrics and source-class provenance;
|
||||
- restricted the production model picker to the explicit active model asset
|
||||
and surfaced that the current building model is locally, not nationally,
|
||||
validated.
|
||||
|
||||
Validated during implementation:
|
||||
|
||||
- backend compile and frontend typecheck passed;
|
||||
- 31 frontend unit tests passed;
|
||||
- focused national coverage, model catalog, project lifecycle and Mol golden
|
||||
regression tests passed;
|
||||
- live resolver checks covered Brussels, Wallonia and all three Belgian
|
||||
maritime legal zones. WALOUS, Walloon flood analytics and multi-epoch marine
|
||||
bathymetry remain real open source-integration work and were not simulated.
|
||||
- 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.
|
||||
|
||||
Reference in New Issue
Block a user