/clear and /restart breaks mcp integration

/clear and /restart leave MCP tools broken; only /mcp reload recovers them

Description

After running /clear (and also /restart), MCP tools stop working correctly in the new session. Restarting the CLI process from scratch (full exit + relaunch) works fine, so the issue is isolated to in-process session/state carryover — not the MCP server config itself. Running /mcp reload after /clear or /restart fixes it without needing a full process exit.

Steps to reproduce

1. Start a session with MCP servers configured and working.
2. Use MCP tools normally — confirm they work.
3. Run /clear.
4. Try to use an MCP tool — it fails / tools are unavailable.
5. Run /restart — issue persists.
6. Run /mcp reload — MCP tools work again.
7. Alternatively, fully exit and relaunch the CLI — works fine on first try.

Expected behavior

/clear and /restart should leave MCP tools in the same working state as a fresh CLI launch, without requiring a manual /mcp reload.

Environment

• Copilot CLI version: 1.0.83
• OS: Linux
• Related: possibly same root cause as #4697 (/clear doesn't terminate previous stdio MCP server child processes)

まず、ここで説明されている /clear、/restart、/mcp reload コマンドの処理と、プロセス内の MCP セッション/状態のライフサイクルを追跡します。これらの経路を新しい CLI の起動および関連する issue #4697 と比較します。/mcp reload を必要とせず、/clear と /restart の後も MCP ツールを利用できれば完了です。