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
JensandClaude Opus 5	5278fcd361	bound the QA evidence overlay and fetch only what it draws ... evidence_geojson emitted one feature per false positive, one per false negative and two per match, with no limit. A regional check of 40k detections against 45k reference footprints produced well over a hundred thousand features in a single response, plus one warning string per unresolvable identifier. The endpoint the entire review workflow depends on therefore failed exactly where review matters most. What to draw is now decided before any geometry is fetched, so the query work is proportional to the result rather than to the size of the check — previously 130k geometries were resolved through an IN clause holding every identifier in the check, to then discard most of them. The budget is split between misses and false positives in proportion to their populations with at least one of each, rather than by strict priority, which would mean a check with 50.000 misses and three false positives never showed one. Confirmations fill what remains, and a match is kept or dropped as a pair because half a match is not reviewable evidence. limit_evidence and evidence_role_counts are removed: plan_evidence supersedes them, and helpers kept alive only by their own tests read like a contract. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-22 15:14:26 +02:00
Codex	0fae53a7de	Harden RC7 API response contracts	2026-07-18 05:07:35 +02:00
Codex	b9674a0e42	Add QA evidence map overlay	2026-06-25 03:17:49 +02:00