docs(session): record the client-local engagement memory limits

packages/api/session-controller/README.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 packages/api/session-controller/README.md
-README.md: 4bbb98b0ee9224f72a571b10e8ae40d32377a747
-README.zh.md: 820dd4c3f56e964cf2b34cb50d5e5f38e35eff68
+README.md: 56d0f17b815a4616707d33bfd84b77446125f742
+README.zh.md: 9d754a5a61da548e1fd6dd10d1332582bdd3d126

packages/api/session-controller/README.md

@@ -101,6 +101,8 @@ No direct effect; model requests remain owned by the Agent and LLM packages.
 - A failed follow resumption remains visible to the caller instead of retrying indefinitely.
 - The raw browser upload is one streaming HTTP request without resumable offsets; a retry sends the file again from byte zero.
 - File-reference completion uses the shared Agent lookup and can resume a cold Session; the `skills/list` catalog is the non-activating alternative for skill metadata.
+- Accepted/running display memory lives only in Client memory and is lost on page reload.
+- That memory is not shared between tabs: one tab can show a converted row while another still shows `New Session` for the same Session.
 
 
 <a id="dev-note"></a>

packages/api/session-controller/README.zh.md

@@ -101,6 +101,8 @@ Fork 复制 `atSeq` 所选的精确事件前缀，包含切点事件，允许在
 - follow 恢复失败会对调用方可见，而不会无限重试。
 - 浏览器原始字节上传使用一次不带断点续传偏移的流式 HTTP 请求；重试会从第零字节重新传输整个文件。
 - 文件引用补全使用共享 Agent lookup，因此可能恢复冷 Session；`skills/list` 目录是不激活 Agent 的 skill 元数据读取路径。
+- 受理/运行的展示记忆只存在于客户端内存，页面重载后即丢失。
+- 该记忆不在 tab 之间共享：同一会话可能在一个 tab 中已转正，在另一个 tab 中仍显示为 `New Session`。
 
 
 <a id="dev-note"></a>