v0.5.37

Fixed

• jobd[mcp] no longer installs an SDK it cannot run against. The MCP specification revision 2026-07-28 shipped alongside mcp 2.0.0 on the same day, and the extra's floor-only mcp>=1.0 resolved straight to it. 2.0.0 is a major rework: the low-level Server class still imports, but its @server.list_tools() / @server.call_tool() decorators are gone (replaced by add_request_handler / MCPServer), so build_server() raises AttributeError: 'Server' object has no attribute 'list_tools' and jobd-mcp dies on startup. Verified against PyPI on 2026-07-28: a clean pip install 'jobd[mcp]' pulled mcp-2.0.0 and the entry point failed; with mcp>=1.0,<2 the same install resolves mcp-1.29.0 and prints jobd-mcp ready. Note that the failure is at startup, not import — import jobd.mcp.server succeeds under 2.0.0 because the decorators run inside build_server(), so an import smoke test would have reported this green. The existing tests/mcp suite does call build_server() and would have caught it, but only if CI had ever installed 2.x; the pin is what keeps that from happening by accident. Migrating to the 2.x API is separate work — the deprecations in the new spec carry a twelve-month minimum window, and every jobd MCP surface is stdio, which the stateless-transport changes do not touch.