Update
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:
Jens
2026-07-27 23:28:43 +02:00
parent 21015757bd
commit c76a746cd7
39 changed files with 3268 additions and 519 deletions
+31
View File
@@ -1,3 +1,34 @@
## 2026-07-27 - Guest demo and product professionalization
- Audited the access experience, workbench information density, responsive
layout and accumulated frontend styling; recorded findings in
`docs/PROJECT_PROFESSIONALIZATION_AUDIT_2026-07-27.md`.
- Added configuration-gated guest access with a short signed session, explicit
guest role, demo-project scope, filtered project listing and backend-enforced
read-only/cross-project restrictions.
- Rebuilt the landing and login hierarchy, added **Als gast verkennen**, mapped
authentication failures to user-facing Dutch messages and improved mobile
navigation and accessibility states.
- Reduced the guest workbench to map exploration and existing quality evidence,
added persistent demo context and removed operator-only controls from the
guest surface.
- Added targeted final layout overrides instead of destructively rewriting the
four historical workbench stylesheets without a complete visual-regression
baseline.
- Added Compose, Unraid, DockerMan and runtime validation settings for guest
enablement. A later packaging follow-up changed the default to enabled whenever
operator authentication is active; installations can still opt out explicitly.
- Validation: 6/6 targeted backend auth/guest tests and 2/2 direct frontend
interaction smokes passed; Python compile, complete frontend TypeScript
typecheck, CSS parsing, Compose YAML, Unraid XML, DockerMan shell syntax and
scoped diff-whitespace checks passed.
- Environment boundary: the supplied frontend dependency tree contains only
Windows-native Rollup/esbuild packages. Vitest and Vite therefore could not
start in this Linux review container, and the available package proxy returned
503 responses/time-outs while fetching Linux replacements. Re-run unit tests
and the production bundle after a clean `npm ci` in the normal Windows or
Linux CI/Docker environment.
## 2026-07-26 - Complete Belgium PyTorch training roadmap
- Added `docs/PYTORCH_TRAINING_ROADMAP_BELGIUM.md` as the executable programme board.