refactor(runtime): move remote response assembly to integrations

docs/architecture/core-decomposition.md

@@ -69,7 +69,7 @@ Rust 编译和链接面。
 | `bitfun-agent-tools` | 轻量 tool DTO / contract、portable tool context facts / provider、runtime restriction、host path normalization / runtime artifact URI / remote POSIX path pure contract、provider-neutral tool path resolution / absolute-path check / runtime artifact reference assembly、file guidance marker、file-read freshness comparison、oversized tool-result preview/rendering policy、allowed-list / collapsed-tool execution gate policy、provider-neutral path policy root matching / denial message、pure manifest/exposure and GetToolSpec presentation/schema/static metadata/detail/result assembly / execution-plan contract、provider-backed tool catalog / GetToolSpec runtime facade、provider-backed GetToolSpec execution result helper / Tool-result vector adapter、generic contextual manifest resolver、generic catalog snapshot provider / GetToolSpec catalog provider、generic registry / static-provider / dynamic-provider / decorator-ref / snapshot-decorator adapter / runtime assembly container、generic readonly/enabled snapshot filter | partial：product registry snapshot access、`ToolUseContext` adapter、session file-read state storage、tool-result filesystem writes、`GetToolSpec` Tool impl 和 concrete tools 仍在 core，并由 core `tools/product_runtime.rs` 作为单一 product runtime owner 组装；core 当前从 `bitfun-tool-packs` provider plan 物化内置工具列表，static-provider 安装 assembly、decorator reference、generic snapshot decorator adapter、provider-backed catalog runtime facade、readonly/enabled 过滤规则、provider-neutral tool path resolution / runtime artifact reference assembly、file guidance/freshness policy、oversized result rendering 与 path policy 判定已委托给 `bitfun-agent-tools` |
 | `bitfun-tool-packs` | 由 feature group 隔离的工具 provider plan | partial：提供 basic / git / mcp / browser-web / computer-use / image-analysis / miniapp / agent-control feature-group 元数据和 product provider group plan；不得声明 concrete tools 已迁移 |
 | `bitfun-services-core` | Config、session、workspace、storage、filesystem、system services | partial：部分 pure helper 已迁出；config/workspace/filesystem runtime 多数仍在 core |
-| `bitfun-services-integrations` | Git、MCP、remote SSH、remote connect、file watch integrations | partial：MCP runtime 已迁入；remote SSH 仍只迁移低风险 contracts/helpers；remote-connect 已拥有 wire DTO、request builder、tracker state / registry lifecycle、tracker event reduction、dialog submission orchestration port/provider、file IO/path resolution helper 与 image-context adapter contract；concrete scheduler/session restore/terminal adapter、workspace-root source、response wrapping 与 product execution 仍在 core |
+| `bitfun-services-integrations` | Git、MCP、remote SSH、remote connect、file watch integrations | partial：MCP runtime 已迁入；remote SSH 仍只迁移低风险 contracts/helpers；remote-connect 已拥有 wire DTO、request builder、tracker state / registry lifecycle、tracker event reduction、dialog submission orchestration port/provider、file IO/path resolution helper、remote file command / response assembly、dialog/cancel/execution accepted response helper、workspace/session response assembly helper 与 image-context adapter contract；concrete scheduler/session restore/terminal adapter、workspace-root source、persistence/workspace service reads 与 product execution 仍在 core |
 | `bitfun-product-domains` | Miniapp 和 function-agent 产品子域 | partial：pure decision、port、MiniApp create/update/draft/apply state transition、storage/builtin contract 与 seed meta timestamp policy 可迁入；IO、worker、built-in asset seeding、Git/AI service runtime 仍在 core |
 | `terminal-core` | 已有 terminal package，移动到 workspace 顶层 `src/crates/terminal` 路径 | done：已在 workspace 顶层 |
 | `tool-runtime` | 已有 tool runtime，移动到 workspace 顶层路径 | done：已在 workspace 顶层 |
@@ -101,11 +101,12 @@ owner 边界，否则不要把一个 feature group 继续拆成更小的 crate
   model catalog poll delta、
   tracker state / registry lifecycle、remote tool preview slimming、legacy image context fallback /
   preference、restore target decision、cancel decision、cancel-task orchestration、
-  RemoteRelay/Bot dialog submission orchestration port/provider、remote workspace path/MIME/full-read/chunk/info helper 与 remote file transfer
-  size/chunk/name policy 可由
+  RemoteRelay/Bot dialog submission orchestration port/provider、remote workspace path/MIME/full-read/chunk/info helper、
+  remote file command / response assembly、dialog/cancel/execution accepted response helper 与 remote file transfer
+  size/chunk/name policy、workspace/session response assembly helper 可由
   `bitfun-services-integrations` 拥有；core 只保留 tracker host adapter、
   global dispatcher compatibility wrapper、session restore 执行、terminal pre-warm adapter、
-  concrete scheduler submit adapter、workspace-root source、response/base64 wrapping 与
+  concrete scheduler submit adapter、workspace-root source、persistence/workspace service reads 与
   `ImageContextData` concrete adapter implementation。
   不要把 tracker state、wire DTO、dialog orchestration 或纯策略 helper 回写到 core。
 - remote-connect runtime owner 进一步外移前必须保持迁移前快照：remote command/response
@@ -291,10 +292,10 @@ owner 边界，否则不要把一个 feature group 继续拆成更小的 crate
     core-owned；HR2 进一步将这些 core-owned product-domain runtime 绑定收敛到
     `src/crates/core/src/product_domain_runtime.rs`，不改变实际执行路径。
   - H3：remaining service/runtime owner。remote-connect 已把 dialog submission
-    orchestration、cancel-task orchestration、terminal pre-warm decision、remote workspace file IO/path helper 与
-    image-context adapter contract 收敛到 owner crate port/provider；
+    orchestration、cancel-task orchestration、terminal pre-warm decision、remote workspace file IO/path helper、
+    workspace/session response assembly helper 与 image-context adapter contract 收敛到 owner crate port/provider；
     concrete scheduler/session restore/terminal adapter、workspace-root source、
-    response wrapping、remote-SSH runtime、agent registry/scheduler 等仍必须
+    persistence/workspace service reads、remote-SSH runtime、agent registry/scheduler 等仍必须
     另起 port/provider 设计和等价评审；HR3 进一步把这些仍 core-owned 的
     service/agent runtime 绑定入口集中到 `src/crates/core/src/service_agent_runtime.rs`，
     不改变 remote-connect、remote-SSH 或 scheduler 执行路径。