@gatherthread/dsh-host 0.1.0-alpha.4 → 0.1.0-alpha.6

package/README.md

@@ -19,7 +19,7 @@ The package does not install a DSH runtime dependency.
 After `@gatherthread/dsh-host` is published, the ordinary three-step path is:
 
 ```text
-npx @deepseek-ai/dsh@0.1.2-rc.1 plugin --profile web add @gatherthread/dsh-host@0.1.0-alpha.4
+npx @deepseek-ai/dsh@0.1.2-rc.1 plugin --profile web add @gatherthread/dsh-host@0.1.0-alpha.6
 npx @deepseek-ai/dsh@0.1.2-rc.1 web
 # In DSH: Settings -> GatherThread / 共序 -> Sign in and pair
 ```
@@ -98,13 +98,20 @@ bounded exponential delay.
 
 Every eligible Session has its own DSH Session id, HTTP abort scope, connector
 state file, runtime identity, heartbeat, canonical cursor and durable outbox.
-The project gate bounds the whole claim-to-settlement operation. This is
-required because the current GatherThread alpha has no claim-abandon or claim
-lease-expiry API. Removing or downgrading a Session cancels its queued permit
-before it can claim a request. Existing single-Session configuration remains
+The project gate bounds the whole claim-to-settlement operation. Claims are
+leased and renewed by accepted progress, so a Session that stops producing work
+releases its request for the exact recorded runtime to reclaim; the gate still bounds this
+connector's own concurrency while it holds one. Removing or downgrading a Session
+cancels its queued permit before it can claim a request. Existing single-Session configuration remains
 valid when `bindingMode` is omitted; both modes resolve the real current actor
 before applying Solo permissions.
 
+During an active prompt, newly durable DSH Host events queue a rate-limited,
+generic progress marker; event bursts coalesce. The marker carries no event text,
+reasoning, headers, or private stream data, but renews the exact claim attempt. Progress, completion,
+and request-linked tool outbox entries are rebound to the renewed attempt after a
+crash recovery, while stale attempts remain fenced by the server.
+
 The installed native plugin stores one account-level model route and reconciles
 every active Project visible to the paired GatherThread identity. Adding a
 Project starts its isolated manager without another pairing step. Archiving a
@@ -112,6 +119,14 @@ Project or revoking access stops only that Project manager; its local workspace
 and DSH Session history are retained. A failure in one Project does not stop
 healthy peers, and discovery retries periodically.
 
+For a `deepseek-official` route, the plugin also advertises the exact models and
+reasoning efforts returned by DSH's public LLM catalog. The GatherThread work
+page may select one advertised combination for an individual Agent request.
+That selection is installed only on the borrowed Agent while the request runs
+and is removed in `finally`; it does not rewrite DSH Web's saved model choice.
+Unsupported combinations fail closed. Older plugins and non-DeepSeek routes
+retain the account route's fixed provider and model.
+
 An existing schema-v1 single-Project pairing keeps its device credential when
 the plugin is upgraded, but deliberately drops the old model binding. The user
 must choose the DSH model and explicitly select **Connect all accessible

package/bundle/manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "name": "@gatherthread/dsh-host",
-  "version": "0.1.0-alpha.4",
+  "version": "0.1.0-alpha.6",
   "license": "Apache-2.0",
   "defaultEnabled": false,
   "hostEntry": "@gatherthread/dsh-host",

package/client/client.js

@@ -302,6 +302,13 @@ function renderNativeControls(input) {
     const models = selectedProvider?.models ?? [];
     controls.push(
       connectionSummary(state),
+      // Reaching this branch means authorization is already "paired": the
+      // "unpaired" and "pairing" states are handled by earlier branches. The
+      // browser approval succeeded, but without a provider and model no runtime
+      // is registered, so a bare stopped connection is indistinguishable from a
+      // fresh install. State the remaining step explicitly.
+      React.createElement("p", { key: "select-model-notice", style: styles.notice },
+        "配对完成后，尚未选择 DSH Provider 与 Model。完成选择并点击下方按钮后，本机 DSH 运行时才会注册到 GatherThread；在此之前，GatherThread 网页无法发现这台 DSH。"),
       input.catalog === undefined
         ? React.createElement("button", {
           key: "load-catalog",

package/cordis.patch.yml

@@ -12,3 +12,21 @@
       inject: [agents, sessions, sessionPersistence, sessionQuery, sessionTitle, workspaceRegistry, llm, credentials, connection]
       config:
         enabled: true
+
+# DSH 0.1.5-rc.x dropped `webServer` from the Connection plugin's own inject list
+# (`["webServer", "credentials"]` became `["credentials"]`), moving it into a
+# nested scope that covers only DSH's new index-injection feature. Connection
+# still reads `owner.webServer` from its *providing* context -- cordis starts
+# every service lookup at the shadow origin, `(ctx[symbols.shadow] ?? ctx).fiber`
+# -- so `connection.rpc.handle()` raises "cannot get property \"webServer\"
+# without inject" for every caller, and the whole plugin tree fails to load.
+# 0.1.2-rc.1 kept the dependency at the top level, so restoring it here is what
+# makes the Host plugin load on both versions.
+#
+# A row patch replaces `inject` wholesale rather than merging, so each entry the
+# 0.1.5 row already declares is repeated: `webRuntime` still feeds this row's
+# `trustedHosts: !!js ctx.webRuntime.trustedHosts` expression, and `credentials`
+# is repeated so the row stays self-sufficient no matter how the Loader folds a
+# row's list together with the module's own `inject` export.
+- id: connection
+  inject: [webRuntime, credentials, webServer]