dsh-mcp-pill 0.2.8 → 0.2.10

package/README.md

@@ -27,7 +27,15 @@ Global MCP connection status pill for the DSH web UI — official bundle form
   (key `mcp-pill`) on ≤ 0.1.5. Each seat is declared by one host only, so the two
   registrations coexist with no version sniffing and the card always has a home;
   values keep flowing through the single settings transport
-  (`settingsScope` on ≤ 0.1.5, `configForms` on ≥ 0.1.7).
+  (`settingsScope` on ≤ 0.1.5, `configForms` on ≥ 0.1.7). The same card is also
+  registered on the root-scope `settings.section` list seat — identity
+  `YOTK · MCP Pill`, id `yotk-mcp-pill`, order `60` — so on a host that declares
+  that seat it is a first-class page one click deep in 设置, additive beside the
+  row seat and never a gate.
+- `@deepseek-ai/schemastery` is a private `dependencies` entry whose floor must be
+  ≥ 3.18.4 (`^3.18.4`): the profile hoists an older line (3.18.2) that satisfies a
+  lower floor, and an entry whose Config exposes no volatile field is dropped from
+  `SettingsForms.describe()` — the card then renders nothing with no error.
 - The pill snaps to one of the chat input's four corners (drag to switch);
   the anchor is remembered in `localStorage` (`dsh.mcpPill.anchor`).
 - The pill mounts inside the composer seat (same stacking level as the input

package/lib/client.js

@@ -1001,6 +1001,43 @@ window.__ModuleLoader__.load({
       }
       ctx.inject(['slots'], registerRowConfig)
 
+      // ── additive seat: the `settings.section` page ─────────────────────────
+      //
+      // 0.1.7-rc.2 also declares the root-scope LIST slot `settings.section`
+      // ("one settings page per list entry"), which puts this same card one
+      // click deep inside 设置 as a first-class page of its own. It is purely
+      // ADDITIVE: the row seat above stays the bundle row's configuration, and
+      // both render the SAME `SettingsCard` through the SAME single transport —
+      // no second settings UI and no second read/write path.
+      //
+      // The seat declares exactly three registrant options — `id` (required),
+      // `order`, `label` — so only those travel here. `label` is a THUNK, like
+      // every label the catalog projects: the shell re-reads it on each
+      // projection instead of caching registrant-localized text.
+      //
+      // Same non-gating shape as the row seat: `slots` is awaited with
+      // `ctx.inject(['slots'], cb)`, the callback RETURNS the registration
+      // disposer, and that disposer is pushed onto disposeSlots so the entry is
+      // owned by the registering fiber and released with the rest on stop /
+      // update / HMR. The seat is host-version dependent — a host that does not
+      // declare it simply never fires the inner `slots.inject`, so this
+      // registration can never gate the plugin.
+      const registerSettingsSection = (sctx) => {
+        disposeSlots.push(sctx.slots.inject('settings.section', () => sctx.slots.register({
+          name: 'settings.section',
+          id: 'yotk-mcp-pill',
+          order: 60,
+          label: () => 'YOTK · MCP Pill',
+        }, function McpPillSettingsSection() {
+          // The section owner shares `close` and nothing else; this card needs
+          // neither `close` nor the host-owned optional `form` prop, because
+          // values keep flowing through the one resolved transport — so the
+          // page branch is literally the row seat's `view === 'page'` render.
+          return e(SettingsCard, { scope, api })
+        })))
+      }
+      ctx.inject(['slots'], registerSettingsSection)
+
       // Pill: fully lifecycle-owned as before, but created hidden — the gate
       // inside startPill reveals it only while /status reports pill.enabled
       // === true (default off). The getter is re-read on every refresh, so the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-mcp-pill",
-  "version": "0.2.8",
+  "version": "0.2.10",
   "description": "EN: Lifecycle-safe MCP status pill and Settings card for DeepSeek Harness Web. ZH: 面向 DeepSeek Harness Web 的生命周期安全 MCP 状态胶囊与设置卡片。",
   "type": "module",
   "main": "lib/index.js",
@@ -20,7 +20,7 @@
     "test": "node --test"
   },
   "dependencies": {
-    "@deepseek-ai/schemastery": "^3.18.1"
+    "@deepseek-ai/schemastery": "^3.18.4"
   },
   "dsh": {
     "bundle": {