refactor(collaboration): converge return delivery and restart recovery in TypeScript

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

@@ -65,6 +65,18 @@ Each page reuses the existing executable-revision request scope; operation
 records remain live reads, and the next page resolves the current code again.
 
 
+Manager result return now uses the existing `collaboration/return_delivery.ts`
+transaction for admission, provider-attempt checkpoints, retry/verification reduction
+and atomic delivery receipts. The two Python exact/legacy delivery coordinators
+and the private attempt-normalization RPC are retired together. Python retains
+original Chat/authority observations, Host fences and real provider IO. Bounded
+scan hints are rechecked under the write lock; an accepted provider attempt is
+persisted before verification, without a second queue or a Python decision fallback.
+Original request/result/route identities, historical codecs and public readback
+remain. This implements one R3/T1–T2 return transaction cutover, not Inbox acceptance,
+source-grant migration, installed adoption or live-provider qualification.
+
+
 <a id="current-delivery-frontier-2026-10-02"></a>
 
 ## Current delivery frontier (post-merge, 2026-10-16)

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

@@ -54,6 +54,16 @@ Python 保留有界地址扫描、请求者注册检查和实时 `Delegations.re
 每页复用既有代码版本请求作用域；操作记录仍实时读取，下一页重新解析当前代码。
 
 
+管家结果回传现由既有 `collaboration/return_delivery.ts` 事务负责准入、provider
+尝试检查点、重试／核验消解和投递回执的原子落盘。Python 的 exact／legacy 两套
+投递编排与私有 attempt 规范化 RPC 同时退役。Python 保留原始 Chat／授权事实读取、
+Host fence 和真实 provider IO。有界扫描只提供读取提示，写入锁内重新检查；provider
+接受写入后的尝试记录先落盘，再继续核验，不增加第二份队列或 Python 决策回退。
+原 request／result／route 身份、历史 codec 和公开回读保留。这实现 R3/T1–T2 的
+一个完整回传事务改造，不等于 Inbox 接收、来源授权迁移、安装采用或真实 provider
+资格已完成。
+
+
 <a id="当前交付边界2026-10-02"></a>
 
 ## 当前交付边界（合入后，2026-10-16）

loopx/capabilities/manager_context/README.md

@@ -623,10 +623,20 @@ read-only verification. A matching message advances the original delivery to
 message, or verified mismatch becomes `explicit_unverified`. CLI, Manager read,
 and Chat expose the same public-safe state and reason without returning the
 provider locator. The Lark adapter keeps locator interpretation and provider
-readback; `manager-context` remains the sole result/delivery writer. The typed
-`control_plane/collaboration/return_delivery.ts` boundary owns provider-neutral
-attempt validation and verification classification; Python retains file-lock,
-persistence and adapter orchestration only.
+readback. The existing `control_plane/collaboration/return_delivery.ts` owner now
+performs delivery admission, state transitions, backoff and atomic delivery-receipt
+writes for exact-instance and legacy routes. It reuses the request, result and
+Goal-lifetime owners. Python observes original Chat/authority facts, holds the
+existing Host fences and invokes the actual transcript/provider adapters.
+
+The obsolete Python exact/legacy delivery coordinators and attempt-normalization
+RPC are removed. The shared transaction accepts bounded scan hints, rechecks each
+selected receipt under its mutation lock, and uses source/revision and exact
+admission-token fences before persistence. Attempt-aware providers persist their
+acceptance checkpoint before verification continues; it is not deferred to a final callback.
+The same stored request/result/route identities and public delivery readback remain.
+This retires this delivery orchestration family, not Inbox acceptance, source grants,
+all Python IO or installed/live-provider qualification.
 
 Unclassified readback exceptions retain the saved attempt and retry with backoff;
 their wording never establishes revoked authority or a missing route. Adapters