The repo shipped five install/publish surfaces that nothing in the project builds, tests or documents as supported any more. Each one carried its own stale docs, and the Docker/Podman path additionally described a Dockerfile whose COPY of statusline/ would have broken the build the moment that directory went away. Removed: vscode-extension/ (16 files, marketplace extension for an ID we do not own); statusline/ (3 files, standalone CLI statusline); the repo-root landing/wiki PWA assets (sw.js, manifest.json, robots.txt, sitemap.xml, og-image.svg, favicon.svg, fonts/ - 17 files for pages that no longer exist); .superpowers/ (4 files of scratch brainstorm state, already covered by .gitignore:55); and the container publish path (Dockerfile, docker-compose.yml, .dockerignore, 5 Makefile targets, 2 npm scripts). Kept deliberately - these are about the USER's containers, not ours: scripts/install-hooks.js container detection and AGENTHUB_ALLOW_CONTAINER_HOOKS (issue #193), server/lib/lane-detect.js docker-compose service detection, server/data/profile-templates/postgres-compose/, server/lib/stage-detect.js 'docker push' detection, the host.docker.internal Prometheus notes, the Config Explorer's reads of the user's own ~/.claude/statusline.py, and .devcontainer/ (its docker-in-docker feature is dropped since it existed only to build the removed Dockerfile). Docs follow the code: ARCHITECTURE.md loses the VS Code, statusline and container sections plus two dead TOC anchors, and its PWA section is rewritten from three PWAs to one; INSTALL.md, SETUP.md, docs/DEPLOYMENT.md, server/README.md, client/README.md, docs/README.md, docs/HOOKS.md and docs/DATABASE.md drop the same. The Makefile target count in ARCHITECTURE.md is corrected 25 -> 17 (it was already stale).
4.9 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.
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.