dsh-code-server-app 0.3.65 → 0.3.66

package/lib/index.js

@@ -105,37 +105,60 @@ if (z === null || z === undefined) {
 
 export const name = 'code-server';
 // connection:client↔host 通道(web 走 webServer 的 /api,desktop 走 IPC 帧管道);
-// settings:设置卡片的数据域。两者在 web 与 desktop profile 下都存在。
+// settings:**设置的数据域**。两条线都有这个服务(所以它可以是硬依赖),但**模型不同**:
+//   · 旧线(rc 0.1.5-rc.x;也含"座位已搬到插件页、数据面还是旧的"0.1.6-alpha.2):
+//     `settings.register(ns, schema)` → `scope.get()/watch()`,值持久化在官方 settings 文档;
+//   · 新线(alpha ≥ 0.1.7-alpha.1):`register/get/watch` 已删除,配置就是**本插件条目自己的 Config**
+//     (可编辑字段必须 `.volatile()`),读值走 `config.<field>.get()` 活引用,变更通知走
+//     `settings/document-updated`。
+// 两条线的选择在 apply 里**按能力探测**(`typeof settings.register === 'function'`),不比较版本号。
 export const inject = ['connection', 'settings'];
 
-/** 设置命名空间:卡片经官方 settings 域读写,持久化到官方 settings 文档。 */
+/** profile 条目 id(cordis.patch.yml 的 `- id: code-server`)。
+ *  新线里它同时也是**设置命名空间**:`ctx.configForms.get(entryId)` 与宿主的 settings.describe
+ *  都按条目 id 取用(表单只展示"活动且可唯一定位"的条目)。客户端半部的 ENTRY_ID 必须与此一致。 */
 export const SETTINGS_NS = 'code-server';
 
-/** 设置卡片 schema(只留三个可改设置:claimExtensions / fullscreenOnOpen / keepResident)。
- *  旧设置文档里残留的 reserveComposer / windowedOpen / fileOpenScope 不再出现在 schema 里 ——
- *  schemastery 的 object 非 strict 会把未知键原样 merge 进解析结果,既不报错也不影响取值,故无需迁移。 */
-export const Config = z.object({
+/**
+ * 可配置字段表(**唯一真源**):两条数据线共用同一份字段定义,只在"是否 volatile"上分叉。
+ *
+ * 为什么必须分叉(0.3.66 实测):
+ *   · 新线(alpha ≥ 0.1.7-alpha.1)把插件配置模型换成"插件条目自己的 Config":
+ *     `ctx.settings.register(ns, schema)` 已删除;宿主只把 **`.volatile()` 字段**当作该条目的可编辑表单
+ *     (settings.describe 按 volatile 投影并明确报错 `Config field "x" is not volatile`),
+ *     且保存会**就地重解析**这个叶子(不重挂插件)⇒ 字段必须 volatile,读值必须走 config.<field>.get()。
+ *   · 旧线要把同一份 schema 注册进官方 settings 域(`settings.register(SETTINGS_NS, schema)`),
+ *     而**那里不能用带 volatile 的 schema**:schemastery 3.18.3 起 volatile 是**解析期**行为
+ *     (`createVolatile(value)` 在 schema 里完成),旧的 settings 域不认识它,会把活引用直接交给线路
+ *     (JSON 化后是空对象 `{}`)⇒ 卡片读到的全是空值。所以旧线注册 `SettingsSchema`(同字段、无 volatile)。
+ *   · rc 线的 schemastery 是 3.18.2,**根本没有 `.volatile()`**(3.18.3 才加)⇒ 无条件调用会在模块
+ *     求值期抛 `TypeError`、整棵插件树加载失败。故一律经 `vol()` 探测能力后再包。
+ *
+ * 旧设置文档里残留的 reserveComposer / windowedOpen / fileOpenScope 不再出现在 schema 里 ——
+ * schemastery 的 object 非 strict 会把未知键原样 merge 进解析结果,既不报错也不影响取值,故无需迁移。
+ */
+const SETTING_FIELDS = {
   /** 服务方式:loopback(默认)独立回环端口;dsh 挂到 DSH webServer 的 /code-server
    *  (同源、无额外端口、复用 DSH 的 Host/Origin + cookie 防护;需要 DSH 提供 webServer 服务,
    *  缺失或注册失败时自动回退 loopback)。没有卡片行:改 cordis.patch.yml 的 config.serve
-   *  或设置文档里的 code-server.serve。 */
-  serve: z.union([z.const('loopback'), z.const('dsh')]).default('loopback'),
+   *  或设置里的 code-server.serve。 */
+  serve: () => z.union([z.const('loopback'), z.const('dsh')]).default('loopback'),
   /** keepResident=true(默认)客户端在宿主 running 后把 IDE 预先加载到"停放区",
    *  切标签/收起侧栏不再重载;false 则只在打开面板时才加载(省内存)。 */
-  keepResident: z.boolean().default(true),
+  keepResident: () => z.boolean().default(true),
   /** 认领类型(0.2.11):按扩展名决定哪些文件交给 VS Code 打开(分号分隔,`*` = 其余类型也认领,
    *  `!ext` = 不认领,排除优先)。**不再区分 session/absolute 作用域** —— 所有
    *  `dsh-resource://file/**` 地址一视同仁。语法、默认值与解析见 lib/claim-types.js。 */
-  claimExtensions: z.string().default(DEFAULT_CLAIM_EXTENSIONS),
+  claimExtensions: () => z.string().default(DEFAULT_CLAIM_EXTENSIONS),
   /** fullscreenOnOpen=true(默认):打开 Code Server 标签(含点开产物/交付文件)时,
    *  客户端把右侧栏切到全屏(铺满窗口);false 则保持 DSH 默认的 push(与对话并排)。
    *  只影响"打开那一刻":之后用户点「退出全屏」不会被抢回去。 */
-  fullscreenOnOpen: z.boolean().default(true),
+  fullscreenOnOpen: () => z.boolean().default(true),
   /** editorBridge=true(默认):启用「编辑器桥」(0.3.0)—— 树内扩展 dshcs-editor-bridge 与
    *  host 之间建立**只读**通道,给 agent 提供 only-the-editor-knows 的上下文(未保存缓冲区、
    *  诊断、活动选区),并让编辑器里的动作能驱动 DSH。关闭后不写 bridge.json、不注册编辑器工具,
    *  扩展会休眠(它读不到配置就不做任何事)。安全模型见 lib/bridge.mjs 顶部。 */
-  editorBridge: z.boolean().default(true),
+  editorBridge: () => z.boolean().default(true),
   /** fim=false(默认):**实验性**的 FIM(幽灵)补全。开启后宿主的编辑器桥多一条**有界的模型调用**
    *  路由(`POST /complete`),编辑器里的内联补全(灰字)由它供给;宿主为此注册一个自己的 LLM
    *  适配器路由 `dshcs-fim`(走 Completions API 的 `/beta/completions`)。
@@ -144,18 +167,37 @@ export const Config = z.object({
    *  不外发内容);②模型在"不该补的位置"会硬凑(实测 2/2 复现),需要编辑器侧判据兜;
    *  ③这条调用**不进 DSH 的 token 计量**(一次性调用不是 loop 请求,不写会话日志),
    *  用量只在扩展状态栏与设置卡里可见。安全模型见 lib/fim-adapter.mjs 顶部。 */
-  fim: z.boolean().default(false),
+  fim: () => z.boolean().default(false),
   /** 停顿多久才发一次补全请求(毫秒)。太小 ⇒ 打字过程中反复触发;太大 ⇒ 失去"补全"的意义。
    *  取值在消费处夹到 [100, 3000](clampDebounce),设置里填什么都不至于打到链路上。 */
-  fimDebounceMs: z.number().default(250),
+  fimDebounceMs: () => z.number().default(250),
   /** 是否允许多行补全(true 默认)。false ⇒ 宿主只回第一行(空首行 = 这次不补)。
    *  关掉它是最省心的安全阀:实测模型在"不该补的位置"会硬凑,多行会把这种噪声放大。 */
-  fimMultiline: z.boolean().default(true),
+  fimMultiline: () => z.boolean().default(true),
   /** 按 glob 禁用补全的文件(分号 / 逗号 / 空白 / 换行分隔;空 = 不禁用)。
    *  语义:`*` 不跨目录、`**` 跨目录、不含 `/` 的模式只匹配文件名、`/` 结尾视作 `/**`。
    *  两侧都会判:扩展侧先判(不发请求),宿主侧再判(防线在服务端)。 */
-  fimDisableGlobs: z.string().default(''),
-});
+  fimDisableGlobs: () => z.string().default(''),
+};
+
+/** volatile 包装(**能力探测**,不看版本号):rc 线的 schemastery 3.18.2 没有这个方法。 */
+const vol = (schema) => (typeof schema.volatile === 'function' ? schema.volatile() : schema);
+
+/** 用同一份字段表建一条 schema;`wrap` 决定字段是否 volatile。 */
+function settingShape(wrap) {
+  const shape = {};
+  for (const [key, make] of Object.entries(SETTING_FIELDS)) shape[key] = wrap(make());
+  return shape;
+}
+
+/** **本插件条目的 Config**(新线:alpha ≥ 0.1.7-alpha.1 的配置模型)。
+ *  字段全部 volatile:这是"宿主把该条目暴露成可编辑表单 + 保存就地重解析"的前提。 */
+export const Config = z.object(settingShape(vol));
+
+/** **旧线注册用 schema**(rc 0.1.5-rc.x 与 0.1.6-alpha.2 的 `settings.register`):
+ *  同字段、**不带 volatile** —— 原因见 SETTING_FIELDS 上方那段(schemastery 的 volatile 是解析期行为,
+ *  旧的 settings 域会把活引用交给线路,卡片会读到空对象)。 */
+export const SettingsSchema = z.object(settingShape((schema) => schema));
 
 const DEFAULT_CONFIG = {
   bin: '',
@@ -663,8 +705,49 @@ let activeBridgeDispatch = null;
 export async function apply(ctx, config) {
   const cfg = { ...DEFAULT_CONFIG, ...(config ?? {}) };
 
-  // ---- 设置:行配置为种子;settings 命名空间持久化(设置卡片写入) ----
+  // ---- 设置:两条数据线(见文件头与 SETTING_FIELDS 的说明) ----
+  // 判据是**能力**不是版本号:旧线的 settings 服务有 register(rc 0.1.5-rc.x,以及数据面还没换的
+  // 0.1.6-alpha.2);新线(alpha ≥ 0.1.7-alpha.1)删掉了它,配置就是本条目自己的 volatile Config。
   const settingsSvc = ctx.get('settings');
+  const legacySettings = settingsSvc !== undefined && settingsSvc !== null
+    && typeof settingsSvc.register === 'function';
+
+  /**
+   * 读一个配置字段的**当前值**。
+   *
+   * 新线:宿主编译期把 volatile 叶子换成**活引用**(`{ get() }`,见 cosmokit 的 createVolatile),
+   * 保存(表单 mutate → profile patch → loader 重解析)只就地更新这个叶子、**不重挂插件**,
+   * 所以每次都现读引用才是"实时值"。旧线(以及 rc 线 3.18.2 的 schemastery,它没有 volatile)
+   * 上 config.<field> 就是普通值 —— 同一个读法两条线都对。
+   */
+  const cfgValue = (field) => {
+    const leaf = config === null || config === undefined ? undefined : config[field];
+    if (leaf !== null && typeof leaf === 'object' && typeof leaf.get === 'function') return leaf.get();
+    return leaf;
+  };
+  /** 有效值 = volatile 活叶子 / 行配置 config > 代码内默认(DEFAULT_CONFIG)。 */
+  const readCfg = (field) => {
+    const live = cfgValue(field);
+    return live === undefined ? cfg[field] : live;
+  };
+  /**
+   * 从**当前配置**拼出与旧线 `scope.get()` 同形的一份快照,交给同一个 commit 函数。
+   * 默认值就地取 DEFAULT_CONFIG / normalize,与旧线 register 分支里的兜底逐项对齐。
+   */
+  const readSettingsSnapshot = () => ({
+    serve: readCfg('serve') === 'dsh' ? 'dsh' : 'loopback',
+    keepResident: typeof readCfg('keepResident') === 'boolean' ? readCfg('keepResident') : true,
+    claimExtensions: typeof readCfg('claimExtensions') === 'string'
+      ? normalizeClaimExtensions(readCfg('claimExtensions'))
+      : DEFAULT_CLAIM_EXTENSIONS,
+    fullscreenOnOpen: typeof readCfg('fullscreenOnOpen') === 'boolean' ? readCfg('fullscreenOnOpen') : true,
+    editorBridge: readCfg('editorBridge') !== false,
+    fim: readCfg('fim') === true,
+    fimDebounceMs: clampDebounce(readCfg('fimDebounceMs')),
+    fimMultiline: readCfg('fimMultiline') !== false,
+    fimDisableGlobs: typeof readCfg('fimDisableGlobs') === 'string' ? readCfg('fimDisableGlobs') : '',
+  });
+
   // connection 是 host↔client 通道(必需);提前取出,供 DSH 同源挂载的 fence 使用。
   const connection = ctx.get('connection');
   if (connection === undefined || connection.fetch === undefined) {
@@ -675,107 +758,146 @@ export async function apply(ctx, config) {
   let keepResident = true; // 客户端常驻预热(0.2.2)
   let claimExtensions = DEFAULT_CLAIM_EXTENSIONS; // 认领类型清单(0.2.11,取代 fileOpenScope)
   let fullscreenOnOpen = true; // 客户端"打开标签即全屏右侧栏"(0.2.9)
-  /** 编辑器桥开关(0.3.0):行配置 cfg.editorBridge 是种子,设置文档里可改并实时生效。 */
-  let bridgeSetting = cfg.editorBridge !== false;
-  /** FIM 补全开关(实验性,0.3.61):行配置 cfg.fim 是种子,设置文档里可改并实时生效。默认关。 */
-  let fimSetting = cfg.fim === true;
+  /** 编辑器桥开关(0.3.0):行配置 cfg.editorBridge 是种子,设置里可改并实时生效。 */
+  let bridgeSetting = readCfg('editorBridge') !== false;
+  /** FIM 补全开关(实验性,0.3.61):行配置 cfg.fim 是种子,设置里可改并实时生效。默认关。 */
+  let fimSetting = readCfg('fim') === true;
   /** FIM 的三个子项(0.3.62):停顿毫秒数 / 是否多行 / 按 glob 禁用(原始文本,消费时解析)。 */
-  let fimDebounceMs = clampDebounce(cfg.fimDebounceMs);
-  let fimMultiline = cfg.fimMultiline !== false;
-  let fimDisableGlobs = typeof cfg.fimDisableGlobs === 'string' ? cfg.fimDisableGlobs : '';
-  if (settingsSvc !== undefined && typeof settingsSvc.register === 'function') {
+  let fimDebounceMs = clampDebounce(readCfg('fimDebounceMs'));
+  let fimMultiline = readCfg('fimMultiline') !== false;
+  let fimDisableGlobs = typeof readCfg('fimDisableGlobs') === 'string' ? readCfg('fimDisableGlobs') : '';
+  /**
+   * 把一份设置快照落到本地状态上,并在**值真的变了**时执行随动副作用。
+   *
+   * 两条线的触发点不同,但落到这里是同一段代码:
+   *   · 旧线:`scope.watch(commitSettings)`(首次装配另走 initial=true,不触发副作用);
+   *   · 新线:`ctx.on('settings/document-updated', …)` → readSettingsSnapshot() → 这里。
+   * 副作用的清单(与 0.3.0 起的语义逐条一致):编辑器桥上下线、FIM 适配器注册/注销、
+   * FIM 三个子项即时生效、状态里的四元组(serve/keepResident/claimExtensions/fullscreenOnOpen)。
+   */
+  const commitSettings = (next, opts) => {
+    const initial = opts !== undefined && opts.initial === true;
+    if (next != null && (next.serve === 'dsh' || next.serve === 'loopback')) {
+      if (next.serve !== serveSetting) {
+        serveSetting = next.serve;
+        console.log(`[code-server] serve updated: ${serveSetting}(下次启动生效)`);
+      }
+    }
+    if (next != null && typeof next.editorBridge === 'boolean') {
+      if (next.editorBridge !== bridgeSetting) {
+        bridgeSetting = next.editorBridge;
+        console.log(`[code-server] editorBridge updated: ${bridgeSetting}`);
+        // 关掉 → 立刻下线(关监听口 + 删配置 + 注销工具);开启 → 起监听口,IDE 在跑就补一份配置。
+        // 首次装配(initial)不做这件事:桥的启动由末尾那个 ctx.effect 负责,重复做会白起一次监听口。
+        if (initial !== true) {
+          if (bridgeSetting === false) {
+            clearBridgeRuntime();
+            void stopBridgeListener();
+          } else {
+            void ensureBridgeListener().then(() => {
+              if (state.status === 'running' && state.pid !== null) {
+                bridgeToken ??= mintBridgeToken();
+                syncBridgeRuntime({ pid: state.pid, startedAt: state.startedAt });
+              }
+            });
+          }
+        }
+      }
+    }
+    // FIM(实验性):开 → 注册我们自己的 LLM 适配器路由(编辑器补全要靠它);
+    // 关 → 注销。翻转立刻生效,不需要重启宿主(扩展侧下一趟 /sync 就会看到 enabled 变了)。
+    if (next != null && typeof next.fim === 'boolean') {
+      if (next.fim !== fimSetting) {
+        fimSetting = next.fim;
+        console.log(`[code-server] fim updated: ${fimSetting}(实验性 FIM 补全)`);
+        if (initial !== true) void ensureFimAdapter();
+      }
+    }
+    // FIM 的三个子项(0.3.62):都**即时生效**,不需要重启宿主 —— 扩展每趟 /sync 都会拿到新值
+    // (停顿与 glob 是扩展侧行为,多行由宿主在返回前裁)。改动只打一行日志,便于事后对齐现场。
+    if (next != null && next.fimDebounceMs !== undefined) {
+      const clamped = clampDebounce(next.fimDebounceMs);
+      if (clamped !== fimDebounceMs) {
+        fimDebounceMs = clamped;
+        console.log(`[code-server] fimDebounceMs updated: ${fimDebounceMs}ms`);
+      }
+    }
+    if (next != null && typeof next.fimMultiline === 'boolean') {
+      if (next.fimMultiline !== fimMultiline) {
+        fimMultiline = next.fimMultiline;
+        console.log(`[code-server] fimMultiline updated: ${fimMultiline}`);
+      }
+    }
+    if (next != null && typeof next.fimDisableGlobs === 'string') {
+      if (next.fimDisableGlobs !== fimDisableGlobs) {
+        fimDisableGlobs = next.fimDisableGlobs;
+        console.log(`[code-server] fimDisableGlobs updated: ${compileGlobList(fimDisableGlobs).length} 条`);
+      }
+    }
+    if (next != null && typeof next.keepResident === 'boolean') {
+      if (next.keepResident !== keepResident) console.log(`[code-server] keepResident updated: ${next.keepResident}`);
+      keepResident = next.keepResident;
+    }
+    if (next != null && typeof next.claimExtensions === 'string') {
+      const normalized = normalizeClaimExtensions(next.claimExtensions);
+      if (normalized !== claimExtensions) {
+        claimExtensions = normalized;
+        console.log(`[code-server] claimExtensions updated: ${claimExtensions} (${describeClaimPolicy(claimExtensions)})`);
+      }
+    }
+    if (next != null && typeof next.fullscreenOnOpen === 'boolean') {
+      if (next.fullscreenOnOpen !== fullscreenOnOpen) {
+        fullscreenOnOpen = next.fullscreenOnOpen;
+        console.log(`[code-server] fullscreenOnOpen updated: ${fullscreenOnOpen}`);
+      }
+    }
+  };
+
+  if (legacySettings) {
+    // ---- 旧线:settings 命名空间(rc 0.1.5-rc.x;也含 0.1.6-alpha.2) ----
     try {
-      const scope = settingsSvc.register(SETTINGS_NS, Config);
+      // 注册**不带 volatile** 的 SettingsSchema:旧的 settings 域会把 volatile 活引用直接交给线路。
+      const scope = settingsSvc.register(SETTINGS_NS, SettingsSchema);
       const rawDoc = settingsSvc.get(SETTINGS_NS);
       if (rawDoc !== undefined && rawDoc !== null) {
-        const resolved = scope.get();
-        serveSetting = resolved && resolved.serve === 'dsh' ? 'dsh' : 'loopback';
-        keepResident = resolved && typeof resolved.keepResident === 'boolean' ? resolved.keepResident : true;
-        claimExtensions = resolved && typeof resolved.claimExtensions === 'string'
-          ? normalizeClaimExtensions(resolved.claimExtensions)
-          : DEFAULT_CLAIM_EXTENSIONS;
-        fullscreenOnOpen = resolved && typeof resolved.fullscreenOnOpen === 'boolean' ? resolved.fullscreenOnOpen : true;
-        bridgeSetting = resolved && typeof resolved.editorBridge === 'boolean' ? resolved.editorBridge : bridgeSetting;
-        fimSetting = resolved && typeof resolved.fim === 'boolean' ? resolved.fim : fimSetting;
-        fimDebounceMs = clampDebounce(resolved && resolved.fimDebounceMs !== undefined ? resolved.fimDebounceMs : fimDebounceMs);
-        fimMultiline = resolved && typeof resolved.fimMultiline === 'boolean' ? resolved.fimMultiline : fimMultiline;
-        fimDisableGlobs = resolved && typeof resolved.fimDisableGlobs === 'string' ? resolved.fimDisableGlobs : fimDisableGlobs;
+        commitSettings(scope.get(), { initial: true });
       }
-      scope.watch((next) => {
-        if (next != null && (next.serve === 'dsh' || next.serve === 'loopback')) {
-          if (next.serve !== serveSetting) {
-            serveSetting = next.serve;
-            console.log(`[code-server] serve updated: ${serveSetting}(下次启动生效)`);
-          }
-        }
-        if (next != null && typeof next.editorBridge === 'boolean') {
-          if (next.editorBridge !== bridgeSetting) {
-            bridgeSetting = next.editorBridge;
-            console.log(`[code-server] editorBridge updated: ${bridgeSetting}`);
-            // 关掉 → 立刻下线(关监听口 + 删配置 + 注销工具);开启 → 起监听口,IDE 在跑就补一份配置。
-            if (bridgeSetting === false) {
-              clearBridgeRuntime();
-              void stopBridgeListener();
-            } else {
-              void ensureBridgeListener().then(() => {
-                if (state.status === 'running' && state.pid !== null) {
-                  bridgeToken ??= mintBridgeToken();
-                  syncBridgeRuntime({ pid: state.pid, startedAt: state.startedAt });
-                }
-              });
-            }
-          }
-        }
-        // FIM(实验性):开 → 注册我们自己的 LLM 适配器路由(编辑器补全要靠它);
-        // 关 → 注销。翻转立刻生效,不需要重启宿主(扩展侧下一趟 /sync 就会看到 enabled 变了)。
-        if (next != null && typeof next.fim === 'boolean') {
-          if (next.fim !== fimSetting) {
-            fimSetting = next.fim;
-            console.log(`[code-server] fim updated: ${fimSetting}(实验性 FIM 补全)`);
-            void ensureFimAdapter();
-          }
-        }
-        // FIM 的三个子项(0.3.62):都**即时生效**,不需要重启宿主 —— 扩展每趟 /sync 都会拿到新值
-        // (停顿与 glob 是扩展侧行为,多行由宿主在返回前裁)。改动只打一行日志,便于事后对齐现场。
-        if (next != null && next.fimDebounceMs !== undefined) {
-          const clamped = clampDebounce(next.fimDebounceMs);
-          if (clamped !== fimDebounceMs) {
-            fimDebounceMs = clamped;
-            console.log(`[code-server] fimDebounceMs updated: ${fimDebounceMs}ms`);
-          }
-        }
-        if (next != null && typeof next.fimMultiline === 'boolean') {
-          if (next.fimMultiline !== fimMultiline) {
-            fimMultiline = next.fimMultiline;
-            console.log(`[code-server] fimMultiline updated: ${fimMultiline}`);
-          }
-        }
-        if (next != null && typeof next.fimDisableGlobs === 'string') {
-          if (next.fimDisableGlobs !== fimDisableGlobs) {
-            fimDisableGlobs = next.fimDisableGlobs;
-            console.log(`[code-server] fimDisableGlobs updated: ${compileGlobList(fimDisableGlobs).length} 条`);
-          }
-        }
-        if (next != null && typeof next.keepResident === 'boolean') {
-          keepResident = next.keepResident;
-          console.log(`[code-server] keepResident updated: ${keepResident}`);
-        }
-        if (next != null && typeof next.claimExtensions === 'string') {
-          const normalized = normalizeClaimExtensions(next.claimExtensions);
-          if (normalized !== claimExtensions) {
-            claimExtensions = normalized;
-            console.log(`[code-server] claimExtensions updated: ${claimExtensions} (${describeClaimPolicy(claimExtensions)})`);
-          }
-        }
-        if (next != null && typeof next.fullscreenOnOpen === 'boolean') {
-          if (next.fullscreenOnOpen !== fullscreenOnOpen) {
-            fullscreenOnOpen = next.fullscreenOnOpen;
-            console.log(`[code-server] fullscreenOnOpen updated: ${fullscreenOnOpen}`);
+      scope.watch((next) => { commitSettings(next); });
+    } catch (error) {
+      console.error(`[code-server] settings unavailable; using defaults (claimExtensions=${DEFAULT_CLAIM_EXTENSIONS}, fullscreenOnOpen=true, keepResident=true): ${error.message}`);
+    }
+  } else {
+    // ---- 新线:本条目自己的 volatile Config(alpha ≥ 0.1.7-alpha.1) ----
+    // 先按活叶子装一遍初值(不触发副作用),再把后续变更挂到 settings 的文档事件上:
+    // volatile 叶子的就地重解析不重挂插件,所以随动必须由事件驱动。
+    commitSettings(readSettingsSnapshot(), { initial: true });
+    ctx.on('settings/document-updated', () => { commitSettings(readSettingsSnapshot()); });
+  }
+
+  // ---- 自带配置页的声明(0.3.66) ----
+  // 本插件的设置面是客户端半部自绘的表单(插件页的 `plugins.bundle.config`),不是按 schema 自动生成的页面。
+  // 上游要求:这类插件在 apply 中于**可选的** `ctx.inject(['settings'], …)` 子级内以 effect 注册
+  // `configure({ auto: false }, ctx.fiber)` —— 子级指明策略所属的插件 fiber(迟加载/被替换的 Settings
+  // 服务也会采用该策略),而"业务插件无需 Settings 即可运行"这条性质靠可选的 inject 保住。
+  // 策略只影响"要不要自动生成页面",不移除配置读写(表单/描述/mutate 仍照常)。
+  if (typeof ctx.inject === 'function') {
+    try {
+      ctx.inject(['settings'], (child) => {
+        const svc = typeof child.get === 'function' ? child.get('settings') : child.settings;
+        if (svc === undefined || svc === null || typeof svc.configure !== 'function') return; // 旧线没有这个能力
+        child.effect(() => {
+          try {
+            return svc.configure({ auto: false }, ctx.fiber);
+          } catch (error) {
+            // 同一个 fiber 注册两次会抛(Settings presentation is already configured for this plugin
+            // instance)。热重载下 apply 可能重跑,而"没有自动页面"只是外观问题 ⇒ 记一条日志就够。
+            console.warn(`[code-server] settings presentation 未注册(不影响配置读写):${error && error.message ? error.message : error}`);
+            return () => {};
           }
-        }
+        }, 'code-server: settings presentation (auto: false)');
       });
     } catch (error) {
-      console.error(`[code-server] settings unavailable; using defaults (claimExtensions=${DEFAULT_CLAIM_EXTENSIONS}, fullscreenOnOpen=true, keepResident=true): ${error.message}`);
+      console.warn(`[code-server] settings presentation 未注册(不影响配置读写):${error && error.message ? error.message : error}`);
     }
   }
 
@@ -789,7 +911,7 @@ export async function apply(ctx, config) {
 
   /** 生效的服务方式:loopback(默认,独立回环端口)| dsh(DSH 同源挂载)。 */
   function requestedServe() {
-    const want = serveSetting === 'dsh' || cfg.serve === 'dsh' ? 'dsh' : 'loopback';
+    const want = serveSetting === 'dsh' || readCfg('serve') === 'dsh' ? 'dsh' : 'loopback';
     if (want === 'loopback') return 'loopback';
     if (webServerSvc === undefined || dshMount === null) {
       console.warn('[code-server] serve=dsh 但 webServer 不可用/挂载失败 → 回退 loopback');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-code-server-app",
-  "version": "0.3.65",
+  "version": "0.3.66",
   "description": "VS Code (from a code-server release) inside DSH: a right-sidebar tab driven by the plugin's own launcher over the in-process VS Code server (lib/launcher.mjs), plus an editor bridge (assets/extensions/dshcs-editor-bridge) that gives the agent what only the editor knows (unsaved buffers, language-server diagnostics, the active selection) and lets editor gestures drive the session. The bridge is completely read-only: all four of its routes (/health, /sync, /old, /event) are reads. Asking DSH from the editor opens a floating dialog inside the DSH page (draggable, resizable, bottom-right): the plugin's client half sends the question as user input (POST /api/code-server/ask/send) and renders that session's new content with DSH's own Markdown renderer - the same @deepseek-ai/dsh-client-ui-primitives instance the UI uses, required from the page's module table, so typography, highlighting and math match the interface and a renderer version mismatch is impossible. Thinking appears as collapsed rows and approval requests (writing outside the workspace / running commands) can be answered in place: whole-plugin write route POST /api/code-server/ask/approve, constrained to pending in-process requests and the outcomes allowed-once/rejected; dialog-first for 5 minutes, handed back to the official card the moment the dialog closes, never auto-approved. There is no build step anywhere: lib/client.js (client half including the dialog panel) and the extension are committed hand-written source, devDependencies holds a single test-only entry, and the published package carries no frontend bundle. Also: the tab claims DSH file addresses (dsh-resource://file/**) by file type (setting claimExtensions), so produced-file chips, delivered-file previews and inline prose mentions open in the workbench; the IDE is a resident surface moved with Element.moveBefore instead of being remounted, so switching sidebar tabs does not reload it; opening the tab switches the right sidebar to fullscreen by default (setting fullscreenOnOpen); a workspace switch re-navigates the workbench with the new ?folder= without restarting the IDE process. Requires a DSH with the right-sidebar services (sidebarRightTabs/sidebarRight, >= 0.1.5-alpha.1); older DSH versions only get an upgrade notice on the settings page. Two serving modes: loopback port (default) or same-origin mount on DSH's own webServer (/code-server, protected by ctx.connection.requestRejection). The diff the bridge opens always has the real pre-write text on the left, taken from result.value.before in tools/post-execute into a bounded snapshot cache and fetched by opaque key over the read-only GET /old, so files that are not open in the editor work too. No code-server Node layer, no argon2, no C++ toolchain.",
   "homepage": "https://github.com/jinsiyu/dsh-code-server-app",
   "repository": {

package/vendor/VENDOR.json

@@ -3,7 +3,7 @@
   "vscodeVersion": "1.138.0",
   "productPath": "stable-59c988c744a240b05b039f57b856a5312f19d5b1",
   "layout": "vscode-only",
-  "preparedAt": "2026-09-22T09:29:00.445Z",
+  "preparedAt": "2026-09-22T13:10:27.713Z",
   "source": "registry",
   "node": "v24.20.0",
   "platform": "linux",