Extract project workspace hook

2026-06-17 07:31:28 +02:00
parent ea70a77c6f
commit c0216823f2
9 changed files with 257 additions and 132 deletions
@@ -1,3 +1,28 @@
+## Sprint 40 Project workspace hook decomposition (2026-06-17)
+
+Changed:
+- Moved project list/create state, area create state and project-scoped area/dataset loading into `frontend/src/hooks/useProjectWorkspace.ts`.
+- Kept demo workflow orchestration in `App.tsx` because it coordinates project, dataset, QA/QC, detection, segmentation and export selections across multiple hooks.
+- Moved default clip-area fallback selection into `frontend/src/hooks/useDatasetWorkflow.ts`.
+- Moved default map-area fallback selection into `frontend/src/hooks/useMapWorkspaceState.ts`.
+- Extended static frontend orchestration tests to lock these ownership boundaries.
+- Updated frontend README, changelog and TODO status.
+
+Validation:
+- `cd backend && python -m pytest tests/test_sprint39_frontend_orchestration_hooks.py -q` passed: 6 tests.
+- `cd frontend && npm run typecheck` passed.
+- `cd frontend && npm run build` passed.
+
+Open:
+- Full readiness and Tower deploy smoke should run before considering this pass deployed.
+
+Limitations:
+- No UX behavior, API contracts, migrations, provider fetching or AI behavior changed.
+- Demo workflow orchestration remains in `App.tsx` until it can be safely split without obscuring cross-module state updates.
+
+Next recommended pass:
+- Run full readiness and Tower deploy verification, then consider extracting the demo workflow coordinator into a dedicated hook.
+
 ## Sprint 39 Frontend orchestration decomposition (2026-06-17)

 Changed: