dsh-agent-persona 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -4,6 +4,31 @@ All notable changes to this project are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.1] - 2026-11-08
+
+这一版修了两个实际会踩到的问题，另外把文档和安装脚本里过时的说法清理了一遍。
+
+### Fixed
+
+- **用「独占提示词」的 Agent 预设时，人设一个字都发不出去。** 这种预设会声明 `complete: true`，DSH 在
+  组装提示词的最后一步会把其他 section 全丢掉，本插件那一节也没了，而且不报错。现在插件在组装结束后
+  看一眼结果：发现只剩预设那一段、人设没进去，就把人设补进去——追加接在后面，替换整段换掉。
+  插件卸载时会把改动还原。
+- 顺手把这层包装写稳了：宿主不让改方法时只跳过这个功能，不影响插件其他部分；插件卸载后即使别的插件
+  也包过一层，这里也不会继续往提示词里塞人设。
+- **「提示词」不再慢一拍。** 以前打开着这个标签去发消息，标签里还是上一轮的 system prompt，得手动点
+  刷新或者整页刷新才更新。现在一轮跑完会自动重新读一次；正在编辑人设时不会动你的草稿。
+
+### Tests
+
+- 补了这些情况的测试：独占提示词下追加 / 替换 / 空正文、普通提示词不重复塞、包装还原、宿主报错时原样
+  返回，以及「插件装好后确实会包上 `assemble`」这一层。
+
+### Changed
+
+- 文档和安装脚本跟上现状：重启说明补了 systemd 托管的做法，插件详情页「界面与功能」和四个界面入口写
+  清楚了；开发文档里的断言数量、`dsh.bundle.patch` 字段名、远程方法数（16 个）一并改正。
+
 ## [0.2.0] - 2026-11-07
 
 插件页自己会管配置了，图标、显示名和最新的 DSH 也对上了。

package/README.md

@@ -22,7 +22,7 @@
 dsh plugin --profile web add dsh-agent-persona
 ```
 
-装完**重启一次 `dsh web`**。profile 的 bundles 只在启动时读取，插件行就是从这里挂进去的。重启后设置左栏会多出 **Agent 人设**；`~/.dsh/dsh-agent-persona/state.json` 里也有加载心跳，写明了加载的文件、人设存哪、一共几条。
+装完**重启一次 `dsh web`**。profile 的 bundles 只在启动时读取，插件行就是从这里挂进去的。如果你的宿主由 systemd 之类的服务托管（比如本机的 `dsh-web-wood`），改用 `sudo systemctl restart dsh-web-wood`，别自己 kill 掉进程再手起。重启后设置左栏会多出 **Agent 人设**；`~/.dsh/dsh-agent-persona/state.json` 里也有加载心跳，写明了加载的文件、人设存哪、一共几条。
 
 升级、卸载同样是 `dsh plugin --profile web update|remove dsh-agent-persona`，重启一次后生效。人设文件不会跟着删，也不会被覆盖。仓库里另有本地安装脚本：`bash scripts/install.sh`（Windows 用 `scripts/install.ps1`）。
 
@@ -54,7 +54,7 @@ dsh plugin --profile web add dsh-agent-persona
 
 关掉「在设置左栏显示「Agent 人设」」只是从设置导航里隐藏，插件详情页仍在，可以继续改人设、随时开回来。插件列表里中文名是「Agent 人设」、英文名是「Agent Persona」，说明文字来自 `locale/`，图标是包根的 `icon.svg`，不跟随主题色。
 
-![插件详情页头部：Agent 人设图标、版本号 v0.2.0 与中文描述](https://raw.githubusercontent.com/Awoodwhale/dsh-agent-persona/main/docs/images/plugin-detail-icon.png)
+![插件详情页头部：Agent 人设图标、版本号与中文描述](https://raw.githubusercontent.com/Awoodwhale/dsh-agent-persona/main/docs/images/plugin-detail-icon.png)
 
 ## 人设列表与编辑
 
@@ -83,7 +83,7 @@ dsh plugin --profile web add dsh-agent-persona
 选中一条会话后，顶部有 **人设 / 提示词 / 管理** 三个面板：
 
 - **人设**：命中了哪条人设、依据是哪几条规则、正文渲染结果，以及就地编辑器；
-- **提示词**：这条会话**实际发出去的** system prompt，可切换渲染/源码、复制、刷新；
+- **提示词**：这条会话**实际发出去的** system prompt，可切换渲染/源码、复制、刷新。一轮对话结束时它会自己重新读一次，不用手动点刷新；如果你正开着编辑框，它不会把你的改动冲掉；
 - **管理**：和设置页同一套卡片，就地新建、启用、编辑、排序、复制、删除。
 
 旁边的只读会话记录弹窗只显示你真正敲进去的内容，插件注入的「看起来像用户消息」的内容会折叠成一行提示；长消息可单条展开，也能跳到最新。
@@ -131,6 +131,11 @@ dsh plugin --profile web add dsh-agent-persona
 
 正文里可以用 `{{model}}` 和 `{{cwd}}`，渲染时替换成当前值；其它 `{{...}}` 会被去掉，不会让整个组装报错。
 
+还有一种情况得说清楚：有些 Agent 预设的人设段会声明 `complete: true`，意思是「这一节就是完整提示词」。
+DSH 组装到最后会把别的 section 全扔掉，插件写的那节也一样，所以这种预设下人设看起来配好了、实际没发出去。
+现在插件会在组装结束后检查一遍：要是只剩预设那一段、人设没进去，就把它补进去——追加接在后面，替换则
+整段换成这条人设。换句话说，遇到这种预设时上面「别人的身份提示优先」就不作数了，那段提示词是唯一的位子。
+
 ## 数据与安全
 
 ```

