docs(notes): state that every tool removal rebuilds the baseline

.agents/notes/implemented/architecture/2026-09-20-dynamic-tool-updates.i18n.yaml

@@ -12,8 +12,8 @@
   en: 2bbb6ab17f2cbb1a
   zh: bb925627b6798548
 /agent-note-active-tool-headers-and-stateful-request-projection/alternatives-considered:
-  en: f1271717cbe0d4a0
-  zh: 367ad512ad08b221
+  en: 311db1f781e386e7
+  zh: 7e3312544154a158
 /agent-note-active-tool-headers-and-stateful-request-projection/consequences:
   en: aa3e68c78ac3f666
   zh: 5ec40c83183fc7e0

.agents/notes/implemented/architecture/2026-09-20-dynamic-tool-updates.md

@@ -26,7 +26,7 @@ DeepSeek translates projected updates into system-role `tool_addition` and `tool
 
 **Scan the complete log on every request.** The cached fold consumes new events and supplies stable snapshots to ordinary and auxiliary calls without adding arbitrary synchronous history readers.
 
-**Rebuild only for immediate baseline removals or mixed additions and removals.** Deferred tools also have request declarations; deleting a tool changes those declarations regardless of its activation position. Addition-only routes cannot express that deletion in history. Every removal therefore rebuilds the baseline, including removal-only updates and removals of later-activated tools. A past reset cannot force every future addition to become immediate: each reset establishes a new baseline from which deferred additions resume.
+**Rebuild the baseline on every removal.** Deferred tools also have request declarations; deleting a tool changes those declarations regardless of its activation position. Addition-only routes cannot express that deletion in history. The rebuild therefore also covers removal-only updates and removals of later-activated tools. A past reset cannot force every future addition to become immediate: each reset establishes a new baseline from which deferred additions resume.
 
 **Reject same-name schema changes during tool registration.** This restriction is not enforced. Immediate failure for a plugin registering an incompatible tool requires comparing the new registration with historical definitions of tools called on each affected current surface, while excluding calls removed by compaction. That registration-time historical and scope-aware check is deferred because of its implementation complexity. Same-name schema changes remain allowed; they rebuild declarations and invalidate prefix reuse even on `in-history` routes.
 

.agents/notes/implemented/architecture/2026-09-20-dynamic-tool-updates.zh.md

@@ -26,7 +26,7 @@ DeepSeek 把投影后的更新转换为 system 角色的 `tool_addition` 和 `to
 
 **每次请求扫描完整日志。** 缓存归约处理新事件，为普通和辅助调用提供稳定快照，不增加任意同步历史读取接口。
 
-**仅在移除立即加载的基线工具或同时添加和移除时重建。** 延迟工具也具有请求声明；删除工具会改变这些声明，与其激活位置无关。addition-only 路由无法通过历史表达删除。因此，每次移除都重建基线，包括仅移除的更新和移除后来激活的工具。一次历史重置不能让所有后续添加都变为立即加载：每次重置确立新基线，后续添加继续采用延迟加载。
+**每次移除都重建基线。** 延迟工具也具有请求声明；删除工具会改变这些声明，与其激活位置无关。addition-only 路由无法通过历史表达删除。因此，仅移除的更新和移除后来激活的工具也会重建基线。一次历史重置不能让所有后续添加都变为立即加载：每次重置确立新基线，后续添加继续采用延迟加载。
 
 **在工具注册时拒绝同名 schema 变化。** 当前不执行此限制。要让注册不兼容工具的插件立即收到异常，需要将新注册与各受影响当前 surface 中已调用工具的历史定义比较，同时排除已被压缩移除的调用。由于实现复杂，注册时结合历史和作用域的检查留待后续实现。同名 schema 变化仍被允许；它们会重建声明，即使在 `in-history` 路由上也会使前缀复用失效。