qwencode: import should also read the Claude-parity project .mcp.json (v0.18.1, code-only surface)

[dyoshikawa]

Background

Carved out of #2507 (its gap 3, explicitly deferred there): Qwen Code v0.18.1 (QwenLM/qwen-code PR #4713, issue #4615) added <projectRoot>/.mcp.json as a Claude-parity project MCP source (packages/cli/src/config/mcpJson.ts normalizes Claude's type-based transport shape; precedence: user settings < .mcp.json < workspace/system settings < --mcp-config; servers untrusted until approved). The surface is implemented in code only — it is not yet in the published mcp.md docs.

rulesync's QwencodeMcp.getSettablePaths returns .qwen/settings.json for both scopes. Generated servers sit at workspace scope and outrank .mcp.json, so nothing rulesync writes is broken — the gap is one-directional: a repo whose servers live in a checked-in .mcp.json is invisible to rulesync import --targets qwencode.

Proposal

Import-only: have the qwencode import path also read <projectRoot>/.mcp.json, merged beneath settings.json (settings win, matching upstream precedence). Do not emit to .mcp.json — that would subject managed servers to the approval gate for no benefit.

Deferred until upstream documents the surface in mcp.md (re-check before implementing).

[dyoshikawa]

Re-checked the deferral condition (2026-07-31): still unmet, keeping this deferred.

• The code surface is still present upstream: packages/cli/src/config/mcpJson.ts exists on QwenLM/qwen-code main (latest release v0.21.2).
• The published MCP docs (docs/users/features/mcp.md) still document only .qwen/settings.json (project) and ~/.qwen/settings.json (user) as MCP configuration sources — no mention of the project-root .mcp.json Claude-parity surface.

Per the deferral note in the issue body, implementation waits until upstream documents the surface in the MCP docs. Will re-check on a future pass.