fix: correct supported Python range to 3.12-3.13

The adk (hand-authored framework) needs Python 3.12; only the generated
REST client runs on 3.11. And watchfiles 0.24.0 cannot build on 3.14
(pyo3 0.22.2 maxes at 3.13), so 3.14 was never installable — the test
matrix's 3.14 leg surfaced that pre-existing mis-advertisement.

- requires-python: >=3.11,<4 -> >=3.12,<3.14
- drop Python 3.11 and 3.14 classifiers
- scripts/test matrix: min 3.12, max 3.13
- regenerate uv.lock / requirements-dev.lock for the narrowed range

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: max-parke-scale

pyproject.toml

@@ -48,14 +48,12 @@ dependencies = [
     "opentelemetry-api>=1.20.0",
 ]
 
-requires-python = ">= 3.11,<4"
+requires-python = ">=3.12,<3.14"
 classifiers = [
   "Typing :: Typed",
   "Intended Audience :: Developers",
-  "Programming Language :: Python :: 3.11",
   "Programming Language :: Python :: 3.12",
   "Programming Language :: Python :: 3.13",
-  "Programming Language :: Python :: 3.14",
   "Operating System :: OS Independent",
   "Operating System :: POSIX",
   "Operating System :: MacOS",

requirements-dev.lock

@@ -28,8 +28,6 @@ anyio==4.12.1
     #   watchfiles
 asttokens==3.0.1
     # via stack-data
-async-timeout==5.0.1 ; python_full_version < '3.11.3'
-    # via redis
 attrs==25.4.0
     # via
     #   aiohttp
@@ -441,7 +439,6 @@ typing-extensions==4.15.0
     #   anyio
     #   fastapi
     #   huggingface-hub
-    #   ipython
     #   langchain-core
     #   langchain-protocol
     #   mcp

scripts/test

@@ -10,8 +10,8 @@ export DEFER_PYDANTIC_BUILD=false
 
 # Note that we need to specify the patch version here so that uv
 # won't use unstable (alpha, beta, rc) releases for the tests
-PY_VERSION_MIN=">=3.9.0"
-PY_VERSION_MAX=">=3.14.0"
+PY_VERSION_MIN=">=3.12.0"
+PY_VERSION_MAX=">=3.13.0"
 
 function run_tests() {
     echo "==> Running tests with Pydantic v2"