fifa17-python: sync tools to running container state

The frozen baseline image predates two hot-patches made in the running
container after build:
* utas_server.py: FUT_MODES-gated offlineSeason block in GetHubData's club
  response (keeps the offline-season summary valid)
* test_hub_offline_season_contract.py added to /app/tools

Sync fifa17-python/tools to the running container (verified byte-identical,
237 files incl. the redir cert pair) and snapshot the live FS as
openfut-fut-backend:python-running-2026-08-10 (docker commit). A fresh build
from the committed sources now reproduces the running backend exactly
(baked SHA256SUMS.txt diffed against the container manifest: identical).

fifa17-recon/docker/fifa17-python/tools/utas_server.py

@@ -1449,8 +1449,23 @@ def hub_data():
     players = len([i for i in STORE.items() if _is_player(i)])
     auctions = len(STORE.listings())
     log("    HUB: clubPlayers=%d auctionCount=%d selling=%d" % (players, auctions, auctions))
-    return {"clubPlayers": players, "auctionCount": auctions,
+    body = {"clubPlayers": players, "auctionCount": auctions,
             "tradePile": {"count": auctions, "selling": auctions, "sold": 0}}
+    if _MODES:
+        # GetHubData's parser 0x180139610 recognises offlineSeason (atom 0x1ec)
+        # and passes it to 0x18013c3a0. The nested scalar fields are STRING
+        # getters, despite representing numbers. Omitting the object leaves the
+        # offline-season summary invalid and the UI aborts before requesting
+        # /season. The initial division matches season_list()/season_user(); the
+        # ten-game length is a live-test hypothesis, isolated behind FUT_MODES.
+        body["offlineSeason"] = {
+            "divisionId": "10",
+            "gamesPlayed": "0",
+            "points": "0",
+            "totalGames": "10",
+            "progressDataVersion": "0",
+        }
+    return body
 
 
 # ---- club stats: the CLUB STATS panel, and probably the MY CLUB tile too ------