chore: release capability resolver v0.1.1

CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to this project are documented in this file. The format foll
 
 ## [Unreleased]
 
+## [0.1.1] - 2026-08-27
+
+### Fixed
+
+- Replaced the stale pre-release install wording with a pinned `v0.1.1` install command and an explicit `v0.1.0` to `v0.1.1` update path in both READMEs.
+
+### Changed
+
+- Advanced the package and compatibility-record release identity to `0.1.1` while retaining the exact DeepSeek Harness `0.1.1-rc.2` compatibility lane and unchanged resolver runtime behavior.
+
 ## [0.1.0] - 2026-08-25
 
 ### Added
@@ -19,5 +29,6 @@ All notable changes to this project are documented in this file. The format foll
 - Split the full loopback UI resolution from a safe model projection so untrusted catalog and current-capability free text cannot enter the `capability_resolve` canonical value, model render, or direct/nested result session content.
 - Revalidate the browser RPC byte, collection, text, and canonical candidate-link limits before any community metadata can render as an external link.
 
-[Unreleased]: https://github.com/striveh/dsh-capability-resolver/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/striveh/dsh-capability-resolver/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/striveh/dsh-capability-resolver/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/striveh/dsh-capability-resolver/releases/tag/v0.1.0

README.md

@@ -13,7 +13,7 @@ Catalog inclusion, topics, stars, and download counts are discovery metadata. Th
 
 ## Status and compatibility
 
-Version `0.1.0` has one declared target: DeepSeek Harness `0.1.1-rc.2`. It does not claim compatibility with an older or newer DSH release.
+Version `0.1.1` has one declared target: DeepSeek Harness `0.1.1-rc.2`. It does not claim compatibility with an older or newer DSH release. This maintenance release changes release metadata and installation guidance; resolver runtime behavior is unchanged from `0.1.0`.
 
 The machine-readable record is [`compatibility/dsh.json`](compatibility/dsh.json). A weekly workflow compares the latest published DSH release and the Git blob digest of the exact official files this plugin relies on. A new release, moved tag, missing authority, or changed digest opens or updates one review issue and fails the workflow. Automation never broadens the compatibility claim.
 
@@ -36,14 +36,21 @@ Prerequisites:
 - Node.js `22.19` or a newer version allowed by the package engine; and
 - pnpm on `PATH`, as required by `dsh plugin`.
 
-After the `v0.1.0` release is published, install the reviewed tag into the Web profile:
+Install the pinned `v0.1.1` tag into the Web profile:
 
 ```sh
-dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.0
+dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.1
 dsh --profile web --dump-config
 dsh web
 ```
 
+To update an existing `v0.1.0` installation, run the same pinned `add` command for `v0.1.1`, inspect the expanded configuration, and restart Web:
+
+```sh
+dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.1
+dsh --profile web --dump-config
+```
+
 Restart a running Web profile after adding, updating, disabling, or removing the bundle. The expanded configuration should contain a `dsh-capability-resolver` layer. The repository commits `lib/` and intentionally has no `prepare`, `preinstall`, `install`, or `postinstall` script, so a GitHub install does not need package build permission.
 
 For an unreleased checkout during development:

README.zh.md

@@ -13,7 +13,7 @@
 
 ## 状态与兼容性
 
-版本 `0.1.0` 只声明一个目标：DeepSeek Harness `0.1.1-rc.2`。它不声称兼容更早或更新的 DSH 版本。
+版本 `0.1.1` 只声明一个目标：DeepSeek Harness `0.1.1-rc.2`。它不声称兼容更早或更新的 DSH 版本。此维护版本只更新发布元数据与安装指引；解析器运行时行为与 `0.1.0` 相同。
 
 机器可读记录位于 [`compatibility/dsh.json`](compatibility/dsh.json)。每周 workflow 会比较 DSH 最新公开 release，并计算本插件依赖的官方文件 Git blob 摘要。出现新 release、tag 移动、事实源缺失或摘要变化时，自动化会新建或更新一个审阅 issue 并让 workflow 失败；它不会自动扩大兼容声明。
 
