docs(stride): describe explicit first continuation review

Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>

Author: loopx-agent

docs/architecture/rfcs/hierarchical-agent-stride-control-v0.md

@@ -1008,6 +1008,26 @@ mid-wake native capture before signalling and releases the original tool respons
 Linux interrupted and completed-wake capture retain their separate qualification;
 strict history, ambiguity, source and deadline predicates remain unchanged.
 
+An explicit destination preparation can reuse the existing cadence owner for
+its first review: configure `--execution-replan-after-turns 1`, perform and settle
+one actual restoration check, then admit the newly due periodic review. That
+check reads retained research/code and public opportunity without changing the
+candidate or submitting it. The review uses current Goal/Todo/lease and fresh
+context identities; source settlements remain historical evidence. After the
+review settles, restore the preregistered normal cadence through
+`configure-goal` before admitting research work. The isolated native receiver
+qualification records independent grow axes, adopts one two-candidate complete
+slice and verifies unchanged deadline, pending cooldown, consumed rounds and
+incumbent. The default receiver path is exercised separately; run
+`benchmark/tests/test_checkpoint_joint_receiver.py` in another fresh guest with
+`LOOPX_JOINT_RECEIVER_STRIDE=1` for the stride variant. This is an
+explicit tested composition, not an automatic restore hook or a new default.
+A Todo-successor repair alone is not a spendable periodic strategy review.
+Matched branches must declare the same preparation/cadence transition and charge
+its full cost. Scripted native-provider execution qualifies transport and
+mechanical adoption, not model judgment, restored Explore graph authority or
+scientific benefit; later-point selection and real branch admission remain open.
+
 Committed native session admission now retains the captured artifact digest in
 the original atomic session binding. Exact controller retries after a lost binding
 reply verify that receipt, current Goal/Agent/profile and unchanged complete

docs/architecture/rfcs/hierarchical-agent-stride-control-v0.zh-CN.md

@@ -817,6 +817,21 @@ pending command；延迟重读及仅向主进程发信号均未恢复。因此
 前明确拒绝中途 native 捕获，继续原工具响应。Linux interrupted 与 completed-wake
 路径分别保留验收，不放宽历史、歧义、源或期限检查。
 
+目标侧显式恢复准备可复用既有 cadence owner 来安排首次复盘：配置
+`--execution-replan-after-turns 1`，完成并结算一次真实恢复检查，再准入新到期的
+periodic review。检查读取保留的研究/代码与公开评测机会，不改候选、不提交。
+复盘使用当前 Goal/Todo/lease 及新 context 身份；源工作结算仅作历史证据。
+复盘结算后，通过 `configure-goal` 恢复预注册的正常频率，再准入研究工作。
+隔离的 native receiver 验证已记录三个轴独立计划的 grow，实际采用一次包含
+两个候选的完整工作切片，并检查 deadline、未到期冷却、已用轮次和 incumbent
+不变；默认 receiver 路径单独验证。在另一个全新 guest 中设置
+`LOOPX_JOINT_RECEIVER_STRIDE=1`，运行
+`benchmark/tests/test_checkpoint_joint_receiver.py` 可验证 stride 变体。
+这是显式且经测试的组合，不是恢复时自动
+触发的 hook，也不改变默认行为。补后继 Todo 的生命周期修复本身不等于可记账的
+periodic 策略复盘。匹配分支须声明相同的准备/频率迁移，并计入完整成本。
+脚本式 native provider 验证传输与机械采用，不证明模型判断、源 Explore graph
+权限恢复或科研收益；中后期研究点选择与真实分支准入仍待完成。
 
 inert verification unit 不授予执行权。目标侧使用新的实验/Host 身份，通过既有
 Goal/session/state admission 进入。历史租约、quota、timer、pending effect 和