docs: sync M4 outcomes into roadmap, architecture, and migration docs
VT migration abandoned (v1.0 scope becomes two projects), Q1 resolved to Gitea PyPI, Q6 resolved as judge exemption (unwired zero-consumer eval scaffolding), migration docs annotated with implementation errata, and the reference/ read-only rule clarified for the worktree workflow.
This commit is contained in:
@@ -1,5 +1,8 @@
|
||||
# Video-Tree-TRM5 迁移文档(迁移即验收)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **本迁移已放弃(2026-07-22 用户拍板: VT 项目本体已放弃,不再迁移)。** 全文保留作历史记录与能力倒推依据——VT 倒推的库能力(R1-R12,含多逻辑角色/cache salt/多模态摘要/OcrTextPort/trust_env/check_health)均已在 M1-M3 交付,不因放弃而回收。v1.0 验收标准改为 GovDoc + CHS 两项目(见 ROADMAP §5)。
|
||||
|
||||
> **定位**: 本文是 `ARCHITECTURE.md §11.2` 的展开——库建成后如何合并进 Video-Tree-TRM5、替换其哪些内部组件。它既是 M4 迁移的操作指南,也是 M1-M3 设计的反向约束(库公共 API 必须让本文描述的迁移成立)。**与 ARCHITECTURE.md 冲突时以 ARCHITECTURE.md 为准。** 全部结论基于 2026-07-20 对 `reference/Video-Tree-TRM5/` 的代码实测(file:line 均为实测证据)。
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user