package/README_EN.md

@@ -22,7 +22,7 @@ Requires DSH `0.2.0-rc.2` or newer; this release is tested on `0.2.2-rc.1` (full
 dsh plugin --profile web add dsh-agent-persona
 ```
 
-Then **restart `dsh web` once**. Profile bundles are read at startup, and the plugin registers itself from there.
+Then **restart `dsh web` once**. Profile bundles are read at startup, and the plugin registers itself from there. If a service manager runs the host (this machine's `web` profile is the systemd unit `dsh-web-wood`), restart that instead: `sudo systemctl restart dsh-web-wood`. Don't kill the process and start `dsh web` by hand.
 
 After the restart the settings sidebar has an **Agent 人设** page, and `~/.dsh/dsh-agent-persona/state.json` contains a load heartbeat saying which file was loaded, where personas are stored, and how many there are.
 
@@ -56,7 +56,7 @@ The plugin detail page has a new **界面与功能** (Interface and features) bl
 
 Turning off **在设置左栏显示「Agent 人设」** only hides the page from the settings navigation. The plugin detail page remains, so you can keep editing and turn the entry back on at any time. In the plugin list the display name is **Agent 人设** in Chinese and **Agent Persona** in English; the description comes from `locale/`, and the icon is `icon.svg` at the package root (it does not follow the theme color).
 
-![Plugin detail header: the Agent Persona icon, v0.2.0, and the Chinese description](https://raw.githubusercontent.com/Awoodwhale/dsh-agent-persona/main/docs/images/plugin-detail-icon.png)
+![Plugin detail header: the Agent Persona icon, version number, and the Chinese description](https://raw.githubusercontent.com/Awoodwhale/dsh-agent-persona/main/docs/images/plugin-detail-icon.png)
 
 ## Personas: list and editor
 
@@ -85,7 +85,7 @@ With **保存人设版本历史** on, every body save appends a diff to `persona
 Select a session and the top of the view has **人设 / 提示词 / 管理** (persona / prompt / manage):
 
 - **人设**: which persona matched, which rules matched, the rendered body, and an inline editor;
-- **提示词**: the system prompt **actually sent** for this session, with rendered/source toggle, copy, and refresh;
+- **提示词**: the system prompt **actually sent** for this session, with rendered/source toggle, copy, and refresh. It also reloads itself when a turn finishes, so you usually don't need the refresh button — and it won't clobber an editor you have open;
 - **管理**: the same cards as the settings page, for creating, enabling, editing, reordering, duplicating, and deleting in place.
 
 Next to it is a read-only conversation log: it shows only what you actually typed, and plugin-injected content that looks like a user message is collapsed into a one-line notice. Long messages can be expanded individually, and you can jump to the latest one.
@@ -133,6 +133,8 @@ Of the four match types, only `完全一致` (exact) normalizes paths (`/a/proje
 
 The body supports `{{model}}` and `{{cwd}}`, substituted with current values at render time. Other `{{...}}` placeholders are removed rather than failing the whole assembly.
 
+One more case worth spelling out: some Agent presets declare `complete: true` on their persona section, meaning "this section is the whole prompt". At the end of assembly DSH throws away every other section, including the one this plugin writes, so the persona looks configured but never reaches the model. The plugin now checks the result after assembly: if only the preset's section is left and the persona is missing, it puts the persona in — appended after it for Append, replacing the whole text for Replace. With such a preset the "someone else's identity wins" rule above no longer applies: that section is the only slot there is.
+
 ## Data and security
 
 ```

package/lib/client.js

@@ -883,7 +883,11 @@
          * session it is showing; otherwise it keeps rendering the one it was first opened for.
          */
         componentDidUpdate(previous) {
-          if (this.sessionId() !== sessionIdOf(previous)) void this.load();
+          if (this.sessionId() !== sessionIdOf(previous)) {
+            void this.load();
+            return;
+          }
+          if (previous.running === true && this.props.running === false && this.state.editing !== true) void this.load();
         }
         sessionId() {
           return sessionIdOf(this.props);
@@ -1144,6 +1148,10 @@
           );
         }
       }
