/ct-documentor

name: ct-documentor
description: Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Carries the CLEO writing and review guides as references and coordinates ct-spec-writer and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.
version: 3.27.0
protocol: null
dependencies:
  - ct-spec-writer
  - ct-adr-recorder
sharedResources:
  - subagent-protocol-base
  - task-system-integration
compatibility:
  - claude-code
  - cursor
  - windsurf
  - gemini-cli
license: MIT
metadata:
  version: 3.27.0
  tier: core
  install: harness
  covers:
    - packages/cleo/src/cli/commands/docs.ts
    - packages/contracts/src/docs-taxonomy.ts
  lastReviewed: 2026-10-27
  stability: stable

Documentation Specialist Context Injection

**Protocol**: @src/protocols/implementation.md **Type**: Context Injection (cleo-subagent) **Version**: 3.0.0

---

Canonical Docs Command Path (T10516 — T11048)

The agent-facing docs surface is simplified to six canonical verbs. Use these as the primary workflow. Legacy verbs remain available but are **advanced or migration surfaces** — do not present them as the default path to agents.

| Canonical Verb | Purpose | When to Use | |---------------|---------|-------------| | `add` | Create a new doc attached to a task/session | First write of any canonical doc | | `update` | Patch/replace an existing doc's content | Fixes, extensions, refreshes | | `fetch` | Retrieve a doc by slug | Reading, reviewing, verifying | | `list` | Browse docs by owner, type, or project | Discovery, checking what exists | | `remove` | Detach a doc from an owner | Cleanup, de-duplication | | `publish` | Mirror an SSoT blob to a git-tracked path | When a doc must live on disk |

**Advanced verbs** (beyond the canonical six): `supersede`, `query --similar`, `graph`, `versions`, `sync`, `merge`, `schema`, `list-types`, `serve`/`open`/`stop`/`viewer-status`, `status`, `publish-pr`, `doctor`.

T13361 retired the legacy verbs `search`, `find`, `rank` (use `query`), `generate`, `export` (use `llm-output`), `gap-check` (use `check`), and `import`; `sync` stays until the T9645 reingest workflow migrates, and `status` stays agent-facing per `cleodocs-rearch-design` §6.

`cleo docs stats` (T13363) is a read-only adoption-metrics probe: add:update ratio from the docs audit log, loose-markdown count (gitignore-aware scan), `docs_wikilinks` edge count, and live `decision_adr_links` count. Use it for pilot baseline comparisons — it never writes.

`cleo docs doctor` (T13447) audits the docs store — dangling `local-file` pointers, docVersion skew vs the audit log, empty topics/related_tasks, `docs_wikilinks` drift, legacy store surfaces, stale drafts — and with `--apply` repairs them after creating a backup automatically. Use it for store hygiene checks; it never edits doc content.

`cleo docs migrate` (T13360) imports legacy docs + history into the re-keyed conduit store inside the migration safety harness (pre-step backup, verified rollback, COMMIT only on full verification). It is additive and idempotent: every imported history row is labeled `origin: migrated`, authors come from the legacy audit log (or the honest `system:migration` attribution — never invented), docs whose content pointers dangle are content-captured or recorded dangling in `conduit_doc_migration_ledger`, and a re-run is a verified no-op. Legacy slugs that already exist natively are counted as native-conflict skips, never clobbered. Run it once per project before the T13361/T13362 retirement lands; it needs no `--force`.

For discovery (`find`, `search`, `schema`, `list-types`), prefer `cleo docs list` first — it returns slug + owner + type without forcing a filesystem walk. Use legacy discovery verbs only when `list` is insufficient.

---

Verify document storage and optional projections separately

After `cleo docs add`, retain the canonical attachment ID and SHA-256, then use `cleo docs fetch <slug>` to verify the accepted bytes. For exact-byte checks, hash the UTF-8 bytes of `data.content` from the JSON response (text docs, T13352; binary docs carry `data.bytesBase64` to decode instead) and compare its digest with `data.metadata.sha256`; rendered content can add a trailing newline.

The add result's `projection` reports captured project identity/root, coverage, diagnostics, the original deadline, and any durable `jobId` or verified receipt. A successful document write can coexist with failed or pending graph/observation work. Preserve those diagnostics and references in the handoff. Missing identity means missing projection coverage; it does not authorize guessing a project.

Optional projection work shares a two-second foreground budget across identity capture, preparation, locking, execution, and verification. Deadline expiry ends foreground observation; synchronous database work is not preempted by a timer. If the outcome is unresolved, inspect the retained job and accepted attachment before explicitly resuming. Do not repeat the add to simulate a retry or assume that a lost worker reply means no write committed. A projection receipt verifies its domain results; it is not an atomic receipt for all document side effects.

Purpose

Context injection for documentation tasks spawned via cleo-subagent. Orchestrates documentation workflows by coordinating specialized skills for lookup, writing, and review.

Skill Coordination

| Skill | Purpose | Invoke When | |-------|---------|-------------| | `cleo docs query` / `list` / `fetch` (and the Context7 MCP for library APIs) | Query existing docs and current external docs | Discovery phas