@wowyuarm/dsh-agent-team 0.1.9 → 0.1.10

package/README.md

@@ -17,7 +17,7 @@ An opt-in plugin for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-
 - **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.
+- **No context babysitting.** Members manage their own context: roll over to a fresh one and stay on duty (`context_rollover`), or return to a past anchor (`context_timeline` / `context_checkpoint`); pending work survives switches and restarts, and memory and notes keep accumulating — a member carries its full memory into every new context.
 
 ## Preview
 
@@ -27,13 +27,13 @@ Agent Team is opt-in: after installation the ordinary DSH page stays as-is, and
 
 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)
+![Team mode in the DSH Web UI: Channels and online Agent members in the sidebar, with the Main Channel showing Task references](assets/readme/team-mode.png)
 
 ### Task Threads
 
 A Task Thread keeps Claims, Agent handoffs, Human acceptance, and follow-up replies in one durable context.
 
-![Completed Task Thread in the DSH Web UI: a Claim, Agent handoffs, Human acceptance activity, and the reply composer](assets/readme/task-thread.png)
+![Task Thread in the DSH Web UI: Claims, 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.
 
@@ -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.2-rc.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
@@ -108,13 +108,6 @@ dsh web
 
 Published packages include built artifacts. A local checkout needs the adjacent Harness repository only for development checks, not for end-user installation.
 
-## Compatibility and limits
-
-- 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.
-
 ## Development
 
 Read [`docs/README.md`](docs/README.md) for the maintained documentation index. The usual checks are:

package/README.zh.md

@@ -17,7 +17,7 @@
 - **Workspace 组织一切。** 不同项目放在不同 Workspace，各自管理自己的 Agents 与 Channels。
 - **Human 管 Channel 与职责。** 你决定谁在哪个频道、负责什么；@提及把工作路由到对的 Agent。
 - **Task Thread 串联推进。** 用 Task 认领方向、Thread 保持上下文，多个 Session Agent 围绕同一条工作线推进而不散乱。工作事实落在同一条 Thread 里，成员之间不会各说各的。
-- **无需操心上下文。** 成员会话超阈值自动压缩，压缩前提示成员先沉淀关键结论。每个成员的 memory 与 notes 跨会话保留，身份与知识不随会话续期丢失。
+- **无需操心上下文。** 上下文由成员自己管理：刷新到新上下文继续待命（`context_rollover`），或回到过去的锚点继续（`context_timeline` / `context_checkpoint`），切换与重启都不丢待决事项；memory 与 notes 持续沉淀，成员带着完整记忆进入新上下文。
 
 ## 预览
 
@@ -27,13 +27,13 @@ Agent Team 是按需启用的：安装后普通 DSH 页面保持原样，Team mo
 
 进入 Team mode 后是频道、受管 Agent 与协作时间线：
 
-![DSH Web UI 中的 Team mode：侧边栏展示频道与 7 位在线 Agent；Main 频道含 Task 引用和 composer 的作为任务开关](assets/readme/team-mode.png)
+![DSH Web UI 中的 Team mode：侧边栏展示频道与在线 Agent 成员；Main Channel 展示 Task 引用](assets/readme/team-mode.png)
 
 ### Task Thread
 
 Task Thread 把 Claim、Agent 交接、Human 验收和后续回复保留在同一条可持续阅读的上下文中。
 
-![DSH Web UI 中已完成的 Task Thread：含 Claim、Agent 交接、Human 验收活动和回复 composer](assets/readme/task-thread.png)
+![DSH Web UI 中的 Task Thread：含 Claim、Agent 交接、Human 验收活动和回复 composer](assets/readme/task-thread.png)
 
 如果觉得有用，欢迎在 [GitHub](https://github.com/wowyuarm/dsh-agent-team) 点个 star，帮更多 DSH 用户发现它。
 
@@ -41,7 +41,7 @@ Task Thread 把 Claim、Agent 交接、Human 验收和后续回复保留在同
 
 ### 1. 检查 DSH
 
-当前版本已针对 DSH `0.1.2-rc.1` 完成认证。如果还没有安装 `dsh`，先使用官方 package 启动 DSH：
+当前版本已针对 DSH `0.1.5-rc.1` 完成认证。如果还没有安装 `dsh`，先使用官方 package 启动 DSH：
 
 ```sh
 npx @deepseek-ai/dsh web
@@ -108,13 +108,6 @@ dsh web
 
 发布包已经包含构建产物。只有开发检查需要相邻的 Harness repository，终端用户安装不需要它。
 
-## 兼容性与限制
-
-- 当前版本已针对 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 中使用。
-
 ## 开发
 
 维护中的文档入口是 [`docs/README.zh.md`](docs/README.zh.md)。常用检查命令：

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wowyuarm/dsh-agent-team",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "A persistent agent team for long-running collaboration in DeepSeek Harness",
   "repository": {
     "type": "git",
@@ -51,7 +51,7 @@
     }
   },
   "dependencies": {
-    "@deepseek-ai/dsh-storage-sqlite": ">=0.1.2-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-storage-sqlite": ">=0.1.5-rc.1 <0.2.0",
     "zod": "^4.4.3"
   },
   "devDependencies": {
@@ -106,6 +106,14 @@
       "types": "./packages/agent-team/lib/types/member-context.d.ts",
       "default": "./packages/agent-team/lib/member-context.js"
     },
+    "./member-time-context": {
+      "types": "./packages/agent-team/lib/types/member-time-context.d.ts",
+      "default": "./packages/agent-team/lib/member-time-context.js"
+    },
+    "./time-format": {
+      "types": "./packages/agent-team/lib/types/time-format.d.ts",
+      "default": "./packages/agent-team/lib/time-format.js"
+    },
     "./member-skills": {
       "types": "./packages/agent-team/lib/types/member-skills.d.ts",
       "default": "./packages/agent-team/lib/member-skills.js"
@@ -122,48 +130,49 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@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",
+    "@deepseek-ai/dsh-agent": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-agent-default-model": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-agent-presets": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-agent-tool-presentation": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-api-remotes": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-api-session-controller": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-api-workspace-controller": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-brand": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-locale": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-input-trigger": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-primitives": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-renderer": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-settings-general": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-sidebar": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-slots": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-workspace": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-command-compact": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-compaction": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-home-paths": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-invariants": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-llm": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-sandbox-policy": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-scope": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-session": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-session-format-catalog": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-session-persistence": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-skill": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-storage-domain": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-token-meter": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-bash": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-fs": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-fs-search": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-jobs": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-pwsh": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-skill": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-todo": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tool-web": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-tools": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-typert-protocol": ">=0.1.5-rc.1 <0.2.0",
+    "@deepseek-ai/dsh-workspace": ">=0.1.5-rc.1 <0.2.0",
     "react": "^18.2.0"
   },
   "keywords": [

package/packages/agent-team/README.md

@@ -2,7 +2,7 @@
 
 English | [中文](README.zh.md)
 
-The Host capability for one Agent Team in a dshHome. `ctx.agentTeam` owns the append-only operation ledger, reconstructs the current collaboration projection, and is the lifecycle owner for member Agents managed by the same capability. Thread Attention and the Member Inbox are durable Host projections. When unread state changes, this package sends one bounded, coalesced context notification through the Agent's public safe-boundary API; it never interrupts an active request or acts as a Session delivery worker. The [Agent Team architecture note](../../../.agents/notes/proposed/architecture/2026-08-15-agent-team-operation-ledger.md) owns the persistence and package-topology decisions.
+The Host capability for one Agent Team in a dshHome. `ctx.agentTeam` owns the append-only operation ledger, reconstructs the current collaboration projection, and is the lifecycle owner for member Agents managed by the same capability. Thread Attention and the Member Inbox are durable Host projections. When unread state changes, this package sends one bounded, coalesced context notification through the Agent's public safe-boundary API; it never interrupts an active request or acts as a Session delivery worker. The [Agent Team architecture note](../../.scratch/archive/2026-08/m1/design/agent-notes/2026-08-15-agent-team-operation-ledger.md) owns the persistence and package-topology decisions.
 
 ## Service contract
 
@@ -65,4 +65,4 @@ The Host ledger and Human status reads do not alter model requests or cache reus
 - **Single Host writer** — concurrent processes over one dshHome are unsupported; operation serialization is process-local.
 - **Permanent ledger** — M1 provides neither snapshots nor compaction, so storage grows with committed collaboration facts.
 - **No remote provider seam** — the package combines the capability definition and its only implementation until a real remote Consumer requires another Provider.
-- **Current DSH SQLite only** — SQLite Session persistence uses the current DSH schema. Delete old Session databases and create new Member sessions; this package provides no migration, compatibility read, or fallback.
+- **No Session migration of its own** — Member Sessions ride the Host's Session persistence and its released-format migration chain; this package provides no Team ledger or Member Session migration, compatibility read, or fallback.

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

@@ -2,7 +2,7 @@
 
 [English](README.md) | 中文
 
-一个 dshHome 内唯一 Agent Team 的 Host capability。`ctx.agentTeam` 拥有 append-only operation ledger、重建当前协作 projection，并作为同一 capability 内 Member Agent 的 lifecycle owner。Thread Attention 和 Member Inbox 是 Host 的持久 projection。未读状态变化时，本包通过 Agent 的公开安全边界 API 发送一次有界、合并的 context 通知；不会中断正在执行的请求，也不运行 Session delivery worker。[Agent Team 架构 Agent Note](../../../.agents/notes/proposed/architecture/2026-08-15-agent-team-operation-ledger.md)记录持久化和包拓扑决策。
+一个 dshHome 内唯一 Agent Team 的 Host capability。`ctx.agentTeam` 拥有 append-only operation ledger、重建当前协作 projection，并作为同一 capability 内 Member Agent 的 lifecycle owner。Thread Attention 和 Member Inbox 是 Host 的持久 projection。未读状态变化时，本包通过 Agent 的公开安全边界 API 发送一次有界、合并的 context 通知；不会中断正在执行的请求，也不运行 Session delivery worker。[Agent Team 架构 Agent Note](../../.scratch/archive/2026-08/m1/design/agent-notes/2026-08-15-agent-team-operation-ledger.md)记录持久化和包拓扑决策。
 
 ## Service 约定
 
@@ -65,3 +65,4 @@ Host ledger 和 Human status read 不改变模型请求或 cache reuse。
 - **单 Host writer** — 不支持多个进程并发写同一 dshHome；operation serialization 只在进程内生效。
 - **永久 ledger** — M1 不提供 snapshot 或 compaction，storage 会随已提交协作事实增长。
 - **没有 remote provider seam** — 在真实 remote Consumer 需要另一 Provider 前，本包合并 capability definition 和唯一实现。
+- **自身不提供 Session 迁移** — Member Sessions 依赖 Host 的 Session persistence 与其已发布格式迁移链；本包不提供 Team ledger 或 Member Session 迁移、兼容读取或回退。

package/packages/agent-team/lib/context-management.js

@@ -19,10 +19,8 @@
  */
 import { SessionId as SessionIdBrand } from '@deepseek-ai/dsh-session';
 import { createHash } from 'node:crypto';
-import { createCheckpointContinuationMessage, createHandoffMessage } from "./context-source.js";
+import { AGENT_TEAM_PLUGIN_ID, createCheckpointContinuationMessage, createHandoffMessage, isAgentTeamContextSource } from "./context-source.js";
 import { CONTEXT_CHECKPOINT_TOOL_NAME, CONTEXT_ROLLOVER_TOOL_NAME, continuationDelivered, foldContextProjection, } from "./context-projection.js";
-/** Plugin identity of the Agent Team Host, for recognizing own notices. */
-const AGENT_TEAM_PLUGIN_ID = '@wowyuarm/dsh-agent-team';
 /** Stable summary of the one-shot rollover pressure notice (ticket 03 wires delivery). */
 export const CONTEXT_PRESSURE_NOTICE_SUMMARY = 'Context pressure: prepare a handoff';
 export class ContextManagementCoordinator {
@@ -133,10 +131,15 @@ export class ContextManagementCoordinator {
         this.capturedInput.delete(memberId);
         return captured;
     }
-    /** Whether one queued message is a Team-owned notice the rederived Inbox replaces. */
+    /**
+     * Whether one queued message is a Team-owned notice the rederived Inbox
+     * replaces. Handoff and continuation envelopes carry the same plugin
+     * attribution but are ordinary delivered context the new generation keeps, so
+     * they are excluded rather than dropped.
+     */
     isTeamNotice(message) {
         const source = message.source;
-        return source.kind === 'plugin' && source.plugin === AGENT_TEAM_PLUGIN_ID;
+        return source.kind === 'plugin' && source.plugin === AGENT_TEAM_PLUGIN_ID && !isAgentTeamContextSource(message);
     }
     /** Drop one Member's bookkeeping; the Host calls this on dispose/removal. */
     stopTracking(memberId) {

package/packages/agent-team/lib/context-projection.js

@@ -20,9 +20,7 @@
  */
 import { createHash } from 'node:crypto';
 import { z } from 'zod';
-import { isCheckpointContinuationMessage } from "./context-source.js";
-/** Plugin identity of the Agent Team Host, for recognizing own notices. */
-const AGENT_TEAM_PLUGIN_ID = '@wowyuarm/dsh-agent-team';
+import { AGENT_TEAM_PLUGIN_ID, continuationCheckpointRefOf, handoffOf, isAgentTeamContextSource, isCheckpointContinuationMessage } from "./context-source.js";
 /** Summary marker of the pre-compaction memory hint. */
 const PRE_COMPACTION_NOTICE_SUMMARY = 'Compaction is imminent; consider persisting key conclusions.';
 /** Team tool whose successful mutations are semantic timeline candidates. */
@@ -246,7 +244,7 @@ function applyContextEvent(state, event, sessionId) {
  */
 function boundaryFromUserMessage(sessionId, seq, message, seenThreads) {
     const source = message.source;
-    if (source.kind === 'agent-team-context-handoff') {
+    if (handoffOf(message) !== undefined) {
         return { key: `handoff:${seq}`, source: 'handoff', label: 'context handoff', seq, turn: -1, turnEndSeq: -1 };
     }
     if (source.kind !== 'plugin' || source.plugin !== AGENT_TEAM_PLUGIN_ID)
@@ -441,9 +439,10 @@ function applyUserMessage(state, seq, message, sessionId) {
     }
     // The quiet continuation notice delivered for one checkpoint completes its
     // delivery state; replay repair reads this to avoid re-scheduling it.
-    if (message.source.kind !== 'agent-team-context-continuation')
+    const continuation = continuationCheckpointRefOf(message);
+    if (continuation === undefined)
         return next;
-    const checkpointRef = message.source.checkpointRef;
+    const checkpointRef = continuation;
     const existing = next.continuations.find(entry => entry.checkpointRef === checkpointRef);
     if (existing !== undefined) {
         if (existing.deliveredSeq !== -1)
@@ -469,10 +468,15 @@ function applyAssistantMessage(state, event) {
 export function carriedInputOf(state) {
     return state.carriedCandidates.filter(candidate => !candidate.consumed).map(candidate => candidate.message);
 }
-/** Whether one queued message is a Team-owned notice the rederived Inbox replaces. */
+/**
+ * Whether one queued message is a Team-owned notice the rederived Inbox
+ * replaces. Handoff and continuation envelopes carry the same plugin
+ * attribution but are ordinary delivered context the new generation keeps, so
+ * they are excluded rather than dropped.
+ */
 function isTeamNotice(message) {
     const source = message.source;
-    return source.kind === 'plugin' && source.plugin === AGENT_TEAM_PLUGIN_ID;
+    return source.kind === 'plugin' && source.plugin === AGENT_TEAM_PLUGIN_ID && !isAgentTeamContextSource(message);
 }
 /** Whether a quiet continuation for one checkpoint was already delivered in this Session. */
 export function continuationDelivered(state, checkpointRef) {

package/packages/agent-team/lib/context-source.js

@@ -1,35 +1,52 @@
 /**
- * Merge-extended message sources for Agent Team context management.
+ * Plugin-attributed message sources for Agent Team context management.
  *
- * The sources ride ordinary `UserMessage`s and never add a Harness
- * `ContextForm`: the handoff snapshot reuses the shipped `snapshot` form, the
- * quieter notices reuse `notice`. Predicates here are the single place that
- * recognizes these notices, so callers never match on localized body text.
+ * Both sources ride ordinary `UserMessage`s under the shipped `plugin` kind
+ * with the `snapshot` context form — the same shape the Harness's own
+ * system-prompt producer writes. This module declares no `MessageSourceMap`
+ * member of its own, and carries no bespoke source members: Session format
+ * migration validates a `plugin` source against a closed member list
+ * (`kind`, `plugin`, `form`, `sections`, `summary`), and refuses every logged
+ * Session that carries anything else. A plugin-declared kind is type-legal yet
+ * refused the same way. See `docs/dsh-release-compatibility.md`
+ * § "Session message sources".
+ *
+ * Everything the Host needs to read back therefore rides the admitted payload
+ * slots: the handoff envelope and the checkpoint correlation both travel as
+ * named {@link ContextSnapshotSection} contributions, distinguished by their
+ * stable section names. Sections are the format's designed slot for structured
+ * producer payload, and they render as named contributions on any
+ * snapshot-aware surface.
+ *
+ * The validators below are the single place that recognizes these messages, so
+ * callers never match on localized body text.
  * @module @wowyuarm/dsh-agent-team/context-source
  */
 import { createUserMessage } from '@deepseek-ai/dsh-llm';
-/** Stable one-line account for checkpoint continuation notices. */
-export const CONTEXT_CONTINUATION_NOTICE_SUMMARY = 'Context checkpoint recorded; work continues in the next turn';
+/** Plugin identity attributing every Agent Team message source. */
+export const AGENT_TEAM_PLUGIN_ID = '@wowyuarm/dsh-agent-team';
 /** Handoff snapshot section name carrying the model-authored prose. */
 export const HANDOFF_SECTION_NAME = 'HANDOFF';
+/** Stable section name marking a checkpoint continuation and carrying its ref. */
+export const CHECKPOINT_SECTION_NAME = 'Checkpoint';
+/** Fixed text of the quiet checkpoint continuation delivered on the next turn. */
+export const CHECKPOINT_CONTINUATION_TEXT = 'A context checkpoint was recorded at the end of the previous turn. Continue the work you were doing.';
 /**
  * Build the first model-facing context of one rollover generation. The Host
  * owns only the verifiable envelope; the prose is the Member's own handoff.
+ *
+ * The envelope sections are additive structure, not the only carrier of these
+ * facts: {@link handoffBody} already states them in the model-facing text, so a
+ * surface that renders only the body loses nothing.
  */
 export function createHandoffMessage(input) {
     return createUserMessage({
         content: [{ type: 'text', text: handoffBody(input) }],
         source: {
-            kind: 'agent-team-context-handoff',
+            kind: 'plugin',
+            plugin: AGENT_TEAM_PLUGIN_ID,
             form: 'snapshot',
-            version: 1,
-            previousSessionId: input.previousSessionId,
-            newSessionId: input.newSessionId,
-            trigger: input.trigger,
-            handoffEventSeq: input.handoffEventSeq,
-            ...(input.checkpointRef === undefined ? {} : { checkpointRef: input.checkpointRef }),
-            ...(input.relatedFiles === undefined || input.relatedFiles.length === 0 ? {} : { relatedFiles: input.relatedFiles.map(file => file.path) }),
-            sections: [{ name: HANDOFF_SECTION_NAME, text: input.handoff }],
+            sections: handoffSections(input),
         },
     });
 }
@@ -38,22 +55,145 @@ export function createHandoffMessage(input) {
  * concluded its turn. Delivery is scheduled only after the checkpoint's
  * successful tool result is durable, so a result-render failure can never
  * leave a ghost continuation behind.
+ *
+ * This is a `snapshot` rather than a `notice` for one reason: the projection
+ * must read the checkpoint ref back out of the durable log to record delivery,
+ * and `sections` is the only admitted payload slot that carries structure. A
+ * notice would have forced the ref into its human-readable one-line summary.
  */
 export function createCheckpointContinuationMessage(checkpointRef) {
     return createUserMessage({
-        content: [{ type: 'text', text: 'A context checkpoint was recorded at the end of the previous turn. Continue the work you were doing.' }],
-        source: { kind: 'agent-team-context-continuation', form: 'notice', summary: CONTEXT_CONTINUATION_NOTICE_SUMMARY, checkpointRef, version: 1 },
+        content: [{ type: 'text', text: CHECKPOINT_CONTINUATION_TEXT }],
+        source: {
+            kind: 'plugin',
+            plugin: AGENT_TEAM_PLUGIN_ID,
+            form: 'snapshot',
+            sections: [{ name: CHECKPOINT_SECTION_NAME, text: checkpointRef }],
+        },
     });
 }
+/**
+ * Read one message's snapshot sections when it is this plugin's own snapshot.
+ * @param message - candidate user message.
+ * @returns the sections, or `undefined` when another producer owns the message.
+ */
+function ownSections(message) {
+    const source = message.source;
+    if (source.kind !== 'plugin' || source.plugin !== AGENT_TEAM_PLUGIN_ID)
+        return undefined;
+    if (source.form !== 'snapshot')
+        return undefined;
+    return source.sections;
+}
+/** The text of one named section, or undefined when it is absent. */
+function sectionText(sections, name) {
+    return sections.find(section => section.name === name)?.text;
+}
+/**
+ * Decode the `Related files` section. The Host writes the exact path array as
+ * JSON, which round-trips every path a file system admits — including one
+ * containing a comma, which the `', '`-joined form this replaced could not.
+ * Sections written before that encoding are still read; the legacy split is a
+ * read-side accommodation for old generations, never a write path.
+ */
+function parseRelatedFiles(text) {
+    try {
+        const parsed = JSON.parse(text);
+        if (Array.isArray(parsed) && parsed.every(path => typeof path === 'string' && path.length > 0)) {
+            return parsed;
+        }
+    }
+    catch {
+        // Not JSON: the section predates the JSON encoding.
+    }
+    return text.split(', ').filter(path => path.length > 0);
+}
+/**
+ * The rollover handoff one message carries, when it is one.
+ * @param message - candidate user message.
+ * @returns the envelope, or `undefined` when the message is not a handoff.
+ */
+export function handoffOf(message) {
+    const sections = ownSections(message);
+    if (sections === undefined)
+        return undefined;
+    const handoff = sectionText(sections, HANDOFF_SECTION_NAME);
+    if (handoff === undefined)
+        return undefined;
+    const previousSessionId = sectionText(sections, HANDOFF_PREVIOUS_SESSION);
+    const newSessionId = sectionText(sections, HANDOFF_NEW_SESSION);
+    const trigger = sectionText(sections, HANDOFF_TRIGGER);
+    const handoffEventSeq = sectionText(sections, HANDOFF_EVENT_SEQ);
+    if (previousSessionId === undefined || newSessionId === undefined)
+        return undefined;
+    if (trigger !== 'model' && trigger !== 'pressure')
+        return undefined;
+    const seq = Number(handoffEventSeq);
+    if (handoffEventSeq === undefined || !Number.isSafeInteger(seq))
+        return undefined;
+    const checkpointRef = sectionText(sections, HANDOFF_CHECKPOINT);
+    const relatedFiles = sectionText(sections, HANDOFF_RELATED_FILES);
+    return {
+        previousSessionId,
+        newSessionId,
+        trigger,
+        handoffEventSeq: seq,
+        ...(checkpointRef === undefined ? {} : { checkpointRef }),
+        ...(relatedFiles === undefined ? {} : { relatedFiles: parseRelatedFiles(relatedFiles) }),
+        sections,
+    };
+}
+/**
+ * The checkpoint ref one continuation notice carries, when the message is one.
+ * @param message - candidate user message.
+ * @returns the checkpoint ref, or `undefined` when the message is not a continuation.
+ */
+export function continuationCheckpointRefOf(message) {
+    const sections = ownSections(message);
+    if (sections === undefined || sections.length !== 1)
+        return undefined;
+    const ref = sectionText(sections, CHECKPOINT_SECTION_NAME);
+    return ref === undefined || ref.length === 0 ? undefined : ref;
+}
 /** Whether one user message is a rollover handoff snapshot. */
 export function isHandoffMessage(message) {
-    return message.source.kind === 'agent-team-context-handoff';
+    return handoffOf(message) !== undefined;
 }
-/** Whether one user message is a checkpoint continuation notice, optionally for one checkpoint. */
+/** Whether one user message is a checkpoint continuation, optionally for one checkpoint. */
 export function isCheckpointContinuationMessage(message, checkpointRef) {
-    const source = message.source;
-    return source.kind === 'agent-team-context-continuation'
-        && (checkpointRef === undefined || source.checkpointRef === checkpointRef);
+    const ref = continuationCheckpointRefOf(message);
+    return ref !== undefined && (checkpointRef === undefined || ref === checkpointRef);
+}
+/**
+ * Whether one message carries a rollover-handoff or checkpoint-continuation
+ * envelope. Ordinary Team notices share this plugin's attribution, so callers
+ * that replace rederived notices must exclude these two families explicitly.
+ */
+export function isAgentTeamContextSource(message) {
+    return isHandoffMessage(message) || isCheckpointContinuationMessage(message);
+}
+/** Envelope section names; stable, because they are read back from the log.
+ * Exported for the legacy-artifact remediation, which rewrites pre-0.1.10
+ * envelopes into exactly these names — one shared vocabulary, no drift. */
+export const HANDOFF_PREVIOUS_SESSION = 'Previous session';
+export const HANDOFF_NEW_SESSION = 'New session';
+export const HANDOFF_TRIGGER = 'Trigger';
+export const HANDOFF_EVENT_SEQ = 'Handoff event seq';
+export const HANDOFF_CHECKPOINT = 'Continued from checkpoint';
+export const HANDOFF_RELATED_FILES = 'Related files';
+/** The envelope contributions of one handoff, prose first. */
+function handoffSections(input) {
+    return [
+        { name: HANDOFF_SECTION_NAME, text: input.handoff },
+        { name: HANDOFF_PREVIOUS_SESSION, text: input.previousSessionId },
+        { name: HANDOFF_NEW_SESSION, text: input.newSessionId },
+        { name: HANDOFF_TRIGGER, text: input.trigger },
+        { name: HANDOFF_EVENT_SEQ, text: String(input.handoffEventSeq) },
+        ...(input.checkpointRef === undefined ? [] : [{ name: HANDOFF_CHECKPOINT, text: input.checkpointRef }]),
+        ...(input.relatedFiles === undefined || input.relatedFiles.length === 0
+            ? []
+            : [{ name: HANDOFF_RELATED_FILES, text: JSON.stringify(input.relatedFiles.map(file => file.path)) }]),
+    ];
 }
 function handoffBody(input) {
     const lines = [