feat(scope): make Belgium and North Sea operational default

docs/API_CONTRACTS.md

@@ -123,7 +123,7 @@ a canonical operational workspace without depending on its position among
 newer operator or benchmark projects:
 
 ```text
-GET /api/v1/projects?name=Kempen%20Regional%20Workbench&limit=1
+GET /api/v1/projects?name=Belgium%20and%20North%20Sea%20Workbench&limit=1
 GET /api/v1/projects?status=archived&limit=50
 ```
 
@@ -135,7 +135,7 @@ Request:
 {
   "name": "Geel building detection demo",
   "description": "Detect buildings and validate against GRB",
-  "region": "Kempen"
+  "region": "Belgium and Belgian North Sea"
 }
 ```
 
@@ -1202,13 +1202,15 @@ Returns object-detection model capability descriptors.
 
 ### GET `/api/v1/detection/model-assets`
 
-Returns local runtime model files discovered in the configured model directory.
-This is a read-only catalog. GeoIntel never downloads, creates, mutates or
-deletes model weights from this endpoint.
+Returns governed local runtime model files. This is a read-only catalog.
+GeoIntel never downloads, creates, mutates or deletes model weights from this
+endpoint.
 
-The backend scans `YOLO_MODELS_DIR` (default `/app/models`) and reports
-supported local model files such as `.pt`, `.onnx` and `.engine`. The active
-model is the file matching `YOLO_MODEL_PATH`.
+The backend scans `YOLO_MODELS_DIR` (default `/app/models`). When
+`YOLO_MODEL_PATH` resolves to an existing file, production catalog output is
+restricted to that explicitly approved active model. When no active model is
+configured, supported `.pt`, `.onnx` and `.engine` files remain visible for
+development/operator discovery but cannot make the configured detector ready.
 
 Response data:
 
@@ -1226,8 +1228,8 @@ Response data:
       "size_bytes": 123456,
       "sha256": "sha256hex",
       "active": true,
-      "status": "available",
-      "limitation_message": "Local runtime model asset. GeoIntel will not download or mutate model weights.",
+      "status": "approved",
+      "limitation_message": "Approved local runtime model asset. GeoIntel will not download or mutate model weights.",
       "will_download_models": false
     }
   ],
@@ -2217,9 +2219,11 @@ sets an explicit Ollama context window and returns
 
 Returns the governed bathymetry source registry in the canonical envelope.
 VHA inland profiles are `operational`. MDK Belgian Continental Shelf is
-`probe_only`. The pinned SPW Walloon bathymetry archive is `operational`
-through a bounded, explicit operator import. There is no browser-side source
-fetch and no arbitrary source URL.
+`not_configured` by default and becomes `operational` only after the operator
+explicitly enables bounded acquisition and pins a coverage identifier. The
+pinned SPW Walloon bathymetry archive is `operational` through a bounded,
+explicit operator import. There is no browser-side source fetch and no
+arbitrary source URL.
 
 ### GET `/api/v1/projects/{project_id}/datasets/bathymetry/sources/mdk_bcp_bathymetry/readiness`
 
@@ -2227,9 +2231,24 @@ Runs one bounded, read-only WCS 1.0.0 `GetCapabilities` request with mandatory
 system TLS verification and a configured response-size limit. Status is one
 of `disabled`, `invalid_configuration`, `tls_error`,
 `endpoint_unavailable`, `invalid_capabilities` or `reachable`. A reachable
-response lists coverage identifiers, advertised formats and CRS values, but
-always returns `acquisition_supported=false`. There is no insecure TLS
-fallback and no `GetCoverage` request.
+response lists coverage identifiers, advertised formats and CRS values. There
+is no insecure TLS fallback and this readiness endpoint never performs a
+`GetCoverage` request.
+
+### POST `/api/v1/projects/{project_id}/datasets/bathymetry/mdk/acquire`
+
+Runs one explicit, bounded WCS 1.0.0 `GetCoverage` acquisition as a synchronous
+Job. The request contains an EPSG:4326 `bbox`, optional persisted `area_id` and
+`force_refresh`. Acquisition is fail-closed unless
+`MDK_BATHYMETRY_ACQUISITION_ENABLED=true`, a coverage identifier is explicitly
+configured, the strict-TLS readiness probe is reachable and that identifier is
+advertised by the live capabilities document.
+
+The configured bbox-area, response-size, timeout and pixel-dimension limits are
+always enforced. A successful GeoTIFF is validated and imported through the
+existing Dataset raster flow with request hash, response hash, acquisition
+time, MDK attribution and the `LAT` vertical reference in provenance. No depth
+values are synthesized and no water volume is inferred.
 
 ### POST `/api/v1/projects/{project_id}/datasets/bathymetry/profiles/acquire`