dsh-weknora-archive

中文 · English

把 DSH（DeepSeek Harness）会话增量归档进 WeKnora 知识库的 host 端插件。是官方只读插件 @wxg-prc-cpg/dsh-weknora（4 个检索工具）的写入侧互补。

功能

工具	说明
weknora_archive_session	归档某个项目的 DSH 会话：定位会话目录 → 解压 session.v3.jsonl.zstd → 提取对话 → 启发式总结（模板：主题/决策/产出/细节/遗留）→ 按文档标题去重后上传；知识库不存在时按项目名自动新建；首次归档附 00_项目总览.md；支持 dry_run 预览
weknora_archive_status	只读：列出本机会话项目目录与会话数，查看目标知识库内已归档文档与解析状态
weknora_archive_list_knowledge_bases	只读：列出该凭据可见的知识库
weknora_archive_create_knowledge_base	新建知识库（注意：新建库可能需在 WeKnora 端配置 embedding 模型，否则文档解析失败）

工具名前缀可通过 toolPrefix 配置（默认 weknora_archive）。工具描述中英双语。

安装

node "/Applications/DSH Desktop.app/Contents/Resources/app/node_modules/@deepseek-ai/dsh/lib/bin.js" \
  plugin --profile web add /path/to/dsh-weknora-archive

配置

走 DSH 官方插件配置机制：插件 bundle 自带 cordis.patch.yml，默认从环境变量读取（key 不落地、不入库）：

字段	环境变量	说明
baseUrl	WEKNORA_ARCHIVE_BASE_URL	WeKnora 部署地址（裸域名或 /api/v1 结尾均可），如 http://weknora.example.com
apiKey	WEKNORA_ARCHIVE_API_KEY	具备写入/摄取能力的 scoped API key
knowledgeBaseId	WEKNORA_ARCHIVE_KB_ID	可选：固定目标库；缺省按项目名自动匹配/新建
sessionsDir	WEKNORA_ARCHIVE_SESSIONS_DIR	可选：会话存储根目录；缺省自动探测 <harness>/sessions
maxSummaryChars	WEKNORA_ARCHIVE_MAX_SUMMARY_CHARS	单篇总结上限（默认 8000）

也可把 cordis.patch.yml 的 insert 行拷进 profile 自己的 cordis.patch.yml 直接填值（注意文件权限）。

隐私说明

• 会话数据只发往你自己配置的 WeKnora 实例，插件不经过任何第三方服务。
• API key 只用于请求头 X-API-Key，绝不写入日志、异常信息、工具结果或本文档；日志输出前统一走 redactConfig() 脱敏。
• 总结为启发式规则生成（无 LLM 参与），凭据类内容不收录完整值。

API 兼容性

认证头为 X-API-Key（非 Bearer），路由中横线风格：GET/POST /knowledge-bases、GET /knowledge-bases/{id}/knowledge、POST /knowledge（multipart 上传 Markdown）、POST /knowledge/{id}/reparse。以你的 WeKnora 实际 API 为准；若有出入只需调整 lib/client.js。

本地单测

npm test   # node test/mock.test.mjs，mock 数据 + mock 客户端，无需网络与凭证

已知边界

• 总结是启发式抽取，不是 LLM 精炼；追求质量可在归档前手工润色。
• 正在运行的会话文件可能解压失败，会被跳过（下次归档自动补上）。
• 新建库的 embedding 配置需在 WeKnora 端完成（PUT 接口会静默丢弃 embedding 字段）。

---

dsh-weknora-archive (English)

A DeepSeek Harness host plugin that incrementally archives DSH sessions into a WeKnora knowledge base — the write-side complement to the official read-only @wxg-prc-cpg/dsh-weknora plugin (4 retrieval tools).

Tools

Tool	Purpose
weknora_archive_session	Archive a project's sessions: locate session dirs → decompress session.v3.jsonl.zstd → extract conversation → heuristic summarize (topic / decisions / artifacts / hard details / leftovers) → dedupe by document title → upload. Auto-creates the knowledge base by project name when absent; adds a 00_项目总览.md overview on first run; dry_run supported.
weknora_archive_status	Read-only: list local session project dirs with counts, and documents already in a target KB with parse status.
weknora_archive_list_knowledge_bases	Read-only: list visible knowledge bases.
weknora_archive_create_knowledge_base	Create a KB (a fresh KB may need an embedding model configured on the WeKnora side).

Prefix is configurable via toolPrefix (default weknora_archive). Tool descriptions are bilingual (EN/中文).

Install

node "/Applications/DSH Desktop.app/Contents/Resources/app/node_modules/@deepseek-ai/dsh/lib/bin.js" \
  plugin --profile web add /path/to/dsh-weknora-archive

Configuration

Uses DSH's official plugin-config mechanism: the bundle ships a cordis.patch.yml that reads environment variables by default (no key hardcoded anywhere):

Field	Env var	Meaning
baseUrl	WEKNORA_ARCHIVE_BASE_URL	Your WeKnora deployment root or /api/v1 root (placeholder in this repo — set your own)
apiKey	WEKNORA_ARCHIVE_API_KEY	Scoped WeKnora API key with ingest capability
knowledgeBaseId	WEKNORA_ARCHIVE_KB_ID	Optional fixed target KB; otherwise matched/created per project
sessionsDir	WEKNORA_ARCHIVE_SESSIONS_DIR	Optional sessions root; auto-detected when empty
maxSummaryChars	WEKNORA_ARCHIVE_MAX_SUMMARY_CHARS	Per-summary cap (default 8000)

Alternatively copy the insert row into your profile's own cordis.patch.yml with literal values (mind file permissions).

Privacy

• Session data goes only to the WeKnora instance you configure — no third-party service involved.
• The API key is used solely in the X-API-Key header and is never logged, never embedded in errors, tool results, or this README; all log paths go through redactConfig().
• Summaries are produced by heuristic rules without any LLM, and credential-looking values are never recorded in full.

API compatibility

Auth is the X-API-Key header (not Bearer); kebab-case routes: GET/POST /knowledge-bases, GET /knowledge-bases/{id}/knowledge, POST /knowledge (multipart Markdown upload), POST /knowledge/{id}/reparse. Defer to your actual WeKnora API; if it differs, only lib/client.js needs changes.

Tests

npm test   # mock data + mock client, no network or credentials required

Known limits

• Summaries are heuristic extractions, not LLM-polished prose.
• A live session file may fail to decompress and is skipped (picked up on the next run).
• Embedding configuration for newly created KBs must be done on the WeKnora side.

License

MIT