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_rc5_release_deployment.py

@@ -62,7 +62,9 @@ def test_runtime_configuration_is_validated_before_container_replacement() -> No
     run_script = (ROOT / "deploy" / "unraid" / "run-dockerman-container.sh").read_text(encoding="utf-8")
 
     validation_index = run_script.index("validate_runtime_config")
-    replacement_index = run_script.index("docker compose down")
+    # The script replaces the container with "docker rm -f"; what matters is
+    # that no removal happens before the runtime config has been validated.
+    replacement_index = run_script.index("docker rm -f geointel")
 
     assert validation_index < replacement_index
     assert "known-default PostGIS password" in run_script