dsh-semble 2.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Liu Kai
+
+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/README.md

@@ -0,0 +1,212 @@
+# dsh-semble
+
+[![npm](https://img.shields.io/npm/v/dsh-semble.svg)](https://www.npmjs.com/package/dsh-semble)
+
+> Semantic code search for DeepSeek Harness.
+>
+> Ask **where** something lives instead of recalling **what** it is called, and the agent finds the
+> file, reads it, then edits.
+
+English | [简体中文](README.zh-CN.md)
+
+`dsh-semble` brings [Semble](https://github.com/MinishLab/semble)'s code index into every DSH
+session as two native MCP tools. `grep` needs a string you already know; this needs a description of
+behaviour — "where is the retry policy applied when a request fails", "which module decides the
+scoring weights". That is usually the moment an agent starts guessing file names.
+
+Nothing to learn beyond that: after installation the tools sit next to `read` and `grep`, and the
+agent decides when the index is worth a call.
+
+## What you get
+
+| Tool | Hand it | Back comes |
+| --- | --- | --- |
+| `mcp__semble__search` | a sentence describing the code or where it lives | ranked `file:line` hits with snippets |
+| `mcp__semble__find_related` | one location you already know | its neighbours: other implementations, callers, tests |
+
+A typical exchange:
+
+> **You:** Where does DSH decide that a plugin is "loaded"?
+>
+> **Agent:** calls `search`, gets a hit in the plugin inventory, opens it with `read`, finds
+> `isEntryLoaded` comparing loader entry names against the package name, and answers from the source
+> rather than from a guess.
+
+## Using the tools
+
+- `repo` — **required**. Absolute path of the repository, or an `https://` git URL. A list searches
+  several repositories at once.
+- `top_k` — default 5. Raise to 10–20 when the first pass misses.
+- `max_snippet_lines` — default 10; `0` returns locations only.
+- `content` — `code` (default), `docs`, `config`, or `all`.
+
+The first query against a repository builds its index (slow, one-time); later queries reuse it.
+Hits are ranked by similarity, so a score near `0.0x` usually means "nothing relevant here" rather
+than "the best answer".
+
+## Install
+
+### Desktop app
+
+**Settings → Plugins → Install**, and paste:
+
+```
+dsh-semble
+```
+
+Pin a version with `dsh-semble@2.0.0`. The settings page is the only supported route for the
+`desktop` profile — the CLI refuses it because the Electron app owns that profile's `node_modules`
+and lockfile.
+
+### CLI
+
+```sh
+dsh plugin --profile web add dsh-semble
+```
+
+The subcommand runs `pnpm add` inside the profile and reconciles `dsh.profile.bundles`, so the bundle
+mounts on the next start. There is no build step, so pnpm needs no `allowBuilds` exemption.
+
+### From source
+
+To track `main`, a fork, or an unreleased commit, install from the repository instead:
+
+```sh
+dsh plugin --profile web add github:CodeIntegrity/dsh-semble
+```
+
+`github:owner/repo`, `git+https://…`, `https://github.com/owner/repo` and `.tgz` URLs are accepted;
+these need `git` on PATH.
+
+### Local checkout
+
+```sh
+dsh plugin --profile web add link:/absolute/path/to/dsh-semble   # macOS / Linux
+dsh plugin --profile web add link:D:\path\to\dsh-semble          # Windows
+```
+
+The profile then points at your working copy, so edits to `cordis.patch.yml` apply on the next start
+without reinstalling.
+
+### Prerequisites
+
+[uv](https://docs.astral.sh/uv/) must be on PATH — `uvx` launches Semble from PyPI:
+
+```powershell
+winget install astral-sh.uv                      # Windows
+```
+
+```sh
+brew install uv                                  # macOS
+curl -LsSf https://astral.sh/uv/install.sh | sh  # macOS / Linux
+```
+
+First start downloads the package and the embedding model (~1–2 min, one-time, offline afterwards).
+Restart DSH once after installing; until then the settings row may read 待重启.
+
+## Settings
+
+Edit the `semble-mcp` row in **Settings → Plugins**:
+
+| Field | Default | Why change it |
+| --- | --- | --- |
+| `args` | `--from 'semble[mcp]' semble` | append `--content all` to index docs and config too |
+| `args` (version) | floating | `semble[mcp]==X.Y.Z` pins a release |
+| `env` | empty | `HF_ENDPOINT` on restricted networks, `SEMBLE_CACHE_LOCATION` to move the index |
+| `cwd` | inherited | keep unset; per-call `repo` values should be absolute paths |
+| `command` | `uvx` | point it at `uvx.exe` if only a `.cmd` shim is installed |
+
+Changing settings restarts the MCP connection; disk index caches survive.
+
+## Platform notes
+
+The bundle ships no OS-specific path and no region-specific endpoint, so one installation serves all
+three platforms. What differs is only what you type:
+
+| Concern | Windows | macOS / Linux |
+| --- | --- | --- |
+| Executable | `uvx.exe`, resolved through PATH | `uvx` |
+| Repository paths | `D:\work\repo` | `/home/me/repo` |
+| Profile home | `C:\Users\<you>\.dsh` | `~/.dsh` |
+| Retrieved paths | keep `\` separators | POSIX `/` |
+
+## Bundled skill
+
+Installation also registers one routing skill, `semble-code-search`. The tools do not advertise
+*when* they are worth calling, and a model that reaches for `grep` first never learns that the index
+existed.
+
+DSH loads skills lazily:
+
+| When | Enters the session | Cost |
+| --- | --- | --- |
+| Before the first request | one catalog entry (name + capped description) | a few hundred bytes per session |
+| Model calls `skill` | the full `skills/semble/SKILL.md` body | ~2 KB, only when used |
+| You type `/semble-code-search` | same body, injected into that step | manual |
+
+The body never enters the system prompt. To keep the tools and drop the skill, delete the
+`ctx.skills.register(...)` call in `lib/index.js`.
+
+## How it works
+
+The bundle inserts two loader rows:
+
+1. `semble-mcp-anchor` — a no-op plugin loaded under this package's own name. DSH decides "loaded"
+   by matching loader entry names against the installed package name, and the MCP client row loads
+   under `@deepseek-ai/dsh-mcp-client`; without the anchor the settings row reads 未加载 / 待重启
+   while the tools work fine.
+2. `semble-mcp` — the official `@deepseek-ai/dsh-mcp-client` row, configured to start
+   `uvx --from "semble[mcp]" semble` over stdio.
+
+Semble itself is **not vendored**. The plugin declares how to launch it from PyPI with a floating
+spec, so upstream bugfixes and new tools arrive on the next server start; only a breaking change to
+the CLI surface would need an edit here.
+
+## Update
+
+Re-run the install with a newer version, or press 更新 in settings:
+
+```sh
+dsh plugin --profile web add dsh-semble@2.0.0
+```
+
+Source installs re-run with the new ref, e.g.
+`dsh plugin --profile web add github:CodeIntegrity/dsh-semble#v2.0.0`.
+
+## Uninstall
+
+**Settings → Plugins → 卸载**, or:
+
+```sh
+dsh plugin --profile web remove dsh-semble
+```
+
+Installed the 1.x source build? Remove it by its old name first:
+`dsh plugin --profile web remove @local/semble-mcp`. The package was renamed in 2.0.0, and the anchor
+row only matches an install whose package name is `dsh-semble`.
+
+The cached index and the HuggingFace model stay on disk and are reused after a reinstall.
+
+## Troubleshooting
+
+| Symptom | Cause | Fix |
+| --- | --- | --- |
+| Row reads 待重启 after install | the host loaded its layer list before the install | restart DSH once |
+| Tools work, row reads 未加载 | `cordis.patch.yml` lost the anchor row | reinstall this version or newer |
+| `mcp__semble__*` never appears | `uvx` missing, or the first download failed | run `uvx --from "semble[mcp]" semble --version` and read the error |
+| First search takes minutes | one-time model download | wait, or set `HF_ENDPOINT` |
+| `ERR_PNPM_GIT_RESOLVE_FAILED` | no network route to github.com | use a tarball URL or a mirror |
+
+## Development
+
+```sh
+git clone https://github.com/CodeIntegrity/dsh-semble
+dsh plugin --profile web add link:$(pwd)   # then edit and restart DSH
+```
+
+No build step: `lib/index.js` is plain ESM and `cordis.patch.yml` is read directly. The only runtime
+dependency is `uv`.
+
+## License
+
+MIT

package/README.zh-CN.md

@@ -0,0 +1,198 @@
+# dsh-semble
+
+[![npm](https://img.shields.io/npm/v/dsh-semble.svg)](https://www.npmjs.com/package/dsh-semble)
+
+> 给 DeepSeek Harness 的语义代码检索。
+>
+> 你只需要问「这东西在哪」，不必先想起它叫什么——agent 自己找到文件、读它、再改。
+
+[English](README.md) | 简体中文
+
+`dsh-semble` 把 [Semble](https://github.com/MinishLab/semble) 的代码索引接进每个 DSH 会话，
+以两个原生 MCP 工具的形式出现。`grep` 要求你手里已经有一个字符串；它要的是一句行为描述——
+「请求失败时重试策略在哪生效」「哪个模块决定了打分权重」。而这种时刻，agent 通常正好开始猜文件名。
+
+除此之外没有要学的东西：装好之后两个工具就摆在 `read`、`grep` 旁边，由 agent 决定什么时候值得查一次索引。
+
+## 你会得到什么
+
+| 工具 | 交给它 | 拿回来 |
+| --- | --- | --- |
+| `mcp__semble__search` | 一句话描述代码做什么、或者它在哪儿 | 按相关度排序的 `file:line` 命中 + 片段 |
+| `mcp__semble__find_related` | 一个你已经知道的位置 | 它的邻居：其他实现、调用方、测试 |
+
+一次典型对话：
+
+> **你：** DSH 判断「插件已加载」是在哪儿决定的？
+>
+> **agent：** 调 `search`，拿到插件清单模块的一条命中，用 `read` 打开，找到 `isEntryLoaded`
+> 把 loader 条目名和包名做比对，然后**基于源码**回答，而不是基于猜测。
+
+## 工具怎么用
+
+- `repo` —— **必填**。仓库绝对路径，或 `https://` git 地址；传数组可同时检索多个仓库。
+- `top_k` —— 默认 5，首轮没命中时提到 10–20。
+- `max_snippet_lines` —— 默认 10，`0` 只返回位置。
+- `content` —— `code`（默认）、`docs`、`config`、`all`。
+
+某个仓库的首次查询要建索引（慢，一次性），之后复用。命中按相似度排序，所以分数接近 `0.0x`
+通常意味着「这儿没有相关内容」，而不是「这是最佳答案」。
+
+## 安装
+
+### 桌面端
+
+**设置 → 插件 → 安装**，粘贴：
+
+```
+dsh-semble
+```
+
+钉住版本写 `dsh-semble@2.0.0`。`desktop` profile 只支持从设置页安装——CLI 会拒绝，
+因为这个 profile 的 `node_modules` 与 lockfile 由 Electron 应用独占。
+
+### 命令行
+
+```sh
+dsh plugin --profile web add dsh-semble
+```
+
+该子命令在 profile 目录里跑 `pnpm add`，随后 reconcile `dsh.profile.bundles`，所以下次启动即挂载。
+没有构建步骤，pnpm 不需要 `allowBuilds` 例外。
+
+### 从源码安装
+
+要跟 `main`、装某个 fork 或装还没发版的提交，走仓库安装：
+
+```sh
+dsh plugin --profile web add github:CodeIntegrity/dsh-semble
+```
+
+支持 `github:owner/repo`、`git+https://…`、`https://github.com/owner/repo` 和 `.tgz` 链接；
+这些需要 PATH 上有 `git`。
+
+### 本地目录
+
+```sh
+dsh plugin --profile web add link:/绝对路径/dsh-semble   # macOS / Linux
+dsh plugin --profile web add link:D:\path\to\dsh-semble  # Windows
+```
+
+之后 profile 指向你的工作副本，改完 `cordis.patch.yml` 下次启动即生效，无需重装。
+
+### 前置条件
+
+PATH 上要有 [uv](https://docs.astral.sh/uv/)——`uvx` 负责从 PyPI 拉起 Semble：
+
+```powershell
+winget install astral-sh.uv                      # Windows
+```
+
+```sh
+brew install uv                                  # macOS
+curl -LsSf https://astral.sh/uv/install.sh | sh  # macOS / Linux
+```
+
+首次启动会下载包与嵌入模型（约 1–2 分钟，一次性，之后离线可用）。装完重启一次 DSH；在那之前设置页那行
+可能显示「待重启」。
+
+## 设置
+
+在 **设置 → 插件** 里编辑 `semble-mcp` 行：
+
+| 字段 | 默认值 | 什么时候改 |
+| --- | --- | --- |
+| `args` | `--from 'semble[mcp]' semble` | 追加 `--content all` 让文档和配置也进索引 |
+| `args`（版本） | 浮动 | 改成 `semble[mcp]==X.Y.Z` 钉版本 |
+| `env` | 空 | 受限网络加 `HF_ENDPOINT`；搬索引加 `SEMBLE_CACHE_LOCATION` |
+| `cwd` | 继承 | 保持不设；每次调用的 `repo` 用绝对路径 |
+| `command` | `uvx` | 如果只装了 `.cmd` 包装，改指向 `uvx.exe` |
+
+改设置会重启 MCP 连接；磁盘上的索引缓存不受影响。
+
+## 平台差异
+
+bundle 不含任何 OS 专属路径、也不含区域专属 endpoint，一份安装三平台通用。真正不同的只有你敲进去的东西：
+
+| 关注点 | Windows | macOS / Linux |
+| --- | --- | --- |
+| 可执行文件 | `uvx.exe`，经 PATH 解析 | `uvx` |
+| 仓库路径 | `D:\work\repo` | `/home/me/repo` |
+| profile 目录 | `C:\Users\<你>\.dsh` | `~/.dsh` |
+| 命中路径分隔符 | 保留 `\` | POSIX `/` |
+
+## 内置 skill
+
+安装同时注册一个路由 skill：`semble-code-search`。工具本身不会说明「什么时候值得用」，而先摸
+`grep` 的模型永远不会发现索引的存在。
+
+DSH 的 skill 惰性加载：
+
+| 时机 | 进入会话的内容 | 成本 |
+| --- | --- | --- |
+| 首次请求前 | 一条目录条目（名称 + 截断描述） | 每会话几百字节 |
+| 模型调 `skill` | 完整 `skills/semble/SKILL.md` 正文 | 约 2 KB，只在实际用到时 |
+| 你输入 `/semble-code-search` | 同一份正文，注入当步 | 手动 |
+
+正文不进系统提示词。只想保留工具、不要 skill，删掉 `lib/index.js` 里的 `ctx.skills.register(...)`
+调用即可。
+
+## 工作原理
+
+bundle 插入两行 loader：
+
+1. `semble-mcp-anchor` —— 以本包名加载的空插件。DSH 判断「已加载」是拿 loader 条目名和已安装包名做匹配，
+   而 MCP 客户端那行是以 `@deepseek-ai/dsh-mcp-client` 加载的；没有这个锚点，明明工具能用，设置页却显示
+   未加载 / 待重启。
+2. `semble-mcp` —— 官方 `@deepseek-ai/dsh-mcp-client` 行，配置为通过 stdio 启动
+   `uvx --from "semble[mcp]" semble`。
+
+Semble 本体**不做 vendored 内嵌**。插件只声明如何从 PyPI 拉起它，且用浮动版本号，所以上游的 bugfix
+与新工具在下次 server 启动时生效；只有 CLI 表面发生破坏性变更时才需要改这里。
+
+## 更新
+
+用更新的版本重跑安装，或在设置页点「更新」：
+
+```sh
+dsh plugin --profile web add dsh-semble@2.0.0
+```
+
+源码安装则换 ref 重跑，例如
+`dsh plugin --profile web add github:CodeIntegrity/dsh-semble#v2.0.0`。
+
+## 卸载
+
+**设置 → 插件 → 卸载**，或：
+
+```sh
+dsh plugin --profile web remove dsh-semble
+```
+
+装过 1.x 源码版的话，先按旧名卸载：`dsh plugin --profile web remove @local/semble-mcp`。
+2.0.0 起改了包名，而锚点行只认包名为 `dsh-semble` 的安装。
+
+已缓存的索引与 HuggingFace 模型留在磁盘上，重装可复用。
+
+## 常见问题
+
+| 现象 | 原因 | 处理 |
+| --- | --- | --- |
+| 装完显示「待重启」 | 宿主在安装前已经加载了层列表 | 重启 DSH 一次 |
+| 工具能用但显示「未加载」 | `cordis.patch.yml` 缺了锚点行 | 重装本版本或更新版本 |
+| `mcp__semble__*` 一直不出现 | 缺 `uvx`，或首次下载失败 | 手动跑 `uvx --from "semble[mcp]" semble --version` 看报错 |
+| 首次检索卡几分钟 | 模型一次性下载 | 等待，或设 `HF_ENDPOINT` |
+| 安装时报 `ERR_PNPM_GIT_RESOLVE_FAILED` | 到 github.com 没有网络通路 | 改用 tarball 链接或镜像 |
+
+## 开发
+
+```sh
+git clone https://github.com/CodeIntegrity/dsh-semble
+dsh plugin --profile web add link:$(pwd)   # 之后改代码、重启 DSH
+```
+
+没有构建步骤：`lib/index.js` 是纯 ESM，`cordis.patch.yml` 直接读取。唯一运行时依赖是 `uv`。
+
+## 许可
+
+MIT

package/cordis.patch.yml

@@ -0,0 +1,48 @@
+# Semble MCP bridge for DeepSeek Harness.
+#
+# Inserts the official @deepseek-ai/dsh-mcp-client row configured to start the
+# Semble MCP server (PyPI project `semble`, MIT, https://github.com/MinishLab/semble)
+# over stdio. No semble source code is vendored here: `uvx` resolves and installs
+# the package from PyPI, so upstream releases (bugfixes, new MCP tools) are picked
+# up automatically on the next server start.
+#
+# Platform policy: this file deliberately contains no OS-specific path and no
+# region-specific endpoint. `command: uvx` is a real executable on every platform
+# uv supports (uvx.exe on Windows, uvx on macOS/Linux), resolved through PATH, so
+# the same row works unchanged everywhere. Everything an operator may need to
+# adapt — repository paths, proxies, mirrors — belongs in the plugin settings,
+# not in the shipped default.
+#
+# Version policy: floating spec `semble[mcp]` follows the latest release.
+# To pin a specific version for stability, edit this row in the DSH plugin
+# settings and change the spec to `semble[mcp]==X.Y.Z`.
+- insert:
+    # Host-side anchor row: an empty plugin loaded under this package's own name.
+    # DSH's plugin inventory (and the Plugin Hub) decide "loaded" by matching loader
+    # entry names against the installed package name, and the MCP client row below
+    # loads under @deepseek-ai/dsh-mcp-client — without this anchor the bundle would
+    # report 未加载 / 待重启 while its tools are actually registered and working.
+    - id: semble-mcp-anchor
+      name: 'dsh-semble'
+
+    - id: semble-mcp
+      name: '@deepseek-ai/dsh-mcp-client'
+      config:
+        serverName: semble
+        transport: stdio
+        command: uvx
+        args:
+          - --from
+          - 'semble[mcp]'
+          - semble
+        failOnStartupError: true
+        # No `env` defaults on purpose: the embedding model
+        # (minishlab/potion-code-16M-v2) is fetched from huggingface.co unless the
+        # operator asks otherwise. On networks where huggingface.co is unreachable,
+        # add the following in the plugin settings rather than here:
+        #
+        #   HF_ENDPOINT: https://hf-mirror.com
+        #
+        # `cwd` is intentionally unset too: the server inherits the host working
+        # directory, and per-call `repo` values should be absolute paths in the
+        # host's own convention (C:\... on Windows, /... on macOS/Linux).

package/icon.svg

@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64">
+  <rect x="5" y="9" width="36" height="46" rx="7" fill="#e8f2fa" stroke="#247bbf" stroke-width="3"/>
+  <path d="M15 24l-6 6 6 6" fill="none" stroke="#247bbf" stroke-width="4" stroke-linecap="round" stroke-linejoin="round"/>
+  <path d="M31 24l6 6-6 6" fill="none" stroke="#247bbf" stroke-width="4" stroke-linecap="round" stroke-linejoin="round"/>
+  <path d="M26 18l-4 24" fill="none" stroke="#247bbf" stroke-width="3" stroke-linecap="round"/>
+  <circle cx="46" cy="44" r="11" fill="none" stroke="#247bbf" stroke-width="5"/>
+  <path d="M54 52l6 6" stroke="#247bbf" stroke-width="6" stroke-linecap="round"/>
+</svg>

package/lib/index.js

@@ -0,0 +1,75 @@
+/**
+ * Semble MCP bundle — host-side anchor plugin.
+ *
+ * Two responsibilities:
+ *
+ * 1. Give the bundle a stable loader entry. The real work is done by the
+ *    `@deepseek-ai/dsh-mcp-client` row declared next to this one in
+ *    cordis.patch.yml, which loads the MCP client under its own module name, so
+ *    a running host would otherwise have no loader entry named after this
+ *    package. DSH's plugin inventory and the Plugin Hub decide "loaded" by
+ *    matching loader entry names against the installed npm package name
+ *    (`isEntryLoaded`), so without an entry of our own the plugin is reported as
+ *    未加载 / 待重启 even while its MCP tools are registered and working.
+ *
+ * 2. Register the bundled routing skill so the model knows *when* the MCP tools
+ *    are worth calling. The skill body ships inside this package (skills/
+ *    semble/SKILL.md) and is registered as a runtime skill, which keeps plugin
+ *    installation a single step: no copying files into ~/.dsh/skills.
+ *
+ * The skill is loaded lazily by DSH: the session catalog carries only the name
+ * and description, and the body text reaches the model only when it calls the
+ * `skill` tool. Reading the file here costs one small synchronous read at host
+ * start and nothing per request.
+ */
+import { readFileSync } from 'node:fs'
+
+export const name = 'semble-mcp'
+
+export const inject = ['skills']
+
+const SKILL_URL = new URL('../skills/semble/SKILL.md', import.meta.url)
+
+/** Strip the YAML frontmatter so filesystem-style SKILL.md files render clean. */
+function stripFrontmatter(markdown) {
+  const match = /^\uFEFF?---\r?\n[\s\S]*?\r?\n---\r?\n/.exec(markdown)
+  return match === null ? markdown : markdown.slice(match[0].length).replace(/^\s*\n/, '')
+}
+
+/** Read the bundled skill body, or `undefined` when the package is incomplete. */
+function readSkillBody() {
+  try {
+    return stripFrontmatter(readFileSync(SKILL_URL, 'utf8')).trim()
+  } catch (error) {
+    // A missing skill file must not take the MCP connection's anchor row down
+    // with it: the tools keep working, only the routing hint is absent.
+    console.warn('[semble-mcp] bundled skill could not be read:', error?.message ?? error)
+    return undefined
+  }
+}
+
+/** Apply: provide the loader anchor and register the bundled routing skill. */
+export default function sembleMcpBundle(ctx) {
+  const content = readSkillBody()
+  if (content === undefined) return
+  // Registered into this plugin's layer, so teardown follows the fiber and the
+  // returned disposer needs no bookkeeping here.
+  ctx.skills.register({
+    name: 'semble-code-search',
+    description:
+      'Find code by what it does, not by exact text. Use when locating an implementation, a caller, or a related pattern before editing, or when a plain text search returns too much noise.',
+    whenToUse:
+      'before a broad code search in a repository, and when a grep result is too noisy to be useful; gives the query shape, the semantic search workflow, and the cost limits of the Semble MCP tools.',
+    content,
+    source: 'bundle:dsh-semble',
+    resourceBase: { kind: 'opaque', description: 'Exposed as the mcp__semble__search and mcp__semble__find_related MCP tools.' },
+    invocation: { modelInvocable: true, userInvocable: true },
+  })
+}
+
+/**
+ * Named form of the same entry point. The loader accepts either the default
+ * export or a module-level `apply(ctx)`, and spelling both out makes the
+ * plugin's shape explicit to readers and to plugin-listing checks.
+ */
+export const apply = sembleMcpBundle

package/locale/en.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "Semble Code Search (MCP)",
+    "description": "Exposes the Semble agent code-search engine as native MCP tools (search / find_related). Starts the official Semble MCP server from PyPI via uvx; follows the latest upstream release automatically."
+  }
+}

package/locale/zh.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "Semble 代码搜索（MCP）",
+    "description": "把 Semble 的 Agent 代码检索引擎接入为原生 MCP 工具（search / find_related）。通过 uvx 从 PyPI 启动官方 Semble MCP 服务器，自动跟随上游最新版本。"
+  }
+}

package/package.json

@@ -0,0 +1,52 @@
+{
+  "name": "dsh-semble",
+  "version": "2.0.0",
+  "type": "module",
+  "main": "lib/index.js",
+  "description": "Semble 语义代码搜索（semantic code search）MCP bundle：安装即用，无需客户端配置。Semble semantic code search for DeepSeek Harness via MCP (search / find_related).",
+  "license": "MIT",
+  "author": "Liu Kai",
+  "icon": "icon.svg",
+  "engines": {
+    "node": ">=22",
+    "dsh": ">=0.2.1-rc.2"
+  },
+  "homepage": "https://github.com/CodeIntegrity/dsh-semble#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/CodeIntegrity/dsh-semble.git"
+  },
+  "bugs": {
+    "url": "https://github.com/CodeIntegrity/dsh-semble/issues"
+  },
+  "keywords": [
+    "dsh",
+    "dsh-plugin",
+    "dsh-bundle",
+    "deepseek-harness",
+    "semble",
+    "mcp",
+    "code-search",
+    "semantic-search"
+  ],
+  "exports": {
+    ".": "./lib/index.js",
+    "./locale/*.json": "./locale/*.json",
+    "./icon": "./icon.svg"
+  },
+  "files": [
+    "lib",
+    "skills",
+    "cordis.patch.yml",
+    "locale/*.json",
+    "icon.svg",
+    "LICENSE",
+    "README.md",
+    "README.zh-CN.md"
+  ],
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  }
+}

package/skills/semble/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: semble-code-search
+description: Find code by what it does, not by exact text. Use when you need to locate an implementation, a caller, or a related pattern in the current repository before editing, or when a plain text search returns too much noise.
+---
+
+# Semble code search
+
+Semantic search over code, exposed by the Semble MCP server as two tools:
+
+- `mcp__semble__search` — describe what the code does or where it lives, get ranked `file:line` hits with snippets.
+- `mcp__semble__find_related` — given one known location, find its siblings: other implementations of the same interface, the callers of a function, the tests for a class.
+
+## When to use it
+
+Use it when you know *what* you are looking for but not *where* it is:
+
+- "where is the retry policy applied when a request fails"
+- "which module decides the scoring weights"
+- "what else implements this provider interface"
+
+Prefer the `grep` and `read` tools when you already have a path, an exact identifier, or a
+short literal to match — the semantic index is a coarse first pass, not a replacement for
+reading the code.
+
+## How to query well
+
+The query is matched against embedded function bodies, so phrase it as behaviour:
+
+- Good: `persist a chunk to the vector store`, `resolve the model name from config`, `stream tokens to the client`.
+- Bad: a stack trace, an error string, a single identifier, or `fix bug`.
+
+Controls, all on both tools unless noted:
+
+- `repo` — **required**. The absolute path of the repository, or an `https://` URL of a git remote.
+  In a session this is normally the session working directory, written the way the host writes paths
+  (`D:\work\repo` on Windows, `/home/me/repo` on macOS/Linux). Pass a list to search several
+  repositories at once. Omitting it fails validation, so always send it.
+- `top_k` — default 5; raise it to 10–20 when the first pass misses.
+- `max_snippet_lines` — default 10; use `0` for locations only, or omit a cap to see a whole chunk.
+- `content` — `code` (default), `docs`, `config`, or `all`; switch to `all` when the answer may live in documentation or configuration.
+
+## Workflow
+
+1. `search` with a behaviour phrase, always passing `repo`.
+2. Open the top hit with the `read` tool, using its `start_line` as `offset`, to confirm it is the
+   right code and not a similarity artifact. Pass the returned path through exactly as given — it
+   keeps `\` separators on Windows and is already POSIX on macOS/Linux. Rewriting separators by hand
+   is where these paths break.
+3. `find_related` on that location when you need callers, siblings, or tests.
+4. Only then edit.
+
+## Costs and limits
+
+- The first query against a repository builds its index; later queries reuse it. Expect the first
+  call in a new repository to be slow.
+- Results are ranked by cosine similarity, so the top hit can be a near-miss. A score close to
+  `0.0x` usually means the index holds nothing relevant — stop instead of forcing the hit.
+- The index may be stale relative to uncommitted edits; when proximity matters, read the file
+  rather than trusting the snippet.
+
+## If the tools are missing
+
+`mcp__semble__search` and `mcp__semble__find_related` only exist when this bundle's MCP connection
+mounted in the current session. If they are absent from your toolset, say so and fall back to
+`grep`/`glob`; do not narrate a call you cannot make.