feat: add map-driven orthophoto analysis

docs/API_CONTRACTS.md

@@ -191,6 +191,36 @@ Response: `DatasetRead` with extracted metadata if supported.
 
 Vector uploads remain stored as original files and are also persisted into `vector_features` as queryable PostGIS state.
 
+### POST `/api/v1/projects/{project_id}/datasets/orthophoto/acquire`
+
+Explicitly acquire a bounded most-recent winter orthophoto selection from the
+official Digitaal Vlaanderen `OMWRGBMRVL` WMS `Ortho` layer.
+
+```json
+{
+  "bbox": {"min_x": 5.10, "min_y": 51.17, "max_x": 5.11, "max_y": 51.18, "crs": "EPSG:4326"},
+  "area_id": "optional-project-area-uuid",
+  "force_refresh": false
+}
+```
+
+The canonical envelope contains a synchronous Job. Its `output_dataset_id`
+identifies the raster Dataset; `result_json` contains provider, layer, pixel
+dimensions, EPSG:4326/EPSG:31370 bounds, sampling resolution, attribution,
+cache reuse and limitation text.
+
+Safety contract:
+
+- every side must measure between 128 m and 1,024 m in EPSG:31370;
+- an optional `area_id` must belong to the project and cover at least 99% of
+  the rectangle;
+- defaults are 1 m/pixel, a 32 MiB response limit and 24-hour exact-request
+  reuse;
+- WMS bytes are georeferenced to EPSG:31370 and persisted only through
+  `DatasetService`; no fetch runs on startup;
+- this is the latest mosaic available at request time, not a historical
+  observation date for every pixel.
+
 ### GET `/api/v1/projects/{project_id}/datasets`
 
 List datasets.