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

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
+36
View File
@@ -10546,3 +10546,39 @@ Decision:
- RC-7 is complete. RC-8 automated frontend and browser release journeys are
active.
## 2026-07-18 - Belgium/North Sea RC-8 release journey automation
Implemented:
- Added four Vitest suites with 12 executable tests for map selection,
coverage resolution, temporal comparison and bootstrap state.
- Added a dry-run-first golden-area operator. It reuses Mol/Kempen and creates
only missing bounded Wallonia, Brussels, language-boundary, coast and
offshore Areas through canonical APIs, with deterministic geometry hashes.
- Added a Playwright release runner and shell wrapper covering every golden
area, governed Mol metrics/provenance, compatible forest history, no-data,
partial coverage, unsupported maritime metrics, simulated provider failure,
persisted map export, real local Ollama context and explicit configured
local YOLO execution.
- Fixed explicit demo seeding so its archived technical project is reactivated
before reuse. A direct service regression protects this lifecycle behavior.
- Added the frontend tests and static E2E/script checks to readiness and copied
the golden-area operator into the all-in-one image.
Validation:
- Repository readiness passed backend compilation, 1,012 backend tests, four
frontend test files with 12 tests, frontend typecheck/build and Alembic head
`202607160001`.
- The live runner completed all Belgium/North Sea journeys against PostGIS
3.6. It persisted an export, received a grounded Ollama answer and completed
configured local YOLO execution through Job and AnalysisRun persistence.
- The successful evidence manifest reports no unexpected browser-console or
failed-request events. Re-running the area operator created zero duplicate
Areas and retained seven unique geometry fingerprints.
Decision:
- RC-8 is complete. RC-9 loading, accessibility and performance hardening is
active.
+28 -2
View File
@@ -151,8 +151,8 @@ editions and licences must still pass source-specific probes before activation.
| RC-5 | complete | deployment, secrets, configuration, fresh install and rollback |
| RC-6 | complete | complete CI, dependency and supply-chain gates |
| RC-7 | complete | critical API envelope typing and contract validation |
| RC-8 | in progress | frontend and browser E2E release journeys |
| RC-9 | pending | loading, accessibility and performance hardening |
| RC-8 | complete | frontend and browser E2E release journeys |
| RC-9 | in progress | loading, accessibility and performance hardening |
| RC-10 | pending | retention, cleanup and national data operations |
| RC-11 | pending | final package, upgrade proof, release tag and handoff |
@@ -428,6 +428,16 @@ offline migration SQL generation.
## RC-8 - Release journey automation
**State: complete.** Four Vitest suites protect selection, coverage, temporal
comparison and bootstrap behavior with 12 tests. The Playwright release runner
provisions seven deterministic land, cross-region, coastal and maritime
golden areas in the national workbench through canonical APIs and executes the complete browser/API
journey against the live PostGIS runtime. Evidence includes governed Mol
metrics and provenance, compatible forest history, no-data, partial coverage,
unsupported maritime metrics, simulated provider failure, persistent export,
real local Ollama context and an explicit configured-YOLO run. The green run
contains no unexpected browser-console or failed-request events.
### Work
- add frontend unit tests for selection, coverage, loading and temporal guards;
@@ -449,6 +459,22 @@ offline migration SQL generation.
- no workflow depends only on source-text assertion tests;
- console and failed-request audits are clean.
### Reproduction
```bash
npm --prefix frontend run test:unit
bash scripts/run_rc8_release_journeys.sh \
http://192.168.10.150:1202 \
artifacts/rc8-release-journeys \
artifacts/rc8-golden-areas.json
```
The second command is intentionally live and mutating. It creates only missing
golden Areas, copies the official Mol/Kempen geometry into the national
workbench with source identifiers, uses the existing explicit demo-fixture flow for AI validation
and writes screenshots plus `manifest.json` under the ignored `artifacts/`
directory.
## RC-9 - UX, accessibility and performance
### Work
+1 -1
View File
@@ -26,7 +26,7 @@ maritieme zones.
bewijzen.
- [x] RC-6: volledige CI, dependency-audit, containerscan en SBOM toevoegen.
- [x] RC-7: kritieke API-routes concrete responsemodellen geven.
- [ ] RC-8: echte frontend- en browser-E2E-releaseflows toevoegen.
- [x] RC-8: echte frontend- en browser-E2E-releaseflows toevoegen.
- [ ] RC-9: loading, toegankelijkheid, widescreen/mobile en performance afronden.
- [ ] RC-10: dataretentie, diskdruk en veilige cleanup operationaliseren.
- [ ] RC-11: fresh install, upgrade, rollback, releasepakket, tag en live