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.
5.1 KiB
Documentation Map
Authoritative inventory of this repository's documentation surface: every doc that must be kept in sync, what each contains, and the stable anchors to grep for when placing an edit. Section line numbers drift — grep the anchor strings, don't trust line numbers.
Tier 1 — primary, always consider
README.md (English, canonical)
The source of truth most other docs mirror. Key sections:
- Feature table — rows like
**Kanban Board**,**Transcript Cache**,**Pre-Existing Session Detection**,**Continuous Project Sync**. Grep a neighboring row label. - Data-flow numbered list — bullets describing hook ingestion, the watchdog, periodic sweep, continuous sync. Grep
Error detection watchdog/periodic server sweep. - Agent State Machine + Session State Machine — two
mermaid stateDiagram-v2blocks. GrepstateDiagram-v2. - Hook Events table —
| Hook Type | Trigger | Dashboard Action |. ListsSessionStart…SessionEnd, plus syntheticCompaction,APIError,TurnDuration,ToolError,Interrupted. Grep## Hook Events. - Configuration / Environment Variables table —
| Environment Variable | Default | Description |. GrepDASHBOARD_PORTorDASHBOARD_HOST.
Translations
This build ships English only. README-VN.md, README-CN.md and README-KO.md were removed, as were the zh and ko UI locales — do not recreate them.
Standalone full translations of README.md. Every README change must be mirrored here at the corresponding section. Conventions:
- Keep in English/code: identifiers, env-var names, event-type names,
awaiting_input_since,pendingInterrupt, "watchdog",fs.watch, model IDs, mermaid transition labels. - Translate prose. "Waiting" → Đang chờ (vi) / 等待中 (zh) / 대기 중 (ko). "watchdog" often kept; in zh sometimes 看门狗.
ARCHITECTURE.md
- Module responsibility table — one row per source file (
scripts/import-history.js,lib/transcript-cache.js,routes/hooks.js,server/index.js, …). Update the row whose file you changed. Grep the file path. - Data-flow + sequence diagrams, state machines, Continuous background sync prose block (grep
Continuous background sync). - Event types line — grep
| Event types |. - ERD / schema mermaid +
event_type "PreToolUse|PostToolUse|Stop|etc".
server/README.md
Backend reference: routes table, Error Detection Watchdog / User-Interrupt (Esc) Recovery / Continuous Project Sync sections, Agent/Session lifecycle mermaid diagrams, Environment Variables bash block under ## Deployment. Update for any backend behavior, route, state, env var, or background service.
client/README.md
Frontend reference: component list, Event Types table (WebSocket broadcast message types like session_created, agent_updated), session/agent status TypeScript unions. Update for new WS message types or client-facing behavior. NOT needed for server-only changes the UI already renders generically.
docs/HOOKS.md
Per-hook deep reference (### 1. SessionStart … ### 8. SessionEnd), the awaiting_input_since overlay rules, the "User interrupts (Esc) — no hook fires" section, transcript-derived sync. Update for any hook semantics or state behavior.
docs/DATABASE.md
Schema reference: sessions / agents / events tables, column docs, status CHECK constraints, lifecycle mermaid diagrams. Update for schema or state-machine changes.
docs/API.md
REST API reference (endpoints, params, example responses). Update for route/response changes. Pair with server/openapi*.js (code, not docs).
docs/PLUGINS.md
Plugin/marketplace docs incl. an Event Types enumeration line — keep it in sync with the canonical event-type list.
docs/I18N.md
i18n architecture: Supported languages list, supportedLngs, the 15 namespaces. Update when adding a language or namespace. Client UI strings live in client/src/i18n/locales/{en,zh,vi}/*.json (code).
Tier 3 — situational
.env.example— every env var belongs here with a sane default + comment.INSTALL.md,SETUP.md— install/run commands.CLAUDE.md,AGENTS.md— agent working guides; update when commands, file locations, or workflows change.docs/README.md— docs index; add a link when a newdocs/*.mdis created.vscode-extension/README.md,statusline/README.md— surface-specific; update only when that surface changes.
Consistency invariants
- The event-type set must match across:
READMEhook table,ARCHITECTUREEvent types line,docs/PLUGINS.md. When adding one, grep the existing set (e.g.TurnDuration) across all and add everywhere it appears. - Env-var set must match across: README tables,
server/README.md,.env.example, and any inlineARCHITECTUREmention. - State-machine diagrams are duplicated across README,
server/README.mdanddocs/DATABASE.md. A transition change touches all of them. - Run
scripts/doc-coverage.sh <term>to confirm a new identifier/var/event reached every doc that should mention it.