Packaging fix for v1.1.0, found by building the AUR package locally after the publish.
1.1.0 moved the MCP host surface to SDK v2 (MCPServer, Client) and pinned the extra at mcp>=2, but tests/mcp/test_mcp.py guarded only on import mcp. With an older SDK installed the two v2-only tests failed instead of skipping — and Arch's extra/python-mcp is 1.28.1, while the AUR recipe runs the offline suite against system packages in check(). makepkg on mklang 1.1.0 therefore fails on an up-to-date Arch box. Repo CI cannot see this: it always installs the extra at its declared floor.
- The suite now probes
mcp.server.mcpserver— the v2 module it actually needs — instead of a version string. Verified on the extracted sdist againstmcp==1.28.1: 567 passed, module skipped; unchanged at mcp 2.0. mklang-mcpnames the SDK floor and echoes the import error, so "installed but too old" is distinguishable from "not installed".packaging/arch/PKGBUILDrecords thepython-mcp>=2floor inoptdepends.
No language or interpreter behaviour change; 1.1.0's contents are otherwise unchanged.