Files
deepseek-harness/packages/core/system-prompt
Tianyi Cui a29bbe1453 Add JSDoc completeness gate for the cordis surface
gen-cordis-catalog now hard-errors (aggregated, not fail-fast) when an
event lacks description prose or a payload @param, or a public service
method lacks JSDoc, a @param per parameter, a @returns on a non-void
result, or an explicit return type annotation. The this receiver and the
trailing waterfall next are exempt on events (mode machinery owned by
@mode); a stale @param naming no real parameter errors, mirroring the
@mode contradiction check. parseJsDoc now ends prose at the first block
tag (standard JSDoc semantics), so the tags never change the rendered
catalog — only Source: line pointers moved.

Fills the ~139 gaps found across the 15 surface files, extends the spec
with negative-path fixtures for every new guard plus the exemptions,
records the decision as an implemented process RFC, and extends the
AGENTS.md typed-events bullet with the authoring rule. Runs inside
verify-cordis-catalog -> doc-sync, so CI and pre-push enforce it with
zero new wiring.
2026-07-04 19:06:35 +08:00
..

dsh-system-prompt

System prompt assembly registry. Plugins contribute ordered text sections and tool-schema providers; the agent loop calls assemble() once per step.

Service: SystemPrompt (ctx key: systemPrompt)

Public API

  • ctx.systemPrompt.section(section: PromptSection): () => void Contribute a section. Disposed with the calling fiber.
  • ctx.systemPrompt.tools(provider: () => ToolSchema[]): () => void Contribute tool schemas (evaluated at each assembly). Disposed with the calling fiber.
  • ctx.systemPrompt.assemble(): Promise<PromptAssembly> Assemble the current prompt. Runs through the system-prompt/assemble waterfall.

Events

Event Mode Purpose
system-prompt/assemble waterfall Mutate/extend the assembly before it reaches the model
system-prompt/change emit A section or tool provider was registered or unregistered

Key types

  • PromptSection{ name, order, text: string | (() => string) }. Sections are concatenated in ascending order.
  • PromptAssembly{ sections: PromptSection[], tools: ToolSchema[] }. Tool schemas are part of the assembly by design: "what the model is told it can do" is one coherent thing, even though adapters transmit schemas as a separate wire field.
  • renderPrompt(assembly) — joins section texts with blank lines.

Merge-extensible: plugins can declare extra fields on PromptAssembly via declaration merging.

Extension points

  • Section providers: AGENTS.md reader, cwd notifier, persona config, etc.
  • Tool schema providers: ToolRegistry registers itself as a tool provider automatically.
  • The system-prompt/assemble waterfall: mutate or replace the assembly (system-prompt configurability, dynamic tool filtering).

What is NOT here

  • Any hardcoded prompt text — every section comes from plugins.
  • Prompt compaction (belongs on the agent/pre-step seam in dsh-agent).