Automate RC8 release journeys

scripts/README.md

@@ -2036,3 +2036,36 @@ bash scripts/rotate_postgres_password.sh \
 The command atomically updates the operator-owned `.env`, changes the matching
 PostgreSQL role and recreates the container. A failed role change restores the
 previous environment file. The generated secret is never printed.
+
+## RC-8 Belgium/North Sea release journeys
+
+Preview the seven release areas without mutating GeoIntel:
+
+```bash
+python scripts/provision_release_golden_areas.py \
+  --base-url http://192.168.10.150:1202 \
+  --output artifacts/rc8-golden-areas.json
+```
+
+Provision only missing Areas and execute the complete live browser/API release
+journey:
+
+```bash
+bash scripts/run_rc8_release_journeys.sh \
+  http://192.168.10.150:1202 \
+  artifacts/rc8-release-journeys \
+  artifacts/rc8-golden-areas.json
+```
+
+The wrapper runs the same operator with `--apply`, then starts the Playwright
+runner. Mol and Kempen retain their official source Area identifiers while
+bounded copies are made selectable in the national workbench. It validates all
+land, cross-region, coast and maritime golden areas;
+governed metrics and provenance; compatible history; no-data, partial,
+unsupported and provider-failure states; persistent map export; real local
+Ollama context; and the explicit configured-YOLO fixture journey.
+
+The command is intentionally live and creates missing Area records, an export,
+an assistant conversation and explicit technical demo AI records. It never
+fetches fake production provider data. Evidence is written below the requested
+ignored `artifacts/` directory as screenshots plus `manifest.json`.