Validate wordpress-trac MCP connectivity for milestone metadata (7.1 availability check)

[Copilot]

This PR addresses the issue requirement to exercise the configured wordpress-trac MCP server, enumerate available tools, and determine whether milestone metadata includes WordPress 7.1.
Result: MCP calls executed successfully at the tool layer, but upstream Trac metadata endpoints returned HTTP 403, preventing milestone verification.

• Scope

  • Performed a no-code validation task only; repository contents were left unchanged.

• MCP tool inventory

  • Confirmed available wordpress-trac tools:
    • getChangeset
    • getTicket
    • getTracInfo
    • searchTickets

• Milestone availability check

  • Invoked getTracInfo for milestones (and sanity-checked other metadata types).
  • All metadata calls returned HTTP 403: Forbidden, so WordPress 7.1 milestone presence could not be confirmed from MCP responses.

{
  "id": "milestones",
  "title": "Error loading milestones",
  "text": "Error: HTTP 403: Forbidden. Available types: components, milestones, priorities, severities, types, statuses",
  "url": "https://core.trac.wordpress.org/",
  "metadata": { "error": true }
}