doco-dsh

Routing an Agent through the 29-tool MCP server to reach a Doco knowledge base adds an unnecessary RPC hop and ties write approval to a single mechanism. doco-dsh plugs directly into the dsh Harness as a native plugin, reusing the same DocoClient from doco-agent-cli so every operation stays in-process and benefits from dsh native approval flows.

Six tools cover the full read path: connection self-check, knowledge-base listing, Search v2 full-text search with completeness proofs and freshness tags, a stable heading-path outline for planning before reading, and token-budgeted block-level reading with cursor-based continuation. When a search returns complete=false or freshness=stale, the plugin explicitly flags the result as incomplete, preventing the Agent from asserting that something is absent from the base. On the write side, doco_save_draft only creates a new draft, guarded by three layers: a synchronous feature switch, dsh native scope approval before commit, and an idempotency-key conflict check. Version conflicts return a stable error code rather than silently overwriting.

Since 0.2.0 the plugin also exposes a unified doco service surface early in the apply lifecycle. Sibling plugins in the same process consume the DocoClient, identity, scope, and error contract through Cordis dependency injection; the current consumer, doco-memory-dsh, turns the knowledge base into a centralized agent memory with recall, remember, and context operations. If you already manage documentation in Doco and run Agents on dsh, and you want safe, auditable reads plus tightly gated draft writes, doco-dsh is the shortest path.