fix(mcp): reload Claude Code plugins in place instead of restarting

[harrymove-ctrl]

Problem

Two things in the setup skill made a first-time install worse than it needed to be. Both were hit in a real session.

1. Claude Code does not need a restart. The skill ended every install with "fully quit and reopen the AI client, on macOS use Cmd+Q". Claude Code applies a newly installed plugin, its MCP server and its lifecycle hooks with /reload-plugins, in the session the user is already in. Sending a user through a full relaunch is a worse hand-off than one slash command, and it is the last thing they read.

2. Rule 8 made agents give up on a restriction they could clear. An agent running in a sandbox gets EPERM when claude plugin install writes ~/.claude/settings.json, because the CLI stages an atomic write through ~/.claude/.cc-writes/. Rule 8 said "stop at the first real blocker and report the exact failure", so the agent stopped and handed the user a list of commands to paste. That is an environment restriction, not a MemWal fault, and the agent's file-editing tools can usually still write the same files.

Changes

apps/app/public/skills/setup

• Rule 7 now says not to ask for a restart when the client can reload in place, and keeps the restart for the clients that genuinely need it.
• Rule 8 now asks for a workaround before a blocker is reported.
• The Claude Code section hands back /reload-plugins and says explicitly not to tell a Claude Code user to quit with Cmd+Q.
• The Restart section carves Claude Code out.
• New troubleshooting row for the sandboxed-agent EPERM case, with the manual install: the enabledPlugins entry, the extraKnownMarketplaces entry, and the installed_plugins.json v2 record shape.
• The final-report template gains a Claude Code variant that leads with /reload-plugins, plus a rule requiring the agent to disclose any workaround it applied.

docs/mcp/claude-code.md

• The install step is now "Reload and sign in" and uses /reload-plugins.
• The MCP-only tab keeps the restart, and says why /reload-plugins does not cover a plain claude mcp add.
• Troubleshooting: /mcp failures and non-firing hooks both point at /reload-plugins, and a new entry covers the sandboxed EPERM install.

docs/mcp/quickstart.md and docs/mcp/reference.md

• One-line carve-outs so the generic "restart the client" guidance does not contradict the Claude Code page.

Verification

The /reload-plugins behaviour was confirmed against Claude Code 2.1.272, which carries the strings "Run /reload-plugins to activate successfully installed plugins" and "Plugin changes apply when the current response finishes (/reload-plugins is queued)". Its refresh path reconnects plugin MCP servers rather than requiring a new process.

The manual install in the new troubleshooting row was carried out end to end on a sandboxed session. Afterwards claude plugin list reported memwal@memwal-plugins 0.0.13 enabled at user scope, and claude mcp list reported plugin:memwal:memwal connected.

Docs only. No package or runtime code is touched.