docs(rfc): clarify reusable agent launch, result return and wake contracts

[huangruiteng]

Goal And Delivered Outcome

R2/R3 already name reusable Agent profiles, work requests and inbox/queue/steer. Their cross-host acceptance still leaves ambiguity when a worker serves a different requester, several requests enter one turn, or a result arrives during coordinator finalization. This RFC-only change makes those cases explicit and ties them to existing owners.

Related to #4574; base: main. Four existing RFCs are updated in English and Chinese:

• Session execution: separate context selection, effective model/tool preferences and authority; distinguish registered identity, resident runtime and active execution; qualify uncertain creation and scoped recovery.
• Semantic handoff: preserve request identity independently of creation ancestry and host turns; commit results before notification, return to the requester and retain them until acknowledged; define sibling/disconnect/interruption cases.
• Execution frontends: specify inbox/queue/steer behavior across active, idle, finalizing and unavailable recipients, with wake admission owned by the existing continuation policy.
• Overall roadmap: prioritize profile/readiness, recoverable request returns and delivery/wake qualification before residency optimization.

Scope And Continuation

Complete within this design scope. All added behavior is proposed qualification, not a shipped cross-host guarantee. Follow-on implementation stays in the existing R2/R3 work and profile/binding, collaboration/outbox and ingress owners. No new factory, scheduler, work ledger, schema, provider model list or default is introduced. The future-facing pass tightened existing contracts instead of adding runtime abstractions.

Validation

• Tested revision: 4dd115887945d44c775bec491ffd4e37ca301b7a
• Run state: finished
• Input classes: synthetic, public_fixture

Check kind	Result	Public-safe evidence / limitation
static	passed	python examples/docs-governance-smoke.py; all 8 new relative links/heading anchors resolve.
static	passed	loopx check --scan-path <changed RFC> for all 8 files: public-boundary scan clean.
static	passed	git diff --check origin/main...HEAD; full EN/ZH contract consistency review.
manual	passed	Compared the proposals with control_plane/collaboration/peers.py, collaboration_mcp.py, onboarding/profile ownership and current RFC acceptance.
static	passed	loopx canary premerge --from-git-diff: 18 selected checks passed, plus all 3 direct diff checks; no failures or manual holds.
real_entrypoint	not_applicable	No executable change; new live multi-agent scenarios are future acceptance requirements, not experiments run by this PR.

Quality qualification matches the final diff. No runtime, API, persisted-state, frontend, CLI or Lark behavior changes; no runtime rollout or shared-authority promotion claimed.

Frontend / Visual Evidence

UI impact: none. This changes RFC prose only, with no product entry point or documentation chrome changes.

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface (README, protocols, dashboard)

Technical Direction

Architecture and research incubator; existing overall-roadmap R2/R3, session/profile acceptance and handoff A8/A10/A18. Shared-authority fixture impact: N/A; no routing or authority implementation changes.

Boundary Checklist

• Diff and public artifacts exclude private state, credentials, raw logs, internal links and machine paths.
• No benchmark jobs or duplicate maintainer-owned benchmark work.
• Scope matches the requested RFC design refinement.
• UI impact is none.
• Commit includes a DCO sign-off.

[huangruiteng]

Approval conclusion (author-owned PR; GitHub blocks formal self-approval)

Reviewed head: 4dd115887945d44c775bec491ffd4e37ca301b7a. 无阻塞发现；本结论仅针对 RFC 设计细化。

动机

R2/R3 已有 profile、工作请求及三种通信模式，但兄弟请求者、一个 turn 合流多项请求、收尾时收到结果等组合缺少明确验收。此次完成的是设计研究融入现有 RFC 的任务；没有把文档更新视为运行时交付或整个路线图完成。

改动思路

继续使用 profile/binding、request/attempt/return、ingress/outbox 及唯一 continuation owner。对照了当前 peers.returns、consume_return、return_result 和 Delegations.read：结果保留、请求者路由及产物复验已有基础，后续应补齐 adapter 资格化。另建工厂、任务账本或调度器会重复这些职责，当前方案没有引入它们。

具体改动

关键内容讲解

• Session RFC 的中英文版本区分上下文、实际执行偏好和权限，补齐 binding readiness、注册/驻留/执行观察以及创建响应不确定时的恢复边界。
• Handoff RFC 的中英文版本明确创建者不一定是请求者；同 turn 多请求仍分别保留结果与验收；结果先提交、再通知，并在请求者确认前持续可读。
• Frontend RFC 的中英文版本补充 active、idle、finalizing/interrupted、unloaded/disconnected 矩阵。Queue 仍面向后续 turn；保存消息不自动授予唤醒或执行权限。
• Overall roadmap 的中英文版本将这些要求链接回 R2/R3，优先 profile/readiness 和可恢复返回，后置驻留优化。

正向设计路径是创建/接入并读回实际配置 → 接收独立请求 → 完成并提交结果 → 原请求者读取/确认 → 现有续跑 owner 决定下一次执行。反向场景覆盖授权撤销、child 缺工具、收尾竞态和通知丢失；这些是提议的验收要求，本次未执行新的真实多 Agent 实验。

对主干的风险

主要风险是把设计要求误读为已有跨宿主保证。逐项检查了 proposed 标记、现有 ingress 表及请求状态关系：没有新 runtime schema、默认行为、安装指令或权限扩大；驻留状态明确为概念区分。中断不证明后代副作用停止，wait 不承担 join 或验收。

语义与 CI 对齐

沿用现有 request/return 与 inbox/queue/steer 词汇；新增内容细化未来资格化，不新增当前机器强制义务。按本次解析出的评审策略，CI 不纳入证据、未查询或等待；本地验证为依据。

验证：python examples/docs-governance-smoke.py 通过；8 个新增相对链接/锚点均可解析；8 文件公开边界扫描通过；git diff --check 通过；风险 premerge 的 18 项及 3 项直接 diff 检查通过，无必需检查失败/跳过。质量回执匹配最终 diff。远端 patch 与本地已审 diff 一致。

我的整体评价

APPROVE。224 行均为四份 RFC 的双语补充，完整覆盖同一条创建—请求—返回—唤醒链；不需要新增 RFC 或生产抽象。未来演进检查已应用：保留原有归属，并修正了可能暗示已实现 schema 或传输 exactly-once 的表述。剩余工作是 R2/R3 中真实本地/云端 adapter 的运行、断线和恢复资格化；本结论不宣称其已完成，也不授权合并。

English verdict: APPROVE - 4dd1158. The bilingual RFC refinements preserve existing owners and clearly separate proposed qualification from shipped behavior. Documentation/link/privacy checks, 18 selected premerge checks and 3 direct checks passed. No new live multi-agent experiment; CI not consulted under the resolved review policy.