diff --git a/docs/session-format-status.i18n.yaml b/docs/session-format-status.i18n.yaml
index 833cd194f6..ef3b64d39c 100644
--- a/docs/session-format-status.i18n.yaml
+++ b/docs/session-format-status.i18n.yaml
@@ -15,11 +15,11 @@
   en: 02d18ba8a66cfb10
   zh: 54b753bbcb8f8a9e
 /session-format-version-and-release-status/finalization-record:
-  en: 9a1b2f4c61551ab7
-  zh: 666a2339c47343e1
+  en: 15b6134dcb3a09d5
+  zh: 4260c82e79baa021
 /session-format-version-and-release-status/release-record:
-  en: ee6e54ebc2b6dd37
-  zh: 928343edfd3fb943
+  en: 83ce79a241b630d7
+  zh: 53f3c461ef731f67
 /session-format-version-and-release-status/updating-the-record:
   en: 7eaa730a2d163bd6
   zh: 53ed7618537db2f5
diff --git a/docs/session-format-status.md b/docs/session-format-status.md
index 9df313da2f..78b6701095 100644
--- a/docs/session-format-status.md
+++ b/docs/session-format-status.md
@@ -36,17 +36,17 @@ V4 has an accepted compatibility baseline in the [checkpoint](persistence-change
 
 Finalization does not freeze every future V4 addition and does not assert publication. The release record below retains the independently verified published version. Ordinary comments, aliases, source locations, and implementation fixes preserving the accepted meaning do not change this baseline.
 
-Before the first V4 publication, every integration of a newer V3-writing master must pass the [explicit V3 vocabulary check](cookbook/adding-a-session-format-version.md#final-v3-vocabulary) against the recorded local source commit. Verify the source pin’s freshness and review new event payload conversions before updating the migration-owned set. After publication, the final V3 vocabulary remains historical and independent of current V4 additions.
+The [final V3 vocabulary](cookbook/adding-a-session-format-version.md#final-v3-vocabulary) remains historical and independent of current V4 additions.
 
 <a id="release-record"></a>
 ## Release record
 
 ```yaml session-format-release
-latestReleasedVersion: 3
-evidenceTag: dsh-v0.1.5-alpha.1
+latestReleasedVersion: 4
+evidenceTag: dsh-v0.2.0-rc.2
 ```
 
-Evidence: published product tag `dsh-v0.1.5-alpha.1`; tagged writer: `packages/core/session/src/types.ts`.
+Evidence: published product tag `dsh-v0.2.0-rc.2`; tagged writer: `packages/core/session/src/types.ts`.
 
 <a id="updating-the-record"></a>
 ## Updating the record
diff --git a/docs/session-format-status.zh.md b/docs/session-format-status.zh.md
index 31e1710632..141917a63c 100644
--- a/docs/session-format-status.zh.md
+++ b/docs/session-format-status.zh.md
@@ -36,17 +36,17 @@ V4 的已接受兼容性基线保存在[检查点](persistence-changes/finalized
 
 定稿不冻结 V4 之后的每项新增，也不表示已发布。下方发布记录保留独立验证的已发布版本。普通注释、别名、源码位置，以及保留已接受含义的实现修复，不改变该基线。
 
-首次发布 V4 前，每次集成仍写入 V3 的较新 master 都必须对已记录的本地源提交执行[显式 V3 词汇校验](cookbook/adding-a-session-format-version.zh.md#final-v3-vocabulary)。更新迁移所有的集合前，要核验源 pin 的新鲜度并审查新事件 payload 的转换。发布后，最终 V3 词汇保持为历史定义，与当前 V4 新增事件无关。
+最终 [V3 词汇](cookbook/adding-a-session-format-version.zh.md#final-v3-vocabulary)保持为历史定义，与当前 V4 新增事件无关。
 
 <a id="release-record"></a>
 ## 发布记录
 
 ```yaml session-format-release
-latestReleasedVersion: 3
-evidenceTag: dsh-v0.1.5-alpha.1
+latestReleasedVersion: 4
+evidenceTag: dsh-v0.2.0-rc.2
 ```
 
-证据：已发布产品标签 `dsh-v0.1.5-alpha.1`；该标签的写入器路径：`packages/core/session/src/types.ts`。
+证据：已发布产品标签 `dsh-v0.2.0-rc.2`；该标签的写入器路径：`packages/core/session/src/types.ts`。
 
 <a id="updating-the-record"></a>
 ## 更新记录