Connection is refused and entitlement returns 404 despite an active Unity AI subscription when configuring an external MCP client

How to reproduce:

1. Sign into the Editor with an account that holds an active Unity AI subscription with auto-renewal disabled
2. Create a new project linked to the organization that holds the subscription
3. Install the AI assistant package
4. Open Project Settings > AI > Unity MCP Server
5. Confirm the Unity Bridge status shows Running with integrations green
6. Configure an external MCP client (Claude Code or Codex) using the automatic configurator
7. Attempt to connect the external client and fetch the tool list
8. Observe the Console

Actual result: The relay reports ECONNREFUSED and the Console repeatedly reports “Error: Code 404”
Expected result: The active Unity AI subscription is recognized and no 404 entitlement error is thrown

Reproducible with: 1.0.0-pre.2 (6000.3.17f1), 2.13.0-pre.2 (6000.3.19f1)

Reproducible on: Windows 11 x64
Not reproducible on: No other environments tested

Notes:

• The failure is isolated to the named-pipe V2 bridge used by the external relay, and coincides with the entitlement 404
• The entitlement 404 is a server-side account check and does not clear with Editor or Hub restarts, sign-out, or project reopen