@gatherthread/dsh-host 0.1.0-alpha.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Yuhan He and contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,161 @@
+# GatherThread DeepSeek Harness Host bundle
+
+This publish-ready, opt-in package binds the writable Sessions of one
+GatherThread Project to distinct DeepSeek Harness Sessions. Installing the
+package adds its identity-marked DSH profile layer; without that explicit
+installation, GatherThread does not load in DSH or alter the GatherThread
+server, Web app, Codex bridge, or Claude adapter.
+
+The normal path is the published `@deepseek-ai/dsh` CLI, not a DSH source
+checkout. The verified distribution is `@deepseek-ai/dsh@0.1.2-rc.1` with the
+`web` profile and its public `sessionPersistence.list` recovery surface. The
+earlier source-only PoC remains fixed to `dsh-v0.1.3-alpha.1`, commit
+`d347e703908d0406b7a7ef80e3a0e594d86b2215`, and is only an advanced diagnostic
+fallback. All version-sensitive Host calls remain inside `src/dsh-compat.ts`.
+The package does not install a DSH runtime dependency.
+
+## Plugin-first connection
+
+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.1
+npx @deepseek-ai/dsh@0.1.2-rc.1 web
+# In DSH: Settings -> GatherThread / 共序 -> Sign in and pair
+```
+
+Check the active CLI with `npx @deepseek-ai/dsh --version`. The normal start
+command already pins `0.1.2-rc.1`. DSH 0.1.2 does not
+expose the root CLI version as a stable Host service, so the package does not
+inspect npx cache paths or claim runtime-version introspection. The install
+command pins the exact verified CLI, while every required Host/Client service is
+validated structurally and fails closed before a request can be claimed.
+
+`dsh plugin --profile web add` is DSH 0.1.2's official package installation
+mechanism. It initializes a missing `web` profile on first use, invokes pnpm,
+and appends only packages declaring `dsh.bundle`. DSH 0.1.2 has no verified
+public plugin marketplace, marketplace index, or registration workflow. This
+repository change prepares the package but does not publish it or modify a real
+DSH profile.
+
+Inside DSH, choose the future GatherThread public service or enter one custom
+server origin. The same field covers an HTTPS LAN host, self-hosted deployment,
+or Tailscale address; plain HTTP is accepted only on loopback. The plugin opens
+an outbound HTTPS connection. A five-minute, single-use short code is confirmed
+through the existing GatherThread browser session or invitation identity.
+Public account registration is not assumed. The resulting long-lived device
+grant is stored only by DSH's credential service and never appears in argv, a
+URL, browser storage, logs, status RPC, or shared history. Once paired, the
+plugin reconnects automatically whenever DSH starts.
+
+Before removal, use **Disconnect** inside the DSH panel to clear the local
+grant, then run:
+
+```text
+npx @deepseek-ai/dsh@0.1.2-rc.1 plugin --profile web remove @gatherthread/dsh-host
+```
+
+The official command removes only this package dependency and profile layer;
+other plugins remain untouched. The repository-level `npm run dsh:connect --
+--help` source-checkout connector and the examples under `bundle/` remain
+advanced/offline diagnostics, not the normal user path.
+
+## Security and recovery
+
+Only allowlisted public text/tool fields leave DSH. Reasoning blocks, raw model
+streams, request headers, replay state, tool-private metadata, and credentials
+are structurally unreachable from the upload mapper. Tool values are redacted
+and bounded. The connector holds one active request, persists a private atomic
+cursor/outbox, reuses DSH's official Session resume/repair path, and releases its
+listeners, timer, HTTP abort signal, Agent handle, and write ownership on unload.
+
+The `web` profile discovers `client/client.js` through DSH's official
+`dsh.client` declaration. The settings Slot uses DSH's authenticated native RPC
+carrier for pairing, configuration, and bounded status. The legacy status route
+is read-only and available only when native RPC is absent. Both paths stay
+behind DSH's same-origin Cookie/Host/Origin checks, and neither sends an
+authorization header to the browser. A permanent 4xx clears displayed project
+and Session details and stops polling; transient failures receive only three
+bounded retries.
+
+Host and browser lifecycles are intentionally separate. Disabling the Host
+Loader entry immediately unregisters the status and RPC routes. Client bundle HMR uses
+the official client-module SSE/fiber refresh path, which drains the previous
+Slot and timer before registering one replacement. At this pinned DSH version,
+adding or removing a package from the client graph is observed by a newly loaded
+page; it is not treated as Host-entry disposal.
+
+## Project binding
+
+`bindingMode: project` discovers Sessions only through the existing
+`GET /v1/projects/:project_id/sessions` and authenticates identity through
+`GET /v1/me`. Viewer Sessions are never writable. A Solo Session is writable
+only by its `owner_user_id`; Multi Sessions use the authoritative owner or
+participant role. A 403 or 404 Project response stops every Session binding for
+that Project, while a
+transient discovery failure preserves the last safe set and retries with a
+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
+valid when `bindingMode` is omitted; both modes resolve the real current actor
+before applying Solo permissions.
+
+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
+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.
+
+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
+Projects** once; the migration never broadens the former Project scope in the
+background. Likewise, an obsolete Client that still submits `projectId` is
+rejected instead of silently treating that choice as account-wide consent.
+
+Each Project uses the same marker-validated `~/GatherThread Projects/<name>`
+workspace as the Codex connection path. The plugin registers that directory
+through DSH's public `workspaceRegistry` service, including for viewer-only
+Projects, but creates and attaches native Agent Sessions only for Sessions the
+paired actor may edit. Existing GatherThread Session titles are applied through
+the public `sessionTitle` service, flushed, and then attached to the Project
+workspace so they appear in DSH's native work page. No private DSH persistence
+file is read or modified. GatherThread-origin conversations use DSH's ordinary
+editable `standard` preset; an obsolete read-only projection is detached from
+the workspace after its editable replacement is durable, without deleting the
+old local log.
+
+For an owner or participant, the first successfully completed human/assistant
+turn in a new DSH conversation creates one creator-owned cloud Solo with the
+same stable Session identity, then uploads that turn atomically. The live Agent
+remains owned by DSH while GatherThread borrows its public handle, so neither
+side disposes the other's conversation. Empty conversations, failed turns, and
+all viewer conversations remain local-only. Creation and turn upload are both
+idempotent across refreshes and reconnects.
+
+## Native bidirectional history
+
+Canonical history is replayed in server sequence order through DSH's public
+`Session.append(..., { surfaceOp: "append" })` API and acknowledged only after
+the public Session flush completes. Human requests use ordinary identified user
+messages. External Agent answers use identified `gatherthread` plugin relay
+messages with visible attribution; this keeps them model-visible without
+forging an `assistant/message` whose provider stream could not pass DSH's
+restore invariants. Stable `gatherthread:<event-id>` message IDs make a retry
+after an uncertain cursor save harmless.
+
+A complete turn typed directly in the bound DSH Session is flushed, reduced to
+public request/final-answer text, and stored in the private connector outbox
+before one atomic `commitLocalTurn`. Reasoning, raw streams, replay state and
+private tool metadata never enter that commit. Transport failures retain the
+same local-turn ID for idempotent replay. Canonical events attributed to the
+same runtime advance the projection cursor but are not appended back to DSH,
+while events written through another harness are imported normally. V1
+connector state deliberately restarts only the native projection cursor at zero
+once so history that the earlier poller observed but discarded is backfilled.

package/bundle/manifest.json

@@ -0,0 +1,32 @@
+{
+  "schemaVersion": 1,
+  "name": "@gatherthread/dsh-host",
+  "version": "0.1.0-alpha.1",
+  "license": "Apache-2.0",
+  "defaultEnabled": false,
+  "hostEntry": "@gatherthread/dsh-host",
+  "clientEntry": "@gatherthread/dsh-host/client",
+  "profileExamples": {
+    "disabled": "disabled.cordis.patch.yml",
+    "singleSession": "enabled.example.cordis.patch.yml",
+    "project": "project.example.cordis.patch.yml"
+  },
+  "deepseekHarness": {
+    "primary": {
+      "distribution": "npm",
+      "package": "@deepseek-ai/dsh",
+      "version": "0.1.2-rc.1",
+      "profile": "web",
+      "persistenceProbe": "list"
+    },
+    "sourceFallback": {
+      "distribution": "source",
+      "tag": "dsh-v0.1.3-alpha.1",
+      "version": "0.1.3-alpha.1",
+      "commit": "d347e703908d0406b7a7ef80e3a0e594d86b2215",
+      "verifiedProfiles": ["headless", "web"],
+      "persistenceProbe": "stat"
+    }
+  },
+  "runtimeDependencies": []
+}