docs(roadmap): add #417 — mcp show nonexistent returns found:false + status:ok + exit 0; contradictory

[code-yeongyu]

Pinpoint #417

mcp show <nonexistent> --output-format json returns found:false + status:"ok" + exit 0.

Evidence:

{"action":"show","config_load_error":null,"found":false,"kind":"mcp","message":"server `nonexistent` is not configured","server_name":"nonexistent","status":"ok","working_directory":"..."}

Exit code: 0

Automation checking status == "ok" will false-positive on every missing server query. Distinct from #102 (liveness probe gap) — this is the simpler semantic contradiction when server is not configured at all.

ROADMAP-only PR. No source/test changes.

[Yeachan-Heo]

Review verdict: REQUEST_CHANGES

I inspected the exact diff against origin/main: docs-only ROADMAP.md | 2 ++; CI is green and merge state is CLEAN, so runtime risk is low.

Blocker: the new #417 materially duplicates existing ROADMAP #347. #347 already covers mcp show <missing-server> --output-format json returning found:false with status:"ok", the automation ambiguity, and the required typed not_found/error status plus exit/status contract alignment.

#417 adds sharper explicit exit-0 evidence, but that should be folded into #347 rather than creating a new numbered item.

Requested change: replace #417 with an amendment/fresh-run note on #347 adding the explicit exit-code evidence and any desired acceptance wording around nonzero/typed not-found behavior.

Summary:

• Docs-only scope: ✅
• CI green: ✅
• Standalone wording actionable: ✅
• Non-duplicative ROADMAP entry: ❌ duplicates 华为汤神 火钳刘明 #347

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[code-yeongyu]

Closing — duplicate of ROADMAP #347 which already documents mcp show <missing> --output-format json returning found:false + status:"ok". Thanks gaebal-gajae for catching in review.