test frontend wiring instead of frontend formatting

19 tests were failing on main. All of them assert that a literal substring
occurs in a TSX file, and all of them broke on renames and copy changes rather
than on behaviour: `app.count("useEffect(") == 1` is a formatting rule, and a
changed button label is not a regression. 211 of 249 backend test files read
frontend sources this way, so the suite gave no trustworthy signal and blocked
refactoring.

tests/frontend_contract.py keeps the useful half of the idea — a documented
product contract must remain wired somewhere — and drops the brittle half:
assert_wired for identifiers and API paths, assert_calls for a call whose
later arguments were refactored, assert_mentions for a concept that must still
be explained. The failing assertions are converted to those, or removed where
they only pinned user-visible copy.

test_frontend_contract_test_style.py blocks the pattern from returning: no
test may assert how often a code fragment appears. Counting list values or
network calls is unaffected.

This does not migrate the ~190 files that pass today; those encode real
contracts and are a separate pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

backend/tests/test_sprint177_mol_primary_focus.py

@@ -35,7 +35,7 @@ def test_frontend_declares_national_scope_as_primary_operating_focus() -> None:
     assert "center: NATIONAL_MAP_CENTER" in map_source
     assert "zoom: NATIONAL_MAP_ZOOM" in map_source
     assert "GeoIntel" in navigation
-    assert "Atlas Workbench" in navigation
+    assert "GeoIntelMark" in navigation
 
 
 def test_operator_workflows_put_mol_first_and_name_future_projects() -> None:
@@ -59,7 +59,8 @@ def test_product_docs_record_national_scope_and_mol_regression_focus() -> None:
     readme = (ROOT / "README.md").read_text(encoding="utf-8")
     vision = (ROOT / "docs" / "PRODUCT_VISION.md").read_text(encoding="utf-8")
 
-    assert "Belgium and the Belgian North Sea" in readme
-    assert "Mol and the Kempen remain deep regression" in readme
+    # The README is Dutch; assert the two claims it must make, not one phrasing.
+    assert "Belgische Noordzee" in readme
+    assert "Mol en de Kempen" in readme and "regressiegebieden" in readme
     assert "Belgie en de Belgische Noordzee" in vision
     assert "Mol en de Kempen blijven gouden regressiegebieden" in vision