@wowyuarm/dsh-agent-team 0.1.14-alpha.1 → 0.1.14

package/README.md

@@ -1,4 +1,4 @@
-# DeepSeek Harness Agent Team
+# dsh-agent-team — Persistent Agent Teams for DeepSeek Harness
 
 [English](README.md) | [简体中文](README.zh.md)
 
@@ -7,7 +7,7 @@
 [![Release](https://img.shields.io/github/v/release/wowyuarm/dsh-agent-team?include_prereleases&style=flat-square)](https://github.com/wowyuarm/dsh-agent-team/releases)
 [![Listed on Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com/p/wowyuarm/dsh-agent-team/)
 
-**dsh-agent-team** gives DeepSeek Harness a persistent agent team for long-running collaboration: agents are durable identities for their sessions, keeping memory and responsibilities across them; Workspaces organize agents and sessions per project; Channels carry responsibilities; Task Threads chain session agents into one line of progress.
+**dsh-agent-team** gives DeepSeek Harness agents that don't reset. Each agent is a durable Member with its own memory, notes, and skills — the Member you set up last week is still the same one this week, after its session ended, its context rolled over, or DSH restarted. You set the direction; Workspaces organize teams per project, Channels route responsibilities, and Task Threads keep one line of progress.
 
 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.
 
@@ -41,7 +41,7 @@ If this looks useful, a star on [GitHub](https://github.com/wowyuarm/dsh-agent-t
 
 ### 1. Check DSH
 
-This release is certified against DSH `0.1.6-alpha.1`. If `dsh` is not installed yet, start DSH with the official package:
+This release is certified against DSH `0.1.5-rc.1`. If `dsh` is not installed yet, start DSH with the official package:
 
 ```sh
 npx @deepseek-ai/dsh web
@@ -125,6 +125,8 @@ Published packages include built artifacts. A local checkout needs the adjacent
 
 ## Development
 
+Contributing: [`CONTRIBUTING.md`](CONTRIBUTING.md) — how to propose a change, what CI runs, and what a pull request should contain.
+
 Read [`docs/README.md`](docs/README.md) for the maintained documentation index. The usual checks are:
 
 ```sh

package/README.zh.md

@@ -1,4 +1,4 @@
-# DeepSeek Harness Agent Team
+# dsh-agent-team — DeepSeek Harness 持久 Agent 团队
 
 [English](README.md) | 简体中文
 
@@ -7,7 +7,7 @@
 [![Release](https://img.shields.io/github/v/release/wowyuarm/dsh-agent-team?include_prereleases&style=flat-square)](https://github.com/wowyuarm/dsh-agent-team/releases)
 [![Listed on Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com/p/wowyuarm/dsh-agent-team/)
 
-**dsh-agent-team** 给 DSH 一个可长期协作的持久 Agent 团队：Agent 是 session 的持久身份，跨会话保持记忆与职责；Workspace 按项目组织 agents 与 sessions；Channel 承载职责分派；Task Thread 把多个 session agent 串成一条推进线。
+**dsh-agent-team** 给 DeepSeek Harness 一批不会归零的 Agent。每个 Agent 是持久的 Member，带着自己的 memory、notes 与 skills——上周你配好的成员，这周还是它，哪怕会话结束、上下文 rollover 或 DSH 重启过。方向由你定；Workspace 按项目组织团队，Channel 路由职责，Task Thread 保持一条推进线。
 
 一个为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供的按需启用插件：只在需要 Team mode 的 profile 安装，普通 DSH Session 保持原有 preset roster。
 
@@ -41,7 +41,7 @@ Task Thread 把 Claim、Agent 交接、Human 验收和后续回复保留在同
 
 ### 1. 检查 DSH
 
-当前版本已针对 DSH `0.1.6-alpha.1` 完成认证。如果还没有安装 `dsh`，先使用官方 package 启动 DSH：
+当前版本已针对 DSH `0.1.5-rc.1` 完成认证。如果还没有安装 `dsh`，先使用官方 package 启动 DSH：
 
 ```sh
 npx @deepseek-ai/dsh web
@@ -125,6 +125,8 @@ dsh web
 
 ## 开发
 
+贡献指南：[`CONTRIBUTING.zh.md`](CONTRIBUTING.zh.md)——怎么提改动、CI 会跑什么、PR 里要写什么。
+
 维护中的文档入口是 [`docs/README.zh.md`](docs/README.zh.md)。常用检查命令：
 
 ```sh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wowyuarm/dsh-agent-team",
-  "version": "0.1.14-alpha.1",
+  "version": "0.1.14",
   "license": "MIT",
   "description": "A persistent agent team for long-running collaboration in DeepSeek Harness",
   "repository": {
@@ -27,7 +27,8 @@
     "check:docs": "node scripts/check-docs.mjs",
     "check:core-skills": "node scripts/check-core-skills.mjs",
     "check:boundaries": "node scripts/check-package-boundaries.mjs",
-    "test": "npm run generate:typert && npm run check:docs && npm run check:core-skills && npm run check:boundaries && vitest run",
+    "check:versions": "node scripts/check-version-consistency.mjs",
+    "test": "npm run generate:typert && npm run check:docs && npm run check:core-skills && npm run check:boundaries && npm run check:versions && vitest run",
     "test:browser": "npm run build && node scripts/run-browser-test.mjs",
     "preview": "node scripts/check-preview-credentials.mjs && npm run build && node scripts/run-preview.mjs",
     "preview:ui": "npm run build && node scripts/run-ui-preview.mjs",
@@ -58,6 +59,7 @@
     }
   },
   "dependencies": {
+    "@wowyuarm/dsh-context-continuity": "^0.1.3",
     "zod": "^4.4.3"
   },
   "devDependencies": {
@@ -145,49 +147,49 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-agent": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-agent-default-model": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-agent-presets": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-agent-tool-presentation": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-api-remotes": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-api-session-controller": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-api-workspace-controller": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-brand": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-locale": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-input-trigger": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-primitives": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-renderer": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-settings-general": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-sidebar": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-slots": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-client-ui-workspace": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-command-compact": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-compaction": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-home-paths": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-invariants": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-llm": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-sandbox-policy": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-scope": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-session": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-session-format-catalog": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-session-persistence": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-skill": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-storage-domain": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-token-meter": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-bash": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-fs": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-fs-search": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-jobs": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-pwsh": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-skill": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-todo": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tool-web": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-tools": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-typert-protocol": ">=0.1.6-alpha.1 <0.1.7",
-    "@deepseek-ai/dsh-workspace": ">=0.1.6-alpha.1 <0.1.7",
+    "@deepseek-ai/dsh-agent": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-agent-default-model": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-agent-presets": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-agent-tool-presentation": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-api-remotes": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-api-session-controller": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-api-workspace-controller": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-brand": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-locale": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-input-trigger": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-primitives": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-renderer": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-settings-general": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-sidebar": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-slots": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-client-ui-workspace": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-command-compact": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-compaction": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-home-paths": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-invariants": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-llm": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-sandbox-policy": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-scope": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-session": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-session-format-catalog": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-session-persistence": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-skill": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-storage-domain": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-token-meter": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-bash": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-fs": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-fs-search": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-jobs": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-pwsh": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-skill": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-todo": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tool-web": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-tools": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-typert-protocol": ">=0.1.5-rc.1 <0.1.6",
+    "@deepseek-ai/dsh-workspace": ">=0.1.5-rc.1 <0.1.6",
     "react": "^18.2.0"
   },
   "keywords": [

package/packages/agent-team/README.md

@@ -28,7 +28,7 @@ Activation applies `tools.allow` as a scoped restriction over the composed prese
 
 Skills are Member-private: the preset has no shared skill-filesystem row, and the Host registers one provider per Member that scans exactly the plugin's bundled read-only core skills (`packages/agent-team/core-skills/` — the `member-skill-manager` meta skill that owns all skill craft guidance) plus that Member's writable `skills/` directory under its private memory path (default roots excluded). Installing is writing into the Member's own directory — directory form `skills/<name>/SKILL.md` with optional references and scripts, or a flat `.md` — and there is deliberately no upload Remote. The persona itself only states the private-space physical facts; the meta skill's description routes skill-management work to it. `skills.allow` filters the catalog through a live selection ref swapped at the same turn boundary; the filesystem watcher feeds discovery after a self-install.
 
-Every team-managed session records `danger-full-access`. Project cwd remains the Workspace path, while private memory lives under `$DSH_HOME/agent-team/members/<memberId>/`. An untitled Member session is named with its handle through the session-title service, so the ordinary Session list shows the Member identity; an explicit rename or any earlier title always wins. The isolated `team-member` preset also provides coding tools including model-facing web search, Workspace instruction discovery, and Team protocol guidance. The host owns the shared Web service and provider; the preset mounts only the model-facing web tool. Its lowercase `memory.md` is a bounded 8 KiB reference index, injected only for that Member when its content changes; `notes/` stays on-demand through filesystem tools. Over-budget indexes receive a maintenance warning, not silent truncation. Ordinary sessions and forks receive no Team identity or private-memory context. At Host startup every enabled Member's private memory is provisioned and an `inactive` Member's is removed with its Session archived; directories the replayed ledger does not reference are never pruned, so leftovers from a discarded ledger stay on disk for the operator. Both that removal and the activation-time migration of a pre-fix colon directory act only on paths inside the running process's own `$DSH_HOME/agent-team/members/`: a recorded path naming a different DSH home (an isolated test home, a second instance) is refused with a warning rather than renamed or deleted, because acting on it would take a Member's real private memory out of its home.
+Every team-managed session records `danger-full-access`. Project cwd remains the Workspace path, while private memory lives under `$DSH_HOME/agent-team/members/<memberId>/`. An untitled Member session is named with its handle through the session-title service, so the ordinary Session list shows the Member identity; an explicit rename or any earlier title always wins. The isolated `team-member` preset also provides coding tools including model-facing web search, Workspace instruction discovery, and Team protocol guidance. The host owns the shared Web service and provider; the preset mounts only the model-facing web tool. Its lowercase `memory.md` is a bounded 16 KiB reference index, injected only for that Member when its content changes, with its current usage (`X.X KiB / 16 KiB`) stated in the block; `notes/` stays on-demand through filesystem tools. Over-budget indexes receive a maintenance warning, not silent truncation. Ordinary sessions and forks receive no Team identity or private-memory context. At Host startup every enabled Member's private memory is provisioned and an `inactive` Member's is removed with its Session archived; directories the replayed ledger does not reference are never pruned, so leftovers from a discarded ledger stay on disk for the operator. Both that removal and the activation-time migration of a pre-fix colon directory act only on paths inside the running process's own `$DSH_HOME/agent-team/members/`: a recorded path naming a different DSH home (an isolated test home, a second instance) is refused with a warning rather than renamed or deleted, because acting on it would take a Member's real private memory out of its home.
 
 Adding a Member to a Channel grants future read/send/claim authority but injects no historical Messages into the member session. Every top-level Message creates a Thread; new Client/tool starts explicitly choose taskless while released-client omission remains taskful, and a Human can later promote a taskless Thread by atomically adding its Task overlay and a structured `promote` Task activity. Thread Attention starts when a Thread is created, a Claim is created, a member follows, a top-level Message mentions them, or a Human confirms an invitation. Ordinary unread is derived from Attention; structured mentions create durable direct markers, while terminal Task changes retain sparse Activity markers for affected followers after Attention ends. `team_inbox` and Thread reads are Host projections, not Session inbox contents. A direct mention context includes its Message body and source; Task/Claim changes — including promotion — include concise transition facts; ordinary unread carries a body-free Thread-first route. Pending hints are coalesced, ignored hints do not loop, and resume/error recovery derives a new hint from durable unread state. For recoverable service failures, the Host wakes a Member after each of the first two consecutive `agent/error` occurrences, then leaves the third failure for the operator; only a clean turn resets that run.
 

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

@@ -28,7 +28,7 @@ Activation 把 `tools.allow` 作为 scoped restriction 应用在已组合的 pre
 
 Skills 是 Member 私有的：preset 不带共享 skill-filesystem row，Host 为每个 Member 注册一个 provider，只扫插件内置的只读 core skills（`packages/agent-team/core-skills/`——`member-skill-manager` meta skill，全部 skill 写作/安装/credentials 引导都在它里面）加该 Member 可写的私有 `skills/` 目录（排除默认 roots）。安装就是往自己目录写——目录形态 `skills/<name>/SKILL.md` + 可选 references/scripts，或平铺 `.md`——有意不提供上传 Remote。persona 只陈述私有空间物理事实，meta skill 的 description 负责"涉及 skill 管理工作时先读我"。`skills.allow` 通过同一 turn 边界换装的 live selection ref 过滤 catalog；自装后的发现由 filesystem watcher 驱动。
 
-每个 Team 管理的 session 都会持久写入 `danger-full-access`。项目 cwd 仍是 Workspace 路径，私有记忆位于 `$DSH_HOME/agent-team/members/<memberId>/`。没有标题的 Member session 会通过 session-title service 以 handle 命名，普通 Session 列表因此直接显示 Member 身份；显式重命名或任何既有标题始终优先。隔离的 `team-member` preset 还提供 coding 工具、面向模型的 Web 搜索、Workspace instruction discovery 和 Team protocol guidance。共享的 Web service 与 provider 仍由 Host 持有；preset 只挂载面向模型的 Web tool。小写 `memory.md` 是有界的 8 KiB 参考索引，只有该 Member 的内容变化时才注入；`notes/` 只通过 filesystem tools 按需读取。超预算索引只产生维护警告，不静默截断。普通 session 和 fork 不获得 Team 身份或私有记忆上下文。Host 启动时会为每个 enabled Member 准备其私有记忆，并对 `inactive` Member 归档其 Session 后删除其私有记忆；重放 ledger 不引用的目录一律不清理，被丢弃 ledger 的遗留物留在磁盘上交给操作者处置。这项删除与 activation 时对旧式 colon 目录的迁移都只作用于当前进程自己的 `$DSH_HOME/agent-team/members/` 之内的路径：记录里指向另一个 DSH home（隔离测试 home、第二个实例）的路径会被拒绝并告警，既不改名也不删除——对它动手等于把 Member 的真实私有记忆搬出它自己的 home。
+每个 Team 管理的 session 都会持久写入 `danger-full-access`。项目 cwd 仍是 Workspace 路径，私有记忆位于 `$DSH_HOME/agent-team/members/<memberId>/`。没有标题的 Member session 会通过 session-title service 以 handle 命名，普通 Session 列表因此直接显示 Member 身份；显式重命名或任何既有标题始终优先。隔离的 `team-member` preset 还提供 coding 工具、面向模型的 Web 搜索、Workspace instruction discovery 和 Team protocol guidance。共享的 Web service 与 provider 仍由 Host 持有；preset 只挂载面向模型的 Web tool。小写 `memory.md` 是有界的 16 KiB 参考索引，只有该 Member 的内容变化时才注入，注入块注明当前用量（已用 X.X KiB / 16 KiB）；`notes/` 只通过 filesystem tools 按需读取。超预算索引只产生维护警告，不静默截断。普通 session 和 fork 不获得 Team 身份或私有记忆上下文。Host 启动时会为每个 enabled Member 准备其私有记忆，并对 `inactive` Member 归档其 Session 后删除其私有记忆；重放 ledger 不引用的目录一律不清理，被丢弃 ledger 的遗留物留在磁盘上交给操作者处置。这项删除与 activation 时对旧式 colon 目录的迁移都只作用于当前进程自己的 `$DSH_HOME/agent-team/members/` 之内的路径：记录里指向另一个 DSH home（隔离测试 home、第二个实例）的路径会被拒绝并告警，既不改名也不删除——对它动手等于把 Member 的真实私有记忆搬出它自己的 home。
 
 把 Member 加入 Channel 只授予之后的 read/send/claim authority，不向 Member session 注入历史 Message。每条顶层 Message 都创建 Thread；新 Client/tool 显式选择 taskless，released Client 省略意图时仍保持 taskful；Human 可之后 promotion taskless Thread，原子附加 Task overlay 与结构化 `promote` Task activity。创建 Thread、创建 Claim、显式 follow、顶层消息 mention 到、或 Human 确认邀请会开始 Thread Attention。普通未读从 Attention 派生，structured mention 形成持久 direct marker；终止 Task 的状态变化会为受影响关注者保留稀疏 Activity marker，即使 Attention 已结束仍可读取。`team_inbox` 和 Thread read 是 Host projection，不是 Session inbox 内容。Direct mention context 包含消息正文和来源，Task/Claim 变化（含 promotion）包含简短状态事实，普通未读提供无正文的 Thread-first 路由。提示会合并，忽略提示不会形成循环，resume/runtime error recovery 会从持久未读状态重新判断是否提示。对于可恢复的服务错误，Host 会在连续 `agent/error` occurrence 的前两次后唤醒 Member；第 3 次错误则交给 operator，只有 clean turn 才会重置这段连续错误。
 

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

@@ -0,0 +1,30 @@
+---
+name: member-memory-manager
+description: Maintain this Member's private memory — what earns a line in the memory.md index, what belongs in a notes/ file instead, how to compact an index past half its budget, and when to demote knowledge that no longer earns a line. Read this skill when the injected memory block shows a maintenance warning, when the index approaches its budget, or before adding or renaming a note.
+---
+
+# Member Memory Manager
+
+`memory.md` is a routing index, not a store, and its budget is real: the injected block states current usage, and past 16 KiB the index is not injected at all — the Member loses its own continuity. Notes are never injected; they are read on demand, so the index must stay small enough to be resident and precise enough to route.
+
+## Three tiers
+
+- **T0 `memory.md` (always injected)** — identity and role, durable rules that must bind every step, what is currently in hand, and one routing line per topic cluster. Target well under 8 KiB; treat 16 KiB as the hard ceiling.
+- **T1 `notes/<cluster>/README.md` (read on demand)** — one line per note in that cluster. What T0 routes to is the cluster count (3–6), not the note count.
+- **T2 `notes/<name>.md` (read on demand)** — one concept per file; update the existing file instead of writing a near-duplicate, and keep evidence, numbers, and commands here rather than in T0.
+
+Screenshots, logs, and generated artifacts belong under `notes/assets/` and earn no index line anywhere.
+
+## What earns a line
+
+Apply one test before writing: would my future self make a wrong decision without this line? If not, it does not belong in T0. Team facts the ledger already owns, event logs, one-off task detail, credentials, and copies of a note's body never qualify.
+
+## Lifecycle
+
+- **Compact as you write.** Past roughly half the budget, merge and drop while adding rather than appending; naming a cluster in T1 is cheaper than naming its notes in T0.
+- **Demote, do not delete.** A rule that stopped binding moves down a tier (T0 to a note, T1 to `notes/archive/`); archived knowledge stays readable and is never silently lost.
+- **Separate rolling from settled.** "In hand" is overwritten as work moves; settled knowledge is compacted in place, and that section never accumulates history.
+
+## Check after reorganizing
+
+Re-read `memory.md` once: under budget, one line per cluster, every routing line resolving to a file that exists, and nothing that must bind every step living only in a note. The injected block reports the current size, so a later injection shows whether the rewrite took.

package/packages/agent-team/lib/context-continuity-host.js

@@ -0,0 +1,91 @@
+/**
+ * The Agent Team's binding of the context-continuity engine: how one Member
+ * resolves to its live Agent and back, how a Member Session's fold state is
+ * read, how a prepared generation swap runs in the Member lifecycle, and the
+ * two domain dimensions the engine refuses to own (which queued messages are
+ * Team notices, and how a rollover's durable identity is named).
+ *
+ * The engine owns every mechanic this module does not state: the idle-boundary
+ * swap, carried input, checkpoint continuations, crash repair. Team owns the
+ * Member vocabulary and the ledger-backed lifecycle behind
+ * {@link TeamContextContinuityOptions.executeTransition}.
+ *
+ * The projection state this host hands the coordinator is the engine's own
+ * (`ContextProjectionState`), read from the unit `context-projection.ts`
+ * registers once per Host — one state shape, one fold, no translation.
+ * @module @wowyuarm/dsh-agent-team/context-continuity-host
+ */
+import { createHash } from 'node:crypto';
+import { ContextContinuityCoordinator, ContextMessageCodec, } from '@wowyuarm/dsh-context-continuity';
+import { SessionId as SessionIdBrand } from '@deepseek-ai/dsh-session';
+import { AGENT_TEAM_PLUGIN_ID } from "./context-source.js";
+/**
+ * The one writer of context-continuity messages for Team. Section names are
+ * the engine's fixed vocabulary; only the plugin identity and the two
+ * subject-facing prose lines are Team's, and both are frozen by history —
+ * durable logs written by earlier generations are read back through this same
+ * identity, so `handoffIntro` and `handoffVerifyNote` reproduce them byte for
+ * byte.
+ */
+export const TEAM_CONTEXT_CODEC = new ContextMessageCodec({
+    pluginId: AGENT_TEAM_PLUGIN_ID,
+    handoffIntro: 'Context handoff: you are continuing as the same Team Member in a fresh private context.',
+    handoffVerifyNote: 'Your handoff from the previous context follows. Verify external state before relying on it; a context change never rolls back files, processes, Team facts, or remote side effects.',
+});
+/**
+ * Team's `ContextContinuityHost`. Every method is a straight delegation except
+ * the three that decide domain meaning: the durable rollover identity, which
+ * queued messages are rederived Team notices, and the projection bridge.
+ */
+export class TeamContextContinuityHost {
+    options;
+    constructor(options) {
+        this.options = options;
+    }
+    agentForSubject(memberId) {
+        return this.options.agentForMember(memberId);
+    }
+    subjectForAgent(agent) {
+        const member = this.options.memberForAgent(agent);
+        if (member === undefined)
+            return undefined;
+        return { id: member.memberId, sessionId: member.sessionId };
+    }
+    projectionForSubject(memberId, sessionId) {
+        return this.options.projectionForMember(memberId, sessionId);
+    }
+    executeTransition(memberId, plan) {
+        return this.options.executeTransition(memberId, plan);
+    }
+    /**
+     * Rollover identity, unchanged from the in-repo coordinator: stable key over
+     * the previous Session and the successful tool call, JSON-encoded so no
+     * delimiter can alias across the two unconstrained fields, then hashed to a
+     * fixed-length digest. Both names are durable — in-flight recovery converges
+     * on `agent-team-rollover-<digest>`, and the ledger records the request id.
+     */
+    rolloverIdentity(previousSessionId, toolCallId) {
+        const stableKey = createHash('sha256').update(JSON.stringify([previousSessionId, toolCallId])).digest('hex');
+        return {
+            newSessionId: SessionIdBrand(`agent-team-rollover-${stableKey}`),
+            requestId: `agent-team:rollover:${stableKey}`,
+        };
+    }
+    /**
+     * A queued message the successor generation rederives from ledger facts: any
+     * Team-attributed message. The engine excludes the handoff and continuation
+     * envelopes before consulting this, so the two are ordinary delivered
+     * context the next generation keeps.
+     */
+    isEphemeralNotice(message) {
+        const source = message.source;
+        return source.kind === 'plugin' && source.plugin === AGENT_TEAM_PLUGIN_ID;
+    }
+    log(message) {
+        this.options.log(message);
+    }
+}
+/** Build the engine coordinator over Team's Member lifecycle. */
+export function createTeamContextManagement(options) {
+    return new ContextContinuityCoordinator(new TeamContextContinuityHost(options), TEAM_CONTEXT_CODEC);
+}