Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Automate RC8 release journeys
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
Details
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
Details
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-18 06:07:44 +02:00
parent 0fae53a7de
commit 55685ba1bd
22 changed files with 2665 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
frontend/README.md
+25
View File
@@ -726,3 +726,28 @@ the active theme as `Beschikbaar`, `Gedeeltelijk`, `Niet gekoppeld` or `Niet
ondersteund`. A coastal or cross-region selection remains visibly split. The
browser never calls NGI, SPW, UrbIS, RBINS or MDK directly and never promotes
an audited catalog entry to operational data without a matching ready Dataset.
## Frontend release tests
Run the deterministic component/hook regression suite locally:
```bash
npm run test:unit
```
Install the browser runtime once and execute the live Belgium/North Sea
journeys from the repository root:
```bash
npx playwright install chromium
bash scripts/run_rc8_release_journeys.sh \
http://192.168.10.150:1202 \
artifacts/rc8-release-journeys \
artifacts/rc8-golden-areas.json
```
The live runner expects a healthy GeoIntel deployment with PostGIS, the
configured local Ollama integration and the configured local YOLO model. It
uses only the explicit technical demo-fixture flow for AI validation. Runtime
screenshots and the machine-readable manifest are ignored build evidence and
must not be committed.