docs(rfc): disclose resume diagnosis corrections and compatibility

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

Author: huangruiteng

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

@@ -235,6 +235,23 @@ Equal public sort keys retain source order; full counts precede display limits;
 read-only result grants neither execution authority nor a lifecycle receipt.
 The adapter exits when its callers consume typed Todo records in-process.
 
+Resume condition diagnosis is now shared by the evaluator and planning owner;
+agent-scope consumes the selected repair lane rather than reinterpreting target
+type/status. Old compact inputs may recover omitted kind/class from typed
+`resume_when` and the same snapshot's monitor records, never from narrative.
+This refinement includes explicit behavior corrections: self-dependencies and
+`todo_done` dependencies on unfinished monitors are `resume_condition_invalid`,
+not ordinary pending waits. Completed historical monitor dependencies remain
+satisfied; missing completion targets remain pending because absence in a
+partial snapshot is not proof of an invalid dependency. Valid generation fences,
+claim/exclusion, capacity and PR waits retain their existing semantics. Invalid
+conditions cannot become exact blocked-successor waits. Monitor completion
+repair stays visible and selectable only in the permitted executor scope.
+No automatic conversion to `monitor_changed`, baseline reset, persisted-state
+rewrite or new writer admission is implied. General add/update admission and a
+generic repair action for every invalid condition remain separate scopes; this
+is not a claim of zero behavior change or full Todo writer closure.
+
 1. **Close the actual command and consumer inventory.** Build on the merged
    create/claim/update and #4053 terminal/successor/archive transactions; do not
    recreate them. Inventory remaining field-edit, monitor, lease, and event

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

@@ -181,6 +181,18 @@ route-continuation、succession-warning 共用 `compact_projection.py` 的字段
 `monitor_changed` 不进入旧 `todo_done:<monitor>` 修复路径。只读结果不授予执行权限，
 也不是生命周期 receipt；caller 在进程内消费 typed Todo record 后可删除此适配层。
 
+条件 evaluator 与规划 owner 现在共用恢复条件诊断；agent-scope 消费已选好的修复 lane，
+不再重新解释 target 类型/状态。旧 compact 输入缺少 kind/class 时，只从 typed
+`resume_when` 和同一快照的 Monitor 记录补足，不从叙述猜测。本次 refinement 包含
+明确行为修正：自依赖，以及对未完成 Monitor 的 `todo_done` 依赖，被诊断为
+`resume_condition_invalid`，不再当作普通 pending wait。历史已完成 Monitor 依赖仍可
+满足；完成依赖的目标缺失仍为 pending，因局部快照中的缺失不能证明依赖非法。合法的
+generation fence、claim/exclusion、capacity 和 PR 等待语义保持。非法条件不进入
+精确 blocked-successor 等待；Monitor 完成依赖的修复仍可见，且仅在合法执行者范围内
+可选。此诊断不自动改写为 `monitor_changed`、重置 baseline、重写持久状态或增加写入
+准入。普通 add/update 准入及覆盖全部非法条件的通用修复动作仍是独立范围；不能宣称
+全量零行为变化或全部 Todo writer 已闭合。
+
 1. **闭合实际命令与 consumer 清单。** 基于已合入的 create/claim/update 和 #4053
    terminal/successor/archive transaction 推进，不重复建设。按真实合同盘点剩余
    字段编辑、monitor、lease、event caller，把规则迁入既有 TS owner，并在同一切片