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

Improve useful default workbench context
GeoIntel CI / docs-smoke (push) Has been cancelled
Details
GeoIntel CI / contract-smoke (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Codex
2026-06-22 23:19:35 +02:00
parent 0a5f99d255
commit aaf1299a5d
8 changed files with 96 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CODEX_EXECUTION_LOG.md
+27
View File
@@ -3445,3 +3445,30 @@ Limitations:
Next recommended pass:
- After deploy and live validation, add a raster fixture/demo upload smoke or continue with map evidence overlay affordances for QA/QC.
## Sprint 96 useful default context (2026-06-22)
Changed:
- Added a guarded default dataset effect in `frontend/src/hooks/useDatasetWorkflow.ts`.
- When project data loads and no dataset is selected, the workbench now auto-opens the first ready vector dataset, falling back to any ready dataset and then the first dataset.
- This gives Data, Map and Exports an immediately useful selected dataset/map layer context for the populated demo flow.
- Added explicit no-raster guidance cards to Detection Lab and Segmentation Lab run controls.
- Added `backend/tests/test_sprint96_useful_default_context.py`.
- Updated `CHANGELOG.md`, `docs/TODO.md` and `frontend/README.md`.
Tested:
- Red step: `python -m pytest backend\tests\test_sprint96_useful_default_context.py -q` failed on missing default dataset selection and no-raster AI Lab guidance.
- `python -m pytest backend\tests\test_sprint96_useful_default_context.py -q` (`2 passed`)
- `python -m pytest backend\tests\test_sprint39_frontend_orchestration_hooks.py backend\tests\test_sprint29_dataset_components.py backend\tests\test_sprint88_ai_lab_density.py -q` (`16 passed`)
- `cd frontend && npm run typecheck`
- `cd frontend && npm run build`
Open:
- Full readiness, deploy and live browser validation are still pending for this pass.
Limitations:
- Frontend usability/default-context hardening only; no API contract, persistence, migration, provider fetching or AI/model behavior changes.
- Detection and segmentation remain correctly blocked without a raster dataset.
Next recommended pass:
- After deploy and live validation, add a raster fixture/demo upload smoke so AI Labs and raster controls can be validated with a connected raster state.