Add governed orthophoto release promotion

docs/DATABASE_IMPLEMENTATION_PLAN.md

@@ -291,13 +291,15 @@ annual Dataset, DatasetVersion and vector_features records with
 `source_version=<year>-definitive`. Earlier annual snapshots are retained and
 provisional v1/v2 publications cannot create rows.
 
-The current-orthophoto release preflight likewise adds no lifecycle table or
-migration. It is read-only and creates neither Dataset nor Job. It compares the
-existing local `source_version` with the official `YYYY.NN` catalog edition
-and verifies WMS/WCS/flight-day evidence for one bounded selection. A later
-governed pixel apply must still create an immutable raster Dataset plus
-DatasetVersion through DatasetService and retain that exact edition/evidence;
-direct metadata backfill of legacy `most_recent_at_*` rows is prohibited.
+Current-orthophoto release management likewise adds no lifecycle table or
+migration. Preflight is read-only; stage and named review are filesystem-only.
+Approved apply uploads the exact checksummed EPSG:31370 GeoTIFF through the
+existing dataset endpoint and DatasetService transaction, creating one normal
+immutable raster Dataset and DatasetVersion with official `YYYY.NN`
+`source_version`, temporal flight-date evidence and release provenance.
+Official editions take precedence over legacy rolling markers in catalog
+comparison, but direct metadata backfill, update or deletion of those legacy
+rows remains prohibited.
 
 ## Geometry normalization