chore(release): prepare MCP 1.0.11

[escott-]

Bumps the workspace, npm package, MCP Registry metadata, and the boundary self-test to 1.0.11, and adds the 1.0.11 changelog. Covers the account-learning setup and diagnostics controls (#141, #142) and the README install command (#138). Same file set as the 1.0.10 prep (#137).

Verification

On ovh-desktop, against main af908d9 plus this change:

• cargo fmt --all --check
• cargo clippy --locked --workspace --all-targets -- -D warnings
• cargo test --locked --workspace --all-targets: all suites pass

Locally:

• release_contract.py resolve-version . push refs/tags/v1.0.11 returns 1.0.11
• public_boundary.py (on a clean copy of the tracked files) and the three script tests pass
• npm test passes 6/6

GitHub Actions runs on this repo currently fail at startup with no runner (including DCO), so they say nothing about this change.

🤖 Generated with Claude Code

[escott-]

Release review: approve to merge (squash). Checked on ovh-desktop against the PR head (55c55e6 on main af908d9).

• The diff is the standard prep set: Cargo.toml (7 lines), 7 Cargo.lock workspace entries, package.json, server.json ×2, test_public_boundary.py and the CHANGELOG ## 1.0.11 entry (Add explicit account-learning controls to setup and diagnostics #141, Use Deep project learning in setup and diagnostics #142, docs: use the plain curl install command in the README quick start #138).
• cargo clippy --locked --workspace --all-targets -D warnings is clean, and cargo test --locked --workspace passes all 18 suites (mcp-tools 1465, mcp-server 956).
• release_contract metadata and resolve-version return 1.0.11; public_boundary, the 4 script tests and npm test (6/6) pass.
• Wire contract versus the published 1.0.10: capabilities are identical and the tool set is the same 35. The only change is the graph description wording ("Neo4j graph outbox operations" becomes "relationship storage graph outbox operations", from Add explicit account-learning controls to setup and diagnostics #141), and graph.inputSchema is identical.
• HTTP transport: /health and /api/v1/health return 200, /api/v1/tools/{name} is routed, no panic.

🤖 Generated with Claude Code