When Mitto fails to bind the MCP server on the default port (5757) because another instance is already listening, implement dynamic port fallback: try N+1, N+2 up to a configurable limit. Surface the collision clearly to the UI (not just a WARN log) so the user knows which features are degraded and why. Acceptance: (1) Second Mitto instance successfully starts MCP on an alternate port when 5757 is taken. (2) UI shows a warning/badge indicating the alternate MCP port. (3) Session-scoped MCP tools work correctly on the alternate port.
When Mitto fails to bind the MCP server on the default port (5757) because another instance is already listening, implement dynamic port fallback: try N+1, N+2 up to a configurable limit. Surface the collision clearly to the UI (not just a WARN log) so the user knows which features are degraded and why. Acceptance: (1) Second Mitto instance successfully starts MCP on an alternate port when 5757 is taken. (2) UI shows a warning/badge indicating the alternate MCP port. (3) Session-scoped MCP tools work correctly on the alternate port.