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.

plugins/agenthub-dashboard/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agenthub-dashboard",
-  "description": "Direct MCP integration with the AgentHub dashboard — real-time session data access, quick stats, and dashboard health monitoring via Model Context Protocol.",
+  "description": "Direct HTTP integration with the AgentHub dashboard — real-time session data access, quick stats, and dashboard health monitoring via the local Agent Monitor API.",
   "version": "1.0.0",
   "author": {
     "name": "Nguyễn Ngọc Trí Vĩ",
@@ -12,6 +12,6 @@
     "url": "https://git.smartgift.io.vn/Smartgift-AI/Claude-Code-Monitor.git"
   },
   "license": "MIT",
-  "keywords": ["dashboard", "mcp", "connector", "real-time", "monitoring", "claude-code"],
-  "categories": ["integration", "mcp", "monitoring"]
+  "keywords": ["dashboard", "connector", "real-time", "monitoring", "claude-code"],
+  "categories": ["integration", "monitoring"]
 }

plugins/agenthub-dashboard/agents/dashboard-operator.md

@@ -22,13 +22,6 @@ keep the dashboard running and observable. You query the dashboard API at
 data-backed output, and you guide the user through starting, restarting, and
 feeding data into the dashboard.
 
-The MCP server (`agenthub`, pointed at `AGENTHUB_DASHBOARD_URL=http://localhost:4820`)
-ships with the root `agenthub` plugin, not with this one — a marketplace subdirectory
-plugin is cached without `mcp/`, so it cannot carry the server binary. When that
-plugin is installed and the MCP server is connected, you have direct tool access
-to the same dashboard operations — mention it to the user as a faster
-alternative to raw `curl`.
-
 ## Available Data Sources
 
 | Endpoint | Returns |
@@ -70,7 +63,6 @@ alternative to raw `curl`.
 - Use ▲/▼ when comparing values across two probes.
 - Give exact, runnable commands and exact endpoint paths.
 - When the dashboard is DOWN, the first thing you print is how to start it.
-- Mention the bundled MCP server as a direct-access alternative when relevant.
 
 ## Constraints
 

plugins/agenthub-devtools/agents/issue-triager.md

@@ -4,8 +4,8 @@ description: >
   Triages Agent Monitor issues by systematically checking the Express API
   (port 4820), SQLite database (better-sqlite3 with WAL mode), WebSocket
   broadcast, hook handler (scripts/hook-handler.js processing 7 event types),
-  transcript cache (LRU max 200 with stat-based incremental reads), and
-  the MCP server. Classifies by severity and provides specific remediation.
+  and transcript cache (LRU max 200 with stat-based incremental reads).
+  Classifies by severity and provides specific remediation.
 model: sonnet
 tools:
   - Bash
@@ -28,7 +28,6 @@ The Agent Monitor has these components:
 - **Hook Handler** (`scripts/hook-handler.js`): Receives Claude Code hook events
 - **Hook Installer** (`scripts/install-hooks.js`): Configures hooks in `~/.claude/settings.json`
 - **Client** (`client/`): React + Vite SPA on port 5173 (dev) or served by Express (prod)
-- **MCP Server** (`mcp/`): Model Context Protocol integration
 
 ## Investigation Process
 
@@ -78,7 +77,7 @@ For each triaged issue, provide:
 ┌─────────────────────────────────────────┐
 │ Issue: [Brief title]                     │
 │ Severity: P[0-3] [Critical/High/Med/Low] │
-│ Component: [server/client/hooks/db/mcp]  │
+│ Component: [server/client/hooks/db]      │
 │ Status: [investigating/identified/fixed]  │
 └─────────────────────────────────────────┘
 

plugins/agenthub/.mcp.json

@@ -1,11 +0,0 @@
-{
-  "mcpServers": {
-    "agenthub": {
-      "command": "node",
-      "args": ["${CLAUDE_PLUGIN_ROOT}/mcp/build/index.js"],
-      "env": {
-        "AGENTHUB_DASHBOARD_URL": "http://localhost:4820"
-      }
-    }
-  }
-}

plugins/agenthub/commands/agenthub-doctor.md

@@ -1,5 +1,5 @@
 ---
-description: Diagnose a plugin-installed AgentHub — Node, bootstrap, server, hooks, CLI, MCP build
+description: Diagnose a plugin-installed AgentHub — Node, bootstrap, server, hooks, CLI
 ---
 
 Run the diagnostic and report what it found. Do not fix anything unless the user
@@ -18,9 +18,7 @@ Print the output verbatim, then add at most three lines of guidance based on the
   Starting a new Claude Code session removes them automatically (the bootstrap
   backs the file up as `settings.json.agenthub-bak` first).
 - `FAIL Server` or `FAIL Runtime deps` → run `/agenthub-update`, then check
-  `~/.claude/agent-dashboard/runtime/bootstrap.log` and `server.log`.
-- `FAIL MCP build` → `mcp/build/` is out of date; run `npm run mcp:build` in a
-  checkout and commit it.
+  `~/.claude/agenthub/runtime/bootstrap.log` and `server.log`.
 - `WARN agenthub CLI` → print the exact `export PATH=...` line from the output.
 - `WARN Skill plugins` → the pipelines name slash commands no installed plugin
   provides. The dashboard is unaffected; `/agenthub:ship-feature(-lane)` is what

plugins/agenthub/commands/agenthub-open.md

@@ -5,7 +5,7 @@ description: Rebuild the dashboard UI and print its URL
 Rebuild the dashboard bundle, then print the URL. Always forces a rebuild so a
 stale bundle (e.g. after a fix commit landed but the bootstrap's build predates
 it) never serves silently. Also finishes the build if the bootstrap's own
-attempt failed (check `~/.claude/agent-dashboard/runtime/client-build.log`).
+attempt failed (check `~/.claude/agenthub/runtime/client-build.log`).
 
 ```bash
 node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-open.js" --force

plugins/agenthub/commands/agenthub-update.md

@@ -46,4 +46,4 @@ node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-doctor.js"
 ```
 
 Report the final state in a few lines. If the bootstrap failed, quote the
-decisive line from `~/.claude/agent-dashboard/runtime/bootstrap.log`.
+decisive line from `~/.claude/agenthub/runtime/bootstrap.log`.