exomind 0.13.0 → 0.14.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "exomind",
-  "version": "0.13.0",
-  "description": "ExoMind 跨平台命令行客户端 — 通过 REST 与 ExoMind 知识库交互(ingest/query/search/review),替代 Windows 不可用的 MCP 客户端。",
+  "version": "0.14.0",
+  "description": "ExoMind 跨平台命令行客户端 — 通过 REST 与 ExoMind 知识飞轮交互(ingest/query/search/review),替代 Windows 不可用的 MCP 客户端。",
   "bin": {
     "exomind": "dist/cli.js"
   },

package/skill/claude/SKILL.md

@@ -20,12 +20,12 @@ If a command fails with "未登录", run `exomind login` first.
 
 ## 数据位置(重要 — 勿误报)
 
-**所有知识库数据都在服务器(youhuale.cn),不在本地。** CLI 通过 REST 上传/查询,**绝不写本地 wiki 目录**(不存在 `~/my-wiki` 之类)。本地仅以下状态文件:
+**所有知识飞轮数据都在服务器(youhuale.cn),不在本地。** CLI 通过 REST 上传/查询,**绝不写本地 wiki 目录**(不存在 `~/my-wiki` 之类)。本地仅以下状态文件:
 - `~/.exomind/config.json` — 凭证
 - `~/.exomind/cache/` — hook 的关键词/实体缓存(从服务器拉的副本)
-- `~/.exomind/manifest.json` — 目录增量摄入的内容哈希清单(去重用,非知识库本身)
+- `~/.exomind/manifest.json` — 目录增量摄入的内容哈希清单(去重用,非知识飞轮本身)
 
-摄入成功后输出 `✓ 已导入服务器知识库`。若要确认数据落地,用 `exomind search <关键词>` 复查。**不要向用户报告"已保存到 ~/my-wiki/entities/X.md"等本地路径——那是错的。**
+摄入成功后输出 `✓ 已导入服务器知识飞轮`。若要确认数据落地,用 `exomind search <关键词>` 复查。**不要向用户报告"已保存到 ~/my-wiki/entities/X.md"等本地路径——那是错的。**
 
 ## 性能注意(ingest / query / synthesize 较慢)
 
@@ -73,7 +73,7 @@ exomind search "关键词" --hybrid     # +向量语义:同义/跨语言/概念
 exomind search "关键词" --rerank     # +LLM 精排(最高准、慢;候选不多时)
 exomind entity "Redis"               # 实体详情 + 关系
 exomind relations "Redis" --depth 2  # 关联实体
-exomind stats                        # 知识库统计
+exomind stats                        # 知识飞轮统计
 exomind topics                       # 选题推荐
 exomind gaps                         # 知识缺口(驱动摄入)
 exomind daily                        # 每日摘要
@@ -86,7 +86,7 @@ exomind topics                              # 选题推荐(基于图谱密度)
 exomind draft new "选题" [--account <号>]    # 生成草稿 + 保存(LLM,1-3min;替代 gen_article.py)
 exomind draft list [--status <状态>]         # 草稿列表
 exomind draft show <id>                      # 看正文
-exomind draft publish <id>                   # 发布到知识库(入库,走 ingest)
+exomind draft publish <id>                   # 发布到知识飞轮(入库,走 ingest)
 exomind draft wechat <id> --account <号>     # 投递公众号草稿箱(真发,返回 media_id;后台仍需群发)
 ```
 链路:`topics` 选题 → `draft new` 生成 → `list/show` 审 → `publish` 入库 / `wechat` 发公众号。

package/skill/codex/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exomind
-description: Use ExoMind to save, ingest, import, search, query, and retrieve knowledge. Trigger when the user asks to remember, archive, save, ingest, import, search, query, or review knowledge, including shorthand commands such as "jdit", "存档", "记住这个", "保存到 ExoMind", "导入", and "查询知识库". Also use it when durable lessons, architectural decisions, investigation results, or root causes should be persisted. Treat these explicit save/import commands as authorization for that write. Do not silently write ordinary conversation to ExoMind. For a directory or multiple files, use one directory ingest command instead of reading or ingesting files individually.
+description: Use ExoMind to save, ingest, import, search, query, and retrieve knowledge. Trigger when the user asks to remember, archive, save, ingest, import, search, query, or review knowledge, including shorthand commands such as "jdit", "存档", "记住这个", "保存到 ExoMind", "导入", and "查询知识库"/"查询知识飞轮". Also use it when durable lessons, architectural decisions, investigation results, or root causes should be persisted. Treat these explicit save/import commands as authorization for that write. Do not silently write ordinary conversation to ExoMind. For a directory or multiple files, use one directory ingest command instead of reading or ingesting files individually.
 ---
 
 # ExoMind (Codex)
@@ -9,7 +9,7 @@ ExoMind is a remote knowledge base. Use it to persist durable knowledge and to r
 
 ## Authorization (important)
 
-- Explicit requests — `jdit`, `存档`, `记住这个`, `保存到 ExoMind`, `导入`, `写入知识库` — authorize THAT write. Proceed.
+- Explicit requests — `jdit`, `存档`, `记住这个`, `保存到 ExoMind`, `导入`, `写入知识库`/`写入知识飞轮` — authorize THAT write. Proceed.
 - Do NOT call a write/ingest for ordinary Q&A with no save intent. You may suggest saving if something is durable.
 - Preserve all Codex tool approvals, sandbox, and host security checks. A user's "jdit" is business authorization, not a reason to bypass host-level confirmations.
 - Read-only retrieval (query / search / entity / relations / stats) may be used whenever the user asks to recall, search, review, or check prior knowledge.