fix: enable MCP server after OAuth completion

[Ayushlm10]

Summary

• Fix opencode mcp auth <server> returns "Unexpected status: disabled" after successful OAuth

When running opencode mcp auth <server>, users see:
┌ MCP OAuth Authentication
│
■ Unexpected status: disabled
│
└ Done

I have some MCPs which are disabled by default: enabled:false. The create() function returns { status: "disabled" } for disabled servers, which the CLI doesn't handle.

Toggling the server via /mcp in the TUI works as connect() explicitly sets enabled: true.

FIX:

After successful OAuth completion, always enable the server (If a user is actively authenticating an MCP server, they want it enabled)

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Duplicate PR Detection Results

No duplicate PRs found.

The searches returned only the PR itself (#6960: "fix: enable MCP server after OAuth completion"), which indicates there are no other open or existing PRs addressing the same issue of MCP servers returning "Unexpected status: disabled" after OAuth completion.

The related PRs that appeared in broader searches (#6629 and #5873) are unrelated to this specific MCP authentication fix and don't address the disabled server status issue.

Summary: This appears to be a unique fix addressing a specific bug with disabled MCP servers during OAuth authentication flow. Safe to proceed.