No warning when the MCP package and the Desktop Tools app are different versions #179

What happened

Updating the pinned MCP package in ~/.claude.json:

"args": ["-y", "--package=github:githubnext/desktop-tools#v0.16.1",
         "desktop-tools-mcp"]

…updates only half of the install. /Applications/Desktop Tools.app stayed at
0.14.0, and the socket symlink points into that app bundle:

~/.local/state/desktop-tools/desktop-client -> /Applications/Desktop Tools.app/Contents/MacOS/desktop-tools-client

The MCP server started fine and handshook as desktop-tools 0.16.1, so there
was no indication anything was wrong until the first tool call:

HOST_NOT_SERVING: Desktop Tools isn't serving
~/.local/state/desktop-tools/desktop.sock, so nothing ran.

That message is accurate for "app not running", but it was also the only
symptom of "MCP updated, app did not". Installing the 0.16.1 DMG and launching
it fixed both.

Suggestions

• On connect, compare the MCP package version with the app's
  CFBundleShortVersionString and surface a mismatch (warn, or include both
  versions in HOST_NOT_SERVING).
• Consider mentioning in the README that updating the npx pin does not update
  the .app, since the app is what holds the macOS permissions.

Environment

MCP 0.16.1 via npx, app 0.14.0 then 0.16.1, macOS 27