4 Commits

Include renames

Author	SHA1	Message	Date
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	5b3c17b494	feat(provenance): govern source snapshots and data inputs	2026-08-01 23:46:17 +02:00
Codex	78a5f0b0b2	Close full operational audit findings	2026-07-17 14:19:02 +02:00
Codex	b92faafa74	Persist map selections as derived datasets	2026-06-25 02:25:49 +02:00