There's an inconsistency in field naming between MCPServer and MCPRemoteProxy resources:

• MCPServer deprecated port in favor of proxyPort
• MCPRemoteProxy still only has port field

Expected behavior: Both resources should use the same field name (proxyPort) for consistency across the operator API.

Suggested fix: Update MCPRemoteProxy CRD to:

• Add proxyPort field
• Deprecate port field (with same deprecation timeline as MCPServer)
• Support both fields during transition period

Impact: This affects API consistency and user experience when working with different workload types.