v1.0.77

v1.0.77

DX: a one-command update and a diagnose command that surfaces the most confusing failure mode - a project-local node_modules/ue-mcp silently shadowing the global install.

CLI

• ue-mcp doctor - read-only diagnosis of every version source: registry latest, npm global, the running server(s) (scanned from process command lines), and the deployed bridge plugin. Flags a project-local node_modules/ue-mcp that shadows the global install (npx runs the local copy, so global updates do nothing), reports the effective version npx would launch, and flags a .mcp.json that uses bare npx ue-mcp - suggesting npx -y ue-mcp@latest so the server self-heals on each launch. (#550)
• ue-mcp update --build - update the npm package, align a stale local shadow to latest, deploy the bridge plugin, rebuild the editor (gated behind --build), then print the doctor table and remind you to relaunch your MCP client. Deploy and build run from the package directly (not via npx), so a local shadow can't intercept them. (#550)

Internals

• The UE_MCP_UPGRADE_AVAILABLE banner now points at ue-mcp update --build and ue-mcp doctor. (#550)