MCP messages adapt to sessions where /mcp can't be run, and reconnecting a disabled server now says so

What

MCP servers connect outside tools to Claude Code. Several MCP messages now use different wording in sessions where Claude Code hides slash-command hints, the same check it uses elsewhere to avoid suggesting commands like /mcp:

• The error for a claude.ai MCP connector that needs connecting drops "(run /mcp to connect it)" in those sessions.
• The text Claude sees about MCP servers that need signing in now has two wordings. One says "Claude cannot start the OAuth flow itself." and points to /mcp. The other keeps the older non-interactive wording, which points to claude mcp or to /mcp in an interactive session.
• In the status summary Claude sees, disabled servers can now be described as "Disabled for this project", telling the user to run /mcp in this project, in a terminal where the session runs. Otherwise the old "Disabled (ask the user to enable via /mcp)" text stays.
• Reconnecting a disabled MCP server now reports that it is disabled. Before, the check tested the wrong value and could never match, so no explanation appeared. In those sessions the message says to run /mcp in the project from a terminal where the session runs; otherwise it keeps the /mcp enable <name> advice.

Why

Claude and Claude Code stop telling people to run a command they may not be able to run from where they are, and reconnecting a disabled server now gives a reason instead of nothing.