Polish GeoIntel workbench and harden Tower deploy
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-28 07:21:48 +02:00
parent 19cf2b5211
commit 438f10fb4b
13 changed files with 1453 additions and 43 deletions
+35
View File
@@ -11633,3 +11633,38 @@ Next gate:
The v6 train/calibration/test/background exports are ready for the next loop
checkpoint; the running v5 iteration remains evidence but cannot supersede
the cleaner v6 corpus.
## 2026-07-28 - Visual release correction (pre-deploy)
- Reviewed the user's consolidated GeoIntel design pass in the running guest
workflow against the live API at desktop, 1024 px laptop and tablet widths.
- Confirmed the revised landing page, guest authentication, map explorer,
full-work-area analysis and quality workspace with browser-rendered evidence.
- Corrected Chromium's internal `details` content-grid behavior so quality
evidence, history and the inspector occupy their intended columns instead of
collapsing into one narrow rail with per-letter filename wrapping.
- Moved the insights panel below the map below 1240 px, kept that combined
workspace internally scrollable and widened the desktop drawer enough to
show complete values such as `5,1% dekking`.
- Guarded optional `scrollIntoView` use so guest login remains functional in
browsers and test environments that do not implement it.
- Preserved the local `frontend-src.tar.gz` transfer archive while excluding it
from Git and Docker build contexts. Restored the explicit
`frontend/node_modules` exclusion required by the Unraid release contract.
- Hardened both Tower wrappers with a scoped untracked-source cleanup after the
remote reset. It removes stale files only from image source directories and
deliberately leaves `.env`, storage, models and PostGIS data untouched.
Verified before deployment:
- `npm run typecheck`
- `npm run build`
- `npm run test:unit` (`43 passed`)
- `py -3 -m pytest -q backend/tests/test_sprint31_unraid_template.py backend/tests/test_docker_runtime_config.py backend/tests/test_sprint193_end_user_workbench.py backend/tests/test_sprint194_regional_timeseries.py` (`56 passed`)
- Browser checks found no horizontal body overflow in the inspected desktop,
laptop and tablet layouts.
Open at this checkpoint:
- Push the verified commit and run the Dockerman-native Tower deployment from
the canonical `/mnt/user/appdata/geointel` checkout.
+9
View File
@@ -971,3 +971,12 @@ This file now starts with the current implementation status. Older preparation/b
- [x] Replace rolling-mosaic training inputs with governed dated 2025 Flanders/Brussels and complete 2023 SPW imagery; retain exact flight-day limitations.
- [x] Reject positive labels over blank/no-data imagery and replace partial SPW 2024 coverage with the complete dated SPW 2023 campaign.
- [x] Exclude GRB/PICC features created after the corresponding dated imagery period while retaining auditable rejection evidence.
# Sprint 229 - Visual release correction and Tower redeploy
- [x] Audit the revised landing page, guest map flow and quality workspace at desktop, laptop and tablet widths.
- [x] Keep the new consolidated GeoIntel design system while correcting the quality-details grid and narrow-laptop result layout.
- [x] Preserve complete insight labels and readable dataset/evidence cards without weakening the map-first workflow.
- [x] Make guest authentication independent of optional browser scrolling support.
- [x] Restore the explicit frontend dependency exclusion required by the Unraid build-context gate.
- [ ] Push the verified release and redeploy the Dockerman-native all-in-one runtime from `/mnt/user/appdata/geointel`.