dsh-model-params 0.1.4 → 0.1.6

package/README.md

@@ -2,7 +2,7 @@
 
 ## English
 
-**Current release: 0.1.4** — models.dev parameter assistant inside the official DeepSeek Harness Models settings page.
+**Current release: 0.1.6** — Portable settings transport: the plugin now resolves the official pi-ai settings scope on both the `settingsScope` (≤ 0.1.5) and `configForms` (≥ 0.1.7-rc.1) hosts, so the provider card keeps working across the rename.
 
 For every configured `llm-pi-ai` provider card (custom OpenAI-compatible gateways such as the ones you add under Settings → Models), a `models.dev 参数` control fetches the official models.dev records for the provider's configured model ids and proposes the metadata pi-ai needs: context window, max output tokens, and reasoning-effort levels. One click writes the merged `models` array back to that provider profile through the official revision-aware Settings API.
 
@@ -25,6 +25,22 @@ models.dev model ids may collide across catalog providers; the matcher prefers t
 - Host 只负责拉取并缓存 models.dev 目录（6 小时，支持公共代理或 `HTTPS_PROXY` 回退），不接触任何 LLM 配置与凭据。
 - models.dev 未收录的模型 id 会明确标记，不写入。
 
+## Install
+
+```powershell
+dsh plugin --profile web add dsh-model-params
+```
+
+Restart the existing DSH Web process afterwards: the Host scans the browser plugin roster at startup, so the provider-card control appears only after that restart. Then open **Settings → Models** and look for `models.dev 参数` on a configured provider card.
+
+Local development, from this package directory:
+
+```powershell
+dsh plugin --profile web add .
+```
+
+Either form records the package in the profile's `dsh.profile.bundles`, which is what mounts the Host lookup route and serves the client bundle.
+
 ## Development
 
 From this directory run:

package/lib/client.js

@@ -22,6 +22,30 @@ window.__ModuleLoader__.load({
 
     const PI_NS = 'llm-pi-ai'
     const API = '/api/model-params/lookup'
+
+    // ── settings-scope portability (DSH 0.1.5 ↔ 0.1.7-rc.1) ──────────────────
+    //
+    // This plugin owns no settings namespace: it extends the OFFICIAL pi-ai
+    // Models page and writes that provider's own `llm-pi-ai` section. The two
+    // supported hosts expose the same scope CONTRACT under different names:
+    //
+    //   ≤ 0.1.5  settingsScope.bind({ namespace })  → SettingsScope<T>
+    //   ≥ 0.1.7  configForms.get(entryId)           → ConfigForm<T>
+    //
+    // Both return getSnapshot()/subscribe()/set()/unset()/mutate() over the same
+    // { status, value, base, user, revision, writable, mode } snapshot, so the
+    // resolved object is used unchanged by the provider card. On 0.1.7-rc.1 a
+    // form's namespace IS the profile entry id, and the pi-ai LLM entry is
+    // mounted as `llm-pi-ai`, so the same key resolves on either host.
+    // `ctx.get` (never a direct property read) keeps the lookup safe when only
+    // one service is mounted: an uninjected property read throws.
+    function resolveSettingsScopeFrom(ctx, namespace) {
+      const binder = ctx.get('settingsScope')
+      if (binder && typeof binder.bind === 'function') return binder.bind({ namespace })
+      const forms = ctx.get('configForms')
+      if (forms && typeof forms.get === 'function') return forms.get(namespace)
+      return undefined
+    }
     const FETCH_TIMEOUT_MS = 20000
     const CSS_ID = 'dsh-model-params/style'
     const LEVELS = ['off', 'minimal', 'low', 'medium', 'high', 'xhigh', 'max']
@@ -274,15 +298,42 @@ window.__ModuleLoader__.load({
       const api = remote && remote.settings
         ? { settings: { mutate: (payload) => remote.settings.mutate(payload.ns, payload.ops, payload.expectedRevision).then((result) => ({ result })) } }
         : undefined
-      const scope = ctx.settingsScope.bind({ namespace: PI_NS })
-      return ctx.slots.inject('settings.models.provider-card', () => ctx.slots.register(
-        { name: 'settings.models.provider-card', key: PI_NS },
-        (props) => e(ModelParamsExtension, { ...props, api, scope }),
-      ))
+      // Version-portable scope on the official pi-ai namespace. Both transport
+      // names are awaited WITHOUT gating activation, and whichever this host
+      // mounts resolves; see resolveSettingsScopeFrom.
+      let scope
+      let cardRegistered = false
+      // The provider card MUST register from inside a context that has the
+      // settings transport, i.e. from the `ctx.inject([...], cb)` callback and on
+      // the CHILD context it hands us. Registering
+      // `settings.models.provider-card` from the bare apply context puts the
+      // entry where the Models page's ledger never sees it, so the extension
+      // never renders even though `register` returned normally. (dshmarket, an
+      // out-of-repo bundle that does render its card, uses this nested shape.)
+      const registerCard = (sctx) => {
+        if (cardRegistered) return
+        const resolved = resolveSettingsScopeFrom(sctx, PI_NS)
+        if (resolved === undefined) return
+        scope = resolved
+        cardRegistered = true
+        sctx.slots.inject('settings.models.provider-card', () => sctx.slots.register(
+          { name: 'settings.models.provider-card', key: PI_NS },
+          (props) => e(ModelParamsExtension, { ...props, api, scope }),
+        ))
+      }
+      // The first wait fires only when settingsScope exists; the second covers a
+      // host that renamed the transport, and its guard keeps the card from
+      // registering twice when both names exist.
+      ctx.inject(['settingsScope'], registerCard)
+      ctx.inject(['configForms'], (sctx) => { if (!cardRegistered) registerCard(sctx) })
     }
 
     exports.name = 'dsh-model-params'
-    exports.inject = ['slots', 'settingsScope', 'remote', 'remote.settings']
+    // 'settingsScope' and 'configForms' are alternatives, not both-required:
+    // cordis resolves each inject name as its own gate, so activation succeeds on
+    // whichever settings transport the host mounts (0.1.5 vs 0.1.7-rc.1). The
+    // dotted remote names stay declared — dropping them fails the loader fiber.
+    exports.inject = ['slots', 'remote', 'remote.settings']
     exports.apply = apply
     return module.exports
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-model-params",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "EN: models.dev parameter assistant for the official DeepSeek Harness Models page: per-provider one-click context / max-output / reasoning-effort fill. ZH: 官方模型设置页的 models.dev 参数助手：按 provider 一键补全上下文、max 输出与推理档位。",
   "type": "module",
   "main": "lib/index.js",