loopx-project · huangruiteng · Sep 13, 2026 · Sep 13, 2026
@@ -156,8 +156,10 @@ changes.
   - **Current boundary:** Proposes ordinary host-tool autonomy, persistent scoped
     conversations, long-horizon semantic continuation and automatic result delivery.
     Includes an official Grok Bot study distinguishing availability from goal
-    continuation; M0–M4 and A1–A16 define delivery and acceptance, with explicit
+    continuation; M0–M4 and A1–A20 define delivery and acceptance, with explicit
     alignment, shared-authority and TS migration dependencies.
+    Cross-session restoration, execution takeover and automatic return are specified
+    separately, reusing #4094 with optional Obelisk gap recall under its own scope.
     Runtime-profile promotion and generic handoff migration have not shipped.
 
 - [Explicit Todo Continuation — Stage A](cross-session-memory-substrate-v0.md)

@@ -6,6 +6,8 @@ Stage A shipped in [#4094](https://github.com/huangruiteng/loopx/pull/4094), mer
 
 Reuse rich/legacy context and the existing note validator/claim transfer boundary. Receiver acceptance of a suggestion is distinct from `handoff adopt` ownership mutation. Stage A's note is replaceable current Todo state, not a private immutable history. The successor maps authorized context to a recoverable brief, references current work, and supplies general assessment/result/automatic-return relations without adding a memory ledger or copying claim authority. CLI `prepare/inspect/adopt` remains usable during migration; frontend/Lark and automatic host continuation must be qualified separately. Same-host, registered-agent, lease-free restrictions continue to apply to this adapter, not every general request. See successor §5.13 for mappings, migration conditions and retained negative cases.
 
+The successor [§5.7](capable-manager-semantic-handoff-v0.md#57-session-and-product-continuity) now distinguishes same-session resume, same-Agent session replacement and cross-Agent takeover. Only the last may require this adapter’s ownership mutation. Automatic brief capture, source-loss recovery, executable-session fencing and original-route result return are explicit future integration work; optional Obelisk recall supplies missing historical evidence, not a replacement transfer grant.
+
 Language mirror: [中文版](cross-session-memory-substrate-v0.zh-CN.md).
 
 Status: a bounded local CLI workflow. The former general memory-substrate

@@ -6,6 +6,8 @@ Stage A 已在 [#4094](https://github.com/huangruiteng/loopx/pull/4094) 以 `2eb
 
 复用 rich/legacy context、既有 note validator 与 claim transfer 边界。接收方接受建议不同于 `handoff adopt` 修改所有权。Stage A note 是可覆盖的当前 Todo 状态，不是私有不可变历史。后继方案将有权限的上下文映射为可恢复 brief，引用当前工作，补齐通用 assessment/result/自动回传关系，不新增 memory ledger 或复制 claim authority。迁移期间 CLI `prepare/inspect/adopt` 保持可用；前端/飞书及自动宿主续接单独验收。同机、注册 Agent、无 lease 限制继续适用于此 adapter，不约束所有通用请求。映射、迁移条件和保留负例见后继 §5.13。
 
+后继 [§5.7](capable-manager-semantic-handoff-v0.zh-CN.md#57-会话与产品连续性) 明确区分原会话恢复、同 Agent 换 session、跨 Agent 接管，只有后者可能需要本 adapter 的所有权变更。自动 brief 捕获、来源消失恢复、执行 session fencing、回原入口报结论是明确的后续集成工作；可选 Obelisk recall 只补缺失历史证据，不替代 transfer grant。
+
 语言镜像：[English](cross-session-memory-substrate-v0.md)。
 
 本阶段替代原通用 memory substrate 方案，基于 canonical Todo authority

@@ -120,6 +120,10 @@ Reward Memory. A later second caller, such as Decision Context or Explore, may
 reuse the provider-neutral historical-evidence contract only after a concrete
 need and independent admission policy exist.
 
+### 3.2 Cross-session continuation caller
+
+The [capable-manager/semantic-handoff RFC §5.7](capable-manager-semantic-handoff-v0.md#57-session-and-product-continuity) proposes an explicit restoration caller for `resume_or_handoff_gap`. It first restores current work and the available deliberate continuation brief, including [Stage A](cross-session-memory-substrate-v0.md) context where applicable, then requests only missing decision evidence. This is a proposed integration, not a shipped caller or a promotion of this provider. Same-Agent replacement can satisfy the initial scope; a different receiver cannot search the source Agent's archive by inheriting a handoff. Authorized source excerpts may travel in the brief without granting archive search. The provider stages, default-off behavior, scope, private result/public receipt boundary and qualification requirements below remain unchanged. Basic continuation must work without Obelisk.
+
 ## 4. Admission policy
 
 The provider is not called on every Turn. A typed policy admits retrieval only

@@ -100,6 +100,10 @@ Obelisk Hit 是历史观察，不是 `reward_memory_active_record_v0`，不得
 Memory。未来如果 Decision Context 或 Explore 出现第二个真实 Caller，应在其拥有独立
 Admission Policy 后复用 Provider-neutral Historical Evidence Contract，而不是提前抽象。
 
+### 3.2 跨 session 续接 caller
+
+[强能力管家/语义交接 RFC §5.7](capable-manager-semantic-handoff-v0.zh-CN.md#57-会话与产品连续性) 提议明确的 `resume_or_handoff_gap` 恢复 caller：先恢复当前工作和已有主动续接 brief（包括适用时的 [Stage A](cross-session-memory-substrate-v0.zh-CN.md) 上下文），再只查询缺失的决策证据。这是拟议集成，不代表 caller 已交付或本 provider 晋级。同 Agent 更换 session 可满足初始 scope；另一接收者不能从 handoff 继承来源 Agent 的 archive 检索权。有权限的来源摘录可随 brief 传递，不同时授予 archive 搜索。下文 provider 阶段、默认关闭、scope、私有结果/公开回执边界及验收要求不变。基础续接必须在没有 Obelisk 时成立。
+
 ## 4. Admission Policy
 
 Provider 不在每个 Turn 调用。只有以下类型化 Situation 才允许检索：