docs(rfc): record the merged state of the host-adapter step registry

PR #7619 registered the ordered host-adapter step kinds and is merged, so
the parent confirmation entry and this entry must stop describing it as a
proposal. Update both mirrors and rebase this entry's baseline onto the
main that carries it.

Signed-off-by: xiaoan17 <anbc1224@gmail.com>

Author: xiaoan17

docs/architecture/rfcs/ledger/controller-executor-unified-contract-v0/2026-10-29-c4-3-adapter-partial-step-characterization.md

@@ -1,7 +1,7 @@
 # C4.3 adapter partial-step characterization
 
 - Parent: [controller/executor RFC, C4.3](2026-10-27-refactor-handoff.md#c43-settlement-adapters-over-existing-primitives).
-- Baseline: `f2990e3de`, 2026-10-29. The settlement owners are unchanged at `3a350c871`.
+- Baseline: `8caaf678e`, 2026-10-29. The settlement owners are unchanged at `1e3401591`.
 - Status: characterization only. No runtime, schema, wire or default change.
 - Follows: [C4.3 settlement obligation comparison](2026-10-29-c4-3-settlement-obligation-comparison.md).
 - [Chinese mirror](2026-10-29-c4-3-adapter-partial-step-characterization.zh-CN.md).
@@ -86,6 +86,6 @@ the confirmation entry withdrew — one typed owner for `guard`,
 `lifecycle_completion` and `validation` — is not reopened here: that entry
 already identified the shipped caller that adopts both paths and recorded the
 candidate as withdrawn. The slice that remains open is the shared owner for
-the ordered host-adapter step kinds, proposed in
+the ordered host-adapter step kinds, merged in
 [#7619](https://github.com/loopx-project/loopx/pull/7619). That is a registry
 slice, not a continuation of the withdrawn unification.

docs/architecture/rfcs/ledger/controller-executor-unified-contract-v0/2026-10-29-c4-3-adapter-partial-step-characterization.zh-CN.md

@@ -1,7 +1,7 @@
 # C4.3 适配器部分步骤行为刻画
 
 - 上级：[controller/executor RFC，C4.3](2026-10-27-refactor-handoff.zh-CN.md#c43-adapter)。
-- 基线：`f2990e3de`，2026-10-29。结算属主自 `3a350c871` 起未变。
+- 基线：`8caaf678e`，2026-10-29。结算属主自 `1e3401591` 起未变。
 - 状态：只做刻画。不改变运行时、schema、wire 或默认值。
 - 上游条目：[C4.3 结算义务对照](2026-10-29-c4-3-settlement-obligation-comparison.zh-CN.md)。
 - [英文版](2026-10-29-c4-3-adapter-partial-step-characterization.md)。
@@ -74,5 +74,5 @@
 与 `validation` 归到一个 typed 属主——在此不重新打开：那条目已经指出了同时采用
 两条路径的已交付调用方，并把该候选记为 withdrawn。仍然开放的切片是为 host-adapter
 有序步骤类型设立共享属主，已在
-[#7619](https://github.com/loopx-project/loopx/pull/7619) 中提出；那是登记切片，
+[#7619](https://github.com/loopx-project/loopx/pull/7619) 中合入；那是登记切片，
 不是被撤回的统一化工作的延续。

docs/architecture/rfcs/ledger/controller-executor-unified-contract-v0/2026-10-29-c4-3-settlement-vocabulary-confirmation.md

@@ -110,7 +110,7 @@ That gap is a separate slice: one shared owner for the ordered host-adapter step
 kinds, registered in the vocabulary registry so that the guard/validation
 distinction becomes machine-readable instead of prose. It must first reconcile
 the in-flight settlement work: #3412, #5677, #7580, #7523. That slice is
-proposed in [#7619](https://github.com/loopx-project/loopx/pull/7619): it
+merged in [#7619](https://github.com/loopx-project/loopx/pull/7619): it
 registers the ordered host-adapter step kinds as their own vocabulary with both
 runtimes as owners, so the two carriers are compared on every drift scan instead
 of hand-kept.

docs/architecture/rfcs/ledger/controller-executor-unified-contract-v0/2026-10-29-c4-3-settlement-vocabulary-confirmation.zh-CN.md

@@ -96,7 +96,7 @@ C4.3 结算义务对照列出一个候选后续切片：*词汇统一（小）
 这是一个独立切片：为 host-adapter 的有序步骤类型给出同一个共享属主，并登记进
 词汇 registry，让 guard/validation 的区别从散文变成机器可读。它必须先调和在途的
 结算工作：#3412、#5677、#7580、#7523。该切片已在
-[#7619](https://github.com/loopx-project/loopx/pull/7619) 中提出：它把 host-adapter
+[#7619](https://github.com/loopx-project/loopx/pull/7619) 中合入：它把 host-adapter
 的有序步骤类型登记为独立词汇，并由两个运行时共同作为属主，于是两个载体在每次
 漂移扫描中都会被比较，而不再靠手工维护。