@@ -36,14 +36,21 @@
 - Node.js `22.19` 或 package engine 允许的更新版本；
 - `PATH` 中有 pnpm，这是 `dsh plugin` 的要求。
 
-`v0.1.0` 发布后，把已审阅 tag 安装进 Web profile：
+把固定的 `v0.1.1` tag 安装进 Web profile：
 
 ```sh
-dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.0
+dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.1
 dsh --profile web --dump-config
 dsh web
 ```
 
+如需把现有 `v0.1.0` 安装更新到 `v0.1.1`，执行同一条固定到 `v0.1.1` 的 `add` 命令，检查展开后的配置，然后重启 Web：
+
+```sh
+dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.1
+dsh --profile web --dump-config
+```
+
 新增、更新、禁用或移除 bundle 后，需要重启正在运行的 Web profile。展开后的配置中应出现 `dsh-capability-resolver` 层。仓库提交预构建 `lib/`，并有意不提供 `prepare`、`preinstall`、`install` 或 `postinstall` 脚本，因此从 GitHub 安装不需要授予 package 构建权限。
 
 开发期间可安装本地未发布 checkout：

compatibility/dsh.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "packageVersion": "0.1.0",
+  "packageVersion": "0.1.1",
   "upstream": {
     "repository": "deepseek-ai/deepseek-harness",
     "defaultBranch": "master",
@@ -15,7 +15,7 @@
   },
   "claim": {
     "level": "single-release",
-    "statement": "Version 0.1.0 targets only DSH 0.1.1-rc.2; release compatibility requires the repository CI and installable-bundle acceptance evidence.",
+    "statement": "Version 0.1.1 targets only DSH 0.1.1-rc.2; release compatibility requires the repository CI and installable-bundle acceptance evidence.",
     "excludes": [
       "DeepSeek endorsement",
       "compatibility with any unlisted DSH release",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-capability-resolver",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Read-only local capability and community plugin discovery for DeepSeek Harness Web",
   "license": "MIT",
   "type": "module",

scripts/verify-package.mjs

@@ -3,6 +3,7 @@ import { dirname, resolve } from 'node:path'
 import { fileURLToPath, pathToFileURL } from 'node:url'
 
 const PACKAGE_NAME = 'dsh-capability-resolver'
+const PACKAGE_VERSION = '0.1.1'
 const PLUGIN_NAME = 'capability-resolver'
 const DSH_VERSION = '0.1.1-rc.2'
 const PATCH_PATH = './cordis.patch.yml'
@@ -106,7 +107,7 @@ try {
 }
 
 check(manifest.name === PACKAGE_NAME, `package name must be ${PACKAGE_NAME}`)
-check(manifest.version === '0.1.0', 'initial package version must be 0.1.0')
+check(manifest.version === PACKAGE_VERSION, `package version must be ${PACKAGE_VERSION}`)
 check(manifest.type === 'module', 'package type must be module')
 check(manifest.main === 'lib/index.js', 'main must be lib/index.js')
 check(manifest.types === 'lib/types/index.d.ts', 'types must be lib/types/index.d.ts')
@@ -223,7 +224,7 @@ for (const readmePath of ['README.md', 'README.zh.md']) {
   } catch (error) {
     failures.push(`cannot read ${readmePath}: ${error instanceof Error ? error.message : String(error)}`)
   }
-  check(readme.includes('dsh plugin --profile web add github:striveh/dsh-capability-resolver#v0.1.0'), `${readmePath} must contain the pinned GitHub install command`)
+  check(readme.includes(`dsh plugin --profile web add github:striveh/dsh-capability-resolver#v${PACKAGE_VERSION}`), `${readmePath} must contain the pinned GitHub install command`)
   check(readme.includes(DSH_VERSION), `${readmePath} must state the sole ${DSH_VERSION} compatibility target`)
   check(readme.includes(CATALOG_URL), `${readmePath} must disclose the fixed catalog URL`)
 }