VS Code spawns MCP servers with a bare `python` from PATH, not the
workspace interpreter, so the README's `"command": "python"` snippet
failed with `No module named minecode` on any pipx or venv install.

Lead with `"command": "minecode"` instead — the console script carries
its own interpreter. Keep the module form as a documented alternative
with a warning, and add a troubleshooting row for `-m minecode`, which
is not a valid entry point.

Also convert .vscode/mcp.json from the array form of `servers`, which
VS Code rejects, to the object form.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>