refactor: finish the AgentHub rename and drop the MCP server

Two leftovers from the rebrand, done together because they touch the same
docs and manifests.

**Data directory.** `agent-dashboard` could not simply be renamed in the
source: it names a real directory holding the live SQLite database. Startup
now moves it once, via `migrateLegacyDataDir()` in `server/lib/claude-home.js`
— a same-filesystem rename, so it is instant even at multiple gigabytes and
cannot leave two divergent copies. `getDataDir()` stays PURE and resolves to
the legacy path until the move happens; the first version of this put the
rename inside the getter, which meant `npm run test:server` relocated the
developer's real database as a side effect. The call sits behind
`require.main === module` and ahead of the router requires, because those pull
in db.js, which opens SQLite at module load. A failed rename is silent and the
old directory keeps being used: an unfashionable directory name beats a blank
database beside an unreachable one. Same treatment for the port-discovery file
(`.agent-dashboard.json` → `.agenthub.json`, old one dropped on write).

Not renamed on purpose: the Sagi localStorage keys (renaming silently resets
everyone's prefs) and the PWA manifest `id` (changing it orphans an installed
app).

**MCP server.** 4 tool calls in 46 days across 577,132 events, against 4,556
lines of TypeScript, a 2 MB committed build artifact, and a pre-commit guard
that had already blocked commits twice. Deleted: `mcp/`, the maintainer skills
and `mcp-reviewer` agent, the build check, `plugins/agenthub/.mcp.json`,
`docs/MCP.md`, 12 npm scripts, 5 Makefile targets, and every doc section
describing it.

Kept, because they are unrelated things sharing the name: the Config
Explorer's MCP tab and its API, per-lane Playwright MCP, the agenthub-config
plugin's MCP audit, and the historical `mcp__plugin_agenthub_*` events that
analytics must keep attributing.

Verified: server 1432/1432, client 459/459, tsc clean, prettier clean. Both
directions of the migration proven — a sandbox-HOME test run leaves the legacy
directory untouched, and a real boot moves it with its contents intact.

server/index.js

@@ -28,6 +28,18 @@ if (!process.env.NODE_ENV) process.env.NODE_ENV = "production";
   }
 })();
 
+// Carry a pre-rebrand `~/.claude/agent-dashboard` over to `~/.claude/agenthub`.
+//
+// Placement is load-bearing in two directions. It must run before the router
+// requires below, because those pull in db.js, which resolves its path and opens
+// SQLite at module load — migrating after that would move the database out from
+// under a live handle. And it must run only when this file *is* the process, not
+// whenever it is required: the test suite imports it dozens of times, and an
+// unguarded call would relocate the developer's real database as a side effect
+// of running `npm test`. It sits after the .env loader so an explicit
+// DASHBOARD_DATA_DIR still suppresses it.
+if (require.main === module) require("./lib/claude-home").migrateLegacyDataDir();
+
 const express = require("express");
 const cors = require("cors");
 const path = require("path");