539051b2c9
The tool render-intent vocabulary (ToolCallView/ToolResultView + members, FileLocation, FileDiff, ToolCallKind) is the UI-facing surface of dsh-tools; it lived inline in index.ts alongside the registry and execution core. Move it to its own presentation.ts module so index.ts is the registry + execute waterfall and the presentation vocabulary is a separate, one-directional dependency. presentation.ts owns ONLY render-intent types and references none of the execution types; index.ts imports the view types for ToolDefinition's presentCall/presentResult signatures (clean acyclic index -> presentation). The opaque `meta` presentation channel (ToolExecuteReturn, ToolResult, ToolExecutionResult) is execution plumbing and stays in index.ts. Public surface unchanged: index.ts re-exports the vocabulary, so consumers (tool-fs/tool-bash/tool-web/tool-todo, the ACP bridge) keep importing from @deepseek-ai/dsh-tools with zero churn. No producer/bridge/test edits; a pure internal relocation with no observable-output change (snapshot goldens untouched).
core/ — product API spine
The packages every harness build is assembled from: the session log, the system-prompt assembly, the tool registry, the agent vocabulary, and the one concrete loop that drives them. These are product packages — the stable surface plugins and consumers build against.
| Package | Role | ctx key |
|---|---|---|
session/ |
Event-sourced session log + in-memory store | ctx.sessions |
system-prompt/ |
Prompt-section + tool-schema assembly registry | ctx.systemPrompt |
tools/ |
Tool registry + tools/execute waterfall |
ctx.tools |
agent/ |
Agent interface, registry, agent/* event vocabulary |
ctx.agents |
agent-loop/ |
The concrete loop plugin: ReactLoopAgent + the loop driver |
ctx.agentLoop |
agent-core/ |
Bundle plugin: the providerless/executor-less/UI-less spine as code | (loads the spine) |
agent-loop is the one concrete implementation of the agent seam and lives here because it is the harness's default product loop; everything else in core/ is interface/vocabulary. Plugins depend on the agent vocabulary, never on agent-loop directly, so the loop stays swappable.
agent-core is the composition counterpart: one bundle plugin that loads the whole providerless spine (timer + llm + sessions + system-prompt + tools + agents + invariants + tool-bash + agent-loop) and forwards agent-loop's agents list as its own config. App packages (ui/stdio-agent, ui/acp-agent) consume it and add only a front door; a leaf adds the swappable backends plus any optional product tools it wants to expose. It lives in core/ because it composes exclusively core/ + interface packages and ships no provider, executor, or UI of its own.