docs(rfc): retain roadmap overview and clarify execution cards

Signed-off-by: huangruiteng <huangrt01@163.com>

Author: huangruiteng

docs/architecture/rfcs/shared-goal-authority-state-provider-v0.md

@@ -2522,6 +2522,15 @@ one-way projections. Do not add a third TS-Markdown backend, bidirectional
 live synchronization, or per-command split authority. Unsupported post-cutover
 commands fail closed; they do not fall back to the old writer.
 
+#### Refactoring roadmap overview
+
+The original direction remains; execution cards expand these stages rather than cancel them:
+
+1. **Close TS transactions and consumers.** Follow [T0–T3](typescript-control-plane-migration-v0.md#execution-cards-after-the-current-stack) to consolidate rules and delete duplicate decisions.
+2. **Permanent projection closure.** D1 below retains Markdown as a long-lived one-way display, never a second business authority.
+3. **One qualified local profile and fenced cutover.** D2/D3 require the real backend, capacity, soak and explicit promotion approval.
+4. **Retirement with named callers.** T4 removes obsolete business writers after their callers exit; permanent rendering and required import/export remain.
+
 #### Durability execution cards
 
 Use the [TS execution cards](typescript-control-plane-migration-v0.md#execution-cards-after-the-current-stack)
@@ -2550,6 +2559,8 @@ source paths, authorize monitor writeback, or change provider/promotion holds.
   Todo-section renderer and canonical journal/outbox. #4097 already recovers
   missing Todo sections with `recovery_scope=todo_sections_only`; reuse it.
   It cannot recover lost independent Goal narrative.
+  The shipped boundary is the [active-state projection contract](../../reference/protocols/active-state-structured-projection-v0.md).
+  Direct Markdown edits must not import themselves into authority; validated edit/import tooling is a separate proposal, never a second writer hidden inside rendering.
 - Evaluate #4101's receipt-retention candidate against its actual merged head;
   do not replace it with another delivery queue. A committed business result
   and pending projection delivery must remain separately observable.

docs/architecture/rfcs/shared-goal-authority-state-provider-v0.zh-CN.md

@@ -2000,6 +2000,15 @@ CLI / Agent / Dashboard → 唯一 TS Todo 事务 owner → canonical authority
 供数；cutover 后，所选 canonical provider 向单向投影供数。不增加第三种 TS-Markdown
 backend、实时双向同步或按命令拆开的权威；晋升后不支持的命令 fail closed，不能回退旧 writer。
 
+#### 重构主线总览
+
+以下规划保留原有方向；执行卡是它们的展开，不是替代或取消：
+
+1. **闭合 TS 事务与 consumer。** 按 [T0–T3](typescript-control-plane-migration-v0.zh-CN.md#当前-stack-合入后的执行卡) 收口规则并删除重复决策。
+2. **永久投影闭合。** 见下方 D1：Markdown 长期保留为单向展示，不恢复为业务权威。
+3. **一个已资格化的本地 profile 与 fenced cutover。** 见 D2、D3：真实 backend、容量、soak 与显式 promotion 批准缺一不可。
+4. **列明 caller 后退役。** 按 T4 删除无调用者的旧业务 writer；永久 renderer 和必要 import/export 保留。
+
 #### 持久化执行卡
 
 命令清单、update/monitor 事务和 consumer 删除统一按
@@ -2023,6 +2032,8 @@ summary，之前消费 legacy summary；真实 CLI 覆盖容量变化和 promote
 - 从 `loopx/control_plane/todos/provider_projection.py`、既有 Todo-section renderer、
   canonical journal/outbox 入手。复用 #4097 已有的缺失 Todo section 恢复及
   `recovery_scope=todo_sections_only`；它不能恢复丢失的独立 Goal 正文。
+  已交付边界以 [active-state projection contract](../../reference/protocols/active-state-structured-projection-v0.md) 为准。
+  直接编辑 Markdown 不得自动导入 authority；显式验证的 edit/import 工具另提方案，不能隐藏在 renderer 中成为第二个 writer。
 - 按 #4101 实际合入 head 评估 receipt-retention 候选，不再建一条 delivery queue。
   业务已提交与投影尚 pending 必须分别可观测。
 - 验证 crash/retry、并发 revision、缺失／陈旧／非法 display、交付前 receipt

docs/architecture/rfcs/typescript-control-plane-migration-v0.md

@@ -203,6 +203,10 @@ label; no legacy prediction is retained without a concrete display consumer.
   Unknown refreshes interrupt statistics, not Todo/replan obligations; no new
   persistent delivery ledger is added. Surface-only supervision and the
   independent small-delivery rule remain unchanged.
+  This exemption requires the parsed target identity and a supported task class;
+  monitor baseline, capability and PR repository/number also bind to the current
+  Todo. Missing actors or stale/mismatched conditions cannot relax supervision.
+  Incomplete legacy conditions remain readable, but are not positive wait proof.
 - Legacy outcome-marker/hint configuration remains readable and preserves
   whether an outcome floor is configured. Its words no longer classify runs.
   No persisted history is rewritten and no new default-off flag restores the
@@ -310,9 +314,9 @@ is not a claim of zero behavior change or full Todo writer closure.
 #### Execution cards after the current stack
 
 This is a **conditional execution plan**, not a merged-status declaration.
-At the 2026-09-09 checkpoint, #4053, #4117 and #4129 are merged; #4122
+At the 2026-09-09 checkpoint, #4053, #4117, #4129, #4122
 (resume diagnosis/planning), #4134 (delivery history) and #4136 (claim diagnosis)
-are open. The canonical delivery-response follow-up is stacked on #4136.
+are merged. The canonical delivery-response follow-up targets that landed main.
 Check their actual merge commits before starting. #4121 (SQLite candidate)
 and #4101 (projection receipt retention) are independent candidates, not
 implicit prerequisites or approved defaults.

docs/architecture/rfcs/typescript-control-plane-migration-v0.zh-CN.md

@@ -155,6 +155,9 @@ classification 保留为历史标签；没有明确展示消费者时，不保
   无绑定的旧 blocker 标签不能建立该例外；其他可执行工作仍由 canonical planner
   选择。unknown 刷新中断统计，不清除 Todo/replan 义务，不新增持久化交付账本。
   连续表层交付监督与独立的小规模交付规则保持不变。
+  该例外必须匹配解析后的 target identity 和合法 task class；monitor baseline、
+  capability、PR repository/number 也绑定当前 Todo。缺失 actor 或陈旧／错配的
+  condition 不能解除监督。旧式不完整条件仍可读取，但不构成正向等待证明。
 - 新交付声明通过现有 writer API 写显式 enum，例如
   `refresh-state --delivery-outcome ... --delivery-batch-scale ...`。
   纯状态刷新仍可不声明交付；本批不强迫每次刷新声明进展。既有写入 enum 校验、
@@ -239,9 +242,9 @@ generation fence、claim/exclusion、capacity 和 PR 等待语义保持。非法
 
 #### 当前 stack 合入后的执行卡
 
-这是**条件式执行规划**，不是已合并声明。2026-09-09 核查时，#4053、#4117、
-#4129 已合并；#4122（resume 诊断／规划）、#4134（交付历史）、#4136（声明诊断）
-仍 open；canonical delivery-response 后续批次叠在 #4136 上。执行前核验实际 merge
+这是**条件式执行规划**，不是所有阶段已完成的声明。2026-09-09 核查时，#4053、#4117、
+#4129、#4122（resume 诊断／规划）、#4134（交付历史）、#4136（声明诊断）均已合并；
+canonical delivery-response 后续批次基于这些已合入的 main。执行前核验实际 merge
 commit。#4121（SQLite 候选）和 #4101（投影 receipt 保留）是独立候选，不自动成为
 依赖或已批准的默认配置。