feat(utas): FIFA17 UTAS migration host + /club adapter mappings

openfut-utas-host: the first live UTAS host. Serves GET /ut/game/<title>/club
from OpenFUT Core via the FIFA17 adapter and reverse-proxies every other UTAS
route verbatim to the Python oracle. Plaintext HTTP/1.1 keep-alive (no TLS);
route classification before execution; a Core error on /club degrades to an
empty page and never falls back to Python. CoreAccess is a host-owned boundary
(the adapter stays transport-agnostic).

openfut-adapter-fifa17::fut: owned_query (wire parse + FIFA id->name mapping,
unknown id = hard error), entities (id<->name from committed tables), and
club_response (FIFA _item shaping; drops items lacking a real FIFA asset id,
never fabricates one).

openfut-core submodule advanced to the reconciled trunk (6acae54 = 8c8a4116
multi-game + eab522a replace_squad/SquadRules + the /club semantic query).
11 host tests + adapter fut tests; 10/10 host mutations killed. rare=SP UNKNOWN.
Retail rendering of Core inventory still blocked on the Core-card->asset-id
identity decision (next phase).

openfut-adapter-fifa17/src/lib.rs

@@ -25,6 +25,9 @@
 //!   Implemented; runtime validated against the retail client.
 //! * [`roster`] — the FUT roster-update response, the last gate before the hub.
 //!   Implemented; not yet runtime validated.
+//! * [`fut`] — FUT/RS4 (UTAS) wire → Core semantic mappings; currently the
+//!   owned-player ("My Squad") search: query parse + FIFA-id→name resolution +
+//!   semantic filter/pagination. Pure mapping; no Rust UTAS host yet.
 //!
 //! Still served only by the Python backend: LSX/Origin (`:4216`), UTAS/RS4
 //! (`:8099`) and POW/EASFC (`:8094`). Roster XML (`:8081`) has an adapter here
@@ -68,6 +71,7 @@
 //! ```
 
 pub mod blaze;
+pub mod fut;
 pub mod redirector;
 pub mod roster;
 pub mod tls;