fix: Add missing fields of FrameworkRenderingTiming

rename FrameworkPipelineTiming to FrameworkRenderingTiming

add vmExecuteStart/End, dataProcessorStrart/End and setInitDataStart/End in FrameworkRenderingTiming.

Change-Id: I94758afb6491967f02e944f546450b987753ff51

Author: partholon

docs/en/api/lynx-api/performance-api/_meta.json

@@ -25,8 +25,8 @@
   },
   {
     "type": "file",
-    "name": "framework-pipeline-timing",
-    "label": "FrameworkPipelineTiming",
+    "name": "framework-rendering-timing",
+    "label": "FrameworkRenderingTiming",
     "overviewHeaders": [],
     "collapsible": true,
     "collapsed": true

docs/en/api/lynx-api/performance-api/framework-pipeline-timing.mdx renamed to docs/en/api/lynx-api/performance-api/framework-rendering-timing.mdx

@@ -1,9 +1,17 @@
 import { RuntimeBadge } from '@lynx';
 
-# FrameworkPipelineTiming
+# FrameworkRenderingTiming
 
 This interface describes the performance data of key stages in [framework rendering](/guide/spec#framework-rendering).
 
+In the [First-screen Rendering](/guide/spec#first-screen-rendering-or-fsr) and [Re-rendering](/guide/spec#re-rendering), the framework is responsible for a series of critical tasks. The diagram below illustrates the significant steps of framework rendering in the entire FSR and Re-rendering processes:
+
+- **The yellow sections represent the key phases of framework rendering**.
+- The green sections represent the key phases of [Engine Rendering (Pixel Pipeline)](/guide/spec#pixel-pipeline), with details available at [PipelineEntry](/api/lynx-api/performance-api/performance-entry/pipeline-entry).
+- The purple sections represent the key phases of [Lynx Engine](/guide/spec#engine), with details available at [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
+
+![Critical Phases in Framework Rendering](https://lf-lynx.tiktok-cdns.com/obj/lynx-artifacts-oss-sg/lynx-website/assets/doc/framework-rendering-timing.png)
+
 ## Instance Properties
 
 ### dsl
@@ -94,9 +102,7 @@ hydrateParseSnapshotStart: number;
 
 The timestamp when the framework starts deserializing [main thread](/guide/spec.html#main-thread-or-lynx-main-thread) information on the [background thread](/guide/spec.html#background-thread-aka-off-main-thread). This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
 
-:::tip
 This property is only valid when `stage` is `hydrate`.
-:::
 
 ### hydrateParseSnapshotEnd
 
@@ -106,12 +112,70 @@ hydrateParseSnapshotEnd: number;
 
 The timestamp when the framework ends deserializing [main thread](/guide/spec.html#main-thread-or-lynx-main-thread) information on the [background thread](/guide/spec.html#background-thread-aka-off-main-thread). This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
 
-:::tip
 This property is only valid when `stage` is `hydrate`.
-:::
+
+### vmExecuteStart
+
+```tsx
+vmExecuteStart: number;
+```
+
+The timestamp when the framework starts executing [`main-thread.js`](/guide/spec.html#instances-of-main-thread-script) in the main thread to initialize the [Javascript Engine](/guide/spec.html#javascript-engine). This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.
+
+This property is only valid when `frameworkRenderingTiming` is present in [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
+
+### vmExecuteEnd
+
+```tsx
+vmExecuteEnd: number;
+```
+
+The timestamp when the framework ends executing [`main-thread.js`](/guide/spec.html#instances-of-main-thread-script) in the main thread to initialize the [Javascript engine](/guide/spec.html#javascript-engine). This timestamp is a Unix timestamp expressed as a floating point (unit: milliseconds), accurate to three decimal places. For example: 1739594612307.429.
+
+This property is only valid when `frameworkRenderingTiming` is present in [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
+
+### dataProcessorStart
+
+```tsx
+dataProcessorStart: number;
+```
+
+The timestamp when the framework starts initial data processing by executing the [DataProcessor](/api/react/interface.dataprocessordefinition.mdx) in the main thread. This timestamp is a floating-point Unix timestamp (unit: milliseconds), accurate to three decimal places. For example: 1739594612307.429.
+
+This property is only valid when `frameworkRenderingTiming` is present in [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
+
+### dataProcessorEnd
+
+```tsx
+dataProcessorEnd: number;
+```
+
+The timestamp when the framework completes initial data processing by executing the [DataProcessor](/api/react/interface.dataprocessordefinition.mdx) in the main thread. This timestamp is a floating-point Unix timestamp (unit: milliseconds), accurate to three decimal places. For example: 1739594612307.429.
+
+This property is only valid when `frameworkRenderingTiming` is present in [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
+
+### setInitDataStart
+
+```tsx
+setInitDataStart: number;
+```
+
+The timestamp when the [update init data](/guide/use-data-from-host-platform#provide-and-update-data) starts. This timestamp is a floating point Unix timestamp (unit: milliseconds), accurate to three decimal places. For example: 1739594612307.429
+
+This property is only valid when `frameworkRenderingTiming` is present in [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
+
+### setInitDataEnd
+
+```tsx
+setInitDataEnd: number;
+```
+
+The timestamp when the [update init data](/guide/use-data-from-host-platform#provide-and-update-data) ends. This timestamp is a floating point Unix timestamp (unit: milliseconds), accurate to three decimal places. For example: 1739594612307.429.
+
+This property is only valid when `frameworkRenderingTiming` is present in [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry).
 
 ## Compatibility
 
 import { LegacyCompatTable } from '@lynx';
 
-<LegacyCompatTable metadata="lynx-api/performance-api/framework-pipeline-timing" />
+<LegacyCompatTable metadata="lynx-api/performance-api/framework-rendering-timing" />

docs/en/api/lynx-api/performance-api/performance-entry/load-bundle-entry.mdx

@@ -199,13 +199,13 @@ paintEnd: number;
 
 The timestamp for the end of completing the final pixelation based on UI and UITree. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.
 
-### frameworkPipelineTiming
+### frameworkRenderingTiming
 
 ```ts
-frameworkPipelineTiming: FrameworkPipelineTiming[keyof FrameworkPipelineTiming];
+frameworkRenderingTiming: FrameworkRenderingTiming;
 ```
 
-Performance data for key stages in [Framework Rendering](/guide/spec#framework-rendering). The type is [`FrameworkPipelineTiming`](/api/lynx-api/performance-api/framework-pipeline-timing).
+Performance data for key stages in [Framework Rendering](/guide/spec#framework-rendering). The type is [`FrameworkRenderingTiming`](/api/lynx-api/performance-api/framework-rendering-timing).
 
 ## Compatibility
 

docs/en/api/lynx-api/performance-api/performance-entry/pipeline-entry.mdx

@@ -4,7 +4,7 @@ import { RuntimeBadge } from '@lynx';
 
 `PipelineEntry` is responsible for recording performance data at key moments during the [Lynx Pipeline](/guide/spec#lynx-pipeline), specifically for [Framework Rendering](/guide/spec#framework-rendering) and [Pixel Pipeline](/guide/spec#pixel-pipeline). It inherits from [`PerformanceEntry`](../performance-entry).
 
-The Lynx Pipeline refers to the complete process from the trigger of rendering to the final display. This process is divided into four main parts: Load, Parse, Framework Rendering (FrameworkPipeline), and Engine Rendering (PixelPipeline).
+The Lynx Pipeline refers to the complete process from the trigger of rendering to the final display. This process is divided into four main parts: [Load](/guide/spec#load), [Parse](/guide/spec#parse), [Framework Rendering](/guide/spec#framework-rendering), and [Pixel Pipeline](/guide/spec#pixel-pipeline).
 
 Due to the frequent triggering of the Lynx Pipeline, the framework only records the following two cases:
 
@@ -169,15 +169,15 @@ The timestamp for the end of executing [UI operations](/guide/spec#ui-op) relate
 paintEnd: number;
 ```
 
-The timestamp for the end of completing the final pixelation based on UI and UITree. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.
+The timestamp when the [paint](/guide/spec#paint) ends. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.
 
-### frameworkPipelineTiming
+### frameworkRenderingTiming
 
 ```ts
-frameworkPipelineTiming: FrameworkPipelineTiming[keyof FrameworkPipelineTiming];
+frameworkRenderingTiming: FrameworkRenderingTiming;
 ```
 
-Performance data for key stages in [Framework Rendering](/guide/spec#framework-rendering). The type is [`FrameworkPipelineTiming`](/api/lynx-api/performance-api/framework-pipeline-timing).
+Performance data for key stages in [Framework Rendering](/guide/spec#framework-rendering). The type is [`FrameworkRenderingTiming`](/api/lynx-api/performance-api/framework-rendering-timing).
 
 ## Compatibility
 

docs/zh/api/lynx-api/performance-api/_meta.json

@@ -25,8 +25,8 @@
   },
   {
     "type": "file",
-    "name": "framework-pipeline-timing",
-    "label": "FrameworkPipelineTiming",
+    "name": "framework-rendering-timing",
+    "label": "FrameworkRenderingTiming",
     "overviewHeaders": [],
     "collapsible": true,
     "collapsed": true

docs/zh/api/lynx-api/performance-api/framework-pipeline-timing.mdx renamed to docs/zh/api/lynx-api/performance-api/framework-rendering-timing.mdx

@@ -1,9 +1,17 @@
 import { RuntimeBadge } from '@lynx';
 
-# FrameworkPipelineTiming
+# FrameworkRenderingTiming
 
 该接口描述了[框架渲染](/guide/spec#framework-rendering)中关键阶段的性能数据。
 
+在 [首屏渲染（First-screen Rendering）](/guide/spec#first-screen-rendering-or-fsr) 和 [重渲染（Re-rendering）](/guide/spec#re-rendering) 中，框架承担了一系列重要任务。下图展示了框架渲染在整个 FSR 和 Re-rendering 流程中的关键作用:
+
+- **黄色部分代表框架渲染中的关键阶段**。
+- 绿色部分代表[引擎渲染(Pixel Pipeline)](/guide/spec#pixel-pipeline)的重要阶段，详细内容可在 [PipelineEntry](/api/lynx-api/performance-api/performance-entry/pipeline-entry) 中查看。
+- 紫色部分代表 FSR 中的 [Lynx 引擎](/guide/spec#engine)的重要任务，详细内容可在 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 中查看。
+
+![框架渲染中的关键阶段](https://lf-lynx.tiktok-cdns.com/obj/lynx-artifacts-oss-sg/lynx-website/assets/doc/framework-rendering-timing.png)
+
 ## 实例属性
 
 ### dsl
@@ -94,12 +102,8 @@ hydrateParseSnapshotStart: number;
 
 框架在[后台线程](/guide/spec.html#background-thread-aka-off-main-thread)反序列化[主线程](/guide/spec.html#main-thread-or-lynx-main-thread)信息开始的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
 
-:::tip
-
 该属性仅当 `stage` 为 `hydrate` 时有效。
 
-:::
-
 ### hydrateParseSnapshotEnd
 
 ```tsx
@@ -108,14 +112,70 @@ hydrateParseSnapshotEnd: number;
 
 框架在[后台线程](/guide/spec.html#background-thread-aka-off-main-thread)反序列化[主线程](/guide/spec.html#main-thread-or-lynx-main-thread)信息结束的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
 
-:::tip
-
 该属性仅当 `stage` 为 `hydrate` 时有效。
 
-:::
+### vmExecuteStart
+
+```tsx
+vmExecuteStart: number;
+```
+
+框架在主线程执行 [`main-thread.js`](/guide/spec.html#instances-of-main-thread-script) 初始化 [Javascript 引擎](/guide/spec.html#javascript-engine)开始的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+
+该属性仅当 `frameworkRenderingTiming` 存在于 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 时有效。
+
+### vmExecuteEnd
+
+```tsx
+vmExecuteEnd: number;
+```
+
+框架在主线程执行 [`main-thread.js`](/guide/spec.html#instances-of-main-thread-script) 初始化 [Javascript 引擎](/guide/spec.html#javascript-engine)结束的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+
+该属性仅当 `frameworkRenderingTiming` 存在于 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 时有效。
+
+### dataProcessorStart
+
+```tsx
+dataProcessorStart: number;
+```
+
+框架在主线程执行[数据预处理函数（DataProcessor）](/api/react/interface.dataprocessordefinition.mdx) 进行初始数据处理开始的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+
+该属性仅当 `frameworkRenderingTiming` 存在于 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 时有效。
+
+### dataProcessorEnd
+
+```tsx
+dataProcessorEnd: number;
+```
+
+框架在主线程执行[数据预处理函数（DataProcessor）](/api/react/interface.dataprocessordefinition.mdx) 进行初始数据处理结束的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+
+该属性仅当 `frameworkRenderingTiming` 存在于 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 时有效。
+
+### setInitDataStart
+
+```tsx
+setInitDataStart: number;
+```
+
+[更新初始数据](/guide/use-data-from-host-platform#提供和更新数据)开始的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+
+该属性仅当 `frameworkRenderingTiming` 存在于 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 时有效。
+
+### setInitDataEnd
+
+```tsx
+setInitDataEnd: number;
+```
+
+[更新初始数据](/guide/use-data-from-host-platform#提供和更新数据)结束的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+
+该属性仅当 `frameworkRenderingTiming` 存在于 [LoadBundleEntry](/api/lynx-api/performance-api/performance-entry/load-bundle-entry) 时有效。
 
 ## 兼容性
 
 import { LegacyCompatTable } from '@lynx';
 
-<LegacyCompatTable metadata="lynx-api/performance-api/framework-pipeline-timing" />
+<LegacyCompatTable metadata="lynx-api/performance-api/framework-rendering-timing" />

docs/zh/api/lynx-api/performance-api/performance-entry/load-bundle-entry.mdx

@@ -201,13 +201,13 @@ paintEnd: number;
 
 基于 UI 和 UITree，完成最终像素化的结束时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
 
-### frameworkPipelineTiming
+### frameworkRenderingTiming
 
 ```ts
-frameworkPipelineTiming:  FrameworkPipelineTiming[keyof FrameworkPipelineTiming];
+frameworkRenderingTiming: FrameworkRenderingTiming;
 ```
 
-[框架渲染](/guide/spec#framework-rendering)中关键阶段的性能数据. 类型为 [`FrameworkPipelineTiming`](/api/lynx-api/performance-api/framework-pipeline-timing)。
+[框架渲染](/guide/spec#framework-rendering)中关键阶段的性能数据. 类型为 [`FrameworkRenderingTiming`](/api/lynx-api/performance-api/framework-rendering-timing)。
 
 ## 兼容性
 

docs/zh/api/lynx-api/performance-api/performance-entry/pipeline-entry.mdx

@@ -4,7 +4,7 @@ import { RuntimeBadge } from '@lynx';
 
 `PipelineEntry` 负责记录 [Lynx Pipeline](/guide/spec#lynx-pipeline) 中[框架渲染（Framework Rendering）](/guide/spec#framework-rendering)和[引擎渲染（Pixel Pipeline）](/guide/spec#pixel-pipeline)关键时刻的性能数据，继承自 [`PerformanceEntry`](../performance-entry)。
 
-Lynx Pipeline 是指从渲染触发到最终显示的完整流程。该流程分为四个主要部分：加载（Load）、解析（Parse）、框架渲染（FrameworkPipeline）、引擎渲染（PixelPipeline）。
+Lynx Pipeline 是指从渲染触发到最终显示的完整流程。该流程分为四个主要部分：[加载（Load）](/guide/spec.html#load)、[解析（Parse）](https://lynxjs.org/guide/spec.html#parse)、[框架渲染（Framework Rendering）](/guide/spec#framework-rendering)、[引擎渲染（Pixel Pipeline）](/guide/spec#pixel-pipeline)。
 
 由于 Lynx Pipeline 触发频繁，框架仅统计以下两种情况：
 
@@ -169,15 +169,15 @@ layoutUiOperationExecuteEnd: number;
 paintEnd: number;
 ```
 
-基于 UI 和 UITree，完成最终像素化的结束时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
+执行[绘制](/guide/spec#paint)结束的时间戳。该时间戳是一个表示为浮点型的 Unix 时间戳（单位：毫秒），精确到小数点后三位。例如：1739594612307.429。
 
-### frameworkPipelineTiming
+### frameworkRenderingTiming
 
 ```ts
-frameworkPipelineTiming:  FrameworkPipelineTiming[keyof FrameworkPipelineTiming];
+frameworkRenderingTiming: FrameworkRenderingTiming;
 ```
 
-[框架渲染](/guide/spec#framework-rendering)中关键阶段的性能数据. 类型为 [`FrameworkPipelineTiming`](/api/lynx-api/performance-api/framework-pipeline-timing)。
+[框架渲染](/guide/spec#framework-rendering)中关键阶段的性能数据. 类型为 [`frameworkRenderingTiming`](/api/lynx-api/performance-api/framework-rendering-timing)。
 
 ## 兼容性
 

packages/lynx-compat-data/lynx-api/performance-api/framework-pipeline-timing.json renamed to packages/lynx-compat-data/lynx-api/performance-api/framework-rendering-timing.json

@@ -1,11 +1,11 @@
 {
   "lynx-api": {
     "performance-api": {
-      "framework-pipeline-timing": {
-        "FrameworkPipelineTiming": {
+      "framework-rendering-timing": {
+        "FrameworkRenderingTiming": {
           "__compat": {
             "description": "",
-            "lynx_path": "api/lynx-api/performance-api/framework-pipeline-timing",
+            "lynx_path": "api/lynx-api/performance-api/framework-rendering-timing",
             "support": {
               "android": {
                 "version_added": "3.1"

packages/lynx-compat-data/lynx-api/performance-api/performance-entry/load-bundle-entry.json

@@ -360,7 +360,7 @@
               }
             }
           },
-          "frameworkPipelineTiming": {
+          "frameworkRenderingTiming": {
             "__compat": {
               "description": "",
               "lynx_path": "api/lynx-api/performance-api/performance-entry/load-bundle-entry",