dsh-baize-rules 0.1.2 → 0.1.4

package/README.md

@@ -1,5 +1,6 @@
 # dsh-baize-rules
 
+[![Listed on dsh-plugin.org](https://dsh-plugin.org/badges/listed.svg)](https://dsh-plugin.org/plugins/bvcvb/dsh-baize-rules)
 ![npm version](https://img.shields.io/npm/v/dsh-baize-rules)
 ![license](https://img.shields.io/npm/l/dsh-baize-rules)
 
@@ -32,7 +33,7 @@ The name comes from **Baize (白泽)** — a mythical beast said to "understand
 
 ```bash
 # Install from npm into the web profile (use the actual published version)
-dsh plugin --profile web add dsh-baize-rules@0.1.2
+dsh plugin --profile web add dsh-baize-rules@0.1.4
 pm2 restart dsh          # Reload when dsh is managed by pm2
 dsh --profile web
 ```
@@ -214,15 +215,25 @@ Change the pure functions in `src/rules.ts` (rendering) or `src/core.ts` (comman
 
 ## Publishing
 
+Releases are **single-source**: bump the version, push a `v*` tag, and GitHub Actions publishes to npm. **Don't run `npm publish` locally** — doing so alongside a tag would conflict, since a version can't be published twice.
+
 ```bash
-pnpm build && pnpm test      # Confirm build & tests pass before publishing
-npm publish --access public  # package.json already has publishConfig.access=public
+# 1. Bump the version: update `version` in package.json + the install example in both READMEs
+# 2. Verify locally
+pnpm build && pnpm test
+# 3. Commit and push the tag to trigger the CI publish job
+git add -A && git commit -m "release: vX.Y.Z"
+git tag vX.Y.Z && git push origin main --tags
 ```
 
-> After publishing, keep the `repository` field pointing to the public git repo so the community can browse and provide feedback.
+The `publish` job in `.github/workflows/ci.yml` runs on `v*` tags, needs the `test` job to pass, and uses the GitHub `NPM_TOKEN` secret.
 
 ---
 
+## Changelog
+
+See [CHANGELOG.md](./CHANGELOG.md).
+
 ## License
 
 [MIT](./LICENSE)

package/README.zh.md

@@ -1,5 +1,6 @@
 # dsh-baize-rules
 
+[![Listed on dsh-plugin.org](https://dsh-plugin.org/badges/listed.svg)](https://dsh-plugin.org/plugins/bvcvb/dsh-baize-rules)
 ![npm version](https://img.shields.io/npm/v/dsh-baize-rules)
 ![license](https://img.shields.io/npm/l/dsh-baize-rules)
 
@@ -32,7 +33,7 @@
 
 ```bash
 # 从 npm 安装到 web profile（版本以发布后的实际版本为准）
-dsh plugin --profile web add dsh-baize-rules@0.1.2
+dsh plugin --profile web add dsh-baize-rules@0.1.4
 pm2 restart dsh          # dsh 由 pm2 托管时重载生效
 dsh --profile web
 ```
@@ -214,12 +215,18 @@ pnpm typecheck             # npx tsc --noEmit
 
 ## 发布
 
+发布是**单一来源**：升版本号、推送 `v*` tag，由 GitHub Actions 自动发布到 npm；**请勿在本地手动 `npm publish`**——否则会跟 tag 触发的发布冲突（同一版本无法重复发布）。
+
 ```bash
-pnpm build && pnpm test      # 发布前确认构建与测试通过
-npm publish --access public  # package.json 已含 publishConfig.access=public
+# 1. 升版本：更新 package.json 的 version + 两份 README 里的安装示例
+# 2. 本地验证
+pnpm build && pnpm test
+# 3. 提交并推送 tag，触发 CI 发布
+git add -A && git commit -m "release: vX.Y.Z"
+git tag vX.Y.Z && git push origin main --tags
 ```
 
-> 发布后建议补上 `repository` 字段指向公开 git 仓库，供社区查阅与反馈。
+`.github/workflows/ci.yml` 的 `publish` job 在 `v*` tag 时运行，需 `test` 通过，并使用 GitHub `NPM_TOKEN` secret。
 
 ---
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-baize-rules",
   "description": "User-set session/global must-do and must-not requirements injected at conversation start (Baize).",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "license": "MIT",
   "type": "module",
   "engines": {
@@ -107,6 +107,10 @@
     "session",
     "baize",
     "must-do",
-    "must-not"
+    "must-not",
+    "deepseek-harness",
+    "agent-rules",
+    "system-reminder",
+    "developer"
   ]
 }