feat: spawn the Rust companion binaries, not Python scripts

The launcher shelled out to `python3 lsx_responder_v2.py` and `python3 autopatch.py`
from a configured tools directory. Both are now Rust binaries built from this
workspace (openfut-lsx, openfut-autopatch), so the launch contract loses the
interpreter and the script directory entirely: nothing to locate, nothing to
configure, and no way to run a stale checkout's copy of a responder.

Service::script() becomes Service::binary(), and resolve_binary() prefers a sibling
of the running launcher -- what a workspace build and any sane install layout both
produce -- falling back to the bare name so a PATH install still works. It returns the
bare name rather than failing so that spawn() stays the single place a missing binary
is reported, instead of two error paths for one condition.

foreign_pid() now matches an argv entry's FILE NAME rather than a suffix, so
`/path/to/openfut-lsx` matches while an unrelated argument that merely ends with the
same text does not. It deliberately still reads argv and not comm: comm is truncated
to 15 characters by the kernel, which would misreport both of these names -- the same
trap that made an earlier `pgrep -f` guard match its own shell.

Dead configuration removed rather than left vestigial: fifa17_python and
fifa17_tools_dir, their Settings controls, and validate_local_services(), whose only
two checks were those fields. A validation hook that can only return Ok(()) would
claim the launcher verifies local-service configuration when there is none. The
preflight tools-dir gate is gone too, while the ptrace_scope check it gated is kept --
that check is real and repairable via "Arm client"; only the gate died.

The env contract is unchanged, so the binaries are drop-in: LSX still receives
FUT_PERSONA_ID/FUT_PERSONA_NAME (the persona has to agree with Blaze's
LoginResponse.SESS.PDTL and UTAS's userInfo.personaId), autopatch still receives
OPENFUT_AUTOPATCH_LOG under XDG_RUNTIME_DIR and --launcher-pid so it cannot outlive
its owner, and each companion still gets its own process group.

74 tests green.

src/preflight.rs

@@ -88,7 +88,7 @@ impl Check {
 /// Run every applicable check. Order is the order the game exercises them.
 pub fn run(cfg: &LauncherConfig) -> Vec<Check> {
     vec![
-        ptrace_scope(cfg),
+        ptrace_scope(),
         ea_redirect(cfg),
         hostname_mapping(cfg),
         backend_reachable(cfg),
@@ -109,16 +109,12 @@ pub fn warnings(checks: &[Check]) -> usize {
 /// autopatch writes to FIFA's process memory; Yama blocks that unless
 /// `ptrace_scope` is 0. At 1 the patch silently does nothing and the game fails
 /// its TLS handshake much later, with no message naming the cause.
-fn ptrace_scope(cfg: &LauncherConfig) -> Check {
+///
+/// Unconditional. autopatch is a workspace binary that ships alongside the
+/// launcher, so there is no configuration that could make this inapplicable —
+/// every launch runs it.
+fn ptrace_scope() -> Check {
     const NAME: &str = "ptrace_scope (autopatch)";
-    // `fifa17_tools_dir` carries a conventional default, so a non-empty value
-    // does not mean the tools are installed. Key off the directory actually
-    // existing: that is what decides whether autopatch will run at all, and it
-    // keeps this from failing on a machine that never uses local services.
-    let tools = cfg.fifa17_tools_dir.trim();
-    if tools.is_empty() || !std::path::Path::new(tools).is_dir() {
-        return Check::skip(NAME, "no local services installed");
-    }
     match std::fs::read_to_string(PTRACE_SCOPE) {
         Ok(v) => ptrace_verdict(&v),
         // Not every kernel has Yama. Absent means unenforced, which is what we want.
@@ -336,12 +332,19 @@ mod tests {
     fn an_unconfigured_launcher_skips_rather_than_passes() {
         // The distinction that matters: a fresh config must not display a column
         // of green ticks. "Not checked" is not "checked and fine".
+        //
+        // `ptrace_scope` is excluded because it is no longer configuration
+        // dependent: it reads this machine's Yama setting and reports a real
+        // verdict either way. `only_ptrace_scope_zero_lets_autopatch_work`
+        // covers it.
         let mut c = cfg();
-        // `default()` points these at conventional paths whose existence varies
-        // by machine. Pin them so the assertion is about the code, not this box.
-        c.fifa17_tools_dir = "/nonexistent/openfut-tools".into();
+        // `default()` points this at a conventional path whose existence varies
+        // by machine. Pin it so the assertion is about the code, not this box.
         c.fifa_game_dir = "/nonexistent/fifa-game-dir".into();
-        let checks = run(&c);
+        let checks: Vec<Check> = run(&c)
+            .into_iter()
+            .filter(|k| k.name != "ptrace_scope (autopatch)")
+            .collect();
         assert!(
             checks.iter().all(|k| k.state == State::Skipped),
             "{checks:#?}"
@@ -360,16 +363,6 @@ mod tests {
         assert!(ptrace_verdict("1").detail.contains("Arm client"));
     }
 
-    #[test]
-    fn ptrace_is_skipped_when_the_tools_dir_does_not_exist() {
-        // Regression: the gate used to be "is the field non-empty", and the
-        // field has a default — so this check ran (and failed) on machines that
-        // never use autopatch at all.
-        let mut c = cfg();
-        c.fifa17_tools_dir = "/nonexistent/openfut-tools".into();
-        assert_eq!(ptrace_scope(&c).state, State::Skipped);
-    }
-
     #[test]
     fn a_malformed_probe_ip_fails_loudly_instead_of_being_skipped() {
         let mut c = cfg();
@@ -432,13 +425,6 @@ mod tests {
         assert_eq!(hostname_mapping(&c).state, State::Pass);
     }
 
-    #[test]
-    fn ptrace_check_is_skipped_when_local_services_are_not_configured() {
-        let mut c = cfg();
-        c.fifa17_tools_dir.clear();
-        assert_eq!(ptrace_scope(&c).state, State::Skipped);
-    }
-
     #[test]
     fn a_dead_backend_port_is_reported_as_a_failure() {
         let mut c = cfg();