fix(session): address restore review feedback

.agents/notes/implemented/architecture/2026-08-05-session-preparation.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write .agents/notes/implemented/architecture/2026-08-05-session-preparation.md
-2026-08-05-session-preparation.md: a3dfb50c8484cfef0cadea1759125a86714d3cbc
-2026-08-05-session-preparation.zh.md: 031e96f0e4446f02946f8c29ddade3fb52fe396e
+2026-08-05-session-preparation.md: d6b6cc190779279d1cc008bca890f3818736e920
+2026-08-05-session-preparation.zh.md: 191ad84db0e7bba38149c90cd91b410187f08f20

.agents/notes/implemented/architecture/2026-08-05-session-preparation.md

@@ -43,7 +43,7 @@ Cold continuable-subagent access follows the same path. Descriptor authorization
 - The cache belongs to one persistence coordinator, not a process-global Session map. Live Sessions are owned by the existing stores and never occupy preparation capacity.
 - A fresh create never claims a cold persisted preparation with the same id. Persistence collisions continue to reject.
 - Third-party persistence implementations retain the abstract `prepare()` fallback through `load()`. They receive the same publication interface but gain exact-object reuse only when they override preparation.
-- Revision validation establishes freshness at the reuse and repair-commit points; it does not add cross-process writer exclusion to a backend.
+- Revision validation establishes freshness at the reuse and repair-commit points; it does not add cross-process writer exclusion to a backend. Retries converge after the durable log remains unchanged for one read/check round trip, so continuous external writers can delay preparation.
 
 ## Verification
 

.agents/notes/implemented/architecture/2026-08-05-session-preparation.zh.md

@@ -43,7 +43,7 @@ agent loop（智能体循环）通过同一条设置与发布流水线消费这
 - 缓存属于单个持久化协调器，而不是进程全局 Session map。实时 Session 由现有存储持有，绝不占用准备容量。
 - 新建流程绝不认领相同 id 的冷持久化准备对象。持久化冲突仍会被拒绝。
 - 第三方持久化实现继续获得通过 `load()` 实现的抽象 `prepare()` 回退。它们使用相同发布接口，但只有覆盖准备流程后才能复用精确对象。
-- Revision 校验在复用点和修复提交点建立新鲜性，但不会为后端增加跨进程 writer 排他。
+- Revision 校验在复用点和修复提交点建立新鲜性，但不会为后端增加跨进程 writer 排他。持久日志在一次读取与复核往返内保持不变后，重试才能收敛，因此持续的外部写入可能延迟准备。
 
 ## 验证