Fix clean-install MCP SDK incompatibility

[odfalik]

Release blocker

Published v0.5.1 declares mcp[cli]>=1.0.0. A clean install now resolves MCP 2.1.1, whose mcp.server.fastmcp module intentionally raises a migration error because FastMCP was renamed. The repository lock still held MCP 1.25.0, masking this in existing tests and release CI.

Fix

• constrain the SDK to the v1 API the server implements: mcp[cli]>=1.0.0,<2
• prepare patch version 0.5.2
• add an artifact-based CI smoke test that builds the wheel and launches its CLI through uvx --from <wheel> ... </dev/null, resolving from wheel metadata instead of the repo lock

Evidence

Reproduction from released clean uv tool:

paper-intelligence 0.5.1
mcp 2.1.1
ModuleNotFoundError: No module named 'mcp.server.fastmcp' ... pin 'mcp<2'

Fixed artifact:

Version: 0.5.2
Requires-Dist: mcp[cli]<2,>=1.0.0
CLEAN_INSTALL_CLI_OK

Validation:

• uv lock --check
• non-integration suite: 14 passed
• uv build --wheel succeeded
• uvx --refresh --from <0.5.2 wheel> paper-intelligence </dev/null succeeded from clean artifact resolution
• git diff --check and compileall clean

Hold: Do not merge, tag, or publish until Oded explicitly authorizes the 0.5.2 release.