Files
AgentHub/skills/update-project-docs/references/doc-map.md
T
nntrivi2001 b7c573f8d9 feat(plugin): ship the repo's skills as ccam plugin skills
The repo root already IS the `ccam` plugin root (`"source": "./"`), so the
conventional `skills/` dir at the root is the plugin's skills dir — while
`.claude/skills/` only loaded for a session whose cwd was inside this
checkout. That is useless for a lane working in another repo, which is why
`ccam skills install` existed at all.

Move all seven skills to `skills/`: they now reach every plugin user as
`/ccam:<name>` (bare `/<name>` as an alias). `ccam skills install` stays as
the fallback for a plain checkout without the plugin, sourcing from the new
path.

Agents deliberately do NOT move. A plugin agent is addressed as
`ccam:qc-local`, which would break the `subagent_type: qc-local` references
in ship-feature-lane; `ccam lanes agents install` keeps writing them into the
lane's own `.claude/agents/`, the highest-priority agent source. MCP was
already plugin-shipped via `plugins/ccam/.mcp.json`.

Mechanical fallout: ~115 source files carry a doc-comment pointer to
`.claude/skills/file-headers/`, repointed to `skills/file-headers/`. The
generic Claude Code config-surface examples in openapi/cc-config (`.claude/
skills/code-reviewer`) describe any user's layout and are left alone.

Also fixes the two file-headers scripts, whose `ROOT=` climbed four levels
from `.claude/skills/file-headers/scripts/` and would have escaped the repo
from the new depth — it scanned sibling projects until corrected to three.

npm run test:server (1160 pass), test:client (422 pass), mcp:typecheck,
mcp:build + mcp:check-build all green.
2026-08-21 17:17:33 +07:00

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-v2 blocks. Grep stateDiagram-v2.
  • Hook Events table — | Hook Type | Trigger | Dashboard Action |. Lists SessionStart…SessionEnd, plus synthetic Compaction, APIError, TurnDuration, ToolError, Interrupted. Grep ## Hook Events.
  • Configuration / Environment Variables table — | Environment Variable | Default | Description |. Grep DASHBOARD_PORT or DASHBOARD_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/MCP.md + mcp/README.md

MCP server + tool reference. Update for new/changed MCP tools.

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 new docs/*.md is 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: README hook table, ARCHITECTURE Event 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 inline ARCHITECTURE mention.
  • State-machine diagrams are duplicated across README, server/README.md and docs/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.