dsh-custom-mode 1.9.8 → 1.9.10

package/README.md

@@ -47,7 +47,7 @@ The mode is **web-profile only**: `agent-presets`, the service that mounts prese
 
 ## Requirements
 
-- **dsh `>=0.1.5-rc.2 <0.2.0-0`**（latest stable `0.1.5-rc.2` and latest preview `0.1.6-alpha.2`）** — declared in `engines.dsh` and as an *optional* peer range. This package never
+- **dsh `>=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0`**（latest stable `0.1.5-rc.2` and the preview line `0.1.6-alpha.2` / `0.1.7-alpha.*`）** — declared in `engines.dsh` and as an *optional* peer range. This package never
   imports `@deepseek-ai/dsh`; it only reads the host services dsh injects.
 - **No build step, no dependencies**: the source is published as-is and uses only Node's standard library.
 - The package version is its own line (`1.0.0`, `1.0.1`, …). Which dsh it supports is declared in

package/client.js

@@ -683,6 +683,13 @@ try {
         ".cpfe-btn-ghost{border-color:transparent;background:transparent}",
         ".cpfe-input{box-sizing:border-box;width:100%;height:34px;padding:0 12px;border-radius:8px;border:.5px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-base);color:var(--dsw-alias-label-primary);font:inherit;font-size:13px}",
         ".cpfe-switch{display:inline-flex;align-items:center;gap:8px;cursor:pointer;font-size:13px;line-height:19px;color:var(--dsw-alias-label-primary)}",
+        // 忙碌期间禁掉草稿类控件的交互（issue #6）。
+        // 状态层已经拦住了改动（`update()` 在 busy 时直接返回），但对**受控组件**来说，
+        // 光拦状态还不够：DOM 会先显示用户敲进去的字/翻过去的开关，等下一次重渲染才被拉回来 ——
+        // 那就是"我明明改了，它自己弹回去了"。`pointer-events` 让点击根本到不了控件，
+        // 视觉上也给一个明确的"此刻不能动"。
+        ".cpfe-busy .cpfe-switch,.cpfe-busy .cpfe-row-toggle,.cpfe-busy .cpfe-input,.cpfe-busy .cpfe-field,.cpfe-busy .cpfe-editor{pointer-events:none;opacity:.65}",
+        ".cpfe-busy .cpfe-editor{cursor:progress}",
         ".cpfe-tag{font-size:11px;line-height:16px;padding:0 5px;border-radius:4px;border:.5px solid var(--dsw-alias-border-l1);color:var(--dsw-alias-label-secondary)}",
         ".cpfe-tag-success,.cpfe-tag-info{color:var(--dsw-alias-state-success-primary)}",
         ".cpfe-tag-warning{color:var(--dsw-alias-state-warn-primary)}",
@@ -1597,6 +1604,9 @@ try {
                   className: "cpfe-field cpfe-desc",
                   value: draft.description,
                   rows: 2,
+                  // 忙碌期间只读（issue #6）。**描述框在 DOM 里排在提示词编辑器前面**，
+                  // 所以只给 `.cpfe-editor` 加 readOnly 是不够的 —— 实测就是这么漏掉的。
+                  readOnly: busy === true,
                   placeholder: t("name.descriptionPlaceholder"),
                   "aria-label": t("name.descriptionPlaceholder"),
                   onChange: (event) => update({ description: event.target.value }),
@@ -1835,7 +1845,9 @@ try {
 
         return react.createElement(
           "div",
-          { className: "cpfe" },
+          // `cpfe-busy` 是 issue #6 的兜底：面板里**所有**会改草稿的控件在忙碌期间一律不可交互。
+          // 逐个控件加 `disabled` 会漏（本轮就漏了行开关与描述框），一个根类 + 一条 CSS 反而漏不掉。
+          { className: busy === true ? "cpfe cpfe-busy" : "cpfe" },
           assistantList,
           react.createElement("p", { className: "cpfe-note" }, t("assistant.switchHint")),
           // 配了却不生效的项：主动点名，而不是让用户对着"我明明写了"发呆。

package/composition.mjs

@@ -348,6 +348,74 @@ function evalDisabledExpression(expression) {
 }
 
 /** Build one row's UI description from its segment text. */
+/**
+ * A row's module specifier: the `name:` line.
+ *
+ * Needed by the declarative backend (dsh ≥ 0.1.7), which must hand `register()` a real row list
+ * rather than a composition file on disk. It is also where the **relative specifiers this feature
+ * emits** (`'./prompt-reader.mjs'`, `'./prompt-tool.mjs'`) surface: on the file-scanning line those
+ * resolve against the preset directory, but `register()` mounts under the *profile's* baseUrl, so the
+ * caller has to rewrite them to absolute `file://` URLs. Measured on 0.1.7-alpha.2: a relative
+ * specifier yields `broken: … never started`, an absolute one mounts.
+ *
+ * @param {string} segmentText - one row's text.
+ * @returns {string|null} the specifier with surrounding quotes stripped, or null when the row has none.
+ */
+export function moduleNameOf(segmentText) {
+  const match = /^\s*name:\s*(.+?)\s*$/m.exec(segmentText)
+  if (match === null) return null
+  return match[1].replace(/^['"]|['"]$/g, '')
+}
+
+/**
+ * A row's `config:` block, as a plain object.
+ *
+ * Deliberately a **small, strict YAML subset**, not a general parser: the only files this reads are
+ * the ones this feature writes (`renderComposition`), whose config blocks are flat scalars. Anything
+ * it cannot represent is skipped rather than guessed — a wrong value here would silently change what
+ * the model sees. Callers that need certainty should compare against {@link moduleNameOf}.
+ *
+ * @param {string} segmentText - one row's text.
+ * @returns {object|null} the config object, or null when the row has no `config:` block.
+ */
+export function configOf(segmentText) {
+  const lines = segmentText.split('\n')
+  const start = lines.findIndex((line) => /^\s*config:\s*$/.test(line))
+  if (start === -1) return null
+  const baseIndent = lines[start].search(/\S/)
+  const out = {}
+  let any = false
+  for (let i = start + 1; i < lines.length; i += 1) {
+    const line = lines[i]
+    if (line.trim() === '') continue
+    const indent = line.search(/\S/)
+    if (indent <= baseIndent) break
+    const match = /^\s*([A-Za-z_][\w-]*):\s*(.*?)\s*$/.exec(line)
+    if (match === null) continue
+    out[match[1]] = parseScalar(match[2])
+    any = true
+  }
+  return any ? out : null
+}
+
+/** Parse one YAML scalar into a JS value, staying conservative: unknown shapes stay strings. */
+function parseScalar(raw) {
+  const value = raw.trim()
+  if (value === '') return ''
+  if (value === 'true') return true
+  if (value === 'false') return false
+  if (value === 'null' || value === '~') return null
+  if (/^-?\d+$/.test(value)) return Number(value)
+  if (/^"(?:[^"\\]|\\.)*"$/.test(value) || /^'(?:[^']|'')*'$/.test(value)) {
+    try {
+      return JSON.parse(value[0] === '"' ? value : `"${value.slice(1, -1).replace(/'/g, "\\'")}"`)
+    } catch {
+      return value.slice(1, -1)
+    }
+  }
+  return value
+}
+
 function describeRow(id, segmentText, children) {
   const own = disabledOf(segmentText)
   const meta = ROW_META[id] ?? {}
@@ -361,6 +429,9 @@ function describeRow(id, segmentText, children) {
     group: children.length > 0,
     disabled: literalOff || fromExpression === true,
     disabledExpression: own.present && own.value.startsWith('!!js') ? own.value : null,
+    // 新线（声明式注册表）要把行交给 register()，需要模块说明符与 config —— 见 moduleNameOf。
+    moduleName: moduleNameOf(segmentText),
+    config: configOf(segmentText),
     label: meta.label ?? id,
     essential: meta.essential === true,
     note: meta.note ?? null,
@@ -604,16 +675,45 @@ export function disableRowsInPlace(text, ids) {
   return applyLevel(text, true, off, false, false)
 }
 
+/**
+ * Module names this installation actually has, injected by the host half.
+ *
+ * Why this exists: {@link unresolvableRows} decides "can this line run here?" by walking the install's
+ * `node_modules`. That works on the file-scanning dsh line, but **0.1.7 has no `dsh-agent-presets`
+ * package and therefore no directory for `shippedPresetsDir()` to find** — the lookup threw, the catch
+ * returned `[]`, and the check silently stopped checking anything. On that line the host half has a
+ * better source: `agentPresets.compositionInventory()` reports every row of every registered preset with
+ * its `moduleName`, which is exactly this set.
+ *
+ * When a set is injected it **replaces** the filesystem probe (it is strictly better information on the
+ * line that needs it). `null` means "not injected" — legacy behaviour.
+ */
+let knownModuleNames = null
+
+/** @param {Iterable<string>|null} names - module specifiers known to be installable here. */
+export function setKnownModuleNames(names) {
+  knownModuleNames = names === null || names === undefined ? null : new Set(names)
+}
+
+/** The injected set, or null when the filesystem probe is in charge. Exported for tests/diagnostics. */
+export function knownModuleNamesInjected() {
+  return knownModuleNames
+}
+
 export function unresolvableRows(text) {
   let root
-  try {
-    root = join(shippedPresetsDir(), '..', '..', '..')
-  } catch {
-    return []
+  let fromFilesystem = false
+  if (knownModuleNames === null) {
+    try {
+      root = join(shippedPresetsDir(), '..', '..', '..')
+      fromFilesystem = true
+    } catch {
+      return []
+    }
+    // **判断不了就不要报警**：如果这个根下根本没有 node_modules（例如测试用的是一个临时出厂目录），
+    // 那么"查不到某个包"只说明我们不知道，不说明那行坏了。误报的代价是用户被引导去关掉本来正常的行。
+    if (existsSync(join(root, '@deepseek-ai')) === false) return []
   }
-  // **判断不了就不要报警**：如果这个根下根本没有 node_modules（例如测试用的是一个临时出厂目录），
-  // 那么"查不到某个包"只说明我们不知道，不说明那行坏了。误报的代价是用户被引导去关掉本来正常的行。
-  if (existsSync(join(root, '@deepseek-ai')) === false) return []
   const out = []
   const lines = text.split('\n')
   for (let index = 0; index < lines.length; index += 1) {
@@ -649,7 +749,12 @@ export function unresolvableRows(text) {
     if (name.startsWith('.') || name.startsWith('cordis:')) continue
     const parts = name.split('/')
     const pkg = name.startsWith('@') ? parts.slice(0, 2).join('/') : parts[0]
-    if (existsSync(join(root, pkg)) === false) out.push({ id: row[2], name })
+    // 注入了集合就用集合（新线：来自 compositionInventory 的 moduleName）——
+    // 子路径说明符（`@scope/pkg/sub`）与它的包名都算命中，否则会把健康行误报成坏行。
+    const present = fromFilesystem
+      ? existsSync(join(root, pkg))
+      : knownModuleNames.has(name) || knownModuleNames.has(pkg)
+    if (present === false) out.push({ id: row[2], name })
   }
   return out
 }

package/index.mjs

@@ -38,6 +38,14 @@
  */
 
 import { writeAtomic, writeAtomicPair } from './atomic.mjs'
+import {
+  BACKEND_DECLARATIVE,
+  BACKEND_UNUSABLE,
+  createDeclarativeBackend,
+  describeBackend,
+  detectPresetBackend,
+  effectiveRosterRows,
+} from './preset-backend/index.mjs'
 import { existsSync, readFileSync, writeFileSync } from 'node:fs'
 import { dirname, join } from 'node:path'
 import { PROMPT_PATH, COMPOSITION_PATH, ROUTE_PATH, PRESET_DIR } from './paths.mjs'
@@ -48,6 +56,7 @@ import {
   modeOf,
   overridesOf,
   readBaseComposition,
+  setKnownModuleNames,
   renderComposition,
   setShippedPresetsDir,
   unresolvableRows,
@@ -692,6 +701,11 @@ const API_PREFIX = '/api'
 const WEB_SERVICES = ['connection', 'agentPresets']
 
 export function apply(ctx) {
+  // 助手目录的根（`$DSH_HOME/.agent-presets`）。
+  // 两条线共用它：旧线由平台扫描这个目录，新线不再扫描但**插件仍然把 composition 写在这里**
+  // —— 它是用户可见、可迁移、可手改的真相，也是旧线唯一的输入。
+  const assistantRoot = dirname(PRESET_DIR)
+
   // Before anything else: make sure the preset tree on disk is complete.
   //
   // A storefront install is a single command (`dsh plugin --profile web add
@@ -706,7 +720,7 @@ export function apply(ctx) {
   // the assistant registry for why a deleted assistant must not come back.
   try {
     seedOnActivation({
-      root: dirname(PRESET_DIR),
+      root: assistantRoot,
       templateDir: packagedPresetDir(),
       // 组成文件**不照搬包内模板**，而是按本机装的那条 dsh 线派生：模板是某一条线渲染出来的，
       // 另一条线可能根本没有它的某些行（实测：预览线的 workflow-ptc 在稳定线上不存在，
@@ -717,26 +731,52 @@ export function apply(ctx) {
     console.error('custom-mode: 初始化 preset 目录时出现意外错误（已忽略）: ' + describe(error))
   }
 
-  ctx.inject(WEB_SERVICES, (scope) => {
+  try {
+    ctx.inject(WEB_SERVICES, (scope) => {
     // Compatibility guard: this plugin reads host APIs that a future DSH release could
     // reshape. Check them once and say so plainly, instead of letting every request
     // fail with an opaque 500.
     // 数据表形式：以后新增一处耦合点，只要在这里加一行 —— README 的耦合点清单与本表同源，
     // 让"上游改了 API 形状"在启动日志里就能看见，而不是等用户报"设置页白屏"。
-    const REQUIRED_APIS = [
+    //
+    // ★ 分两级，而不是一张"缺一即死"的表。理由是一次实测：`agentPresets.remove()` 在
+    //   dsh 0.1.7 上**不存在**（preset 定义改在内存里，删除要走 register() 返回的 disposer），
+    //   而本插件早已为它写了 noRemoveApi 降级文案 —— 把它列进必需项，会让**整个设置页**
+    //   在 0.1.7 上被自己关掉（实测 stderr：'设置页将不可用'）。
+    //   能力缺失该逐个降级，不该一票否决整页。
+    const CORE_APIS = [
       ['agentPresets.list()', () => typeof scope.agentPresets?.list === 'function'],
-      ['agentPresets.remove()', () => typeof scope.agentPresets?.remove === 'function'],
       ['connection.fetch.register()', () => typeof scope.connection?.fetch?.register === 'function'],
     ]
-    const missing = REQUIRED_APIS.filter(([, probe]) => !probe()).map(([name]) => name)
-    if (missing.length > 0) {
+    const OPTIONAL_APIS = [
+      // 旧线的文件系统语义；新线由 preset-backend 的 declarative 后端用 disposer 补上。
+      ['agentPresets.remove()', () => typeof scope.agentPresets?.remove === 'function'],
+      ['agentPresets.copy()', () => typeof scope.agentPresets?.copy === 'function'],
+    ]
+    const missingCore = CORE_APIS.filter(([, probe]) => !probe()).map(([name]) => name)
+    if (missingCore.length > 0) {
       console.error(
-        'custom-mode: 当前 DSH 版本缺少所需 API：' +
-          missing.join('、') +
+        'custom-mode: 当前 DSH 版本缺少必需 API：' +
+          missingCore.join('、') +
           '。设置页将不可用，请核对 DSH 版本或提 issue。',
       )
       return
     }
+    const absentOptional = OPTIONAL_APIS.filter(([, probe]) => !probe()).map(([name]) => name)
+
+    // 判据是**能力**不是版本号：0.1.7 仍是 alpha，按版本号写的分支会在下一次发布时静默失配。
+    const backendVerdict = detectPresetBackend(scope)
+    console.log(
+      'custom-mode: ' +
+        describeBackend(backendVerdict) +
+        (absentOptional.length > 0 ? ' · 可选能力缺失: ' + absentOptional.join('、') : ''),
+    )
+    if (backendVerdict.id === BACKEND_UNUSABLE) {
+      for (const reason of backendVerdict.reasons) console.error('custom-mode: ' + reason)
+      // 显式不可用，好过用错后端去写用户的 preset。
+      console.error('custom-mode: 设置页将不可用（本插件不会写入任何 preset）。')
+      return
+    }
 
     /**
      * Resolve the shipped-preset directory through the roster, which reports each
@@ -759,8 +799,17 @@ export function apply(ctx) {
       return shippedReady
     }
 
-    /** The roster, or an empty list — discovery itself reports broken rows rather than throwing. */
-    const roster = async () => {
+    /**
+     * 声明式注册表（dsh ≥ 0.1.7）下 preset 必须由插件自己注册；旧线只需把文件写到磁盘、平台自己去扫。
+     * 这里是后端的唯一实例（旧线为 null，所有相关分支都是空操作）。
+     */
+    const declarative =
+      backendVerdict.id === BACKEND_DECLARATIVE
+        ? createDeclarativeBackend({ scope, log: console.log, warn: console.error })
+        : null
+
+    /** 原始 roster：只读、无副作用。同步逻辑走它，避免与 {@link roster} 互相递归。 */
+    const rawRoster = async () => {
       const rows = await scope.agentPresets.list()
       if (!Array.isArray(rows)) {
         // 形状变了：静默返回空列表会让页面显示"一个助手都没有"，比报错更难查（曾经就因为
@@ -771,9 +820,114 @@ export function apply(ctx) {
         }
         return []
       }
-      return rows
+      // 新线的 list() 只有显示元数据（没有 trust / path），而 roster 的消费者（assistants.mjs、
+      // 整个路由层）都建立在这两个字段上。在这里从磁盘补出来，下游就不必做线判断。
+      return effectiveRosterRows(rows, { root: assistantRoot, backendId: backendVerdict.id })
     }
 
+    /**
+     * 把磁盘上的助手同步进注册表 —— **仅新线**（旧线上 `declarative` 为 null，整体是空操作）。
+     *
+     * 新线没有目录扫描，注册与注销都由本插件负责：不跑这一步，用户在设置页里新建/改名/删除的
+     * 助手就不会出现在选择器里。所以每次**写操作之后**都要重来一遍。
+     */
+    const doSync = async () => {
+      // 先把"本机有哪些模块"喂给 composition 层。
+      //
+      // 它原本靠文件系统探测出厂目录（`shippedPresetsDir()` 往上推三层找 node_modules），
+      // 而 **0.1.7 没有那个目录**：探测抛错、catch 返回 []、于是"本行能否在本机运行"的检查
+      // **静默失效**（不报错，也不报警）。新线上有更好的来源 ——注册表自己就知道每个已注册
+      // preset 的每一行的 moduleName。
+      // 放在这里而不是外面：`ctx.inject` 的回调不是 async（写成 await 会让模块直接语法错误）。
+      if (declarative !== null) {
+        try {
+          const inventory = await scope.agentPresets.compositionInventory()
+          const rows = (Array.isArray(inventory) ? inventory : []).flatMap((preset) => preset?.rows ?? [])
+          const names = rows.map((row) => row.moduleName).filter((name) => typeof name === 'string')
+          if (names.length > 0) {
+            setKnownModuleNames(names)
+            console.log(`custom-mode: 已注入 ${names.length} 个出厂行模块名（compositionInventory），供"本行能否在本机运行"的判定使用`)
+          }
+        } catch (error) {
+          // 注入不了就退回文件系统判定 —— 那是旧线的正常路径，不是错误状态。
+          console.error('custom-mode: 读取 compositionInventory 失败（回退文件系统判定）: ' + describe(error))
+        }
+      }
+      if (declarative === null) return
+      try {
+        const rows = await rawRoster()
+        const targets = []
+        for (const assistant of assistantsFromRoster(rows)) {
+          const dir = assistantDir(rows, assistant.id)
+          if (dir !== undefined) targets.push({ ...assistant, dir })
+        }
+        const results = await declarative.sync(targets)
+
+        // 核对每个助手的 composition：有没有"本机装不了的启用行"。
+        //
+        // 为什么必须由我们说出来：新线没有出厂 composition 可派生（`seedOnActivation` 只能回落到
+        // 包内模板），而模板可能来自**另一条** dsh 线。平台对含未知行的 preset 的处置是
+        // **静默把整个模式从所有选择器里丢掉**，设置页却照常工作 —— 用户只会看到"我的模式不见了"。
+        // 这一步把它变成一条指名道姓的日志。
+        for (const target of targets) {
+          try {
+            const text = readFileSync(join(target.dir, 'agent.cordis.yml'), 'utf8')
+            const bad = unresolvableRows(text)
+            if (bad.length > 0) {
+              console.error(
+                `custom-mode: 助手 "${target.id}" 有 ${bad.length} 行在本机装不了 —— ` +
+                  bad.map((b) => `${b.id}(${b.name})`).join('、') +
+                  '。含这种行的模式会被平台静默地从选择器里丢掉；可在设置页用"按本线修复"关掉它们。',
+              )
+            }
+          } catch (error) {
+            // 读不到就没法判 —— 不猜。
+            console.error(`custom-mode: 无法核对助手 "${target.id}" 的 composition: ${describe(error)}`)
+          }
+        }
+        const ok = results.filter((r) => r.ok === true)
+        const failed = results.filter((r) => r.ok === false)
+        // 成功也要说：新线上「设置页里能看到助手」完全取决于这一步，
+        // 而它此前是静默的 —— 出问题时没有任何一行日志能说明"到底同步了几个"。
+        console.log(
+          `custom-mode: 声明式注册表同步完成 —— 目标 ${targets.length} 个助手，成功 ${ok.length} 个` +
+            (failed.length > 0 ? `，失败 ${failed.length} 个` : '') +
+            `（${ok.map((r) => r.id).join(', ') || '无'}）`,
+        )
+        if (failed.length > 0) {
+          console.error(`custom-mode: ${failed.length} 个助手的 preset 未能挂载 —— 见上面的具体原因。`)
+        }
+      } catch (error) {
+        console.error('custom-mode: 同步 preset 到注册表失败（已忽略）: ' + describe(error))
+      }
+    }
+
+    /**
+     * 路由层用的 roster：首次调用会等**启动同步**完成，之后不再等。
+     *
+     * 为什么不是简单地 await 一次：`ctx.inject` 的回调不是 async（实测写成 `await` 会让模块
+     * 直接语法错误、插件加载失败），所以启动同步只能在这里补等；而它只该等一次 ——
+     * 写操作之后的重同步由 `resyncPresets` 负责，不该让每个请求都等一遍。
+     */
+    let startupSync = null
+    const roster = async () => {
+      if (startupSync !== null) {
+        const pending = startupSync
+        startupSync = null
+        await pending
+      }
+      return rawRoster()
+    }
+
+    /** 写操作之后调用：重新对齐注册表。失败已在内部记录，不抛出。 */
+    const resyncPresets = async () => {
+      startupSync = null
+      await doSync()
+    }
+
+    // 启动即同步：新线不是"写盘即生效"，第一次进来必须先注册。
+    startupSync = doSync()
+
     /**
      * One Fetch-shaped handler for the whole surface.
      *
@@ -872,12 +1026,24 @@ export function apply(ctx) {
           path: API_PREFIX + pathname,
           methods: [...methods],
           requestBody: 'buffered',
-          fetch: (request) => handle(request, pathname),
+          fetch: async (request) => {
+            const response = await handle(request, pathname)
+            // 写成功之后，把注册表同步到磁盘的新状态。
+            // 旧线上 `declarative` 是 null，这里恒为空操作；新线上没有它，用户在设置页
+            // 新建/改名/删除的助手就不会出现在选择器里 —— 是本插件最容易被漏掉的一步。
+            if (declarative !== null && request.method !== 'GET' && response.ok) await resyncPresets()
+            return response
+          },
         }),
         'custom-mode.route' + pathname,
       )
     }
-  })
+    })
+  } catch (error) {
+    // ctx.inject 自身抛错（例如宿主改了它的签名）会让整段装配静默消失：没有路由、没有日志。
+    // 这一层是把它变成一条可读的错误。
+    console.error('custom-mode: ctx.inject 注册失败（这是个 bug，请提 issue）: ' + describe(error))
+  }
 }
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-custom-mode",
-  "version": "1.9.8",
+  "version": "1.9.10",
   "description": "Custom modes and custom prompts for DeepSeek Harness (dsh): edit a mode's system prompt on the settings page (it takes effect on the next model step), pick its base mode, switch plugin rows one by one, and keep several assistants side by side — coding, chat or roleplay (RP) personas (multi-mode / multi-agent).",
   "license": "MIT",
   "type": "module",
@@ -58,13 +58,14 @@
     "locales.mjs",
     "journal.mjs",
     "cordis.patch.yml",
+    "preset-backend/",
     "preset/"
   ],
   "scripts": {
     "test": "node ../test/run.mjs"
   },
   "peerDependencies": {
-    "@deepseek-ai/dsh": ">=0.1.5-rc.2 <0.2.0-0"
+    "@deepseek-ai/dsh": ">=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0"
   },
   "publishConfig": {
     "access": "public",
@@ -76,6 +77,6 @@
     }
   },
   "engines": {
-    "dsh": ">=0.1.5-rc.2 <0.2.0-0"
+    "dsh": ">=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0"
   }
 }

package/preset-backend/declarative.mjs

@@ -0,0 +1,180 @@
+/**
+ * declarative 后端：dsh ≥ 0.1.7 的「声明式注册表」。
+ *
+ * ## 与 legacy 后端的差别，一句话
+ *
+ * 旧线上，插件只是**把文件写到磁盘**（`$DSH_HOME/.agent-presets/<id>/`），平台自己去扫、去挂；
+ * 新线上没有目录扫描，插件必须**自己把 preset 注册进注册表**，并持有返回的 disposer。
+ *
+ * ## 三条由实测定下来的硬约束（0.1.7-alpha.2）
+ *
+ *  1. **相对模块说明符不工作。** 本插件的 composition 里有 `name: './prompt-reader.mjs'` 这类
+ *     相对路径；旧线上它相对 preset 目录解析，而 `register()` 在 profile 的 baseUrl 下挂载。
+ *     实测：相对路径 → `broken: … never started`；绝对 `file://` URL → 正常 mount。
+ *     ⇒ `toPluginRows()` 必须把相对说明符改写成绝对 URL。
+ *  2. **`register()` 的返回值是 disposer**，注销唯一手段；服务上没有 `remove()`。
+ *  3. **同一个 id 重复注册会抛 `Duplicate agent preset`**
+ *     ⇒ 重新挂载前必须先 dispose 旧的。
+ *
+ * ## 不写任何文件
+ *
+ * 新线不需要把 preset「落到磁盘」才生效，所以这里只读 composition、只动内存注册表。
+ * `agent.cordis.yml` 仍然写盘 —— 它是用户可见、可迁移、可手改的真相，也是旧线唯一的输入。
+ */
+
+import { existsSync, readFileSync } from 'node:fs'
+import { join } from 'node:path'
+import { pathToFileURL } from 'node:url'
+import { parseComposition } from './parse-composition.mjs'
+
+export const BACKEND_ID = 'declarative'
+
+/** Evaluate a `!!js` predicate. Only ever applied to text this feature itself wrote. */
+function resolveDisabled(value) {
+  if (value !== null && typeof value === 'object' && typeof value.__js === 'string') {
+    try {
+      // eslint-disable-next-line no-new-func
+      return Boolean(new Function(`"use strict"; return (${value.__js});`)())
+    } catch {
+      // 表达式求值不了时按"关掉"处理：宁可少一行能力，也不要让整条 preset 挂载失败。
+      return true
+    }
+  }
+  return value === true
+}
+
+/** A `./x.mjs` specifier becomes an absolute file:// URL; package specifiers pass through. */
+export function absoluteSpecifier(specifier, presetDir) {
+  if (typeof specifier !== 'string' || !specifier.startsWith('.')) return specifier
+  return pathToFileURL(join(presetDir, specifier)).href
+}
+
+/**
+ * Turn parsed composition rows into the row objects `register()` takes.
+ *
+ * Group rows keep their `isolate` realm and their children: the composition's own comments require a
+ * service row to sit inside such a group, or it publishes into the root realm and collides.
+ *
+ * @param {Array<object>} rows - rows from {@link parseComposition}.
+ * @param {string} presetDir - the assistant's directory, the base for relative specifiers.
+ * @returns {Array<object>} plugin rows.
+ */
+export function toPluginRows(rows, presetDir) {
+  if (!Array.isArray(rows)) return []
+  const out = []
+  for (const row of rows) {
+    if (row === null || typeof row !== 'object' || typeof row.id !== 'string') continue
+    const plugin = { id: row.id }
+    if (typeof row.name === 'string') plugin.name = absoluteSpecifier(row.name, presetDir)
+    if (row.group === true) {
+      plugin.group = true
+      if (row.isolate !== undefined && row.isolate !== null) plugin.isolate = row.isolate
+      plugin.config = toPluginRows(row.config, presetDir)
+    } else if (row.config !== undefined && row.config !== null) {
+      plugin.config = row.config
+    }
+    if (row.disabled !== undefined) plugin.disabled = resolveDisabled(row.disabled)
+    out.push(plugin)
+  }
+  return out
+}
+
+/**
+ * @param {{
+ *   scope: object,
+ *   log?: (m: string) => void,
+ *   warn?: (m: string) => void,
+ * }} deps
+ */
+export function createDeclarativeBackend({ scope, log = console.log, warn = console.error }) {
+  /** presetId → { dispose, dir } —— 当前挂在注册表里的东西，注销的唯一凭据。 */
+  const mounted = new Map()
+
+  async function unmount(id) {
+    const entry = mounted.get(id)
+    if (entry === undefined) return
+    mounted.delete(id)
+    try {
+      await entry.dispose()
+    } catch (error) {
+      warn(`custom-mode: 注销 preset "${id}" 时出错（已忽略）: ${describe(error)}`)
+    }
+  }
+
+  /** Build the definition for one assistant directory, or null when it has no composition. */
+  function buildDefinition(assistant) {
+    const file = join(assistant.dir, 'agent.cordis.yml')
+    if (!existsSync(file)) return null
+    const rows = parseComposition(readFileSync(file, 'utf8'))
+    const plugins = toPluginRows(rows, assistant.dir)
+    if (plugins.length === 0) return null
+    const definition = { id: assistant.id, plugins }
+    if (assistant.name !== undefined && assistant.name !== '') definition.name = assistant.name
+    if (assistant.description !== undefined && assistant.description !== '') definition.description = assistant.description
+    if (Number.isFinite(assistant.order)) definition.order = assistant.order
+    return definition
+  }
+
+  /**
+   * (Re)mount one assistant. Idempotent: an already-mounted id is disposed first, because the
+   * registry refuses a duplicate id outright.
+   */
+  async function mountOne(assistant) {
+    let definition
+    try {
+      definition = buildDefinition(assistant)
+    } catch (error) {
+      // 解析失败是**用户可见**的问题（手改坏了 composition），要显式说，不能静默跳过。
+      warn(`custom-mode: 预设 "${assistant.id}" 的 composition 解析失败 —— ${describe(error)}。该助手不会出现在选择器里。`)
+      await unmount(assistant.id)
+      return { ok: false, error: describe(error) }
+    }
+    if (definition === null) {
+      await unmount(assistant.id)
+      return { ok: false, error: 'no composition' }
+    }
+    await unmount(assistant.id)
+    try {
+      const dispose = await scope.agentPresets.register(definition)
+      mounted.set(assistant.id, { dispose, dir: assistant.dir })
+      return { ok: true }
+    } catch (error) {
+      // register 会抛（Duplicate / id 空 / 已存在）：说清是哪个助手、哪条错误。
+      warn(`custom-mode: 注册预设 "${assistant.id}" 失败 —— ${describe(error)}`)
+      return { ok: false, error: describe(error) }
+    }
+  }
+
+  /** Bring the registry in line with the given assistant list: mount all, drop the rest. */
+  async function sync(assistants) {
+    const results = []
+    for (const assistant of assistants) results.push({ id: assistant.id, ...(await mountOne(assistant)) })
+    const wanted = new Set(assistants.map((a) => a.id))
+    for (const id of [...mounted.keys()]) {
+      if (!wanted.has(id)) {
+        await unmount(id)
+        results.push({ id, ok: true, unmounted: true })
+      }
+    }
+    return results
+  }
+
+  async function disposeAll() {
+    for (const id of [...mounted.keys()]) await unmount(id)
+  }
+
+  return {
+    id: BACKEND_ID,
+    /** 新线不把 preset 落到磁盘，注册表就是唯一真相。 */
+    writesPresetFiles: false,
+    sync,
+    mountOne,
+    unmount,
+    disposeAll,
+    mountedIds: () => [...mounted.keys()],
+  }
+}
+
+function describe(error) {
+  return String((error && error.message) || error)
+}

package/preset-backend/detect.mjs

@@ -0,0 +1,101 @@
+/**
+ * 能力探测：判定当前 dsh 线用的是哪一种 agent-preset 机制。
+ *
+ * ## 为什么按能力探测，而不是按版本号
+ *
+ * preset 机制在 0.1.7 被整体换过（见 notes/2026-09-22-双线适配设计.md §1）：
+ *
+ *   0.1.2 … 0.1.6   `@deepseek-ai/dsh-agent-presets`（复数）—— **扫目录** `$DSH_HOME/.agent-presets/`，
+ *                   服务带读改删三件套 `read` / `copy` / `remove`，`list()` 的行带 `trust` 与 `path`。
+ *   0.1.7 +         `@deepseek-ai/dsh-agent-preset`（单数）+ `-registry` —— **声明式注册表**，
+ *                   不扫目录，服务有 `register` / `compositionInventory` / `select`，但**没有** remove。
+ *
+ * 0.1.7 仍在 alpha（已到 alpha.2），接口还会动。按版本号写分支会在下一次发布时**静默失配**，
+ * 而按能力探测天然面向未来。
+ *
+ * ## 判据的选取
+ *
+ * 主判据是 **`remove` 的有无**：它是"文件系统语义"的直接标志 —— 旧线能删磁盘上的 preset 目录，
+ * 新线的定义在内存里、只能靠 `register()` 返回的 disposer 注销。
+ * 辅以 `register` / `compositionInventory` 作交叉验证；**信号矛盾时不猜**，落到只读降级态并显式报告。
+ */
+
+/** 后端标识。字符串而不是布尔，便于日志与测试断言。 */
+export const BACKEND_LEGACY = 'legacy-dir'
+export const BACKEND_DECLARATIVE = 'declarative'
+export const BACKEND_UNUSABLE = 'unusable'
+
+/**
+ * Probe the agent-preset service and decide which backend to drive it with.
+ *
+ * @param {{agentPresets?: object}} scope - the scoped context carrying `agentPresets`.
+ * @returns {{
+ *   id: string,
+ *   capabilities: {list: boolean, register: boolean, remove: boolean, copy: boolean, read: boolean,
+ *                  inventory: boolean, select: boolean},
+ *   reasons: string[],
+ *   conflict: boolean,
+ * }}
+ */
+export function detectPresetBackend(scope) {
+  const svc = scope?.agentPresets
+  const capabilities = {
+    list: typeof svc?.list === 'function',
+    register: typeof svc?.register === 'function',
+    remove: typeof svc?.remove === 'function',
+    copy: typeof svc?.copy === 'function',
+    read: typeof svc?.read === 'function',
+    inventory: typeof svc?.compositionInventory === 'function',
+    select: typeof svc?.select === 'function',
+  }
+  const reasons = []
+
+  // 核心前提：没有 list() 就既读不到 roster，也没法判断任何事。
+  if (!capabilities.list) {
+    reasons.push('agentPresets.list() 不可用 —— 无法读取 preset roster')
+    return { id: BACKEND_UNUSABLE, capabilities, reasons, conflict: false }
+  }
+
+  // 旧线的标志：文件系统语义齐全（remove 是其中最不会误报的一个 —— 新线确实没有它）。
+  const looksLegacy = capabilities.remove
+  // 新线的标志：声明式注册面存在。
+  const looksDeclarative = capabilities.register && capabilities.inventory
+
+  if (looksLegacy && looksDeclarative) {
+    // 两条线的特征同时出现：可能 upstream 把两套并了，也可能是我们判错了。
+    // **不猜** —— 显式报告并走只读，避免用错后端写坏用户的 preset。
+    reasons.push(
+      '同时探测到两套机制的特征（既有 remove()，又有 register() + compositionInventory()）。' +
+        '这可能是 dsh 换用了一套兼容层；本插件不在这种情况下写入任何 preset，' +
+        '只做只读展示。请提 issue 并附上 dsh --version。',
+    )
+    return { id: BACKEND_UNUSABLE, capabilities, reasons, conflict: true }
+  }
+
+  if (looksLegacy) {
+    reasons.push('agentPresets.remove() 存在 —— 文件系统语义的旧线（扫 $DSH_HOME/.agent-presets/）')
+    return { id: BACKEND_LEGACY, capabilities, reasons, conflict: false }
+  }
+
+  if (looksDeclarative) {
+    reasons.push('agentPresets.remove() 不存在，但 register() + compositionInventory() 存在 —— 声明式注册表的新线')
+    return { id: BACKEND_DECLARATIVE, capabilities, reasons, conflict: false }
+  }
+
+  reasons.push(
+    '既没有 remove()（旧线的文件系统语义），也没有 register() + compositionInventory()（新线的声明式注册表）。' +
+      '这不像任何一条已知的 dsh 线。',
+  )
+  return { id: BACKEND_UNUSABLE, capabilities, reasons, conflict: false }
+}
+
+/** 人类可读的一行摘要，供启动日志使用。 */
+export function describeBackend(verdict) {
+  const on = Object.entries(verdict.capabilities)
+    .filter(([, v]) => v)
+    .map(([k]) => k)
+  const off = Object.entries(verdict.capabilities)
+    .filter(([, v]) => !v)
+    .map(([k]) => k)
+  return `backend=${verdict.id} · 有: ${on.join(',') || '(无)'} · 无: ${off.join(',') || '(无)'}`
+}

package/preset-backend/index.mjs

@@ -0,0 +1,143 @@
+/**
+ * preset-backend —— 让设置页在两条 dsh 线上跑同一套逻辑。
+ *
+ * ## 这个目录解决什么
+ *
+ * preset 机制在 0.1.7 被整体换过：旧线**扫目录**、服务带读改删；新线是**声明式注册表**、
+ * 不扫目录、没有 remove。设置页本身（UI、双语、composition 编译、提示词读写）两线一模一样，
+ * 差别只在三处：
+ *
+ *   A 路径     —— 助手目录在哪、prompt/composition 文件在哪
+ *   B roster   —— 「有哪些助手」从哪知道
+ *   C 出厂组成 —— base mode 的 composition 从哪来
+ *
+ * 本模块把这三处收成一个后端对象（见 notes/2026-09-22-双线适配设计.md §3）。
+ *
+ * ## 关键设计：新线上**合成 roster**，而不是让下游到处分支
+ *
+ * 新线 `list()` 返回的行没有 `trust` / `path`（实测），而 `assistants.mjs` 的
+ * `assistantsFromRoster` / `assistantDir` 与 `index.mjs` 的整个路由层都建立在这两个字段上。
+ * 与其把线判断散布到十几处调用点，不如在**这一处**补出一个与旧线同形的行列表：
+ * 助手本来就是磁盘上的目录（`$DSH_HOME/.agent-presets/<id>/`），扫一遍即可。
+ * 这样路由层零改动，两条线走同一段代码。
+ */
+
+import { existsSync, readFileSync, statSync } from 'node:fs'
+import { basename, join } from 'node:path'
+import { scanManagedDirs } from '../assistants.mjs'
+import { parseComposition } from './parse-composition.mjs'
+
+export { detectPresetBackend, describeBackend, BACKEND_LEGACY, BACKEND_DECLARATIVE, BACKEND_UNUSABLE } from './detect.mjs'
+export { createDeclarativeBackend, toPluginRows, absoluteSpecifier } from './declarative.mjs'
+export { parseComposition, CompositionParseError } from './parse-composition.mjs'
+
+/** The managed-assistant marker file, same name `assistants.mjs` uses. */
+const SEED_MARKER = '.custom-mode.json'
+const COMPOSITION_FILE = 'agent.cordis.yml'
+const META_FILE = 'preset.yml'
+
+/**
+ * Read `preset.yml` beside a composition.
+ *
+ * Uses the same small parser as the composition: the file is written by this feature
+ * (`yamlScalar`), so a strict subset is enough, and a hand-broken meta must not take the page down.
+ *
+ * @param {string} dir - assistant directory.
+ * @returns {{name?: string, description?: string}} whatever could be read.
+ */
+export function readPresetMeta(dir) {
+  const file = join(dir, META_FILE)
+  if (!existsSync(file)) return {}
+  try {
+    const parsed = parseComposition(readFileSync(file, 'utf8'))
+    if (parsed === null || typeof parsed !== 'object' || Array.isArray(parsed)) return {}
+    const out = {}
+    if (typeof parsed.name === 'string') out.name = parsed.name
+    if (typeof parsed.description === 'string') out.description = parsed.description
+    return out
+  } catch {
+    // 元数据读不了不是致命问题：目录里还有 composition，助手仍应出现（只是名字退回 id）。
+    return {}
+  }
+}
+
+/**
+ * Directories under `root` that this feature manages.
+ *
+ * Delegates to `assistants.mjs:scanManagedDirs` on purpose. My first version invented its own
+ * predicate (look for `.custom-mode.json` inside each assistant directory) and therefore found
+ * **nothing** — measured: the preset root held `.agent-presets/.custom-mode.json` (a root-level
+ * "this feature owns this root" marker) while the assistant directory had no such file, so
+ * `sync()` reported "目标 0 个助手". The real predicate is "has prompt.md, and either ships
+ * prompt-reader.mjs or the composition still references it". Reusing it also means the two
+ * definitions cannot drift.
+ *
+ * @param {string} root - user preset root.
+ * @returns {string[]} absolute directory paths, sorted for a stable roster order.
+ */
+export function scanManagedAssistantDirs(root) {
+  return scanManagedDirs(root)
+}
+
+/**
+ * Synthesize roster rows in the shape `assistants.mjs` expects, by scanning the disk.
+ *
+ * Only needed on the declarative line, whose `list()` does not carry `trust` / `path`.
+ * On the legacy line the platform's own rows are richer (they include `broken` diagnostics),
+ * so callers should prefer them and fall back to this.
+ *
+ * @param {string} root - user preset root (`$DSH_HOME/.agent-presets`).
+ * @returns {Array<{id: string, trust: 'user', path: string, name: string, description: string}>}
+ */
+export function synthesizeRosterRows(root) {
+  return scanManagedAssistantDirs(root).map((dir) => {
+    const meta = readPresetMeta(dir)
+    return {
+      id: basename(dir),
+      trust: 'user',
+      path: join(dir, COMPOSITION_FILE),
+      name: meta.name ?? '',
+      description: meta.description ?? '',
+    }
+  })
+}
+
+/**
+ * The roster to drive the settings page with.
+ *
+ * Legacy line: the platform's rows already describe authored presets, so they are used as-is.
+ * Declarative line: its rows are display metadata only, so authored presets are re-derived from disk
+ * and **merged** with whatever the registry reported (registry rows win for `broken`, which is a
+ * mount diagnostic only the platform can produce).
+ *
+ * @param {Array<object>} rows - `agentPresets.list()` result.
+ * @param {{root: string, backendId: string}} options
+ * @returns {Array<object>} rows including every authored assistant.
+ */
+export function effectiveRosterRows(rows, { root, backendId }) {
+  const platform = Array.isArray(rows) ? rows : []
+  if (backendId !== 'declarative') return platform
+
+  const byId = new Map()
+  for (const synth of synthesizeRosterRows(root)) byId.set(synth.id, synth)
+
+  // 注册表能给出 mount 诊断（broken），合并进合成行；合成行提供 trust/path。
+  for (const row of platform) {
+    if (row === null || typeof row !== 'object' || typeof row.id !== 'string') continue
+    const synth = byId.get(row.id)
+    if (synth === undefined) continue
+    if (typeof row.broken === 'string' && row.broken !== '') synth.broken = row.broken
+    if (typeof row.name === 'string' && row.name !== '') synth.name = row.name
+    if (typeof row.description === 'string' && row.description !== '') synth.description = row.description
+  }
+  return [...byId.values()]
+}
+
+/** True when `dir` looks like a managed assistant directory (used to validate a path). */
+export function isManagedAssistantDir(dir) {
+  try {
+    return statSync(dir).isDirectory() && existsSync(join(dir, SEED_MARKER))
+  } catch {
+    return false
+  }
+}

package/preset-backend/parse-composition.mjs

@@ -0,0 +1,177 @@
+/**
+ * A deliberately small YAML reader, sized to `agent.cordis.yml`.
+ *
+ * ## Why this exists
+ *
+ * The declarative backend (dsh ≥ 0.1.7) needs the composition as **JS row objects** to hand to
+ * `agentPresets.register()`; there is no file for the platform to scan any more. Three routes were
+ * ruled out by measurement before writing this:
+ *
+ *  1. **Borrow the host's parser** — `createRequire(import.meta.url).resolve('@deepseek-ai/cordis-plugin-loader')`
+ *     fails from inside a profile-installed plugin (measured), so the loader's YAML entry is unreachable.
+ *  2. **Reconstruct the rows from `compositionInventory()`** — it returns a **flattened** row list
+ *     (`entryId` / `moduleName` / `enabled`), so the `isolate` groups that service rows must sit inside
+ *     are lost. The composition's own comments say a service row outside such a group collides with
+ *     other presets at mount, so flattening is not an option.
+ *  3. **Skip the text and re-render** — the composer works by *text surgery* (it preserves comments and
+ *     `!!js` predicates byte-for-byte), so it has no structured row model to hand out.
+ *
+ * ## What it supports, and what it refuses
+ *
+ * Only what this feature's own files contain: block sequences, nested block mappings, block scalars
+ * (`|`, `|-`, `>`, `>-`), quoted and plain scalars, comments, and the `!!js` tag. Anything else is
+ * refused with a located error rather than guessed — a mis-read row silently changes what the model
+ * sees, which is the failure this repository least tolerates.
+ *
+ * `!!js` values are returned as `{ __js: "<source>" }` so callers decide how to evaluate them; this
+ * module never runs anything.
+ */
+
+/** Thrown with the offending line number so a broken composition is diagnosable, not mysterious. */
+export class CompositionParseError extends Error {
+  constructor(message, line) {
+    super(`${message}（第 ${line} 行）`)
+    this.name = 'CompositionParseError'
+    this.line = line
+  }
+}
+
+const isBlank = (line) => line.trim() === '' || line.trim().startsWith('#')
+const indentOf = (line) => line.length - line.trimStart().length
+
+/**
+ * Parse a composition document into plain JS.
+ *
+ * @param {string} text - the composition file's contents.
+ * @returns {any} the document (a block sequence for a composition file).
+ */
+export function parseComposition(text) {
+  const lines = String(text).split('\n')
+  const state = { lines, index: 0 }
+  skipBlank(state)
+  if (state.index >= lines.length) return null
+  return parseNode(state, indentOf(lines[state.index]))
+}
+
+function skipBlank(state) {
+  while (state.index < state.lines.length && isBlank(state.lines[state.index])) state.index += 1
+}
+
+/** The next content line, or undefined. */
+function peek(state) {
+  skipBlank(state)
+  return state.lines[state.index]
+}
+
+/**
+ * Parse the block starting at the current line, whose entries are indented at least `indent`.
+ * A line beginning with `- ` opens a sequence; anything else opens a mapping.
+ */
+function parseNode(state, indent) {
+  const line = peek(state)
+  if (line === undefined) return null
+  return /^\s*-(\s|$)/.test(line) ? parseSequence(state, indent) : parseMapping(state, indent)
+}
+
+function parseSequence(state, indent) {
+  const out = []
+  for (;;) {
+    const line = peek(state)
+    if (line === undefined || indentOf(line) < indent || !/^\s*-(\s|$)/.test(line)) break
+    const lineNo = state.index + 1
+    const rest = line.trimStart().slice(1)
+    // `- ` on its own, or `- key: value` inline.
+    const inline = rest.trimStart()
+    if (inline === '') {
+      state.index += 1
+      out.push(parseNode(state, indent + 1))
+    } else if (/^[^:]+:(\s|$)/.test(inline)) {
+      // Inline mapping start: rewrite it as a mapping at its own column and re-parse.
+      state.lines[state.index] = ' '.repeat(indent + 2) + inline
+      out.push(parseMapping(state, indent + 2))
+    } else {
+      state.index += 1
+      out.push(parseScalar(inline, lineNo))
+    }
+  }
+  return out
+}
+
+function parseMapping(state, indent) {
+  const out = {}
+  for (;;) {
+    const line = peek(state)
+    if (line === undefined || indentOf(line) < indent) break
+    if (/^\s*-(\s|$)/.test(line)) break
+    const lineNo = state.index + 1
+    const match = /^([A-Za-z_][\w.-]*)\s*:(.*)$/.exec(line.trim())
+    if (match === null) throw new CompositionParseError(`无法把这一行读成映射项：${JSON.stringify(line.trim())}`, lineNo)
+    const key = match[1]
+    const tail = match[2]
+    state.index += 1
+    if (tail.trim() === '') {
+      // Value is a nested block (or null when nothing is indented under it).
+      const next = peek(state)
+      if (next === undefined || indentOf(next) <= indent) out[key] = null
+      else out[key] = parseNode(state, indentOf(next))
+    } else if (/^[|>][-+]?\d*\s*$/.test(tail.trim())) {
+      out[key] = parseBlockScalar(state, indent, tail.trim())
+    } else {
+      out[key] = parseScalar(tail.trim(), lineNo)
+    }
+  }
+  return out
+}
+
+/** A `|`/`>` block scalar: consume every more-indented line, keeping its text. */
+function parseBlockScalar(state, indent, header) {
+  const fold = header.startsWith('>')
+  const stripFinal = header.includes('-')
+  const body = []
+  let blockIndent = -1
+  while (state.index < state.lines.length) {
+    const line = state.lines[state.index]
+    if (line.trim() !== '' && indentOf(line) <= indent) break
+    body.push(line)
+    state.index += 1
+  }
+  while (body.length > 0 && body[0].trim() === '') body.shift()
+  while (body.length > 0 && body[body.length - 1].trim() === '') body.pop()
+  if (blockIndent === -1) {
+    blockIndent = body.reduce((min, l) => (l.trim() === '' ? min : Math.min(min, indentOf(l))), Number.MAX_SAFE_INTEGER)
+    if (blockIndent === Number.MAX_SAFE_INTEGER) blockIndent = indent + 2
+  }
+  const text = body.map((l) => l.slice(blockIndent)).join('\n')
+  const value = fold ? text.replace(/\n(?!\n)/g, ' ') : text
+  return stripFinal ? value : value + '\n'
+}
+
+/**
+ * A scalar: `!!js` tagged, quoted, or plain.
+ *
+ * Plain scalars stay strings — the composer only ever writes strings, booleans and numbers, and a
+ * bare word like `standard` must not become a date or a number.
+ */
+export function parseScalar(raw, lineNo = 0) {
+  const value = raw.trim()
+  if (value === '') return null
+  if (value.startsWith('!!js')) {
+    const source = value.slice(4).trim()
+    if (source === '') throw new CompositionParseError('!!js 后面没有表达式', lineNo)
+    return { __js: source }
+  }
+  if (value === 'true') return true
+  if (value === 'false') return false
+  if (value === 'null' || value === '~') return null
+  if (/^-?\d+$/.test(value)) return Number(value)
+  if (/^"(?:[^"\\]|\\.)*"$/.test(value)) {
+    try {
+      return JSON.parse(value)
+    } catch {
+      throw new CompositionParseError(`双引号标量无法转义：${value}`, lineNo)
+    }
+  }
+  if (/^'(?:[^']|'')*'$/.test(value)) return value.slice(1, -1).replace(/''/g, "'")
+  if (/^[[{]/.test(value)) throw new CompositionParseError(`不支持流式集合：${value}`, lineNo)
+  return value
+}

package/seed.mjs

@@ -79,7 +79,12 @@ export function starterComposition(options = {}) {
   } catch (error) {
     console.error(
       'custom-mode: 无法从本机安装的出厂组成派生播种文件（' + describe(error) + '），改用包内模板。' +
-        '如果这条 dsh 线与该模板的差异行不匹配，模式可能被判为 broken 而不出现在选择器里。',
+        // 0.1.7 起这条是**预期**的：那条线不再有 `@deepseek-ai/dsh-agent-presets` 包，
+        // 因而没有 presets/ 目录可派生 —— 出厂定义改成了 web-app bundle 里的声明行。
+        // 模板能不能用不靠猜：宿主半边随后会用 `compositionInventory()` 的模块名集合
+        // 逐行核对，装不了的行会指名报出来（见 index.mjs 的 doSync）。
+        '若该 dsh 线已改用声明式 preset（0.1.7+），这是预期回退：那条线没有 presets/ 目录。' +
+        '插件随后会核对模板的每一行能否在本机运行，装不了的行会被指名报出。',
     )
     return null
   }