@wowyuarm/dsh-agent-team 0.1.6 → 0.1.8

package/README.md

@@ -11,6 +11,14 @@
 
 An opt-in plugin for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness): install it only where Team mode is needed; ordinary DSH sessions keep their normal preset roster.
 
+## Core ideas
+
+- **Agents are first-class team members, not just sessions.** Each member keeps its own memory, responsibility boundaries, and private space (memory, notes, and skills), while all agents collaborate in one shared project Workspace; multiple Workspaces manage multiple teams.
+- **Workspaces organize everything.** Different projects live in different Workspaces, each managing its own Agents and Channels.
+- **The Human routes Channels and responsibilities.** You decide who is in which channel and what they own; mentions route work to the right agent.
+- **Task Threads carry one line of progress.** Claims set the direction, Threads hold the context, and multiple session agents advance the same line of work without talking past each other — the facts of the work live in one Thread.
+- **No context babysitting.** Member sessions compact automatically past the threshold, with a pre-compaction hint to persist key conclusions first. Every member keeps its own memory and notes across sessions, so identity and knowledge survive session renewal.
+
 ## Preview
 
 Agent Team is opt-in: after installation the ordinary DSH page stays as-is, and Team mode is one additional entry in the sidebar footer.
@@ -27,15 +35,13 @@ A Task Thread keeps Claims, Agent handoffs, Human acceptance, and follow-up repl
 
 ![Completed Task Thread in the DSH Web UI: a Claim, Agent handoffs, Human acceptance activity, and the reply composer](assets/readme/task-thread.png)
 
