dsh-bailinghub 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,7 @@
+# Changelog
+
+## 0.1.0 - 2026-08-18
+
+- Add an installable DeepSeek Harness bundle for BailingHub.
+- Expose the existing submit, get, and bounded-wait MCP tools under the `bailinghub` namespace.
+- Pin `bailinghub-mcp-server@0.1.1` and keep route and credentials outside model arguments.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 BailingHub Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/PRIVACY.md

@@ -0,0 +1,11 @@
+# Privacy
+
+This bundle adds no telemetry and stores no BailingHub credentials or task payloads.
+
+Task text submitted through the installed tools is sent to the BailingHub deployment chosen
+by the operator. DeepSeek Harness, the configured model provider, BailingHub, and the target
+business system each have their own data-retention boundary. Review those deployments before
+using personal, confidential, or regulated data.
+
+Do not include tokens, private URLs, personal information, or production payloads in public
+issues, screenshots, or compatibility reports.

package/README.md

@@ -0,0 +1,105 @@
+# BailingHub for DeepSeek Harness
+
+[简体中文](README.zh-CN.md) | English
+
+Run governed tasks from DeepSeek Harness against a business route already connected to
+BailingHub, then track the same job and read its available result. You can do this from the
+Harness Web UI on your own computer without opening the embedded chat page in each business
+backend.
+
+This is an independent community integration. It is not developed, certified, endorsed, or
+recommended by DeepSeek.
+
+## What You Get
+
+After installation, DeepSeek Harness discovers three native tools:
+
+| Harness tool | What it does |
+| --- | --- |
+| `mcp__bailinghub__submit_governed_job` | Submit task text with a stable request ID |
+| `mcp__bailinghub__get_governed_job` | Read the current state and public result of one job |
+| `mcp__bailinghub__wait_for_governed_job` | Wait briefly for the same job without resubmitting it |
+
+BailingHub remains the control plane between the model and the business system. The URL,
+Client Token, and route are operator configuration, not model arguments. The model cannot
+switch to another route or supply administrator, executor, approval, or business-system
+credentials through these tools.
+
+## Install
+
+Prerequisites:
+
+- Node.js `22.19.0+` or `24+`;
+- `pnpm` and `@deepseek-ai/dsh@0.1.0-rc.7`;
+- a reachable [BailingHub deployment](https://github.com/bailinghub/bailinghub#quick-start);
+- one BailingHub Client Token restricted to the route you want this Harness profile to use.
+
+```bash
+npm install --global pnpm @deepseek-ai/dsh@0.1.0-rc.7
+dsh plugin --profile web add dsh-bailinghub@0.1.0
+```
+
+Configure the process that starts Harness:
+
+```bash
+export BAILINGHUB_BASE_URL='https://hub.example.com'
+export BAILINGHUB_CLIENT_TOKEN='replace-with-a-route-scoped-client-token'
+export BAILINGHUB_ROUTE='order_assistant'
+```
+
+Then verify the composed profile and start the local Web UI:
+
+```bash
+dsh --profile web --dump-config
+dsh web
+```
+
+The default Web UI is local to your computer. Ask Harness to submit a task through
+BailingHub, preserve the returned `job_id`, and wait for or query that same job.
+
+For a first try, use a task supported by your configured route and say explicitly: submit it
+once with a stable `request_id`, preserve the returned `job_id`, and query that same job if a
+bounded wait times out.
+
+## Correct Task Flow
+
+1. Generate one stable `request_id` for one business request.
+2. Call `mcp__bailinghub__submit_governed_job` once.
+3. Preserve its `job_id`.
+4. Call `wait_for_governed_job`, or call `get_governed_job` later.
+5. A wait timeout is not a failed task. Do not submit a replacement request.
+
+## Identity and Permission Boundary
+
+Using the local Harness UI removes the need to open a business backend's embedded chat UI;
+it does **not** turn the Harness login or local user into a trusted business identity.
+Version `0.1.0` deliberately does not accept an acting subject as tool input. A route or
+downstream business system must still resolve trusted identity and perform final
+authorization. If the selected action requires identity that the configured path cannot
+establish, it should remain unavailable or be rejected.
+
+This bundle governs only tasks submitted through its three BailingHub tools. It does not
+intercept or govern every other tool installed in DeepSeek Harness.
+
+## Supply-Chain Note
+
+This bundle contains no custom runtime JavaScript, no production dependencies, and no
+install scripts. When Harness starts the bundle, its built-in MCP Client runs the pinned
+command `npx -y --package=bailinghub-mcp-server@0.1.1 bailinghub-mcp-server` outside the
+agent sandbox. The first start may
+need npm network access. Review and pin the package before using it in a sensitive
+environment; production images may pre-cache the exact version.
+
+Non-loopback HTTP is rejected by the MCP server by default. Only set
+`BAILINGHUB_ALLOW_INSECURE_HTTP=true` on a controlled private network where TLS terminates at
+another trusted boundary.
+
+## Compatibility and Feedback
+
+The first release is verified against DeepSeek Harness `0.1.0-rc.7`,
+`bailinghub-mcp-server@0.1.1`, and BailingHub Client API v1. Harness is still a developer
+preview, so each Harness release requires a compatibility smoke test.
+
+Report problems through [GitHub Issues](https://github.com/bailinghub/bailinghub-dsh-plugin/issues).
+Never include tokens, private deployment URLs, personal information, or production business
+payloads.

package/README.zh-CN.md

@@ -0,0 +1,94 @@
+# BailingHub for DeepSeek Harness
+
+[English](README.md) | 简体中文
+
+在电脑上的 DeepSeek Harness 里，通过 BailingHub 向已经接入的业务 route 发起受控任务，
+并在同一会话中持续查看状态和可用结果，不必再进入每个业务后台里的嵌入聊天入口。
+
+这是独立社区集成，不是 DeepSeek 官方开发、认证、合作、背书或推荐的插件。
+
+## 使用者得到什么
+
+安装后，DeepSeek Harness 会发现三个原生工具：
+
+| Harness 工具 | 能力 |
+| --- | --- |
+| `mcp__bailinghub__submit_governed_job` | 使用稳定请求 ID 提交一项业务任务 |
+| `mcp__bailinghub__get_governed_job` | 查询同一个任务的当前状态和公开结果 |
+| `mcp__bailinghub__wait_for_governed_job` | 有界等待同一个任务，不重复提交 |
+
+BailingHub 仍位于模型与业务系统之间。中枢地址、Client Token 和 route 都由运营者预先
+配置，不是模型参数；模型不能借工具参数切换 route，也不能提交管理员凭据、执行器凭据、
+审批结论或业务系统密钥。
+
+## 安装
+
+前置条件：
+
+- Node.js `22.19.0+` 或 `24+`；
+- 已安装 `pnpm` 与 `@deepseek-ai/dsh@0.1.0-rc.7`；
+- 一套可访问的 [BailingHub](https://github.com/bailinghub/bailinghub#快速上手)；
+- 一个只允许目标 route 的 BailingHub Client Token。
+
+```bash
+npm install --global pnpm @deepseek-ai/dsh@0.1.0-rc.7
+dsh plugin --profile web add dsh-bailinghub@0.1.0
+```
+
+在启动 Harness 的终端或进程环境中配置：
+
+```bash
+export BAILINGHUB_BASE_URL='https://hub.example.com'
+export BAILINGHUB_CLIENT_TOKEN='替换为仅允许指定-route-的-client-token'
+export BAILINGHUB_ROUTE='order_assistant'
+```
+
+检查最终配置，然后启动本机 Web 界面：
+
+```bash
+dsh --profile web --dump-config
+dsh web
+```
+
+接下来可以直接要求 Harness 通过 BailingHub 提交任务、保存返回的 `job_id`，并等待或
+查询同一个任务。
+
+第一次尝试时，请选择当前 route 已支持的任务，并明确要求：使用稳定 `request_id` 只提交
+一次，保存返回的 `job_id`；有界等待超时后，只查询同一个任务，不要重新提交。
+
+## 正确任务流程
+
+1. 为一项业务请求生成一个稳定的 `request_id`；
+2. 只调用一次 `mcp__bailinghub__submit_governed_job`；
+3. 保存返回的 `job_id`；
+4. 短时调用 `wait_for_governed_job`，或者稍后调用 `get_governed_job`；
+5. 等待超时不等于任务失败，不能因此重新提交一份替代任务。
+
+## 身份与权限边界
+
+使用本机 Harness 界面，省掉的是“必须打开业务后台聊天入口”这一步；它不代表 Harness
+登录态或本机用户自动成为可信业务身份。`0.1.0` 有意不接受模型传入行动主体。route 或
+下游业务系统仍需解析可信主体并执行最终授权；如果目标动作必须具备业务身份，而当前接入
+路径无法建立该身份，该动作就应保持不可用或被拒绝。
+
+本 Bundle 只治理通过这三个 BailingHub 工具提交的任务，不会自动拦截 Harness 中安装的
+其他工具。
+
+## 供应链说明
+
+这个 Bundle 没有自定义运行时代码、生产依赖和安装脚本。Harness 启动时，会由内置 MCP
+Client 在 Agent 沙箱之外执行固定命令
+`npx -y --package=bailinghub-mcp-server@0.1.1 bailinghub-mcp-server`。首次启动可能需要
+访问 npm；敏感环境应审查并固定版本，生产镜像可提前缓存该精确版本。
+
+MCP Server 默认拒绝非回环明文 HTTP。只有在受控私网中已经由其他可信边界终止 TLS 时，
+才可设置 `BAILINGHUB_ALLOW_INSECURE_HTTP=true`。
+
+## 兼容范围与反馈
+
+首版验证范围为 DeepSeek Harness `0.1.0-rc.7`、`bailinghub-mcp-server@0.1.1` 与
+BailingHub Client API v1。Harness 当前仍是 Developer Preview，升级 Harness 后应重新
+执行兼容性 Smoke。
+
+问题请提交到 [GitHub Issues](https://github.com/bailinghub/bailinghub-dsh-plugin/issues)。
+请勿附带 Token、私有部署地址、个人信息或生产业务数据。

package/SECURITY.md

@@ -0,0 +1,20 @@
+# Security Policy
+
+Report vulnerabilities through a private GitHub Security Advisory in this repository.
+Do not put tokens, private deployment URLs, personal information, or raw business payloads
+in a public issue.
+
+## Boundary
+
+This bundle contributes configuration only. It has no custom runtime JavaScript, production
+dependencies, or install-time scripts. On Harness startup, the built-in DSH MCP Client runs
+the exact external command
+`npx -y --package=bailinghub-mcp-server@0.1.1 bailinghub-mcp-server` outside the agent sandbox.
+Treat that package as trusted executable code and review any version change before upgrade.
+
+Use a dedicated BailingHub Client Token restricted to one route. The bundle must never
+receive an administrator token, executor token, approval credential, business-system secret,
+or acting-subject credential. Route, URL, and token stay in operator-controlled environment
+configuration and are never model tool arguments.
+
+Non-loopback HTTP is denied by default. Do not enable insecure HTTP on an untrusted network.

package/cordis.patch.yml

@@ -0,0 +1,15 @@
+- insert:
+    - id: mcp-bailinghub
+      name: '@deepseek-ai/dsh-mcp-client'
+      config:
+        serverName: bailinghub
+        transport: stdio
+        command: npx
+        args: ['-y', '--package=bailinghub-mcp-server@0.1.1', 'bailinghub-mcp-server']
+        env:
+          BAILINGHUB_BASE_URL: !!js process.env.BAILINGHUB_BASE_URL ?? ''
+          BAILINGHUB_CLIENT_TOKEN: !!js process.env.BAILINGHUB_CLIENT_TOKEN ?? ''
+          BAILINGHUB_ROUTE: !!js process.env.BAILINGHUB_ROUTE ?? ''
+          BAILINGHUB_ALLOW_INSECURE_HTTP: !!js process.env.BAILINGHUB_ALLOW_INSECURE_HTTP ?? 'false'
+        toolCallTimeoutMs: 90000
+        failOnStartupError: true

package/docs/COMPATIBILITY.md

@@ -0,0 +1,15 @@
+# Compatibility
+
+| Component | Verified version |
+| --- | --- |
+| DeepSeek Harness | `0.1.0-rc.7` |
+| DSH MCP Client | in-box version shipped by `0.1.0-rc.7` |
+| BailingHub MCP Server | `0.1.1` |
+| BailingHub Client API | `bailing.client-api.v1` |
+| Node.js | `22.19.0+` |
+
+DeepSeek Harness is currently a developer preview. Compatibility with another Harness release
+must be rechecked before changing this table or the package's supported range.
+
+The bundle uses DSH's in-box `@deepseek-ai/dsh-mcp-client`; it intentionally does not install a
+second copy into the profile. The stdio child is pinned to `bailinghub-mcp-server@0.1.1`.

package/docs/PROJECT_BOUNDARIES.md

@@ -0,0 +1,22 @@
+# Project Boundaries
+
+The dependency direction is one-way:
+
+```text
+dsh-bailinghub
+  -> DeepSeek Harness in-box MCP Client
+  -> bailinghub-mcp-server
+  -> BailingHub public Client API
+  -> operator-selected business route
+```
+
+This repository owns only the DSH bundle and its compatibility evidence. It does not fork or
+modify DeepSeek Harness, BailingHub Core, the generic MCP adapter, or a downstream business
+system.
+
+The integration does not establish a trusted business subject, grant permissions, make an
+approval decision, or replace the business system's final authorization. It also does not
+govern DSH tools that are unrelated to the three BailingHub MCP tools.
+
+DeepSeek and DeepSeek Harness are names of their respective owners. This is an independent
+community integration, not an official DeepSeek plugin or partnership.

package/package.json

@@ -0,0 +1,59 @@
+{
+  "name": "dsh-bailinghub",
+  "version": "0.1.0",
+  "description": "Use DeepSeek Harness to submit and follow governed business tasks through BailingHub.",
+  "license": "MIT",
+  "type": "module",
+  "author": {
+    "name": "BailingHub Contributors",
+    "email": "niejingchuan@live.com"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bailinghub/bailinghub-dsh-plugin.git"
+  },
+  "bugs": {
+    "url": "https://github.com/bailinghub/bailinghub-dsh-plugin/issues"
+  },
+  "homepage": "https://github.com/bailinghub/bailinghub-dsh-plugin#readme",
+  "keywords": [
+    "deepseek-harness",
+    "dsh",
+    "dsh-plugin",
+    "bailinghub",
+    "mcp",
+    "ai-agent-governance",
+    "business-system-automation",
+    "human-in-the-loop",
+    "audit-trail",
+    "self-hosted"
+  ],
+  "files": [
+    "cordis.patch.yml",
+    "README.zh-CN.md",
+    "SECURITY.md",
+    "PRIVACY.md",
+    "CHANGELOG.md",
+    "docs/COMPATIBILITY.md",
+    "docs/PROJECT_BOUNDARIES.md"
+  ],
+  "engines": {
+    "node": "^22.19.0 || >=24.0.0"
+  },
+  "scripts": {
+    "check:project": "node scripts/check-project.mjs",
+    "check:release-tag": "node scripts/check-release-tag.mjs",
+    "test": "node --test tests/*.test.mjs",
+    "verify": "npm run check:project && npm test",
+    "prepack": "npm run verify"
+  },
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  },
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  }
+}