9 Commits

Include renames

Author	SHA1	Message	Date
JensandClaude Opus 5	c6837ec1b2	split the map workspace into a view model and two views ... MapWorkspace.tsx was 3.157 lines: a props interface, 1.200 lines of derived state and handlers, and two complete render paths — the map-first explorer and the advanced workbench behind it. It is now five modules, and the container is nineteen lines that choose between the two. The obstacle was the props signature. The explorer reads 97 derived values and the workbench 40, so passing them individually would have produced a 97-field interface — worse than the file it replaced. Extracting the derived state into a hook that returns one object solves it: MapWorkspaceViewModel is ReturnType<typeof useMapWorkspaceViewModel>, so the shape is derived from what the hook actually produces and cannot drift from it. Each view then names two typed objects, and the JSX moved unchanged. The contract tests found the one place where widening a negative assertion is wrong. "The map workspace performs no transport" was true of the old file and false of the whole feature, because the hooks call the API by design. It is now scoped to the presentational modules, which is what it always meant. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-22 22:38:25 +02:00
JensandClaude Opus 5	9c29577b82	collapse five duplicate overlay blocks into one tested builder ... MapWorkspace held five near-identical useMemo blocks deciding which raster image the map draws under the active theme — terrain, flood depth, thematic raster, WALOUS land cover and bathymetry. Each filtered partitions by source name, read bbox_epsg4326 and assembled the same overlay shape, so the parts that genuinely differ per theme were buried in the repetition. One builder makes the rule testable and leaves only the source, the label and the opacity varying. A raster whose bounds are unusable is now skipped rather than drawn from a partial bbox: an overlay in the wrong place is worse than no overlay. The legend asked "are these thematic or WALOUS overlays" by inspecting two of the five lists. That is a property of the source, so it says so directly. Two contract tests needed fixing rather than repointing. One asserted `"api" not in source.lower()`, which the new hook name useMapImageOverlays matches inside "useM-api-mageOverlays" — as would rapid, capital or therapy. The contract is that this component talks to no API client, so it now says that. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-22 18:56:21 +02:00
Codex	87345f1a8c	feat(ui): redesign GeoIntel as Atlas Workbench	2026-07-19 14:24:54 +02:00
Codex	78a5f0b0b2	Close full operational audit findings	2026-07-17 14:19:02 +02:00
Codex	b5bcd9b041	feat: simplify regional end user workbench	2026-07-14 21:40:32 +02:00
Codex	a3df753732	Polish workbench workspace usability	2026-06-17 20:57:43 +02:00
Codex	ee2929ae83	Refactor workbench into task-based UI shell	2026-06-17 20:39:06 +02:00
Codex	521b06dd1c	Polish workbench UI layout	2026-06-17 18:09:18 +02:00
Codex	acf95905ca	Extract QA and map workbench components	2026-06-17 04:14:35 +02:00