Fix MCP timeout handling on Python 3.10; document 3.10 support

Author: beacoder

README.md

@@ -7,7 +7,7 @@ FSM-driven execution · OpenAI-compatible · built for daily use and easy custom
 
 [![CI](https://github.com/beacoder/python-agent-harness/actions/workflows/ci.yml/badge.svg)](https://github.com/beacoder/python-agent-harness/actions/workflows/ci.yml)
 [![PyPI](https://img.shields.io/pypi/v/python-agent-harness.svg)](https://pypi.org/project/python-agent-harness/)
-[![Python](https://img.shields.io/badge/python-3.11%2B-blue)](https://www.python.org/downloads/)
+[![Python](https://img.shields.io/badge/python-3.10%2B-blue)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 
 </div>
@@ -225,7 +225,7 @@ python_agent_harness/
 
 ## Development
 
-Requires Python ≥ 3.11. CI runs against Python 3.11, 3.12, and 3.13.
+Requires Python ≥ 3.10. CI runs against Python 3.10, 3.11, 3.12, and 3.13.
 
 ```sh
 make test                           # unit tests

python_agent_harness/mcp/manager.py

@@ -23,6 +23,7 @@
 from __future__ import annotations
 
 import asyncio
+import concurrent.futures
 import contextlib
 import threading
 import time
@@ -102,7 +103,10 @@ def run(
         while True:
             try:
                 exc = future.exception(timeout=0.1)
-            except TimeoutError:
+            # concurrent.futures.TimeoutError is the builtin TimeoutError on
+            # 3.11+ but a distinct class on 3.10 — catch the futures one so
+            # the poll-timeout branch works on every supported Python.
+            except concurrent.futures.TimeoutError:
                 # future still running: enforce deadline / cancellation
                 if deadline is not None and time.monotonic() >= deadline:
                     future.cancel()