Yichen Jiang
5ed79887fb
None of these change behavior; each said something that was not true. `SessionCwdConflict`'s doc block had been left stranded above the `AgentPresetConflict` inserted under it, so one class carried a comment about the other and the second carried none. The roster comment named a `.system` directory that does not exist; the shipped root is `config/agent-presets/`, and `system` is the trust its entries carry. The real-composition test attributed the disabled `api-gateway` row to "side effects outside this process" alongside the port and the exporter. It is disabled for a different reason — the api-proxy cannot mount in this layer at all — and hiding that behind the same phrase would leave a later layer unable to tell whether the line can come out. One test claimed to refuse an adoption while asserting only that the header records the preset; it now says what it checks. `PERSONA_SECTION`/`PERSONA_ORDER` existed twice, once in the registry that declares the slot and once restated in the row that replaces it — a drift that would land a preset's persona beside the deployment's instead of shadowing it. The registry exports them now. The preset conflict message read "already runs agent preset undefined" for a session that records none, which is the shape a deployment with no roster produces; it names that case instead, with the regression that reaches it through the gateway. Finally, `PresetTree.write()` drops the `loader/config-update` the inherited method emits — recorded on the override, since a future edit-while-running flow needs its own persistence path.
61 lines
2.2 KiB
TypeScript
61 lines
2.2 KiB
TypeScript
/**
|
|
* A per-agent persona as a composable row.
|
|
*
|
|
* `dsh-system-prompt` owns the global persona as its own config, and registers
|
|
* that section unconditionally — so this row is **scope-only**. Mounted inside
|
|
* an agent preset it shadows the deployment persona for that one session,
|
|
* exactly like the per-child persona `dsh-subagent` installs; mounted globally
|
|
* it collides with the registry's own registration and fails loud.
|
|
*
|
|
* That constraint is the reason the row exists. An agent preset cannot mount
|
|
* the prompt registry itself, so without a row of its own a preset could
|
|
* change an agent's tools but never its identity.
|
|
* @module @deepseek-ai/dsh-persona
|
|
*/
|
|
|
|
import type { Context } from 'cordis'
|
|
import z from 'schemastery'
|
|
import type {} from '@deepseek-ai/dsh-system-prompt'
|
|
|
|
// Imported rather than restated: the registry declares the slot this row
|
|
// replaces, and two hardcoded copies would drift into a preset whose persona
|
|
// silently lands beside the deployment's instead of shadowing it.
|
|
import { PERSONA_ORDER, PERSONA_SECTION } from '@deepseek-ai/dsh-system-prompt'
|
|
|
|
export { PERSONA_ORDER, PERSONA_SECTION }
|
|
|
|
/** Cordis plugin name. */
|
|
export const name = 'persona'
|
|
|
|
/** The prompt registry this row contributes to. */
|
|
export const inject = ['systemPrompt']
|
|
|
|
/** Plugin config: the persona text this composition contributes. */
|
|
export interface Config {
|
|
/**
|
|
* Persona prose rendered as the `deployment:persona` section. A template:
|
|
* complete `{{…}}` groups interpolate strictly against registered prompt
|
|
* variables. Empty text drops the section at render, matching the registry.
|
|
*/
|
|
text: string
|
|
}
|
|
|
|
/** Runtime schema for the persona row. */
|
|
export const Config: z<Config> = z.object({
|
|
text: z.string().required(),
|
|
})
|
|
|
|
/**
|
|
* Register the persona section for the mounting context's scope.
|
|
* @param ctx - an agent scope context; an unscoped context collides with the
|
|
* prompt registry's own persona registration and rejects.
|
|
* @param config - the persona text.
|
|
*/
|
|
export function apply(ctx: Context, config: Config): void {
|
|
ctx.effect(() => ctx.systemPrompt.section({
|
|
name: PERSONA_SECTION,
|
|
order: PERSONA_ORDER,
|
|
text: config.text,
|
|
}), 'persona.section()')
|
|
}
|