docs(agent-team): keep merged architecture summary within budget

docs/architecture.i18n.yaml

@@ -30,8 +30,8 @@
   en: e1e3a44140036f25
   zh: 84c70c969e5ad216
 /deepseek-harness-architecture/capability-seams:
-  en: c34e2531f90ac953
-  zh: 5b8455374dea3ee0
+  en: a5bc20c3f2a1b370
+  zh: 91773a281410b2f4
 /deepseek-harness-architecture/where-new-behavior-goes:
   en: 9b2eb0539a9cd0d6
   zh: 4f575277b91d4e5c

docs/architecture.md

@@ -134,7 +134,7 @@ A **seam** is a swappable capability with three roles: a **Service Definition**
 
 Seams are why one provider swap changes the whole product. Filesystem and subprocess providers share one execution world, so pointing them at a remote sandbox moves Bash, PTY, and LSP with them, with no provider forks. [Subagent providers](subsystems/subagent.md) vary just as widely behind one interface, from a fresh child agent to a delegated turn in another product.
 
-[Experimental Agent Teams](subsystems/agent-team.md) is a published opt-in coordination seam on `ctx.agentTeams`, with a durable roster and task board plus direct Agent inbox messaging layered over continuable subagents.
+[Experimental Agent Teams](subsystems/agent-team.md) exposes opt-in `ctx.agentTeams` coordination with durable roster and task state plus direct inbox messaging over continuable subagents.
 
 ## Where new behavior goes
 

docs/architecture.zh.md

@@ -138,7 +138,7 @@ Session 消费方只了解当前逻辑格式。仅 header 的 `stat` 与 `list`
 
 seam 正是替换一个提供方就能改变整个产品的原因。文件系统与进程提供方共享同一个执行世界，因此把它们指向远程沙箱，也就把 Bash、PTY 和 LSP 一并搬了过去，无需提供方专用 fork。[subagent 提供方](subsystems/subagent.zh.md)在同一个接口之后同样千差万别，从新建一个子 agent，到把一个轮次委派给另一个产品。
 
-[实验性 Agent Teams](subsystems/agent-team.zh.md) 是 `ctx.agentTeams` 上公开发布、显式启用的协作 seam，在可继续 subagent 之上提供持久 roster、任务板和直接 Agent inbox 消息。
+[实验性 Agent Teams](subsystems/agent-team.zh.md) 通过显式启用的 `ctx.agentTeams`，在可继续 subagent 之上提供持久 roster、任务状态和直接 inbox 消息协作。
 
 ## 新行为的归属位置