-### No context babysitting
-
-Member sessions compact automatically once token usage passes the threshold, and each member gets a pre-compaction hint to persist its key conclusions first. Every member keeps its own memory and notes across sessions, so identity and knowledge survive session renewal.
+If this looks useful, a star on [GitHub](https://github.com/wowyuarm/dsh-agent-team) helps other DSH users find it.
 
 ## Quick start
 
 ### 1. Check DSH
 
-This release is certified against DSH `0.1.1-rc.2`. If `dsh` is not installed yet, start DSH with the official package:
+This release is certified against DSH `0.1.2-rc.1`. If `dsh` is not installed yet, start DSH with the official package:
 
 ```sh
 npx @deepseek-ai/dsh web
@@ -104,7 +110,7 @@ Published packages include built artifacts. A local checkout needs the adjacent
 
 ## Compatibility and limits
 
-- This release is certified against DSH `0.1.1-rc.2`.
+- This release is certified against DSH `0.1.2-rc.1`, and requires it: earlier DSH versions are not supported.
 - The bundle is single-host. It does not provide distributed consensus, Team direct messages, nested Threads, or semantic Direction deduplication.
 - The current DSH SQLite Session schema rejects databases from older DSH versions. Delete the old Session database and start fresh when upgrading across that boundary; this bundle does not migrate it.
 - Team-managed Agent Sessions use `danger-full-access`. Use them only in trusted Workspaces.

package/README.zh.md

@@ -11,6 +11,14 @@
 
 一个为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供的按需启用插件：只在需要 Team mode 的 profile 安装，普通 DSH Session 保持原有 preset roster。
 
+## 核心想法
+
+- **Agent 是 Team 的一等单位，不只是会话。** 每个 Agent 成员有自己的记忆与职责边界，以及私有空间——memory、notes 与 skills 单独维护；同时所有 Agent 在同一个共享项目 Workspace 下协作，多 Workspace 可管理多支 Team。
+- **Workspace 组织一切。** 不同项目放在不同 Workspace，各自管理自己的 Agents 与 Channels。
+- **Human 管 Channel 与职责。** 你决定谁在哪个频道、负责什么；@提及把工作路由到对的 Agent。
+- **Task Thread 串联推进。** 用 Task 认领方向、Thread 保持上下文，多个 Session Agent 围绕同一条工作线推进而不散乱。工作事实落在同一条 Thread 里，成员之间不会各说各的。
+- **无需操心上下文。** 成员会话超阈值自动压缩，压缩前提示成员先沉淀关键结论。每个成员的 memory 与 notes 跨会话保留，身份与知识不随会话续期丢失。
+
 ## 预览
 
 Agent Team 是按需启用的：安装后普通 DSH 页面保持原样，Team mode 只是侧栏底部多出的一个入口。
@@ -27,15 +35,13 @@ Task Thread 把 Claim、Agent 交接、Human 验收和后续回复保留在同
 
 ![DSH Web UI 中已完成的 Task Thread：含 Claim、Agent 交接、Human 验收活动和回复 composer](assets/readme/task-thread.png)
 
-### 无需操心上下文
-
-成员会话在 token 用量超过阈值后自动压缩，压缩前会提示成员先沉淀关键结论。每个成员的 memory 与 notes 跨会话保留，身份与知识不随会话续期丢失。
+如果觉得有用，欢迎在 [GitHub](https://github.com/wowyuarm/dsh-agent-team) 点个 star，帮更多 DSH 用户发现它。
 
 ## 快速开始
 
 ### 1. 检查 DSH
 
-当前版本已针对 DSH `0.1.1-rc.2` 完成认证。如果还没有安装 `dsh`，先使用官方 package 启动 DSH：
+当前版本已针对 DSH `0.1.2-rc.1` 完成认证。如果还没有安装 `dsh`，先使用官方 package 启动 DSH：
 
 ```sh
 npx @deepseek-ai/dsh web
@@ -104,7 +110,7 @@ dsh web
 
 ## 兼容性与限制
 
-- 当前版本已针对 DSH `0.1.1-rc.2` 完成认证。
+- 当前版本已针对 DSH `0.1.2-rc.1` 完成认证，并且要求该版本：更早的 DSH 版本不受支持。
 - Bundle 是单 Host，不提供分布式共识、Team direct message、嵌套 Thread 或 Direction 语义去重。
 - 当前 DSH SQLite Session schema 不接受旧版 DSH 的数据库。跨越该边界升级时，删除旧 Session 数据库并重新开始；本 bundle 不负责迁移。
 - Team 管理的 Agent Session 使用 `danger-full-access`。只在可信 Workspace 中使用。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wowyuarm/dsh-agent-team",
-  "version": "0.1.6",
+  "version": "0.1.8",
   "description": "A persistent agent team for long-running collaboration in DeepSeek Harness",
   "repository": {
     "type": "git",
@@ -38,7 +38,6 @@
     "client": {
       "platform": "web",
       "inject": [
-        "@deepseek-ai/dsh-client-runtime",
         "@deepseek-ai/dsh-api-remotes",
         "@deepseek-ai/dsh-client-ui-sidebar",
         "@deepseek-ai/dsh-client-ui-layout",
@@ -51,7 +50,7 @@
     }
   },
   "dependencies": {
-    "@deepseek-ai/dsh-storage-sqlite": ">=0.1.1-rc.2 <0.2.0",
+    "@deepseek-ai/dsh-storage-sqlite": ">=0.1.2-rc.1 <0.2.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {
@@ -122,45 +121,48 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-agent": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-agent-default-model": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-agent-presets": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-agent-tool-presentation": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-api-remotes": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-brand": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-locale": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-runtime": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-input-trigger": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-primitives": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-settings-general": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-sidebar": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-slots": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-workspace": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-command-compact": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-compaction": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-home-paths": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-invariants": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-llm": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-sandbox-policy": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-scope": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-session": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-session-persistence": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-storage-domain": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-token-meter": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-bash": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-fs": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-fs-search": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-jobs": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-pwsh": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-skill": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-todo": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tool-web": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-tools": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-typert-protocol": ">=0.1.1-rc.2 <0.2.0",
-    "@deepseek-ai/dsh-workspace": ">=0.1.1-rc.2 <0.2.0",
+    "@deepseek-ai/dsh-agent": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-agent-default-model": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-agent-presets": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-agent-tool-presentation": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-api-remotes": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-api-session-controller": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-api-workspace-controller": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-brand": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-locale": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-input-trigger": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-primitives": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-renderer": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-settings-general": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-sidebar": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-slots": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-workspace": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-command-compact": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-compaction": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-home-paths": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-invariants": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-llm": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-sandbox-policy": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-scope": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-session": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-session-persistence": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-skill": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-storage-domain": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-token-meter": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-bash": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-fs": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-fs-search": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-jobs": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-pwsh": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-skill": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-todo": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-web": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tools": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-typert-protocol": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-workspace": ">=0.1.2-rc.1 <0.2.0",
     "react": "^18.2.0"
   },
   "keywords": [

package/packages/agent-team/README.md

@@ -18,6 +18,8 @@ Every operation record carries a positive global sequence, unique operation and
 
 Member creation commits one stable Member/session/Workspace/preset/private-memory identity before unpublished Agent setup. Setup mounts the selected preset and validates its marked `team_message` plus all five Team tools before publication. Failure leaves only that Member unavailable. Suspend waits for the owned `AgentHandle` to stop; resume and Host remount restore the exact persisted session.
 
+Archival is the reversible third state between suspend and remove, for Members and Channels alike. `archiveMember` commits `team/member-archived`, disposes the live session while keeping private memory and the Session log on disk, archives the Session from grouping surfaces, and releases the Member's active Claims with public `claims_released` Activities plus Attention/marker cleanup. `archiveChannel` commits `team/channel-archived` with the same release shape across every owner on the Channel's Threads. Memberships survive both forms — hidden state, not departure. Archived entities are gone from every Team API surface: projections, ref resolution (their Task refs stop resolving, so message bodies render plain text), and ref-addressed reads (`readThread`/`threadHistory`/`threadObservations`/`listClaims` reject with an explicit archived error) — while the facts stay complete in the ledger for replay and a future restore; that boundary is the archival-vs-remove divide. Removal from archived stays available as the data hygiene path; there is no restore entry point yet (mirroring archived dsh sessions).
+
 Members optionally carry durable capability intent (`capabilities.tools.allow`, `capabilities.skills.allow`). It flows verbatim through every lifecycle operation, replays unchanged after Host restart, and commits without known-name validation so Harness upgrades can never break old ledgers; divergence from known names surfaces at activation as derived, non-persisted `capabilityWarnings`. `tools.allow` is a deliberate interface reservation (no UI write path today) that future Runtime Revision manifest orchestration depends on. Edits follow absent-clears semantics like `model`: a caller that does not manage capabilities must echo the stored value back or its edit clears the override.
 
 Activation applies `tools.allow` as a scoped restriction over the composed preset surface (mount → restrict → validate) with the five Team tools force-unioned over the configured list; unknown names drop with a warning rather than failing the Member. A live allow-list edit swaps the restriction at a turn boundary in the same Session — idle Members apply immediately, and an edit racing a running turn waits for it while later lifecycle operations queue behind the wait. Restriction failures isolate to that Member's activation diagnostic.

package/packages/agent-team/README.zh.md

@@ -18,6 +18,8 @@ Service 使用 `ctx.storageDomain`、`ctx.workspaceRegistry`、`ctx.agents`、`c
 
 创建 Member 时，先提交稳定的 Member/session/Workspace/preset/private-memory 身份，再执行 unpublished Agent setup。Setup 挂载指定 preset，并在发布前检查带 marker 的 `team_message` 和全部五个 Team tools。失败只把该 Member 标为 unavailable。Suspend 等待所属 `AgentHandle` 完全停止；resume 和 Host remount 恢复同一个持久 session。
 
+归档（archival）是介于 suspend 与 remove 之间的可逆第三态，Member 与 Channel 通用。`archiveMember` 提交 `team/member-archived`，dispose 活跃 session（私有记忆与 Session log 留在磁盘），把 Session 从分组面归档，并释放该 Member 的活跃 Claim（公开 `claims_released` Activity + Attention/marker 清理）。`archiveChannel` 提交 `team/channel-archived`，对该频道全部 Threads 上所有 owner 做同样的释放。两种归档都保留 Memberships——是隐藏而非离开。归档实体在所有 Team API 面上"默认不存在"：投影、ref 解析（其 Task ref 不再解析，消息正文渲染为纯文本）、按 ref 的读取（`readThread`/`threadHistory`/`threadObservations`/`listClaims` 以明确的 archived 错误拒绝）——而事实在 ledger 中完整保留，供重放与未来恢复；这条边界正是归档与 remove 的分界。从归档态 remove 仍可用（数据卫生路径）；本轮有意不提供恢复入口（对齐 dsh session 归档现状）。
+
 Member 可携带持久能力意图（`capabilities.tools.allow`、`capabilities.skills.allow`）。它随全部 lifecycle operation 原样流转，Host restart 后原样重放，commit 时不做已知名校验（Harness 升级不会破坏旧 ledger）；与已知名的偏差在 activation 时派生为不持久化的 `capabilityWarnings`。`tools.allow` 是有意的接口预留（当前无 UI 写入路径），供后续 Runtime Revision manifest 编排依赖。编辑语义与 `model` 一致（absent 即清除）：不管理 capabilities 的调用方必须回传已存储的值，否则其编辑会清掉该覆盖。
 
 Activation 把 `tools.allow` 作为 scoped restriction 应用在已组合的 preset 面上（mount → restrict → validate），五个 Team tools 在配置之上强制并集；未知名 drop + warning，不使 Member 失败。对 live Member 的 allow-list 编辑在 turn 边界同 Session 换装 restriction——idle 立即生效，与 running turn 竞争的编辑等待其结束，后续 lifecycle 操作在该等待之后排队。restriction 失败只隔离为该 Member 的 activation diagnostic。

package/packages/agent-team/core-skills/member-skill-manager/SKILL.md

@@ -7,6 +7,8 @@ description: Create, install, revise, or retire this Member's private skills, in
 
 A skill preserves a reusable way of working. It is not a memory, a personal preference, or a record of one event.
 
+Skills are private to this Member — no other human or agent can read this directory. When a Team message or your session output needs the method, restate the relevant content there; citing a skill by name does not transfer it to anyone.
+
 ## Decide
 
 Create or revise a skill when the method has been demonstrated in real work and will make later work clearer or more reliable. Keep one-off work, changing facts, and personal continuity in this Member's notes and memory index instead.