4 Commits

Include renames

Author	SHA1	Message	Date
NuklearRabbit	7fbb42c9ef	test: align source contracts with modular workbench	2026-08-29 01:52:08 +02:00
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
Codex	78a5f0b0b2	Close full operational audit findings	2026-07-17 14:19:02 +02:00
Codex	de9c11327c	Add map QA evidence drilldown	2026-06-25 02:42:58 +02:00