+      const PersonaViewLive = (props) => {
+        const running = props.useSession((snapshot) => snapshot?.running === true);
+        return h(PersonaView, { ...props, running });
+      };
       const dotState = (persona) => {
         if (persona === void 0) return "off";
         if (!persona.enabled) return "off";
@@ -3011,7 +3019,7 @@ ${state.proposal.trim()}
             id: "agent-persona",
             order: 30,
             label: () => "\u4EBA\u8BBE"
-          }, PersonaView));
+          }, PersonaViewLive));
         };
         const dropTabSeat = () => {
           if (!tabSeatMounted) return;

package/lib/index.d.ts

@@ -263,6 +263,30 @@ export declare const applyPersonaMode: (assembly: any, { mode, deploymentPrefix
     deploymentPrefix: any;
     mode: any;
 }) => any;
+/**
+ * Fold a persona into a prompt that one `complete: true` section owns.
+ *
+ * An agent preset may declare its own persona with `complete: true`; the registry then hands back that single
+ * section as the whole system prompt, and it does so *after* the `system-prompt/assemble` waterfall — so no
+ * listener can add a section of its own, and this plugin's section is discarded before it ever renders. The
+ * only place a persona can still live is inside that section.
+ * @param assembly - an assembled prompt.
+ * @param persona - `{ text, mode }` of the persona that claims this assembly, or `undefined`.
+ * @returns the assembly with the persona folded in, or the input when nothing applies.
+ */
+export declare const applyCompletePersona: (assembly: any, persona: any) => any;
+/**
+ * Reach the prompts a `complete: true` section owns.
+ *
+ * `assemble()` is wrapped instead of listening to the waterfall because the registry collapses the section
+ * list *after* dispatching it: the waterfall's sections are overwritten by the complete one. Disposal restores
+ * the original method, so unloading the plugin leaves no trace.
+ * @param systemPrompt - the prompt registry service.
+ * @param readPersona - resolves `{ text, mode }` for one assembly context, or `undefined`.
+ * @param warn - diagnostic sink.
+ * @returns the disposer that restores `assemble`.
+ */
+export declare const bridgeCompletePrompt: (systemPrompt: any, readPersona: any, warn?: () => void) => () => void;
 /**
  * Session ids the user has archived. The registry is asked first; the workspace
  * store file is the fallback, and an unreadable store simply means "none".

package/lib/index.js

@@ -1236,6 +1236,81 @@ export const applyPersonaMode = (assembly, { mode, deploymentPrefix }) => {
     }
     return changed ? { ...assembly, sections: next } : assembly;
 };
+/**
+ * Fold a persona into a prompt that one `complete: true` section owns.
+ *
+ * An agent preset may declare its own persona with `complete: true`; the registry then hands back that single
+ * section as the whole system prompt, and it does so *after* the `system-prompt/assemble` waterfall — so no
+ * listener can add a section of its own, and this plugin's section is discarded before it ever renders. The
+ * only place a persona can still live is inside that section.
+ * @param assembly - an assembled prompt.
+ * @param persona - `{ text, mode }` of the persona that claims this assembly, or `undefined`.
+ * @returns the assembly with the persona folded in, or the input when nothing applies.
+ */
+export const applyCompletePersona = (assembly, persona) => {
+    const text = typeof persona?.text === 'string' ? persona.text.trim() : '';
+    if (text === '')
+        return assembly;
+    const sections = assembly?.sections;
+    if (!Array.isArray(sections) || sections.length !== 1)
+        return assembly;
+    const [only] = sections;
+    // Our own section surviving means this is a normal prompt: the waterfall already placed the persona, and
+    // folding it in again would print it twice.
+    if (only?.name === SECTION_NAME)
+        return assembly;
+    const current = typeof only?.text === 'string' ? only.text : '';
+    // `replace` takes the prompt over, which is the honest reading of "replace" when the preset owns every word;
+    // `append` keeps that prompt and puts the persona right after it, where section order 1 would have been.
+    // Trailing whitespace is dropped first so a complete prompt ending in a newline does not gain a blank line.
+    const body = current.trimEnd();
+    const next = persona.mode === 'replace' ? text : body === '' ? text : `${body}\n\n${text}`;
+    return next === current ? assembly : { ...assembly, sections: [{ ...only, text: next }] };
+};
+/**
+ * Reach the prompts a `complete: true` section owns.
+ *
+ * `assemble()` is wrapped instead of listening to the waterfall because the registry collapses the section
+ * list *after* dispatching it: the waterfall's sections are overwritten by the complete one. Disposal restores
+ * the original method, so unloading the plugin leaves no trace.
+ * @param systemPrompt - the prompt registry service.
+ * @param readPersona - resolves `{ text, mode }` for one assembly context, or `undefined`.
+ * @param warn - diagnostic sink.
+ * @returns the disposer that restores `assemble`.
+ */
+export const bridgeCompletePrompt = (systemPrompt, readPersona, warn = () => { }) => {
+    const original = systemPrompt?.assemble;
+    if (typeof original !== 'function')
+        return () => { };
+    // The wrapper is disposable state, not a permanent tombstone: after the plugin unloads it must stop folding
+    // even when another plugin has wrapped `assemble` on top of it and the original method cannot be restored.
+    let active = true;
+    const patched = async (context) => {
+        const assembly = await original.call(systemPrompt, context);
+        if (!active)
+            return assembly;
+        try {
+            return applyCompletePersona(assembly, readPersona(context));
+        }
+        catch (error) {
+            warn('could not fold the persona into a complete system prompt', error);
+            return assembly;
+        }
+    };
+    try {
+        systemPrompt.assemble = patched;
+    }
+    catch (error) {
+        // A host that freezes or seals the service must only cost this feature, never the whole plugin.
+        warn('could not wrap assemble(); personas will not reach a complete prompt', error);
+        return () => { };
+    }
+    return () => {
+        active = false;
+        if (systemPrompt.assemble === patched)
+            systemPrompt.assemble = original;
+    };
+};
 /** Read one event's plain text out of the shapes DSH session logs use. */
 const eventText = (event) => {
     const parts = [];
@@ -1895,6 +1970,15 @@ export function apply(ctx, config = {}) {
     catch (error) {
         warn(`section "${SECTION_NAME}" is already registered; keeping the live one`, error);
     }
+    // A preset that owns the whole prompt (`complete: true`) never renders our section, so the persona has to be
+    // folded into the section that preset does own. Registered through the effect, so unloading restores
+    // `assemble` instead of leaving a wrapper behind.
+    ctx.effect(() => bridgeCompletePrompt(ctx.systemPrompt, (context) => {
+        const persona = resolvePersona(currentStore().personas, subjectOf(context?.agent)).persona;
+        if (persona === undefined || persona.text.trim() === '')
+            return undefined;
+        return { text: sanitizePersona(persona.text, warn), mode: persona.mode };
+    }, warn), 'agent-persona.complete-bridge');
     // The store is this plugin's instruction source, so no tool call may write it. The guard is monotonic: once
     // it refuses a call nothing later can allow it. Registered through the effect, so unloading the plugin
     // removes it instead of leaving a process-wide refusal behind.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-agent-persona",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Workspace personas for DeepSeek Harness (DSH): create many system-prompt personas and scope each one by workspace path or session id (exact / prefix / regex / contains), managed from a Web settings page with Markdown editing and AI tuning.",
   "icon": "./icon.svg",
   "type": "module",

package/scripts/install.ps1

@@ -3,7 +3,7 @@
 #   pwsh -File scripts/install.ps1
 #   pwsh -File scripts/install.ps1 -Profile my-profile
 #   pwsh -File scripts/install.ps1 -Profile web -Target .
-#   pwsh -File scripts/install.ps1 -Profile web -Target dsh-agent-persona@0.1.1
+#   pwsh -File scripts/install.ps1 -Profile web -Target dsh-agent-persona@0.2.1
 param(
   [string]$Profile = "web",
   [string]$Target  = "dsh-agent-persona"
@@ -58,14 +58,19 @@ Installed into profile "$Profile" (this checkout is v$Version).
 
 dsh.profile.bundles is read at STARTUP, so restart the host now:
 
-    dsh web
+    dsh web                                  # if you started the host by hand
+    # if a service runs it, restart that service instead; on Linux hosts that
+    # use systemd the unit is often named like dsh-web-<user>
 
 Then check it loaded:
 
     Get-Content "$State"
-    # 设置 -> Agent 人设        the management page
-    # 对话页顶部「人设」        the per-session view
-    # 设置 -> 通用设置           carries nothing from this plugin
+    # 设置 -> Agent 人设        完整管理页（可在插件页的「界面与功能」里隐藏这个入口）
+    # 对话页顶部「人设」        当前会话的人设 / 实际发送的提示词
+    # 插件 -> dsh-agent-persona 图标、README 和「界面与功能」开关；设置入口被隐藏后从这里回去
+    # dsh-better-sidebar 右侧  「Agent 人设」卡片（装了那个插件才有）
+
+The switches on the plugin page and in Settings write the same prefs, so either place works.
 
 Personas live in one file, shared by every profile unless you override config.storePath:
 

package/scripts/install.sh

@@ -4,7 +4,7 @@
 #   bash scripts/install.sh                    # published package, profile "web"
 #   bash scripts/install.sh my-profile         # another profile
 #   bash scripts/install.sh web .              # this checkout (development)
-#   bash scripts/install.sh web dsh-agent-persona@0.1.1   # a pinned version
+#   bash scripts/install.sh web dsh-agent-persona@0.2.1   # a pinned version
 set -euo pipefail
 
 PROFILE="${1:-web}"
@@ -56,14 +56,18 @@ Installed into profile "${PROFILE}" (this checkout is v${VERSION}).
 
 dsh.profile.bundles is read at STARTUP, so restart the host now:
 
-    dsh web            # or stop the running one and start it again
+    dsh web                                  # if you started the host by hand
+    sudo systemctl restart dsh-web-wood      # if systemd runs it (use your unit name)
 
 Then check it loaded:
 
     cat "${STATE}"
-    # 设置 → Agent 人设        the management page
-    # 对话页顶部「人设」        the per-session view
-    # 设置 → 通用设置           carries nothing from this plugin
+    # 设置 → Agent 人设        完整管理页（可在插件页的「界面与功能」里隐藏这个入口）
+    # 对话页顶部「人设」        当前会话的人设 / 实际发送的提示词
+    # 插件 → dsh-agent-persona 图标、README 和「界面与功能」开关；设置入口被隐藏后从这里回去
+    # dsh-better-sidebar 右侧  「Agent 人设」卡片（装了那个插件才有）
+
+The switches on the plugin page and in Settings write the same prefs, so either place works.
 
 Personas live in one file, shared by every profile unless you override config.storePath:
 

package/src/client.ts

@@ -1001,7 +1001,13 @@ const readPrefs = () => {
        * session it is showing; otherwise it keeps rendering the one it was first opened for.
        */
       componentDidUpdate(previous) {
-        if (this.sessionId() !== sessionIdOf(previous)) void this.load()
+        if (this.sessionId() !== sessionIdOf(previous)) {
+          void this.load()
+          return
+        }
+        // A finished turn may have produced a new system prompt while the tab stayed open. Reload so
+        // 「提示词」 is current; skip while the inline editor is open so typing is never clobbered.
+        if (previous.running === true && this.props.running === false && this.state.editing !== true) void this.load()
       }
 
       sessionId() {
@@ -1287,6 +1293,16 @@ const readPrefs = () => {
     }
 
 
+    /**
+     * The conversation tab receives the session snapshot hooks; the sidebar card does not. Subscribe
+     * here so a turn that finishes while 「提示词」 is open can refresh itself instead of showing the
+     * previous turn's prompt until the reader reloads the page.
+     */
+    const PersonaViewLive = (props) => {
+      const running = props.useSession((snapshot) => snapshot?.running === true)
+      return h(PersonaView, { ...props, running })
+    }
+
     const dotState = (persona) => {
       if (persona === undefined) return 'off'
       if (!persona.enabled) return 'off'
@@ -3406,7 +3422,7 @@ const since = (timestamp) => {
           id: 'agent-persona',
           order: 30,
           label: () => '人设',
-        }, PersonaView))
+        }, PersonaViewLive))
       }
       const dropTabSeat = () => {
         if (!tabSeatMounted) return

package/src/index.ts

@@ -1223,6 +1223,75 @@ export const applyPersonaMode = (assembly, { mode, deploymentPrefix }) => {
   return changed ? { ...assembly, sections: next } : assembly
 }
 
+/**
+ * Fold a persona into a prompt that one `complete: true` section owns.
+ *
+ * An agent preset may declare its own persona with `complete: true`; the registry then hands back that single
+ * section as the whole system prompt, and it does so *after* the `system-prompt/assemble` waterfall — so no
+ * listener can add a section of its own, and this plugin's section is discarded before it ever renders. The
+ * only place a persona can still live is inside that section.
+ * @param assembly - an assembled prompt.
+ * @param persona - `{ text, mode }` of the persona that claims this assembly, or `undefined`.
+ * @returns the assembly with the persona folded in, or the input when nothing applies.
+ */
+export const applyCompletePersona = (assembly, persona) => {
+  const text = typeof persona?.text === 'string' ? persona.text.trim() : ''
+  if (text === '') return assembly
+  const sections = assembly?.sections
+  if (!Array.isArray(sections) || sections.length !== 1) return assembly
+  const [only] = sections
+  // Our own section surviving means this is a normal prompt: the waterfall already placed the persona, and
+  // folding it in again would print it twice.
+  if (only?.name === SECTION_NAME) return assembly
+  const current = typeof only?.text === 'string' ? only.text : ''
+  // `replace` takes the prompt over, which is the honest reading of "replace" when the preset owns every word;
+  // `append` keeps that prompt and puts the persona right after it, where section order 1 would have been.
+  // Trailing whitespace is dropped first so a complete prompt ending in a newline does not gain a blank line.
+  const body = current.trimEnd()
+  const next = persona.mode === 'replace' ? text : body === '' ? text : `${body}\n\n${text}`
+  return next === current ? assembly : { ...assembly, sections: [{ ...only, text: next }] }
+}
+
+/**
+ * Reach the prompts a `complete: true` section owns.
+ *
+ * `assemble()` is wrapped instead of listening to the waterfall because the registry collapses the section
+ * list *after* dispatching it: the waterfall's sections are overwritten by the complete one. Disposal restores
+ * the original method, so unloading the plugin leaves no trace.
+ * @param systemPrompt - the prompt registry service.
+ * @param readPersona - resolves `{ text, mode }` for one assembly context, or `undefined`.
+ * @param warn - diagnostic sink.
+ * @returns the disposer that restores `assemble`.
+ */
+export const bridgeCompletePrompt = (systemPrompt, readPersona, warn = () => {}) => {
+  const original = systemPrompt?.assemble
+  if (typeof original !== 'function') return () => {}
+  // The wrapper is disposable state, not a permanent tombstone: after the plugin unloads it must stop folding
+  // even when another plugin has wrapped `assemble` on top of it and the original method cannot be restored.
+  let active = true
+  const patched = async (context) => {
+    const assembly = await original.call(systemPrompt, context)
+    if (!active) return assembly
+    try {
+      return applyCompletePersona(assembly, readPersona(context))
+    } catch (error) {
+      warn('could not fold the persona into a complete system prompt', error)
+      return assembly
+    }
+  }
+  try {
+    systemPrompt.assemble = patched
+  } catch (error) {
+    // A host that freezes or seals the service must only cost this feature, never the whole plugin.
+    warn('could not wrap assemble(); personas will not reach a complete prompt', error)
+    return () => {}
+  }
+  return () => {
+    active = false
+    if (systemPrompt.assemble === patched) systemPrompt.assemble = original
+  }
+}
+
 /** Read one event's plain text out of the shapes DSH session logs use. */
 const eventText = (event) => {
   const parts = []
@@ -1858,6 +1927,15 @@ export function apply(ctx, config = {}) {
     warn(`section "${SECTION_NAME}" is already registered; keeping the live one`, error)
   }
 
+  // A preset that owns the whole prompt (`complete: true`) never renders our section, so the persona has to be
+  // folded into the section that preset does own. Registered through the effect, so unloading restores
+  // `assemble` instead of leaving a wrapper behind.
+  ctx.effect(() => bridgeCompletePrompt(ctx.systemPrompt, (context) => {
+    const persona = resolvePersona(currentStore().personas, subjectOf(context?.agent)).persona
+    if (persona === undefined || persona.text.trim() === '') return undefined
+    return { text: sanitizePersona(persona.text, warn), mode: persona.mode }
+  }, warn), 'agent-persona.complete-bridge')
+
   // The store is this plugin's instruction source, so no tool call may write it. The guard is monotonic: once
   // it refuses a call nothing later can allow it. Registered through the effect, so unloading the plugin
   // removes it instead of leaving a process-wide refusal behind.