@wowyuarm/dsh-agent-team 0.1.5 → 0.1.7

package/README.md

@@ -7,12 +7,26 @@
 [![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** helps a human manage tasks in an orderly way and use agents as true collaborators: agents are persistent identities for their sessions; 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 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.
 
 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.
+
+![Ordinary DSH Web UI with the Team entry highlighted in the sidebar footer](assets/readme/dsh-entry.png)
+
+Entering Team mode shows Channels, managed Agents, and the collaboration timeline:
+
 ![Team mode in the DSH Web UI: Channels and seven online Agents in the sidebar; the Main Channel shows Task references and the composer’s task switch](assets/readme/team-mode.png)
 
 ### Task Threads
@@ -21,11 +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)
 
+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
@@ -94,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.
@@ -117,6 +133,10 @@ npm pack --dry-run
 
 Architecture and the collaboration contract are documented in [`docs/architecture.md`](docs/architecture.md) and [`docs/team-collaboration.md`](docs/team-collaboration.md).
 
+## Acknowledgments
+
+The collaboration shape of dsh-agent-team — named agent members, Channels, Task Threads, @mention routing, and per-member memory — originates from and borrows several design ideas from [Raft](https://raft.build/). Thank you for the work.
+
 ## License
 
 [MIT](LICENSE)

package/README.zh.md

@@ -7,12 +7,26 @@
 [![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** 帮助 human 有序管理任务、把 agents 用成真正的协作者：Agent 是 session 的持久身份；Workspace 按项目组织 agents 与 sessions；Channel 承载职责分派；Task Thread 把多个 session agent 串成一条推进线。
+**dsh-agent-team** 给 DSH 一个可长期协作的持久 Agent 团队：Agent 是 session 的持久身份，跨会话保持记忆与职责；Workspace 按项目组织 agents 与 sessions；Channel 承载职责分派；Task Thread 把多个 session agent 串成一条推进线。
 
 一个为 [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 只是侧栏底部多出的一个入口。
+
+![普通 DSH Web UI，侧栏底部高亮 Team 入口](assets/readme/dsh-entry.png)
+
+进入 Team mode 后是频道、受管 Agent 与协作时间线：
+
 ![DSH Web UI 中的 Team mode：侧边栏展示频道与 7 位在线 Agent；Main 频道含 Task 引用和 composer 的作为任务开关](assets/readme/team-mode.png)
 
 ### Task Thread
@@ -21,11 +35,13 @@ Task Thread 把 Claim、Agent 交接、Human 验收和后续回复保留在同
 
 ![DSH Web UI 中已完成的 Task Thread：含 Claim、Agent 交接、Human 验收活动和回复 composer](assets/readme/task-thread.png)
 
+如果觉得有用，欢迎在 [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
@@ -94,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 中使用。
@@ -117,6 +133,10 @@ npm pack --dry-run
 
 架构和协作协议见 [`docs/architecture.zh.md`](docs/architecture.zh.md) 与 [`docs/team-collaboration.zh.md`](docs/team-collaboration.zh.md)。
 
+## 致谢
+
+dsh-agent-team 的协作形态——具名 Agent 成员、Channel、Task Thread、@mention 路由与成员级记忆——来源于 [Raft](https://raft.build/) 并借鉴了它的若干设计。感谢他们的工作。
+
 ## 许可证
 
 [MIT](LICENSE)

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@wowyuarm/dsh-agent-team",
-  "version": "0.1.5",
-  "description": "Help humans organize tasks and let agents collaborate - a Team plugin for DeepSeek Harness",
+  "version": "0.1.7",
+  "description": "A persistent agent team for long-running collaboration in DeepSeek Harness",
   "repository": {
     "type": "git",
     "url": "https://github.com/wowyuarm/dsh-agent-team.git"
@@ -12,6 +12,7 @@
     "cordis.patch.yml",
     "packages/agent-team/lib/**/*",
     "packages/agent-team/preset/**/*",
+    "packages/agent-team/core-skills/**/*",
     "packages/tool-agent-team/lib/**/*",
     "packages/client-agent-team/lib/**/*",
     "README.md",
@@ -37,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",
@@ -50,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": {
@@ -105,6 +105,10 @@
       "types": "./packages/agent-team/lib/types/member-context.d.ts",
       "default": "./packages/agent-team/lib/member-context.js"
     },
+    "./member-skills": {
+      "types": "./packages/agent-team/lib/types/member-skills.d.ts",
+      "default": "./packages/agent-team/lib/member-skills.js"
+    },
     "./tools": {
       "types": "./packages/tool-agent-team/lib/types/index.d.ts",
       "default": "./packages/tool-agent-team/lib/index.js"
@@ -117,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,14 @@ 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.
+
+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 the Host prunes `member:`-shaped private-memory directories that the replayed ledger does not reference — leftovers from discarded ledgers, since a version-bumped medium rejects at open and starts empty. Prune failures fail startup; entries outside the `member:` shape are left untouched.
 
 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

@@ -18,6 +18,14 @@ 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。
+
+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 启动时会清理重放 ledger 不再引用的 `member:` 形态私有记忆目录——这些是 ledger 被丢弃后的遗留（版本提升的 medium 在 open 时被拒绝并以空状态重启）。清理失败会使启动失败；非 `member:` 形态的条目保持原样。
 
 把 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-skill-manager/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: member-skill-manager
+description: Create, install, revise, or retire this Member's private skills, including how a skill manages its configuration and credentials. Read this skill before creating, installing, revising, or retiring any skill in this Member's private skills directory, or when repeated or fragile work has produced a reusable method worth preserving as a skill.
+---
+
+# Member Skill Manager
+
+A skill preserves a reusable way of working. It is not a memory, a personal preference, or a record of one event.
+
+## 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.
+
+## Create Or Install
+
+This Member's private skills live in its private skills directory — the absolute path injected into your context (the one ending in `/skills`); it is outside the Workspace cwd, so never use a cwd-relative path for it. A skill is a directory there:
+
+```
+<private-skills>/my-skill/
+  SKILL.md          # required: front matter + instructions
+  references/       # optional: longer material only some uses need
+  scripts/          # optional: runnable helpers the skill calls
+```
+
+Install an offered skill by copying its directory there; no registration command is needed — the catalog discovers the change within its filesystem-watch window, so a later catalog query lists it. A single flat `.md` file also works, but the directory form is the norm for anything that carries references or scripts.
+
+Use a short lowercase hyphenated name. Keep the directory name and the `name` field the same, and do not reuse a name this catalog already lists (built-ins included).
+
+## Write
+
+Describe the method the next Member turn needs, not general advice it already knows. Make the description name the real triggers. Keep the main instructions in `SKILL.md` short. Put substantial scripts, references, or templates beside `SKILL.md` only when they are repeatedly useful. For a substantial new or revised skill, read [Writing Great Skills](references/writing-great-skills.md).
+
+## Review
+
+Read the finished skill once. Check that its name, description, directory, and method agree, and that nothing already in this Member's catalog owns the same method or name.
+
+Writing or changing a skill adds no tools, credentials, permissions, or external services. The current turn keeps its existing skill list; a later turn discovers the change.
+
+## Configuration and credentials
+
+A skill that needs an API key, token, or other secret keeps it in its own `auth.json` (JSON, one file per skill, inside that skill's directory) and reads it from there at run time; it never puts the secret in `SKILL.md`, scripts, messages, notes, or any other persisted text. Non-secret settings live in `config.json` beside it. Document the exact read/use convention in the skill's `SKILL.md` (file names, expected JSON shape, and how scripts consume them). See [Configuration and Credentials for Skills](references/auth-and-config.md) for the operating convention.

package/packages/agent-team/core-skills/member-skill-manager/references/auth-and-config.md

@@ -0,0 +1,30 @@
+# Configuration and Credentials for Skills
+
+A skill may need credentials (API keys, tokens) or non-secret configuration (endpoints, limits, defaults). This is the operating convention for how a Member manages those files when installing an external skill or creating its own.
+
+## File layout
+
+Every skill keeps its own files inside its skill directory:
+
+- `auth.json` — credentials. JSON object; one entry per service or purpose, e.g. `{"weread": "<api-key>"}`.
+- `config.json` — non-secret configuration. JSON object; whatever the skill needs, e.g. `{"baseUrl": "https://...", "maxResults": 5}`.
+
+A skill that needs neither file simply does not have them. Do not scatter credential files elsewhere or share one file across skills.
+
+## Writing a skill's SKILL.md
+
+The skill's `SKILL.md` must document how the skill reads these files:
+
+- the exact file names and expected JSON shape,
+- how scripts consume them (for example `AUTH=$(cat auth.json)` in a shell script, or `json.load(open("auth.json"))` in Python, resolved relative to the skill directory),
+- which config keys exist and what they do.
+
+## What never goes in plain text
+
+Credentials do not appear in `SKILL.md`, in scripts, in messages, in notes, in the Member's memory index, or in any other persisted or shared text. Scripts read them from `auth.json` at run time; they are never echoed into output, logs, or chat. When a Human provides a credential through a DM or attachment, write it into the skill's `auth.json` and reference it only as a file.
+
+## Creating or installing a skill
+
+- Create or copy the skill directory into this Member's private skills directory (the absolute injected path ending in `/skills`).
+- If the skill needs credentials or configuration, create `auth.json` / `config.json` in that directory with the layout above and document the read convention in its `SKILL.md`.
+- When the skill is a copy of an external skill that already has its own layout, keep that layout unless it conflicts with this convention; resolve conflicts by moving credentials into `auth.json` and updating `SKILL.md` accordingly.

package/packages/agent-team/core-skills/member-skill-manager/references/writing-great-skills.md

@@ -0,0 +1,17 @@
+# Writing Great Skills
+
+A skill makes a method more predictable across future work. Keep the process stable; let judgment and output remain appropriate to the situation.
+
+## Description
+
+The description is the skill's index. State what it does and the distinct situations that should cause it to be read. Do not spend it on details that belong in the body.
+
+## Instructions
+
+Put the steps every use needs in `SKILL.md`. Give fragile steps a concrete completion check. Keep definitions, variants, and long examples in a directly linked reference when only some uses need them.
+
+Use the least rigid form that preserves the method: guidance for judgment, a parameterized recipe for a preferred pattern, and a precise script only for work that is fragile or must be repeatable.
+
+## Prune
+
+Keep each rule in one place. Remove duplicated, stale, and obvious advice. A skill should carry only the knowledge that changes how the next turn can work.