9 Commits

Include renames

Author	SHA1	Message	Date
Jens	0e3c1b20e9	docs(accuracy): refresh governed scan and training evidence	2026-08-30 06:00:57 +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
JensandClaude Opus 5	6572e4ad5f	scope frontend contracts to the feature, not to one file ... 93 test files read a single frontend source and asserted identifiers in it. The MapWorkspace split showed what that costs: 24 tests went red for a move that changed no behaviour at all. A contract belongs to the feature — a container, its hooks, its domain layer — not to whichever file currently holds it. 232 read sites now resolve through read_feature(). The distinction that makes this safe is direction: a *positive* contract ("this is wired") may widen, because the identifier must still exist somewhere in the feature; a *negative* one ("this component performs no transport") is a statement about one file, and widening it would quietly weaken the check. The 73 single-file reads that remain are exactly those, and a guard now enforces the rule for new tests. Verified rather than assumed: of the 732 migrated positive assertions, 644 still match exactly one module — as specific as before — and the other 86 already spanned a container and its hook by nature. Two apparent misses are an artefact of the checking regex reading an escaped newline literally. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-22 22:05:43 +02:00
Jens	52addf2297	Update	2026-07-27 18:38:52 +02:00
Codex	78a5f0b0b2	Close full operational audit findings	2026-07-17 14:19:02 +02:00
Codex	b50b250f72	feat: simplify regional workbench language	2026-07-14 23:15:50 +02:00
Codex	b5bcd9b041	feat: simplify regional end user workbench	2026-07-14 21:40:32 +02:00
Codex	9fff0c5706	fix: isolate regional project context	2026-07-14 18:41:05 +02:00
Codex	bb7310e015	feat: add official Kempen operating scope	2026-07-14 18:32:32 +02:00